Reference

mpo200 Privacy Policy For Your Account

The mpo200 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice controlsContact path
mpo200 mpo200 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact path matters when a data request and an account task arrive together.

Account access If you cannot sign in after phone verification, use the account support path shown on the access screen. Tell us whether the issue concerns a device change, an incorrect phone number or a request to see the personal data connected with your account.
Wallet records For a DANA, OVO, GoPay or QRIS privacy question, send the payment date, amount reference and wallet name through the available support channel. We use those details to locate the transaction without asking you to send a wallet password.
Receipt checks A payment receipt or virtual account reference helps us separate a cashier-status question from a personal-data request. Keep the original receipt, hide unrelated wallet details and share only what our support route asks for.
HANDLING DETAILS

Six Practical Privacy Controls At mpo200

We handle privacy through the same account steps you already recognise: phone verification, wallet matching, device access and support requests.

Data we collect

We collect account details you enter, phone verification results, sign-in events and transaction references needed to connect a cashier action with your account. When you open a mobile lobby, device and browser signals may also be recorded for session protection.

Cookies and sessions

Cookies and similar session tools help keep you signed in while moving from the lobby to the cashier. They can remember a short-lived access state on your browser, while clearing them may require phone verification again before account access.

Account security

Phone verification is part of the account access path, and we use sign-in and device signals to identify unusual attempts. Never send a password, wallet PIN or one-time code in a support message, even when asking about your Privacy Policy rights.

Payment matching

A DANA, OVO, GoPay or QRIS reference is used to match a requested payment with the right account and status. Bank transfer and virtual account records serve the same checking purpose, so we can investigate a receipt without exposing unrelated account data.

Retention period

We keep personal and transaction records for the period needed to operate the account, resolve payment disputes, protect access and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the removal or anonymisation process in the policy.

Changes and requests

You can ask us to access, correct or clarify eligible personal data through the account support route. State the request plainly and include the account phone number; we may verify your identity first, and the outcome depends on local law and the record involved.

Privacy Policy Questions For Indonesian Accounts

These answers focus on the questions we expect you to ask before opening an account or sending a data request. They cover account access, wallet references, mobile sessions and correction steps, so you can choose the right support route without sharing more personal detail than necessary.

It explains how we collect, use, protect and retain account, device, session and payment-reference data. It also describes how you can ask for access, correction or clarification. The policy applies when you create an account, sign in, browse a lobby or contact support.

Your phone number supports account creation and phone verification before access. It helps us connect your sign-in with the correct account and respond to a data request. Keep the number current, and contact support if the number shown during access is incorrect.

Yes. We explain how payment references and status details from DANA, OVO, GoPay and QRIS may be matched to your account. We can use those records to check a receipt or resolve a mismatch, but you should never send a wallet PIN.

We may record device and browser signals, sign-in events and session details when you access the mobile or desktop lobby. These records help protect account access and investigate unusual activity. They are handled with the other data categories described in the Privacy Policy.

Use the support path connected to your account and state whether you want access, correction or clarification. Include your account phone number and the relevant record date, but not a password or one-time code. We may verify your identity before responding.

You can submit a removal request through the account support route. We assess which records can be removed, retained or anonymised because payment disputes, account protection and legal duties may require limited retention. The result depends on local law and the record involved.

Start with the support route shown beside your account or cashier area, especially when the question concerns a wallet reference or receipt. Describe the concern and provide only necessary account details. We will direct the request to the relevant privacy or account-handling path.