Reference

deli66 Privacy Policy And Your Data

deli66 Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening the lobby.

Clear data purposesWallet status contextAccess where local law permitsAccount request path
deli66 deli66 Privacy Policy And Your Data
HELP WITH DATA

Where To Ask About Privacy Policy

A clear account route helps you raise a Privacy Policy question without sending sensitive details through the wrong path.

Account help Use the account help path for a Privacy Policy request about your profile, phone…
Wallet status If your question concerns DANA, OVO, GoPay or QRIS records, include the transaction reference…
Receipt check For a bank transfer or virtual account privacy question, attach only the receipt details…
DATA PRACTICES

How We Handle Your Privacy Choices

Privacy work is tied to ordinary account actions, not a separate hidden process.

Account details

We use the contact details and phone verification information you submit to create, maintain and protect your account.

Payment references

DANA, OVO, GoPay and QRIS references help us identify wallet status and reconcile account activity.

Cookies and devices

Cookies can remember session choices and help us identify unusual sign-in behaviour.

Security controls

We use sign-in checks, session records and account verification to reduce unauthorised access.

Retention periods

We keep records only for the period needed for the purpose described in this Privacy Policy, account security, dispute handling…

Change requests

You can ask us to access, correct or remove eligible personal data by using account help and identifying the record…

Privacy Policy Questions For deli66

These Privacy Policy answers focus on the searches we expect you to make before opening an account. They explain the data connected with login, payments, devices and account activity in plain terms, while keeping every request subject to where local law permits. If your situation is not covered, use the account help route with a transaction reference or account identifier.

The deli66 Privacy Policy covers account details, phone verification, device and cookie records, lobby activity, security logs and payment references. It explains why we use each category, how long records may remain and how you can request access, correction or removal where local law permits.

Our Privacy Policy distinguishes wallet status references from your private wallet credentials. We may receive a transaction reference for DANA, OVO, GoPay or QRIS, but you should never send a wallet password or one-time code through account help or a privacy request.

Phone verification helps us confirm account ownership and protect access when you sign in or change account details. The related record may support security checks, including a mobile browser change, but it is used for the account purpose described in the Privacy Policy.

Use the signed-in account help path and identify the email or phone number connected with your account. State that you want a Privacy Policy data access request and mention the record sought, such as a QRIS reference, cookie record or activity linked to Crash Countdown Round.

Yes, you can request correction or deletion of eligible data through account help. We may verify that you control the account before acting, and some payment, security or dispute records may need to remain for a stated purpose where local law permits.

Cookies and browser storage can keep a session connected while you move from login to the lobby. Clearing them may sign you out, remove saved choices and trigger phone verification again. Our Privacy Policy explains these uses and the choices available in your browser.

Start with the account help path and include a short description of the concern, plus an account identifier or payment reference when relevant. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send only the details needed to locate the record.