Reference

dragon69 Privacy Policy for Your Account

dragon69 Privacy Policy sets out what we collect, why we use it and how you can request changes before opening or using an account.

Account dataWallet recordsCookie choicesAccess requests
dragon69 dragon69 Privacy Policy for Your Account
CONTACT ROUTES

Get Help With A Privacy Request

You can raise a Privacy Policy question without explaining your full account history in a public message. Start with the support path beside the login area, describe the data request, and include only the account detail needed to locate it. If your question concerns DANA, OVO, GoPay or QRIS, keep the payment receipt reference available so we can separate wallet status from account identity.

Team online

Account access route

Use the support link beside login when you need to confirm which account details we hold or when a phone verification step prevents you from reaching the privacy request path.

Wallet data route

For DANA, OVO, GoPay or QRIS records, send the relevant receipt reference through support. We use it to locate the transaction record without asking you to share an unnecessary wallet password.

Correction request

Tell us which account field, device detail or cookie preference needs attention. We can then assess the request under this Privacy Policy and the local rules that apply to your access.

HANDLING DETAILS

Inside dragon69 Privacy Controls

We keep this policy practical by linking each data category to a clear account action. A phone verification step helps us distinguish an account request from an unverified message, while wallet references…

Account data

We may hold your account identifiers, phone verification result and sign-in history to operate access and respond to a Privacy Policy request. We use only the details needed to connect your request with the correct account.

Cookies and settings

Cookies can remember choices made in your browser and help us understand whether a session remains active. You can clear browser cookies, although that may require another login or reset selected preferences.

Security checks

We compare sign-in details, device signals and verification status when an account request appears unusual. This helps us avoid disclosing account data to a person who has not completed the required access step.

Retention periods

We retain account, support and wallet records for the period needed for the stated purpose, account reconciliation or a legal requirement. When a record is no longer needed, handling follows the applicable local rule.

Changing your data

Request a correction through the support path beside login and identify the field that needs updating. We may ask for phone verification before changing an account detail connected to wallet records.

Who receives requests

Our account support team handles Privacy Policy questions and routes wallet-related cases for checking. A DANA, OVO, GoPay or QRIS reference may help us match the right record without broad disclosure.

Privacy Policy Questions About dragon69

These answers address the Privacy Policy searches we hear most often from Indonesian account holders. They cover account creation, wallet references, browser data, correction requests and the access conditions that apply when you contact us.

It covers account details, phone verification, sign-in activity, device and browser data, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that a request comes from the account holder before we discuss account data or change a field. It is an account access step, not a request to share your wallet password.

Yes. The Privacy Policy explains how we use DANA and QRIS references to match a payment status or receipt question with the correct account, while keeping unrelated wallet details outside the support case.

Open the support path beside login, state which account, device or cookie detail needs correction, and provide the smallest useful reference. We may complete phone verification before changing account data.

It describes cookies, browser settings, device type and technical connection details created when you access from Android or desktop. These records help maintain a session, remember choices and assess unusual access.

We keep account, support and wallet records for the period needed for the stated purpose, reconciliation or a legal requirement. The applicable retention approach depends on local law and the record category.

Yes. Use the support route shown beside login and ask which data category concerns you. We can explain the request path before you complete account creation, where local law permits access to the service.