Reference

Privacy Policy for kurnia898 Accounts

Our Privacy Policy explains how kurnia898 handles the account, device and wallet details you provide before you enter Live Baccarat, Cleocatra or other lobby areas.

Account recordsWallet detailsDevice choicesPolicy requests
kurnia898 Privacy Policy for kurnia898 Accounts
REQUEST PATHS

Get Privacy Policy Help At Account Level

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages. Start from your signed-in account and use the support path beside the cashier area, especially when a wallet reference, phone verification step or device record needs attention. We can use the details you provide to locate the relevant account entry and explain the next privacy step.

Team online

Account privacy request

Use the account support route to ask what personal details are connected with your sign-in, phone verification or lobby activity. Include the account identifier shown to you so we can locate the correct record.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, contact us through the support path beside the cashier area. Share the receipt reference, not another person’s wallet details, when asking for a correction.

Access correction request

If a device check or phone verification step prevents access where local law permits, tell us through account support. We will use your request to review the relevant security record and explain available action.

DATA CONTROLS

Data Choices Inside kurnia898

We separate account operations from policy requests so you can ask about personal details without reopening every account setting.

Account data

We use your account details to create sign-in access, complete phone verification and connect your selected lobby activity to the correct account. We do not ask you to place another person’s identity details in a privacy request.

Cookies and devices

Cookies can remember policy choices and sign-in preferences on your browser. On mobile, the path from login to the lobby may create device security records; clearing cookies can require you to verify again.

Wallet matching

DANA, OVO, GoPay and QRIS references help us identify the payment record you ask about. Bank transfer and virtual account details are checked against the account reference supplied during the transaction.

Account security

Phone verification and sign-in checks help protect your account from an unfamiliar device. Keep your password and verification code private, and contact account support if a login record does not look familiar.

Record retention

We retain account, security and transaction records only for the operational, dispute and legal purposes described in this Privacy Policy. When a record is no longer needed, our handling process moves it toward removal or anonymisation.

Changes and contact

You can ask us to correct inaccurate personal details, explain a record or clarify how a cookie works. Send the request through the signed-in support route so we can confirm which account the request concerns.

Privacy Policy Questions Indonesia Users Ask

These Privacy Policy answers focus on the account steps you are most likely to check before opening an account with kurnia898. They cover wallet references, mobile access, cookies, corrections and local availability. If your question involves a specific receipt or sign-in, use the account support path so we can respond to the relevant record.

The kurnia898 Privacy Policy covers account details, phone verification, device signals, cookies, lobby activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

Phone verification helps connect your sign-in with the correct account and supports account security. It may also help us investigate an unfamiliar device or a request to correct account access details.

Yes. The Privacy Policy explains how we handle QRIS receipts and references from DANA, OVO and GoPay. These details help us check the payment record you identify when requesting support.

You can ask us to correct inaccurate account or contact details through the signed-in support route. Include the account identifier and describe the specific record, without sending another person’s personal details.

Cookies may remember your policy choices and sign-in preferences. If you clear them on your phone, the next visit can ask you to confirm preferences or complete a security check before lobby access.

We keep account, security and transaction records for the operational, dispute and legal purposes stated in the Privacy Policy. Retention depends on the record type and whether a support or payment question remains open.

Access and eligibility depends on local law. Where local law permits, the Privacy Policy applies to your account while specific handling or access requirements may vary according to the location connected with your request.