Reference

Privacy Policy for dewi 11 slot

dewi 11 slot Privacy Policy explains what we collect when you create an account, enter the lobby, use DANA or QRIS, and contact account help.

Account clarityWallet contextDevice controlsPolicy requests
dewi 11 slot Privacy Policy for dewi 11 slot
HELP WITH REQUESTS

Get Privacy Help Through Your Account

A clear contact route matters when a Privacy Policy question concerns your own account rather than a general explanation. Start from the account help path near the cashier area and include the phone contact or account identifier connected to your request. We use those details to locate the right record, check wallet status when relevant and avoid sending private account details to the wrong person. For access questions, eligibility remains where local law permits, and we may ask for an account step before changing personal data.

Team online

Account help path

Use the account help route beside the cashier path for a Privacy Policy request. Include your account identifier and the subject of your question, so we can separate a personal data request from a DANA, OVO, GoPay or QRIS status query.

Receipt and status check

If your request relates to a bank transfer or virtual account reference, attach the receipt details shown in your account. We use the reference to check the record, confirm ownership and explain what data is retained for reconciliation without exposing another account's transaction.

Access clarification

When a Privacy Policy question involves sign-in or eligibility, tell us the device path and account step that stopped. We can explain the relevant record and next action, while access remains where local law permits rather than assuming every Indonesian location has the same status.

DATA HANDLING

What We Keep And Why

We keep this policy practical by connecting each data category to an account task you can recognise.

Account details

We use the phone contact and account details you submit to create, locate and protect your account. A clear account path helps us match a Privacy Policy request to the correct record, and we may request an account step before discussing private details or changing them.

Wallet references

Payment references are handled for status checks and reconciliation, not as a reason to describe unrelated activity. DANA, OVO, GoPay and QRIS records can show whether a request belongs to your account, while bank transfer and virtual account references support receipt matching.

Device and sessions

Device type, browser signals and session events can help us identify a sign-in problem or investigate access that does not look familiar. We use these details for account protection and support checks, including when your mobile path reaches the lobby differently from desktop.

Cookies

Cookies may keep essential session settings and help the account path work between sign-in and the lobby. You can manage browser cookie controls, but removing necessary cookies may interrupt access or require another account step where local law permits.

Retention approach

We retain records for as long as needed for account operation, security checks, support follow-up or required legal purposes. When a record no longer serves one of those purposes, our handling process considers deletion or de-identification rather than keeping it without a reason.

Changes and contact

You can ask what personal data we hold, request a correction or question a particular use through account help. Include the phone contact linked to your account and describe the requested change; we may verify ownership before acting on it.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions we expect before an account step: what data is collected, why wallet references appear, how device details are used and how to request a change. We keep the wording tied to actual account actions, including sign-in, wallet status and support contact. If your question concerns eligibility or access from Indonesia, the relevant position is where local law permits.

It covers account details, phone verification, device and session signals, cookies, wallet references, support records and policy requests. It also explains why we use those details for access, security, reconciliation and account help, with eligibility handled where local law permits.

DANA and QRIS can create account-linked status or receipt references when you use those payment paths. We may handle the reference to match a request, check ownership and explain a pending record. The policy also applies to OVO, GoPay, bank transfer and virtual account references.

We may collect device type, browser signals and session events connected with account access. These details help us investigate an unfamiliar sign-in, explain a mobile path issue or protect the account. They are handled for those operational reasons rather than to build unrelated personal profiles.

Open the account help path and state which personal detail needs correction. Include the phone contact or account identifier linked to your record, plus the reason for the request. We may verify ownership before making a change, so private information is not altered by the wrong person.

Retention depends on the purpose of the record. Account, security, support, payment reconciliation and legal records may remain while they are needed for those purposes. We then consider deletion or de-identification instead of keeping information without an operational or legal reason.

Yes. Send the request through account help and identify the phone contact connected with your account. We can explain the categories held, such as account, device, cookie, support or wallet references, after an ownership check. Access to the service remains where local law permits.

Cookies may preserve essential session choices between mobile sign-in and the lobby. Your browser controls can remove or restrict them, although that may interrupt the account path or require another sign-in step. We use cookie data for session function and related account checks.