Reference

m2000 Privacy Policy, Clearly Explained

The m2000 Privacy Policy shows how we handle your account details, wallet records and device data before you open the lobby.

Account clarityWallet recordsDevice controlsCookie choices
m2000 m2000 Privacy Policy, Clearly Explained
HELP WITH PRIVACY

Get Help With A Data Request

A clear support path matters when your account name, phone number or wallet receipt needs attention.

Account help route Use the support form linked from the login screen for access, correction or deletion…
Receipt privacy check If a QRIS, bank transfer or virtual account receipt is part of your request…
Account access concern When a phone verification or sign-in concern involves personal data, describe the device path…
HOW WE HANDLE IT

Privacy Controls From Login To Lobby

Privacy starts at the account step and continues when you move between a mobile browser and desktop session.

Account collection

At account creation, we collect the details needed to identify your account and complete phone verification.

Payment references

For QRIS, bank transfer and virtual account activity, we use transaction references to connect a receipt with your account.

Device signals

A mobile browser or desktop session may provide device and browser signals that help us recognise unusual access and protect…

Cookie choices

Cookies can remember session settings and privacy preferences when you return to the lobby.

Retention periods

We keep account, support and transaction records only while they serve the stated purpose or a legal requirement.

Request changes

Ask for a copy, correction, restriction or deletion through the account help route linked from login.

Answers Before You Open An Account

These Privacy Policy answers focus on the questions you may have before creating an m2000 account from Indonesia. They cover wallet references, phone verification, cookies, device access, retention and the practical route for requesting a copy or correction. Where an answer concerns account eligibility or lobby access, the position depends on local law.

The m2000 Privacy Policy covers account details, phone verification, payment references, device signals, cookies, support requests and retention. It explains why we use each category, how we protect access to related records, and how you can ask for a copy, correction or deletion.

No. Our privacy process uses transaction references and receipt details when we need to match DANA, OVO or GoPay activity with your account. We do not ask you to provide a wallet password through the account help route or a Privacy Policy request.

We may use the QRIS reference, amount and related account details to match a payment, check a receipt or investigate wallet status. Share only the reference needed for your request. We use the record for the stated purpose and applicable legal duties.

Use the support form linked from the login screen and state that you want a copy of your personal data under the m2000 Privacy Policy. Include a safe account identifier and the preferred contact path. We may verify account ownership before releasing records.

Yes, you can request a correction or deletion through account help. Tell us which detail is wrong or which record you want removed. We assess the request under applicable rules, and some transaction or legal records may need to remain for a required period.

Cookies can retain session settings and your privacy choices, while device and browser signals can help identify unusual sign-in behaviour. You can restrict cookies in your browser. Necessary restrictions may affect login continuity, and account access depends on local law.

We retain records while they support the stated account, support, security or legal purpose. When that purpose ends, we remove, anonymise or separate the relevant data where applicable. A privacy request through account help can ask about the period for a specific record.