Reference

Legal access for your mp008 account

mp008 Legal sets out how account access, wallet records and policy requests work before you enter the lobby.

Phone verificationLocal-law accessPolicy request pathWallet record clarity
mp008 Legal access for your mp008 account
POLICY HELP DESK

Get help with Legal requests

A clear support route matters when a Legal question affects your account or wallet status.

Account access If phone verification blocks your policy request, use the account access path shown on the sign-in screen. Tell us which step stopped, and we can direct the request to the account record without asking for your wallet password.
Wallet evidence For a DANA, OVO, GoPay or QRIS question, attach the payment reference displayed on your receipt, not your wallet PIN. We compare the reference with the account record before explaining a status or requesting a correction.
Policy changes When you want a Legal term clarified or a stored detail corrected, select the policy request option in support. Include the exact account detail and the change you seek so our team can follow one traceable request.
RECORDS AND CONTROL

What we do with your Legal data

Legal handling is easier to understand when each record has a defined purpose. We use account and payment references to verify access, investigate mismatches and respond to policy requests; we do not…

Account details

We use the phone number linked to your account for the verification step before access. If that number changes, request an update through support rather than opening a second account, so the Legal record stays connected.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a transaction to the correct account. We ask for the receipt reference when needed, while wallet PINs remain private to you.

Cookie settings

Cookies can keep your sign-in session and selected page settings working between visits. You can manage cookie controls in your browser; changing them may require another sign-in before a Legal request can be sent.

Account security

Phone verification is checked before account access, and our support path will not require your wallet PIN. Use your own device where possible and contact us promptly if a sign-in or payment reference does not match your activity.

Retention requests

We keep request and transaction records only for the operational, account and legal purposes that apply to the service. Ask support what record is involved, why it is retained and whether a correction or removal request can be processed.

Contact ownership

The account holder should send Legal requests through the signed-in support panel or the access contact path. We may ask for matching account details before changing records, so another person cannot alter your policy history.

Answers about mp008 Legal access

These Legal answers cover the account steps and records most relevant before you open the lobby. They explain how we handle access, payment evidence, cookies and correction requests, while local eligibility remains dependent on the rules that apply to you. If your situation is not covered, send a specific request through the support path connected to your account.

mp008 Legal covers account access, phone verification, payment references, cookies, data requests and policy communications. It also explains that access depends on local law, so you should check the terms that apply to your location before opening a lobby area or sending a wallet transaction.

No access statement applies universally. Your eligibility depends on local law and the terms shown for your account. If you are unsure, check the access wording before signing in, then ask support through the displayed contact path rather than attempting to bypass a restriction.

We use the DANA or QRIS receipt reference to match a payment with the correct account when a status needs checking. Send the reference through support, but never send a wallet PIN. A mismatch may require phone verification or further account checks.

Yes, send a correction request through the signed-in support panel or the access contact path. State the exact detail, the corrected value and why it is wrong. We may verify your phone and account record before changing the stored Legal information.

Cookies can maintain your sign-in session and selected page settings, which helps the Legal request form load with the right account context. You can change browser cookie controls, but doing so may sign you out or require another verification step.

Requests should come from the account holder through the account support route. We may compare the request with your phone verification and account details before discussing records. Do not share your sign-in details or wallet PIN with another person.

Use the policy topic in the signed-in support panel, or the contact path shown on the access screen when you cannot sign in. Include the displayed restriction, your linked phone number and any relevant reference so we can identify the correct request.