Reference

d2000m Privacy Policy for Your Account

Our Privacy Policy shows exactly how d2000m handles the account details behind your lobby access, including phone verification and wallet checks for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet status recordsAccount access controlsPolicy request path

Explore Our Lobby Read FAQ

How Privacy Policy Applies To You

d2000m Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you create or use a d2000m account, contact our support path, browse the lobby, or submit a payment through an available Indonesian rail. We may handle your phone number, account identifiers, sign-in records, device and browser details, cookie choices, payment references

1
and messages you send to us. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match a receipt with the correct account, but we do not use those details to create unrelated profiles. We use access logs and security checks to detect unusual
2
sign-in activity, protect account sessions and resolve wallet-status questions. Availability and eligibility depend on local law. This notice is available from the d2000m footer, and we may update it when our data practices change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where Privacy Questions Reach Us

A clear contact route matters when you want to check, correct or remove account data.

DATA PRACTICE

Six Practical Privacy Controls We Use

Privacy work is part of the account flow, not a separate promise hidden from you. We separate sign-in details from payment references, use cookies to remember selected settings, and check device signals…

Account data

We use your phone number, contact details and account identifiers to create access, complete phone verification and respond to account requests. We do not need your wallet password to answer a Privacy Policy question, and you should not include that secret in a message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show whether a payment event belongs to your account. We use the reference for matching and status checks, while avoiding unnecessary collection of unrelated wallet credentials.

Cookies

Cookies can keep a language choice, remember a session setting or help us understand whether the Privacy Policy link opened correctly. You can manage cookies through your browser settings, though disabling some may require another sign-in or reset saved preferences.

Security checks

We may compare sign-in time, browser details and device signals to spot an unusual account session. A new phone or browser can trigger an extra account check before access continues, helping us separate your normal login from an unexpected attempt.

Retention periods

We keep personal data only for as long as its stated purpose requires, including account support, payment reconciliation, security checks or a legal record. When a record is no longer needed for those purposes, we remove it or separate it from direct account identifiers.

Policy changes

If our data practice changes, we place the revised Privacy Policy on the d2000m site and update its date or wording. Check the footer before using your account again; contacting support lets you ask which section changed and how it affects your records.

Privacy Policy Answers For d2000m

These Privacy Policy answers focus on the account, device and payment questions we expect you to ask before opening access. Each response points back to a practical action: read the footer policy, complete phone verification, check a wallet reference or contact our support path. If a matter depends on your location or account status, we explain that condition rather than applying one answer to every Indonesian account.

It covers personal data used for account creation, phone verification, sign-in security, cookie settings, support messages and payment references. It also explains retention, policy changes and how to request access or correction. You can read the Privacy Policy from the site footer before opening an account.

We use your phone number to create and verify the account connected to your access. It can also help us identify the correct record when you ask about a sign-in or payment status. We may request a verification step before discussing account data with you.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match receipts and status events with your account. Do not send wallet passwords or unrelated payment credentials in a support request.

Contact our account support path and state that you want to access the personal data linked to your d2000m account. Include the phone number or email used for access, but not your password. We may verify ownership before explaining which records can be provided.

Yes. Send a correction request through the support path and identify the account detail that is inaccurate. We may ask you to complete phone verification before changing it. For payment references, include the relevant DANA, OVO, GoPay or QRIS receipt code so we update the right record.

Cookies may remember a session setting, language choice or the fact that you opened the Privacy Policy on your browser. You can manage them in your mobile browser settings. If cookies are disabled, you may need to sign in again or select certain preferences each time.

No. We retain records for the purpose that requires them, such as account support, payment reconciliation, security checks or a lawful record. When that purpose ends, we remove the data or separate it from direct identifiers. You can ask support why a particular record remains.

d2000m Privacy Policy for Your Account

Where Privacy Questions Reach Us

Six Practical Privacy Controls We Use

Account data

Payment references

Cookies

Security checks

Retention periods

Policy changes

Privacy Policy Answers For d2000m

01 What does the d2000m Privacy Policy cover?

02 Why does d2000m need my phone number?

03 Does the Privacy Policy cover DANA and QRIS details?

04 How can I request a copy of my account data?

05 Can I ask d2000m to correct my personal data?

06 How do cookies affect my mobile account access?

07 Does d2000m keep account and payment data forever?

Related Pages