Reference

d200m Privacy Policy For Account Access

d200m Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
d200m d200m Privacy Policy For Account Access
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path makes this Privacy Policy useful when you need to ask about a record, a cookie or an account detail. Contact us through the support route shown on d200m and include the phone number or account reference connected with your request. Do not send a wallet PIN, full password or one-time verification code. We may ask for a safe account check before discussing personal data, especially when a request concerns DANA, OVO, GoPay, QRIS or a bank transfer.

Team online

Privacy request

Use the support contact shown on our site to ask what personal data we hold, why it is used, or which account step created it. Add your account reference so we can route the request without asking you to disclose a password or wallet PIN.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment date, method and visible transaction reference through support. We use those details to locate the record while keeping the request focused on the relevant account activity.

Access concern

When a new phone, browser or login causes a privacy concern, tell us which device path you used and when it happened. We can check session signals and account access records without requesting the secret credentials that protect your account.

DATA HANDLING

What We Do With Account Details

Privacy Policy choices should be understandable before you move from phone verification to the lobby.

Account creation

When you open an account, we collect the details needed for account setup and phone verification. This lets us connect your login with the correct account record before you enter the lobby. We do not need your wallet password to complete this account step.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, time and status record. Bank transfer and virtual account activity may create matching bank references. We use these records to reconcile account activity and investigate a missing or delayed status.

Cookies

Cookies can remember your session, language setting and privacy choice on the device you use. Clearing browser storage may sign you out or require the phone verification step again. You can manage cookie controls through your browser, although some account functions may then need another check.

Security signals

We may record device type, browser details, approximate connection data and login times to identify unusual account access. A switch from mobile to desktop can therefore produce separate session records. These signals support account protection and are not a request for your private wallet credentials.

Retention period

We keep personal and transaction records for as long as they serve account support, security, reconciliation or legal purposes. When a record no longer has one of those purposes, we remove it or reduce its identifying detail through our retention process, subject to lawful record-keeping needs.

Change request

You can ask us to correct inaccurate account details, explain a processing purpose, or review a deletion request where local law permits. Send the request through our support path with a safe account reference. We may verify ownership before making a change to protect your account.

Privacy Policy Answers For d200m

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. They cover the practical points: what we collect, how wallet records are matched, why cookies appear, how to request a correction and what happens when you change devices. If your situation is not covered, contact us through the support route on d200m with an account reference rather than sending secret credentials.

It covers personal details collected during account creation and phone verification, login and device records, cookie choices, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention and how you can request access or correction.

Phone verification connects the person opening an account with the correct account record and helps reduce unauthorised access. The Privacy Policy treats the phone detail as account data used for access and security. We will not ask you to send your one-time code through support.

Yes. The policy covers transaction references, status, timing and related account matching for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These details help us check whether a payment belongs to your account without requesting your wallet password.

A new phone can create a separate device and session record, and our security checks may ask you to confirm account access again. The Privacy Policy still applies to the original account data. Tell support if the change was unexpected, and include timing without sending secret credentials.

Where local law permits, you can ask us what account data we hold or request correction of an inaccurate detail. Use the support contact shown on our site and provide a safe account reference. We may verify ownership before releasing or changing personal data.

We retain data while it supports account access, security checks, payment reconciliation, support handling or legal record-keeping. Once those purposes end, we remove the record or reduce identifying detail through our retention process, unless a lawful reason requires it to remain available.

The policy is written for our Indonesia account flow and applies where local law permits. Access or eligibility depends on local law, so you should check the rules that apply to your location. Our support team can explain how to submit a privacy request but cannot change that legal condition.