Reference

Privacy Policy for Your dragon4d Account

Our dragon4d Privacy Policy shows what account, device and wallet details we use when you open access to Live Baccarat Royal, Bogor Lucky Slots or other lobby areas.

Account clarityWallet data careDevice accessPolicy requests
dragon4d Privacy Policy for Your dragon4d Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact path matters when you want to check a record or ask about the Privacy Policy. Start from the support route connected to your account so we can match your request with the correct login and verification details. Include the email or phone linked to your account, the relevant date, and a short description of the change you want. For wallet questions, attach the payment receipt reference rather than sending a full wallet password or security code.

Team online

Account request

Use the account support path to ask which personal details are linked to your login. We may ask you to complete phone verification before discussing records, so a request cannot be matched to the wrong account.

Wallet record

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date through support. We use those details to locate a status record while keeping your wallet PIN and one-time code out of the request.

Access concern

If an unfamiliar device appears in your account activity, contact us through the signed-in support route and change your password. We can review the access event and explain which verification step is needed next.

DATA HANDLING

How We Protect Account Data

Privacy work is part of the account flow, not a page kept apart from it.

Collected details

We may handle your account contact details, login events, phone verification result, support messages and payment references.

Cookie controls

Cookies can keep your session working and retain basic access preferences on the browser you use.

Account protection

Phone verification before account access helps us distinguish you from someone attempting to use your login.

Retention choices

We retain records only for the period needed for account service, security checks, dispute handling or a legal requirement.

Correction request

If your contact detail is wrong, tell us the field that needs changing and provide the account identifier requested by…

Deletion request

You can ask whether eligible personal data may be removed from your account record.

Privacy Policy Questions For Your Account

These Privacy Policy answers cover the account situations you are most likely to face before opening access or while checking a wallet record. We keep the route practical: use the signed-in support path, provide only the details needed to locate your account, and complete phone verification when we need to confirm that the request comes from you.

It covers account contact details, login and device activity, phone verification records, support messages, cookies and payment references. It also explains why we use each category, how retention works, and how you can request access, correction or removal where applicable.

Yes. We may handle a DANA or QRIS reference, status, amount and date needed to match an account transaction. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We do not ask you to send a wallet PIN.

Phone verification helps confirm that an account request comes from the account holder before we discuss personal records or change access details. It also helps us respond safely when a login or device pattern looks different from your usual activity.

Open the support route connected to your account and ask for a data access request. Include your linked phone or email and the record category you need. We may complete an identity check before sharing anything connected with your account.

Yes. Send the incorrect field and the replacement detail through account support. We may ask for phone verification or another account check before changing it. If a correction cannot be made, we will explain the reason and the available next step.

Retention depends on the record type and the reason it was collected. Account security, transaction matching, dispute handling or a legal requirement may require a period of storage. Ask support about a specific record, and we will explain the relevant route.

You can ask us to assess a removal request through the signed-in support path. We will check whether the data is still needed for account security, transaction matching or a legal requirement. Where removal is allowed, we will confirm the action taken.