Reference

dhx4d Privacy Policy For Indonesia

The dhx4d Privacy Policy explains how we collect, use and protect the details you provide when opening an account, checking wallet status or entering the lobby.

Clear data purposesWallet record controlsPhone verification detailsContact route included
dhx4d dhx4d Privacy Policy For Indonesia
CONTACT YOUR WAY

Privacy Questions Reach Our Support

A clear contact route matters when your account record, phone check or wallet reference needs attention.

Account channel Use the support path connected to your account for a Privacy Policy request.
Wallet status If your request concerns DANA, OVO, GoPay or QRIS records, send the payment reference…
Record changes Tell us whether you need a copy, correction, deletion assessment or clarification about cookies.
DATA HANDLING

What We Protect And Retain

Privacy depends on practical handling, not a vague promise. We separate account access records from support conversation details, limit internal use to the task being completed and apply…

Account details

We handle the name, phone number and account credentials you submit for account access.

Device signals

Your browser or phone may send device and sign-in signals used to identify unusual access.

Cookie choices

Cookies can keep a session working and help us understand which policy pages load correctly.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with the related account event.

Account security

We do not ask you to place a password or full wallet credential in a support message.

Retention requests

We keep personal records while they support account operation, security checks or legal duties.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what happens around sign-in, phone verification, cookies, payment references and personal requests. If your question involves a specific record, contact us through the account support path rather than posting credentials in a message. We can then check the relevant event and explain the next step under the Privacy Policy.

The dhx4d Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it and how you can ask for a copy, correction or deletion assessment.

We use your phone number to create the account connection and complete phone verification before account access. It also helps us identify the correct record when you request a Privacy Policy change or ask about a DANA or QRIS transaction.

Yes. The Privacy Policy includes transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to check payment status, reconcile receipts and respond to a request about your own account.

Send a request through the support path connected to your account and state that it concerns the Privacy Policy. We may ask for phone verification or another account step, then explain which personal records can be provided under local law.

You can ask us to correct inaccurate account details through the secure support channel. Include the affected field and the correct value, but do not send a password or full wallet credential. We verify the request before changing the record.

We retain personal information while it supports account operation, security checks, payment reconciliation or legal duties. When those needs end, we remove or anonymise the record where possible. You can ask support about a particular category and its retention reason.

The Privacy Policy applies to account activity where local law permits. Access and eligibility depends on local law, so your location and circumstances may affect whether an account can be used. Contact support if you need a policy clarification for your region.