Reference

mpo2121jp Privacy Policy for Your Account

The mpo2121jp Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the lobby and your wallet.

Clear data purposesWallet record controlsPhone verification contextIndonesia access wording
mpo2121jp mpo2121jp Privacy Policy for Your Account
PRIVACY HELP PATH

Where to Ask About Your Data

A clear contact path matters when a wallet reference, phone detail or sign-in record needs checking. Start from the account support area and describe the Privacy Policy request in plain English, including the account identifier and the issue you can see. We use the smallest practical set of details to locate the record, and we may ask for an account step or phone verification before discussing private data. If you are in Semarang or elsewhere in Indonesia, the same request path applies where local law permits.

Team online

Account data request

Use the support path connected to your mpo2121jp account when you want to ask what personal details we hold. Include your account identifier and the specific record, such as a phone verification entry or a DANA payment reference, so we can narrow the request.

Wallet record question

For a mismatch involving OVO, GoPay, QRIS, bank transfer or a virtual account, tell us which rail appears in your account and what status you see. We use that detail to separate a payment record question from a broader Privacy Policy request.

Access and correction

If your account details are out of date, ask through the account support route for a correction or access check. We may confirm the phone linked to the account before sharing or changing personal data, helping keep another person from receiving your records.

DATA HANDLING DETAILS

How We Apply This Privacy Policy

We apply the Privacy Policy to the practical events that occur during an account session: login, phone verification, wallet status checks, lobby access and support contact.

Account details

We may collect the details needed to create and maintain your account, including contact details and the phone verification result. We use them for sign-in, account notices, security checks and support replies rather than treating every account field as open-ended permission.

Cookies and devices

Cookies can keep a session connected and remember a practical setting on your browser. Device and connection signals may help us recognise a suspicious login or explain why a mobile session cannot reach the lobby. You can clear browser data, although sign-in may need to be repeated.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be attached to an account record so the displayed payment status can be checked. Bank transfer and virtual account details serve the same matching purpose. We do not describe a wallet reference as unrelated profile data.

Account security

Phone verification before account access helps us distinguish the account holder from an unknown sign-in attempt. Keep your login details private and contact support if a device path looks unfamiliar. We may review security events before changing access or releasing account data.

Retention approach

We keep account, payment and security records only for the period needed for the stated service, dispute handling, security checks or a legal duty. A request to remove data may not erase records that must remain available for those limited purposes.

Your requests

You may ask about the data linked to your account, request a correction, or ask how a particular record is used where local law permits. Send one clear request through the account support route; we may verify ownership before responding to protect your privacy.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before you open an account or connect an Indonesian wallet. They cover the records created by phone verification, mobile access, payment matching and support contact. If a situation is not covered here, use the account support path with the relevant account or wallet reference, and remember that access depends on local law.

The Privacy Policy treats phone verification as an account security step. We may record the result and related sign-in event to confirm access and investigate unusual activity. Before discussing private account data or changing access, we may ask you to confirm the phone linked to your account.

We may store payment references, status details and account links needed to match a DANA, OVO, GoPay or QRIS transaction. These records help us investigate a missing status or receipt. The Privacy Policy limits their use to the stated payment, account, security or legal purpose.

Bank transfer and virtual account records may include a reference, amount status and account association needed for reconciliation. We use those details to identify the payment path and respond to a support request. Retention can continue when security, dispute handling or local law requires it.

Yes, where local law permits, you can request correction of inaccurate account data through the account support route. State which field is wrong and provide the account identifier. We may verify your phone or another account step before making a change or confirming private details.

You can ask what personal data is linked to your account and how a specific record is used, where local law permits. A focused request about a phone event, cookie setting or QRIS reference helps us respond accurately. Ownership checks may apply before disclosure.

The retention period depends on the type of record and its purpose. Account and security data may be retained for access protection, while payment references may remain for reconciliation, disputes or a legal duty. The Privacy Policy does not promise removal where retention is required.

Contact the account support path promptly and describe the device, time and sign-in event you noticed. We may use device and connection logs to investigate, then ask for phone verification before changing access. Do not send wallet passwords or unrelated personal details in the request.