Reference

mpo007 Privacy Policy for Your Account

mpo007 Privacy Policy explains how we handle your account details, device signals and payment records when you use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
mpo007 mpo007 Privacy Policy for Your Account
PRIVACY CONTACT

Check Privacy Help Beside Cashier Status

A clear support route helps you ask about the Privacy Policy without sending payment details through an unverified channel. From your signed-in account, open the support form beside the cashier path and include the phone number on the account plus a short description of your request. We can then match a DANA receipt, QRIS reference or device-access concern to the right account record.

Team online

Policy questions

Use the signed-in support form to ask how your phone number, login event or verification record is handled under the Privacy Policy. Keep your request specific so we can locate the relevant account entry.

Wallet records

If a DANA, OVO, GoPay or QRIS reference appears in a privacy request, share only the receipt detail needed for matching. We do not need your wallet PIN or full authentication secret.

Access concerns

When a new device, browser session or phone-verification step raises a data concern, tell us through account support. We use the account path to separate a genuine request from an unverified message.

DATA HANDLING

Browse Data Choices Across Your Account

The Privacy Policy describes what we retain, why we retain it and how you can ask for a correction.

Account creation

We use the details you submit during account creation to make your profile available and to complete the stated access steps. Phone verification confirms that a request is connected with the account holder before account data is discussed.

Device signals

Browser type, device markers, login time and approximate session signals can help us spot unusual access. On mobile, these records relate to the path from sign-in to the lobby rather than to unrelated apps on your phone.

Cookie controls

Cookies can keep a session active, remember selected settings and help us understand page use. Your browser controls can clear or restrict cookies, although some account steps may then need to be completed again.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event with the correct account. We do not ask you to send a wallet PIN when checking a payment record.

Security retention

Login, verification and transaction records may remain for the period needed to protect accounts, resolve disputes and meet applicable legal duties. Retention can differ by record type and depends on local law.

Change requests

You can ask us to correct account details, explain a data use or address a deletion request through support. We may request account verification first, so another person cannot change your records.

Find Answers About mpo007 Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to check before opening access. Each answer points back to the same account and support path, with local payment examples so you know which records may be involved.

It covers account details, phone verification, login and device signals, cookies, game-page activity, payment references and support requests connected with your use of mpo007 where local law permits.

We use the phone number submitted during account creation and verification to connect access requests with the correct account, protect sign-in activity and respond to a Privacy Policy request.

Yes. The Privacy Policy covers references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account steps needed to match a cashier event.

You can send a correction request through the signed-in support form. We may ask for phone verification or another account check before changing details, so your records remain protected.

Cookies may keep your session and selected settings available on a mobile browser. You can restrict them in browser controls, but sign-in or verification steps may need to be repeated.

Retention depends on the record, its security or dispute purpose and applicable legal duties. The Privacy Policy explains the relevant period, and the result depends on local law.

Use the support form inside your signed-in account and describe the request clearly. Include only the payment reference or account detail needed to locate the record, never a wallet PIN.