Reference

mpo2121trusted Privacy Policy: Your Data Path

mpo2121trusted Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, choose DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesPrivacy requests
mpo2121trusted mpo2121trusted Privacy Policy: Your Data Path
REQUEST HELP

Contact Routes for Privacy Requests

A clear request path helps you ask about the data attached to your account without sending sensitive wallet credentials. Start from the account support route when you are signed in, or use the contact path shown on our site if access is stalled. Include the email or phone detail linked to your account, the subject of your request, and any DANA or QRIS receipt reference that helps us locate the right record.

Team online

Account request

Ask us to confirm, correct or explain account details after sign-in. We may ask for the phone verification step linked to your account before discussing personal records.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the transaction reference rather than a password. This helps us check status without exposing wallet credentials.

Access route

If you are in Surabaya or elsewhere in Indonesia and cannot reach account support, use the site contact path and describe the device, browser step and privacy request in plain English.

HANDLING PRACTICES

Six Data Practices Behind Your Account

We keep this policy practical by connecting each data use to an account action you can recognise.

Account details

We use the details entered during account creation to identify your account, complete phone verification and respond to access questions. Please keep your contact detail current so requests reach the right record.

Payment references

A DANA, OVO, GoPay or QRIS reference can connect a receipt or status question to your account action. We do not need your wallet password to investigate that reference.

Browser cookies

Cookies can remember session choices on your phone or desktop browser. You can clear them through browser settings, although clearing cookies may require you to repeat the sign-in path.

Security signals

Device, browser and sign-in signals help us identify unusual account activity and protect access. If a check interrupts your session, support may ask for account details before discussing records.

Retention period

We keep account, support and transaction references only for the operational, security or dispute-handling period they require. When a record is no longer needed, our handling process moves it toward removal.

Change requests

You can request access, correction or removal of eligible personal details through our contact route. State the account identifier and requested action; we may verify ownership before making a change.

Privacy Policy Questions for Indonesian Accounts

These Privacy Policy answers focus on the account, device and wallet questions you may search before opening access. If your situation is not covered, contact us with the account detail and transaction reference that best identifies your request; access remains where local law permits.

It covers account details, phone verification, sign-in activity, browser cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions.

We use phone verification to confirm account access and help protect personal records. If you ask about account data, we may use that step to check that the request comes from the account holder.

Yes. The Privacy Policy covers references and status details connected with DANA and QRIS actions. Send the receipt reference when asking for help, and never send a wallet password or security code.

Cookies can retain session choices on your mobile browser and reduce repeated steps. Clearing them through browser settings may sign you out or require another account access check the next time you return.

You can request correction of eligible account details through our contact route. Include the account email or phone detail, explain the change, and complete any ownership check needed before we update the record.

Retention depends on why a record exists, such as account access, security, support or a transaction question. We move records toward removal when the operational or dispute-handling need ends.

You may ask for access to, clarification of or removal of eligible personal data through support. We will assess the request under applicable rules, verify ownership, and explain any limit where local law permits.