Reference

Legal clarity for your mpo200 account

mpo200 Legal sets out how we handle account access, identity checks, payment records and policy requests before you enter the lobby.

Account termsData handlingPolicy requestsLocal-law access
mpo200 Legal clarity for your mpo200 account
HELP PATHS

Get help with a Legal request

A clear contact route matters when a policy question affects your account or payment record. We separate account access, wallet status and policy-change requests so you can include the right detail at the first step. Add your account identifier, the affected payment rail and the date shown on your receipt; that gives us a practical starting point without asking you to repeat the same story across different requests. We can then direct the issue to the relevant policy path.

Team online

Account access path

If a Legal condition blocks account access, use the account help path and include the exact message shown after phone verification. We can match that request to your account record and explain which policy step applies where local law permits.

Wallet status path

For DANA, OVO, GoPay or QRIS records, use the wallet-status path with your receipt reference and selected rail. This lets us check whether the policy concern is about identity, account ownership or a pending cashier record.

Policy change path

When you want to ask about data correction, cookie choices or account-record retention, use the policy request path. State the change you want and the account email or phone detail we can use to locate the relevant record.

DATA PRACTICE

How we handle policy obligations

We apply the Legal policy to the information needed for account access, payment matching and security checks, rather than treating every page visit as an account event.

Account data

We use account details to identify your profile, complete the phone-verification step and connect a policy request to the correct record. Keeping your phone and account details current helps us avoid sending a data decision to the wrong account.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained beside the account event it relates to. We use that pairing to check receipt status and respond to a Legal question about payment ownership.

Cookie choices

Cookies can preserve a login session, language preference and selected page state on your device. You can clear stored cookies through your browser controls, although doing so may require another account access step before policy pages load correctly.

Account security

Phone verification is part of the account access path, and we may ask for matching account details before discussing a private record. Do not send a password in a policy request; use the account identifier we ask for instead.

Retention questions

If you ask how long a record is kept, identify the record type, such as a QRIS receipt, account message or verification event. We will assess the applicable policy purpose and tell you whether correction, deletion or continued retention applies.

Change requests

To request a correction or other permitted change, describe the field, the current value and the value you believe is accurate. We may verify ownership first, then record the request and explain the next policy action available.

Answers before you open an account

These Legal answers focus on the decisions you may need to make before opening an account or asking about an existing record. We explain the practical route for access, data, cookies and payment evidence without treating the policy as a general lobby description. If your situation depends on location, the applicable outcome depends on local law.

mpo200 Legal covers account access, phone verification, payment-record handling, cookies, security checks, retention and requests to correct eligible data. It also explains that access and eligibility depends on local law, so the policy outcome can vary by your supported Indonesian region.

Access is available only where local law permits. A location or eligibility check may affect account opening and continued access. If the page shows a restriction, use the account access path and include the message displayed so we can explain the relevant policy condition.

Phone verification helps connect an account request to the person controlling the account detail. It also gives us a security checkpoint before discussing private records, including DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We may keep a selected payment rail, receipt reference, account event and related status so we can match a transaction question to the correct record. For a correction request, provide the rail and receipt detail rather than sending a password.

Yes. Use the policy request path and identify the account field, its current value and the correction you want. We may confirm account ownership before acting, then explain whether the requested change can be made under the current Legal policy.

Cookies can retain session and preference details on your browser, which may reduce repeated access steps. You can clear them through browser controls, but the next visit may require phone verification or another account check before you reach policy pages.

Choose the path that matches the issue: account access for a policy block, wallet status for a payment record, or policy request for data, cookies and retention. Include your account identifier and concise evidence so we can route the concern accurately.