Reference

Privacy Policy for Your durian666 Account

Our Privacy Policy explains how we handle the details connected with your durian666 account, from phone verification to wallet activity through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests
durian666 Privacy Policy for Your durian666 Account
CONTACT THE TEAM

Privacy Help Beside Account Support

A clear request path helps you ask about the Privacy Policy without searching through payment screens.

Account questions Ask about the Privacy Policy through account support when phone verification blocks access.
Wallet records If a DANA, OVO, GoPay or QRIS receipt does not match your account, send…
Policy requests For access, correction or deletion questions, state the exact account detail involved and the…
DATA HANDLING

Six Privacy Controls We Keep Visible

We keep the Privacy Policy practical by tying each control to an account action you can recognise.

Account collection

When you open an account, we collect the details needed for account creation and phone verification.

Device signals

Your mobile browser may provide device and session signals that help us recognise repeated access or unusual sign-in behaviour.

Cookie choices

Cookies can remember settings and help us measure whether pages load correctly on mobile and desktop.

Payment records

We retain payment references and status details needed to reconcile a receipt or investigate a wallet query.

Retention timing

We keep personal records only for the period needed for account operation, security checks, dispute handling and applicable legal duties.

Change requests

You can ask us to access, correct or delete eligible personal details through account support.

Privacy Policy Questions About durian666

These Privacy Policy answers address the account and payment questions we hear most often from people in Indonesia. They also explain how to reach us when a record needs checking, especially after phone verification or a wallet receipt issue. If your situation is different, use the account support route and describe the specific data or access event.

The durian666 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can request access, correction or deletion where local law permits.

Yes. The Privacy Policy covers payment references and status checks for DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity. We use those records to reconcile account transactions, and we do not ask for your wallet password.

We use phone verification to create and protect your account access. It helps us check that a request comes from the account holder before we discuss personal records or apply a change. The access process depends on local law and the applicable account rules.

You can ask for access to eligible personal data through account support. Tell us which account detail or payment reference you mean, then complete the ownership check. We explain the records available, any legal limit and the next step for your request.

Send a correction request through the secure account support route and identify the inaccurate detail. We may ask for phone verification or another account check before changing it. Payment and security records may require additional review where local law or transaction duties apply.

We keep data for the period needed to operate your account, protect access, resolve payment questions and meet applicable legal duties. Retention can differ by record type, including a QRIS receipt or bank transfer reference, so support can explain the relevant category.

Use account support to ask which cookies relate to settings, page performance or account operation. We can explain the purpose of the cookie and the effect of changing its choice. Your browser may also provide controls, while access depends on local law.