Reference

Open dragon969 Privacy Policy Clearly

dragon969 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and enter the lobby from your device.

Account dataWallet recordsDevice choicesPolicy requests
dragon969 Open dragon969 Privacy Policy Clearly
REQUEST HELP SAFELY

Check Privacy Support From Your Account

A clear support route helps you act on this Privacy Policy without sending sensitive details through an unverified channel.

Account request Use the support path connected to your signed-in account when you want to ask…
Wallet status For DANA, OVO, GoPay or QRIS questions, include the payment reference and account contact…
Access concern If a new device, phone change or sign-in event looks unfamiliar, tell us through…
CONTROL YOUR RECORD

Browse Privacy Choices Inside dragon969

Privacy controls work best when each request is tied to a specific account action. We separate ordinary account use from security checks, payment matching and support correspondence, then use the relevant record…

Data collection

We collect account details when you create access, confirm your phone or change a setting. Activity records can include sign-in time, device type and actions connected with Live Blackjack Royal or other selected lobby titles.

Cookie choices

Cookies and related device signals can support session continuity, language settings and security checks. Your browser controls can limit them, although changing those settings may affect account access or require another phone verification step.

Account security

A phone verification step helps connect account access to the contact detail you supplied. If sign-in behaviour changes, we may review device and security records before restoring access to wallet status or account settings.

Retention period

We retain account, payment reference and support records only for the period needed for security, transaction matching, dispute handling and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Correction request

You can ask us to correct an inaccurate phone detail, account preference or support record through the account support path. We may compare the request with your existing verification step before changing the stored information.

Privacy contact

For a copy, deletion question or explanation of this Privacy Policy, contact us through signed-in account support. Describe the requested record, such as a QRIS reference or device event, and avoid sending passwords.

Find Answers About Privacy Policy

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access. They explain the practical route for checking data, changing details and raising a security concern. If your situation involves a local restriction, our response depends on local law and the account records available for verification.

The dragon969 Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, payment references and support correspondence. It explains why we use each category, how retention works and how you can request access or correction through the signed-in account path.

We use your phone number to create the account contact record and complete the phone verification step before account access. It can also help us identify a security request or correct an account issue. We do not need your wallet password for a Privacy Policy request.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us match a receipt or wallet status to your account without treating your payment password as an account support detail.

Sign in, open the account support path and ask for a copy of the data linked to your account. Name the category you want, such as phone verification, device access or QRIS references. We may confirm your account contact before releasing the requested record.

You can request a correction through signed-in account support. Tell us which detail is inaccurate, such as a phone number, account preference or support record. We compare the request with existing account verification, then handle the change where local law permits.

On mobile, cookies or similar device signals may keep your session active, retain a setting and help identify unusual sign-in behaviour. Browser controls can restrict them, but you may need to sign in again or complete phone verification before reaching account settings.

Use the signed-in account support path as soon as you notice an unfamiliar device event. Share the approximate time and device type, but not your password. We can check security records and may pause account changes while confirming your identity under the Privacy Policy.