Reference

Privacy Policy for Your 8988a Account

Your 8988a Privacy Policy explains how we handle account details, wallet records and device signals while you move between Live Blackjack Salon, Crash Countdown Round and the lobby.

ACCOUNT DATAWALLET RECORDSCOOKIE CHOICESACCESS REQUESTS
8988a Privacy Policy for Your 8988a Account
PRIVATE HELP ROUTES

Get privacy help beside your wallet

A privacy question should not require guesswork, especially when it involves a DANA receipt or a device used to open your account. We keep the contact route close to the signed-in support area so you can describe the record, attach a payment reference and ask for a clear response. Please avoid sending wallet passwords or full card details. Our team uses the account details you provide to locate the relevant request and may ask for an account step or verification detail before discussing personal data.

Team online

ACCOUNT SUPPORT

Open the support route after signing in and state whether your request concerns account details, a cookie choice, device access or a payment record. We use the account step to direct your question to the right privacy handling queue.

WALLET RECEIPT

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and status shown in your account rather than a wallet password. This lets us check the relevant record while limiting the personal details shared in your message.

ACCESS QUESTION

If your account cannot open on mobile or desktop, tell us the device type, browser and last account step completed. We may use those technical details to separate a privacy request from an access or security check.

DATA HANDLING DETAILS

How 8988a protects account data

We handle privacy as an account process, not as a vague promise. Access checks, wallet matching and support replies each use only the details needed for that task.

DATA USE

We use your name, phone number, account activity and verification status to provide signed-in access, match support requests and protect the account. Game activity such as Live Blackjack Salon is handled as an account event, not as a reason to collect unrelated personal details.

COOKIE SETTINGS

Cookies and similar browser storage can remember session choices, language settings and security events. You can clear browser storage or adjust available cookie controls, though removing necessary session data may require you to sign in again before reaching the lobby.

ACCOUNT SECURITY

We check sign-in activity, device type, browser details and network signals to identify unusual access. If a security check interrupts the account path, we may request phone verification before restoring access; never place a wallet password in a support message.

PAYMENT RECORDS

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event can create a reference, status and receipt record. We use those fields to reconcile the account and answer payment questions, while keeping wallet login credentials outside our requested support details.

RETENTION PERIOD

We retain account, security, payment and support records only for the period needed for the stated purpose, dispute handling and legal duties. When a record is no longer needed, our process is to remove it, anonymise it or restrict further use.

CHANGE REQUESTS

To ask us to correct, access, restrict or remove personal data, use the signed-in support route and identify the account step concerned. We may verify ownership before acting, and the response depends on local law and any required record-keeping duty.

Privacy Policy answers for Indonesian accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a data request. We explain the records connected with local wallets, mobile access and account verification in plain terms. If your situation involves a specific payment reference or access event, use the signed-in support route so we can look at the correct account record.

The 8988a Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, payment references and security events. It applies when you use our pages, mobile browser path or signed-in account, including records connected with DANA, OVO, GoPay, QRIS and bank transfer.

We use your phone number to create and protect the account path, complete phone verification and help match a support request to the correct account. We may also use its status when an unusual device or login event appears, with handling subject to the 8988a Privacy Policy.

No. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account events, we use payment references, status and receipt details to match activity to your account. We do not ask you to place a wallet password in support messages or send it through our account path.

Sign in, open the account support route and state whether you want access, correction, restriction or removal of a specific record. Identify the account step, device or payment reference involved. We may verify ownership, and the available action depends on local law.

We keep account, security, payment and support records for the period needed for their stated purpose, dispute handling and legal duties. A DANA receipt or QRIS reference may therefore remain after the related account event, then be removed, anonymised or restricted when no longer needed.

Yes. You can clear browser storage or adjust the cookie controls available on your mobile browser. Necessary session data supports account access, so clearing it may sign you out and create a new session record the next time you open the lobby.

Some requests, retention duties and access decisions depend on local law. Our Privacy Policy applies where local law permits, and we explain any limit when we respond. If you cannot sign in, provide the device type and last completed account step through support.