Reference

Privacy Policy for Your des666 Account

Our Privacy Policy tells you exactly why we collect account, device and wallet details when you use des666 in Indonesia.

Account dataWallet recordsCookie choicesPhone checks
des666 Privacy Policy for Your des666 Account
HELP WITH REQUESTS

Get A Clear Data Contact Path

A privacy request should not leave you guessing which account detail to provide.

Account help Use the account help path when you want to ask what personal details we…
Wallet records Choose the cashier support route for a question about DANA, OVO, GoPay, QRIS, bank…
Access concerns Tell us when a device session, sign-in check or local access decision needs clarification.
DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by describing the records behind familiar account actions.

Account security

We use phone verification and sign-in details to help protect your account from an unfamiliar access attempt.

Device signals

Our Privacy Policy covers browser, device and session signals created while you move from login to the lobby.

Cookie choices

Cookies can keep a session active and remember selected account settings.

Wallet matching

When you use QRIS or a local wallet, we retain the reference needed to match the cashier event with your…

Retention requests

Retention depends on the reason a record exists, such as account security, payment matching or a request you send us.

Policy changes

When this Privacy Policy changes, we update the policy page so you can compare the current handling of account, device…

Privacy Policy Answers For des666

These Privacy Policy answers focus on the account questions you are most likely to have before opening or continuing an Indonesia account. We explain the data connected to phone verification, wallet checks, device access and cookies in plain terms. Each answer points you back to the account help path when a request needs a record-specific response. Eligibility and lobby access depends on local law, so the same policy wording applies where local law permits.

It covers account details, phone verification, device and session signals, cookies, wallet and cashier references, security checks, retention and requests to change or clarify a record. It applies when you access the account path, lobby or cashier from an Indonesia device where local law permits.

We use the phone verification step to confirm that the account access request belongs to the registered account. The resulting record can also help us investigate a sign-in question. We keep that detail for account security and handling periods described in the Privacy Policy.

Yes. The policy covers the transaction references and wallet status connected with DANA, OVO, GoPay and QRIS. It also covers bank transfer and virtual account references when you use those routes, so a receipt can be matched to the correct account.

You can send that request through the account help path near the cashier area. Tell us which account detail, device session or wallet reference you mean. We may need an account step to identify the correct record before explaining what we hold.

Cookies can maintain your session and remember selected settings while you move from mobile login to the lobby. Your browser controls whether cookies remain available. Removing them may sign you out or require the phone verification step again before account access.

Use account help and name the registered detail you believe is incorrect. We will use the account verification step to locate the record, assess the request and explain the result. Wallet references may require a matching receipt before a change can be assessed.

Yes. Account and lobby access depends on local law. Where local law permits, we use the account, device and location signals needed for that decision and explain a related question through support. The Privacy Policy describes the data categories involved in that process.