Reference

dewata888 Privacy Policy for Your Account

dewata888 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet referencesCookie choicesAccess requests
dewata888 dewata888 Privacy Policy for Your Account
PRIVACY SUPPORT

Where to Send a Privacy Request

A clear contact path helps when your account record or wallet reference needs attention.

Account support Use the support path connected with your account when you need to ask what…
Payment privacy For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, attach the…
Access concern If a sign-in or device check blocks your privacy request, tell us which device…
DATA PRACTICES

How We Handle Your Personal Data

Privacy choices work best when the handling steps are visible. We separate account operation from the requests you make about your data, and we use access checks before discussing a private record.

Collection

We collect details you enter for an account, phone verification results, sign-in events, browser or device signals, support correspondence and payment status references. When you open Ocean Pearl Reels or Live Roulette Royal, activity records may help keep the session connected to the correct account.

Use

We use personal data to provide the account path you request, display wallet status, confirm payment receipts, protect sessions and answer support questions. A record connected with Football Score Chase or another lobby area is used for account operation and security, not as a reason to request unrelated details.

Cookies

Cookies and similar browser storage can keep your session active, remember selected settings and help us understand page errors. You can manage browser permissions on your phone or desktop, although removing required cookies may interrupt login, phone verification or the route back to the lobby.

Account security

We may compare sign-in, device and phone verification signals when access looks unusual. Never send us your password or one-time code. If you change phone access, contact support from the account route so we can explain the ownership check before discussing private account data.

Retention

We retain account, support and transaction-status records only as long as needed for the stated service, security checks, dispute handling and applicable legal duties. Retention can differ by record type. A deletion request does not automatically remove records we must keep for those purposes.

Your request

You can ask for a copy, correction or eligible removal of personal data, or ask how a record is used. Send the request through account support with enough detail to locate it. We may verify ownership first, then explain the action, limits and expected next step.

Privacy Policy Questions for dewata888

These Privacy Policy answers focus on the account actions you are most likely to search for before opening or using an account in Indonesia. They explain the information connected with login, phone verification, cookies, local wallets and privacy requests. If your situation is not covered, send the account detail and payment reference through support without including a password or one-time code. Any access or eligibility question depends on local law.

The dewata888 Privacy Policy covers account details, phone verification, sign-in records, device and browser signals, cookies, support messages and payment status references. It explains why we use those details for account access, security, support and legal duties, including activity involving DANA, OVO, GoPay or QRIS.

Phone verification helps us check that a person requesting account access or a privacy change controls the account contact. We may use the result with sign-in and device signals. Do not send a one-time code to support; if access stalls, use the account support path instead.

Yes. The Privacy Policy covers payment status references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use a receipt reference, date or status detail to match the requested event, while you should hide passwords, wallet credentials and one-time codes.

You can request access to, or correction of, eligible personal data through account support. Include the account contact detail and explain the record you want checked. We may confirm ownership before responding, and access depends on local law and any applicable retention duty.

Cookies can remember session settings, support login continuity and help us identify page errors on a mobile or desktop browser. You can change browser permissions, but blocking required cookies may interrupt phone verification or account access. Optional cookie choices can be managed through your browser settings.

We keep different records for different periods based on account operation, security, support, transaction questions and applicable legal duties. A request to remove data may not apply to records that must be retained. Support can explain the relevant handling reason for the record you identify.

Use the account support route for a Privacy Policy question, access request, correction request or security concern. State whether it concerns login, cookies, phone verification or a wallet receipt, and include only safe reference details. We will use the request to locate the right record and explain the next step.