Reference

Your Privacy Policy Starts With Clarity

The editor slot Privacy Policy explains what we collect, why we use it and how you can ask about your account records before opening access.

Account recordsWallet activityCookie choicesPolicy requests
editor slot Your Privacy Policy Starts With Clarity
CONTACT ROUTE

Questions Reach The Right Support Path

A privacy question should not get mixed with a wallet-status issue, so we keep the contact route close to the account area.

Privacy request Use the policy contact route shown on this page when you want to ask what account data we hold, why it is used or how to request a correction. We may ask you to confirm the account phone number before discussing private records.
Wallet reference If your question involves DANA, OVO, GoPay, QRIS or a bank transfer, share the transaction reference rather than wallet credentials. This lets us trace the relevant status while keeping sensitive login details out of the support conversation.
Access concern For a privacy issue after phone verification, describe the device path you used, such as mobile browser or desktop browser, and the time of the event. We use those details to separate an account-security concern from a simple session problem.
ACCOUNT SAFEGUARDS

Account Data Stays Under Your Control

We handle this policy area through practical account controls rather than vague promises. Our records are connected to the actions needed to verify an account, display wallet status and respond to a…

Data handling

We use contact, verification, device and transaction-status details for account operation, security checks, support investigation and legal duties. A game title such as Live Roulette Royal may appear in activity records only when needed to connect an account action with the relevant session.

Cookies

Cookies and similar browser storage can keep a session working and help us understand whether a login or policy page loaded correctly. You can manage browser cookie settings on your device, though changing them may affect sign-in continuity or saved preferences.

Account security

Phone verification is required before account access, and we use account and device signals to check unusual activity. Never send a password or wallet PIN through a privacy request. If a login concern appears, contact us through the account support route.

Retention

We keep records only for the period needed for the purpose described in this policy, account support, payment reconciliation, security checks or applicable legal duties. When a record is no longer needed, our handling follows the relevant deletion or restriction process.

Your request

You can ask what personal data we hold, request a correction, ask about use, or raise a deletion or restriction request where local law permits. We may verify your identity through the account phone number before making a change.

Policy contact

Send your request through the contact path linked with this Privacy Policy and describe the exact record involved. Mention whether it concerns account access, QRIS status, cookies or a mobile session so we can route it to the right internal check.

Privacy Policy Questions For editor slot

These answers address the searches we hear most often about the editor slot Privacy Policy. They focus on account data, Indonesian wallet references, browser activity and the steps available when you want clarification or a change. If your situation is not covered, use the policy contact route and include the smallest useful detail.

It covers account details, phone verification, device and browser activity, cookie use, payment-status references and records created when you contact support. It also explains retention, security handling and the requests you can make where local law permits.

We do not need your DANA, OVO, GoPay or QRIS wallet password for a transaction-status check. We may receive a reference, method label and processing status so we can connect the payment event to your account without asking for private wallet credentials.

Phone verification helps connect an account request to the right person before access is provided and before private records are discussed. It also supports security checks when a login comes from a different browser or device path.

Use the contact route attached to this Privacy Policy and state whether you want access, a correction, restriction or deletion request. Include your account phone number only through the secure request path; we may verify it before responding.

We retain each category only as long as needed for account operation, support, payment reconciliation, security or applicable legal duties. The period can differ by record type. You may ask us to explain the reason for keeping a specific record.

Yes. Your mobile browser provides its own cookie and site-storage controls. Turning some settings off can interrupt sign-in continuity or preferences, but it does not prevent you from sending a Privacy Policy request through the contact path.

Yes. Access, correction, deletion and restriction options depend on local law and the nature of the record. We will explain which request applies to your account and may ask for phone verification before sharing private information.