Reference

Open dragon99 Privacy Policy Clearly

The dragon99 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, use DANA or QRIS, and contact us about account…

Account dataWallet referencesCookie choicesPrivacy requests
dragon99 Open dragon99 Privacy Policy Clearly
CONTACT ROUTES

Find Privacy Help Beside Account Support

A privacy question should not get mixed with a wallet-status issue, so we keep the request path clear. Use the account support route when you need help identifying a sign-in record, phone verification detail or payment reference connected with your profile. Tell us which account step is involved and avoid sending a password or full wallet credentials. For a formal Privacy Policy request, include the email or phone detail attached to your account so we can check ownership before responding.

Team online

Account detail request

Ask us to identify the personal details linked with your dragon99 account, including the phone verification step. We may ask for an account check before sharing records, so another person cannot request details using only a username.

Wallet reference check

If DANA, OVO, GoPay, QRIS, bank transfer or virtual account data appears in a support case, tell us the date and reference shown on your receipt. We use those details to locate the record without requesting your wallet password.

Policy change request

Send correction, access or deletion requests through our account support contact and mark them as a Privacy Policy matter. We review the request, confirm account ownership and explain any legal reason a record must remain available.

DATA PRACTICES

Explore How We Handle Your Details

The Privacy Policy is supported by practical account controls rather than broad promises. We separate sign-in details from payment references, record device and browser events that help protect account access, and use…

Account collection

We collect details needed to create and maintain your account, including contact information and phone verification status. If a field is optional, the policy explains its purpose so you can decide whether to provide it before moving through the account flow.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference connected with your account, while bank transfer and virtual account records support reconciliation. We use these references for account servicing and status checks, not as a public display of your identity.

Cookie controls

Cookies can remember a sign-in preference, support page operation and help us understand technical errors. Your browser settings can remove or restrict them, although some account steps may need cookies to remain available for the page to work.

Device signals

When you sign in through a phone or desktop browser, we may record device, browser and connection signals used to detect unusual access. These signals help us investigate an account issue without asking you to disclose a password in a support message.

Retention periods

We keep account, support and transaction records only for the period needed for the stated purpose, account servicing or applicable obligations. The exact period can differ by record type, and you may ask support how a particular record is handled.

Your requests

You can ask to access, correct or remove personal details where local law permits. Include the account contact used at registration and describe the requested change; we verify ownership first and explain the result or any restriction that applies.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and payment questions we hear most often from people in Indonesia. They explain what can be requested, why verification may be needed and how device, cookie and wallet records fit into an account case. If your situation is not covered, use the privacy contact route above and include only the details needed to locate your account.

It covers account details, phone verification, device and browser signals, cookies, support cases and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains retention, security handling and the process for privacy requests.

You may request access to personal details connected with your account where local law permits. Send the request through account support using the contact attached to registration. We verify ownership first, then explain which records can be provided and in what form.

The contact attached to your account helps us distinguish your request from an unauthorised attempt. We may ask for a further account check, but you should never send a password, full wallet login or security code in a privacy message.

We may retain transaction references, receipt details or wallet-status information needed for reconciliation and support. The Privacy Policy does not treat those references as a public profile. A request about a specific record should include its date and visible reference where available.

Cookies can support sign-in preferences, page operation and technical error checks. Your browser can restrict or remove them, but some account steps may not function as intended afterward. The Privacy Policy describes the purposes, and your browser controls remain available.

Retention depends on the type of record and the purpose for keeping it. Account, support and payment references may remain for account servicing or applicable obligations. You can ask support about a particular record and request removal where local law permits.

Contact account support and identify the account detail that needs correction, such as a phone number or contact record. We confirm ownership, review the request and explain the result. A correction may be limited when a record must remain unchanged for an applicable obligation.