Reference

mop888 Privacy Policy for Your Account

mop888 Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can ask about your records.

Clear data purposesWallet status checksPhone verification
mop888 mop888 Privacy Policy for Your Account
CONTACT PATHS

How to Ask About Your Privacy Policy

A direct support route helps you ask what data is connected with your account without guessing which team to contact.

Account support path Use the support route connected to your account when you want to ask about stored details, phone verification or a correction. Include your account reference rather than sending a wallet password. We can then match the request to the right account record.
Wallet status question For a DANA, OVO, GoPay or QRIS status question, share the transaction reference and payment rail name through the account support path. We use that information to check the record while limiting the request to the payment event you identify.
Privacy request If you want to ask about access, correction or deletion of personal data, state the request clearly and use the phone or account details already attached to your profile. We may verify account control before discussing or changing protected records.
HANDLING DETAILS

Six Ways We Handle Your Data

Our privacy practice follows the account actions you can recognise: opening an account, completing phone verification, signing in from a device, checking a wallet reference and contacting support.

Account creation

When you open an account, we use the details needed to create your profile and provide account access. A phone verification step may be required before protected account actions. We do not need a wallet password to identify the account connected with your request.

Payment references

DANA, OVO, GoPay and QRIS can produce payment references that help us match a cashier event with your account. Bank transfer and virtual account records serve the same checking purpose. We use the reference to investigate status, not to request secret wallet credentials.

Cookies and devices

Cookies and device signals can remember a session, support login continuity and help us spot an unusual access pattern. Your mobile browser may create a different session after its storage is cleared. Signing in again lets us connect the new session to your verified account.

Account protection

Phone verification, login records and device checks help us protect account access. If a request involves changing protected details, we may ask you to confirm control through the account step already linked to your profile before we disclose or update information.

Retention practice

We retain account and payment references for as long as needed for the purpose described here, including resolving an open status question or maintaining account records. When a record is no longer needed for that purpose, our handling moves toward removal or separation from active account use.

Changes and requests

You can contact us to ask what personal data is held, request a correction, or ask whether a record can be removed. Give enough account detail for a safe match, and describe the exact change. We may keep a request record so its outcome can be checked later.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the searches we expect before an account is opened or a wallet status is checked. They explain the practical route for account data, cookies, payment references, corrections and contact requests. If your question concerns eligibility or access, the relevant position depends on local law.

The mop888 Privacy Policy covers data connected with account creation, phone verification, login activity, device sessions, support messages and payment references. That includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks.

We use your phone number to create or identify your account and to support phone verification before protected access. It also helps us match a privacy request to the correct profile. We do not ask you to provide a wallet password through a support message.

Yes. The Privacy Policy covers cookies and device signals used to keep a mobile session working, support login continuity and identify unusual access patterns. Clearing browser storage can end a session, so you may need to sign in again through your verified account.

We use DANA and QRIS references to check whether a payment event matches your account and the status you asked about. The same approach applies to OVO, GoPay, bank transfer and virtual account records. Send only the reference needed for that check.

You can contact the account support path and ask what personal data is held or request a correction. Include your account reference and describe the exact record. We may verify that you control the account before sharing details or applying a change.

We keep account and payment references for the time needed to support the stated purpose, resolve an open status question and maintain relevant account records. When a record is no longer needed for that purpose, handling moves toward removal or separation from active account use.

Yes. Where account access or eligibility is discussed, it depends on local law. The Privacy Policy explains our data handling, but it does not change a local rule. If you need clarification, contact support with your account reference and location context.