Reference

Privacy Policy for Your durian66 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your durian66 account, including phone verification, device access and wallet status.

Account dataWallet detailsCookie choicesPolicy requests
Browse Our Lobby Read FAQ
durian66 Privacy Policy for Your durian66 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

Questions about our Privacy Policy should be sent through the same account support route used for login and wallet-status concerns. Tell us which account detail or policy point you are asking about, and include the phone number linked to your account without sharing a password or wallet PIN. We can then check the relevant account record, payment receipt or device session. This route is also suitable if you are in Makassar and need help understanding a data request before changing account details.

Team online

Account privacy request

Use account support to ask what personal details are linked with your durian66 profile, why a phone verification step appears, or how to request a correction. We may ask for an account detail so we can distinguish your request from another account.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in a payment-status question, send the receipt reference rather than a PIN or password. We use that reference to locate the relevant record and explain how it is handled under our Privacy Policy.

Device access concern

Tell us if your account opened on an unfamiliar phone, browser or session. We can review the access details connected with that request and explain the available account-security step without asking you to disclose private wallet credentials.

DATA HANDLING

What You Can Expect From This Policy

Privacy Policy questions often concern more than a registration form, so we explain the operational details behind account handling.

Account data use

We use the details you provide to create and maintain your account, complete phone verification, respond to support questions and connect a payment status with the correct account. We avoid collecting wallet PINs through support and do not need them to investigate a receipt reference.

Cookie controls

Cookies and similar browser signals help us remember session settings, measure basic page performance and identify repeated access patterns. You can manage cookie permissions through your browser settings, although changing them may affect login continuity or the way policy pages load.

Account security

Phone verification helps connect account access with the number you submitted. Device and session details can help us investigate an unfamiliar login or repeated failed access. Keep your password private, sign out on shared devices and never send a wallet PIN in a message.

Payment references

DANA, OVO, GoPay and QRIS may create a reference or status record when you use a wallet route. We use the reference to reconcile the account request and answer payment questions, while the wallet credential remains with you and should not be shared.

Retention choices

We keep account, support and transaction records for the period needed to operate the service, investigate security events and meet applicable legal duties. When a record no longer has a valid purpose, our handling process is to remove or de-identify it where appropriate.

Change requests

You can ask us to correct account details, explain a data use, provide the basis for a retention period or consider a deletion request through account support. Include the relevant phone or receipt reference, but leave out passwords, wallet PINs and full security codes.

Privacy Policy Answers for durian66

These Privacy Policy questions focus on the account, device and wallet matters you are most likely to check before opening or using an account. We keep the answers tied to durian66 processes, including phone verification, DANA and QRIS references, browser cookies and the support route for correction or deletion requests. If your question concerns whether access is available in your location, eligibility depends on local law.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay or QRIS. It explains why we use those records, how we protect account access and how you can request correction or deletion.

Phone verification helps us connect an account request with the number you submitted and investigate access concerns. It also reduces confusion when support checks a login or wallet-status question. We do not ask you to send your password, wallet PIN or full security code.

No. A DANA or QRIS payment may produce a reference or status record that helps us match the request with your account, but your wallet PIN is not needed for that check. Never send a PIN, password or complete security code through support.

We may use device and session signals to keep account access working, investigate unfamiliar activity and understand basic browser performance. Cookies can remember session settings. You can adjust cookie permissions in your browser, though login continuity or page behaviour may change.

Yes. Send a request through account support and identify the account detail you want checked, such as a phone number, profile field or payment reference. We may verify that the request belongs to you before explaining the record or applying a correction.

You can submit a deletion request through account support. We assess which records can be removed and which must remain for security, transaction handling or legal duties. We will explain the result and any required account step without asking for your wallet PIN.

We retain account, support and transaction records only for the operational, security or legal period connected with their purpose. The period can differ by record type and local requirement. When a record no longer has a valid purpose, we remove or de-identify it where appropriate.

Related Pages

durian66 Indonesia FAQ Account information Thunder Zeus Slots Access guide