Reference

dewi11 Privacy Policy For Your Account

Our Privacy Policy explains how we use account details, device signals, cookies and payment records when you access dewi11.

Clear data purposesCookie choicesAccount request pathIndonesia access
dewi11 dewi11 Privacy Policy For Your Account
REQUEST HELP

Get Privacy Help Near Account Support

A privacy question should not require you to search through the lobby. Use the account support route shown after sign-in and describe whether your request concerns login data, a wallet receipt or…

Account access If your phone verification or login record needs checking, send the account identifier shown in your profile through our support route. We use it to match the request without asking you to repeat unrelated details.
Wallet records For a DANA, OVO, GoPay or QRIS privacy query, include the payment reference and date visible on your receipt. This helps us separate a data request from a normal wallet status check.
Cookie choices If a cookie setting behaves differently on your mobile browser, tell us the device path and browser setting you used. We can explain the available choice and record a request to change stored preferences.
CONTROL YOUR DATA

Keep Control From Login To Lobby

We handle this policy area through practical account controls rather than vague promises. Phone verification links your access to the account step you completed, while session checks help protect a mobile route…

Account data

When you open an account, we use the details you submit to create access and complete phone verification. Contact details are kept separate from a game preference such as Mobile Legends or Bingo where the process allows.

Payment records

A DANA, QRIS, bank transfer or virtual account reference can be retained to reconcile a cashier event and investigate a disputed status. We use the payment record for that purpose, not as a general profile label.

Device sessions

On mobile and desktop, we may read device and browser signals that help identify a session or detect unusual access. These signals support account security while you move from login to the lobby.

Cookies

Cookies can keep a session working, remember a selected setting or help us understand page errors. Your browser controls can clear them, although removing required cookies may interrupt account access.

Retention

We keep account, support and payment records for as long as needed for the stated service, security checks or applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to correct account data, explain its use or request deletion where local rules permit. Include your account identifier and the precise change so we can verify ownership before acting.

Find Privacy Policy Answers Quickly

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We keep the wording tied to actual account steps, including phone verification, mobile access, cookies and payment references. If your situation is not covered, use the support route connected to your account and mention the exact data or event you want us to check.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for the account access step and phone verification. It helps us connect a sign-in request to the correct account and investigate login issues without relying only on a device.

Yes. The policy covers data created when you use a mobile browser from login to the lobby, including device signals, session data and cookie settings needed for pages to function.

We may retain the payment route, reference, date and status so the cashier event can be reconciled or checked. A privacy request about DANA or QRIS should include the receipt reference.

Yes. Send a correction request through the account support route, include your account identifier and explain the field that is wrong. We verify ownership before changing data connected to account access.

Ask through account support and identify the records you want removed. We assess the request against operational and legal retention duties; where local law permits, data no longer needed can be removed or de-identified.

Yes. Your access, eligibility and certain data requests depend on local law. We apply the Privacy Policy to the service available in your region and explain any limits when we respond.