Reference

Open dian4d Privacy Policy For Your Account

Our Privacy Policy shows what we collect when you create an account, complete phone verification and move between the Live Dealer Lobby, slot rooms and local wallet pages.

Account clarityWallet dataCookie choicesContact route
Explore Our Lobby Read FAQ
dian4d Open dian4d Privacy Policy For Your Account
CONTACT YOUR WAY

Find Privacy Policy Support From Account

A direct support path helps you ask about Privacy Policy matters without sending sensitive details through an unrelated route. Start from your account support area and include the email or phone detail linked to your account, the subject of your request and any payment reference that helps us locate the record. We will use only the material needed to respond and may ask you to complete an account check before changing personal data.

Team online

Account data request

Ask us to confirm which account details we hold, such as your phone verification status or contact record. We may request an account check before releasing a copy or discussing information linked to your dian4d access.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears unclear, send the transaction reference through the account support path. We compare the reference with the payment record and limit the response to the data needed for that question.

Correction request

Tell us when your account contact detail or other personal data needs correction. We verify the request against the account before updating the record, and we explain if a legal or security record must remain unchanged.

DATA HANDLING

Explore How We Handle Privacy Choices

Privacy Policy work is part of the account flow rather than a separate promise. We separate sign-in details from payment references where practical, restrict account changes behind verification and use device signals…

Account details

We collect information you enter for an account, such as a phone number, and the result of the phone verification step. This lets us identify your account and apply the Privacy Policy to the correct record rather than to an unverified request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can contain a reference, amount and status. We use those fields to match a cashier event or receipt, not to request access to your private wallet credentials.

Device signals

Your browser, device type and basic access signals may be recorded for login continuity and account protection. If you switch from mobile to desktop, these signals help us assess the session without treating the device itself as your identity.

Cookies and storage

Cookies can keep a selected setting, support sign-in flow and help us understand whether a policy page was opened. Browser controls can clear or restrict them, although some account functions may then require another sign-in step.

Retention questions

We keep personal and transaction records for the periods needed for account operation, security checks and applicable legal duties. Ask through support for the reason a category is retained and we will explain the relevant period or restriction.

Requests and changes

You can request access, correction or deletion of eligible personal data through the account support path. We first confirm that the request comes from you, then explain what can change and what must remain for security or legal reasons.

Browse Privacy Policy Answers Before Access

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain the practical path for account data, payment references, cookies, device access and correction requests. If your situation is not listed, use the support route above and keep your question focused on the specific record you want us to check.

It covers account details, phone verification, device and browser signals, cookies, payment references and support requests connected with your access. It also explains why we use each category, how long records may remain and how you can request access or correction.

No. Our Privacy Policy concerns payment references and status details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not ask for your private wallet password. A receipt reference may be used to check a disputed account event.

Phone verification links an account request to the contact detail you supplied and helps us prevent changes made by someone else. The Privacy Policy treats the number and verification result as account data, used for access checks and related support requests.

Yes, you can request access to eligible personal data through the account support path. Include the linked phone or contact detail and the category you want checked. We may confirm your identity first, then explain the available copy, format or restriction.

Cookies and browser storage can remember settings and support a continuous sign-in path between the policy page and lobby. You can clear or restrict them in your browser. The Privacy Policy explains that doing so may require another account check.

You can ask us to correct an eligible phone, contact or account detail through support. We compare the request with your account before making a change. If a transaction or security record cannot be edited, we will explain why it remains.

Access and eligibility depends on local law, and some retention or disclosure duties can also vary by jurisdiction. Our Privacy Policy describes the account handling used for Indonesia access where local law permits. Contact support if you need a jurisdiction-specific explanation.

Related Pages

dian4d Indonesia About Us Account information dian4d Casino Live Dealer Lobby