Reference

level 789 Privacy Policy

level 789 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and support requests.

Account detailsWallet recordsCookie choicesContact requests
level 789 level 789 Privacy Policy
HELP WITH PRIVACY

Reach Us About Your Data

A direct support path helps you question a record, correct an account detail or ask how a wallet reference is used.

Account access desk If your phone verification or login record looks incorrect, contact our account support route…
Wallet record help For a DANA, OVO, GoPay or QRIS reference, include the payment rail, amount shown…
Privacy request route Ask us to access, correct or clarify personal data through the privacy contact route…
DATA HANDLING

What We Do With Policy Details

Our Privacy Policy is practical: it connects each data category with an account task and a clear reason for keeping it.

Account data

We use your contact details and phone verification state to create the account path, help you recover access and send account-specific replies. We do not need your DANA, OVO or GoPay password to match a payment status.

Device signals

Login time, browser type and basic device signals can help us identify an unusual access attempt. These signals support account protection when you move between a mobile browser and desktop, but they are not a substitute for your phone verification.

Cookies

Cookies can remember session settings, keep the account path working and help us understand which policy page was opened. You can manage browser cookie controls, though disabling necessary cookies may interrupt login or the path to Live Blackjack Salon.

Wallet matching

Payment records show the rail and status linked to an account action, such as a QRIS scan or bank transfer reference. We use this narrow transaction context to investigate a receipt or status question, not to request private wallet credentials.

Retention timing

We keep account, transaction and support records only while they serve account administration, dispute handling, safety checks or legal duties. When a record no longer needs to remain available for those reasons, our processes remove or de-identify it where possible.

Change requests

You can ask us to correct contact details, explain a data category or clarify how a cookie works. Send the request through our privacy contact route; we may verify ownership first so another person cannot alter your account record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or contact support. They explain the data connected with login, phone verification, wallets, cookies and access requests without asking you to disclose unnecessary private details. If your question concerns a record not covered here, use the privacy contact route and include the relevant account step.

It covers personal details linked to your account, phone verification, login activity, device signals, cookies, wallet references and support messages. It also explains why we use those records, how long they may remain available and how you can ask for access or correction where local law permits.

Yes. We may receive a payment rail, reference code, amount and status when you use DANA, OVO, GoPay or QRIS. This lets us match a cashier event to your account and answer a receipt question. We do not ask for your wallet password or PIN.

Phone verification helps connect the account to the contact detail you provide and supports access recovery when a login issue occurs. We use its status for account administration and protection. If eligibility or access is discussed, it depends on local law and applies where local law permits.

You can request a correction through the privacy contact route, such as changing an incorrect contact detail. Include the account identifier and explain the error, but do not send a password or wallet PIN. We may confirm ownership before changing the record linked to your account.

Cookies may keep a mobile session active, remember settings and support the route from login to the lobby. Your browser controls can remove or restrict them. Necessary cookies may still be required for account access, so changing those controls can interrupt the session.

We retain records while they support account administration, transaction matching, support follow-up, security checks or legal duties. The period can differ by record type and applicable law. When continued retention is no longer needed, we remove or de-identify the record where possible.

Use the privacy contact route shown on this page and describe whether you want access, correction or clarification. Add the relevant account step, such as phone verification or a QRIS reference, while withholding passwords and PINs. We may verify ownership before responding.