Reference

Privacy Policy For Your den303 Account

Clear account records, wallet handling and access choices sit at the centre of our Privacy Policy.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
den303 Privacy Policy For Your den303 Account
CONTACT THE TEAM

Three Ways To Ask About Privacy

A direct support route helps you ask what we hold, why a record appears, or how to correct an account detail. Start inside your signed-in account and choose the support path near account and wallet status. Include the phone number linked to your account and a clear request, but do not send your password or full payment credentials. We may ask for enough detail to confirm that the request comes from you before discussing personal data.

Team online

Account support path

Open the support option from your signed-in account when you need a copy of your personal data or an explanation of a phone verification record. We use the account details already attached to the request to help confirm your identity.

Wallet record query

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference and date through the account support route. We can then separate a payment-status question from a request about the personal data linked to that record.

Correction request

Tell us which account field is inaccurate and what should replace it. After an identity check, our team records the requested change and may retain the earlier value where it is needed for security, dispute handling or a transaction trail.

HANDLING DETAILS

Six Privacy Controls We Explain Clearly

We keep this policy practical by linking each privacy point to an account action you can recognise.

Data we receive

We may receive your phone number, account credentials, verification details, device signals and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related references can be linked to your account so we can identify the requested payment.

Cookie choices

Cookies and similar browser storage can keep your session open, remember a language or region setting and help us detect unusual sign-in behaviour. You can adjust cookie controls in your browser, although blocking necessary storage may interrupt account access.

Account security

We use phone verification before account access and may compare device or session signals when a login appears unusual. Never share your password or verification code with support. If your device changes, sign in through the normal account path and contact us about any unfamiliar activity.

Payment matching

A payment reference helps us match a DANA or QRIS event with the correct account without asking you to send a wallet password. For bank transfer and virtual account records, we use the supplied reference and transaction details to check status and resolve a receipt query.

Retention decisions

We keep personal data only for the period needed for account operation, security checks, transaction records, dispute handling and legal requirements. When a record no longer serves one of those purposes, our handling process moves it toward deletion or anonymisation where applicable.

Changes and requests

You can ask for access, correction or clarification through the signed-in support path. If we update this Privacy Policy, we place the revised version on the policy page and show the effective date so you can compare the change before continuing with your account.

Privacy Policy Answers For den303

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with login, local wallet activity, mobile access, cookies and requests for changes. If your question is specific to a DANA, OVO, GoPay or QRIS reference, use the support path inside your account and include the relevant date or receipt number. We will use that detail to locate the correct record.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It also explains how we use those records for account access, security, wallet matching, retention and requests to inspect or correct personal data.

We may collect your phone number, login details, verification record, device signals and messages sent through support. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, transaction references may also connect with your account.

Sign in through the usual account path and open support near your account or wallet status. Ask for the personal data connected with your account, identify the phone number on file, and complete any identity check needed before we discuss the records.

Yes. The Privacy Policy explains that cookies or browser storage can maintain a mobile session, remember settings and help identify unusual sign-in behaviour. You can change cookie controls in your browser, but blocking necessary storage may affect account access.

We use the payment reference, date and status connected with your account to match a DANA or QRIS event and investigate a receipt query. We do not need your wallet password. These records may remain while transaction, security or legal needs apply.

Yes, you can request a correction through the signed-in support path. State which field is wrong and provide the accurate replacement. We may confirm your identity first, and an earlier value can remain where needed for security, disputes or transaction records.

The Privacy Policy explains data handling, but it does not decide eligibility. Access depends on local law and any required account checks. If you need help with an access or verification question, contact us from the account support route without sharing your password.

Related Pages

den303 Indonesia Banjarmasin Lucky Slots Speed Baccarat Room Access guide FAQ