Reference

Open the cuan18 Privacy Policy

The cuan18 Privacy Policy shows how we handle your account details, wallet records and device signals when you access Live Blackjack Table or Papua Paradise Megaways.

Account dataWallet recordsCookie choicesSecurity checks
cuan18 Open the cuan18 Privacy Policy
CONTACT YOUR WAY

Find the privacy support route

A clear contact route matters when your account record or wallet reference does not look right.

Account contact Use the support route linked to your account when you want to ask about personal data, phone verification or a correction. We may ask for account details needed to locate the record, but we will not ask you to send your password or one-time access code.
Wallet status For a DANA, OVO, GoPay or QRIS privacy question, share the payment date and reference shown in your receipt. This lets us check the matching account event without requesting your wallet PIN, full card details or other credentials.
Access concern If an unfamiliar device reaches your account, contact support through the account path and mention the device type, approximate time and affected session. We can use those details to assess access activity while keeping your private message focused.
DATA HANDLING

Browse the controls behind this policy

Privacy choices work best when the handling steps are visible. We separate account identity details from the operational records needed to trace a wallet event, and we use device signals to help…

Account records

We use your name, contact details and phone-verification status to maintain the account record and respond to access requests. Keeping these fields current helps us distinguish your account from another account when you ask for a copy or correction.

Payment references

A DANA, OVO, GoPay or QRIS reference can connect a wallet event to your account without giving us your wallet PIN. Bank transfer and virtual account records may also be retained to reconcile the specific transaction and answer a status query.

Cookies and sessions

Cookies and similar session tools help keep login state, language choices and security checks working across a phone or desktop browser. You can manage cookie controls in your browser, although restricting necessary cookies may affect account access.

Device protection

We may record device type, browser details, connection signals and session times to identify unusual account activity. These signals can support a security check when a new phone reaches the lobby or when a login pattern changes.

Retention timing

We keep personal data while it serves account operation, security, dispute handling or a legal requirement. When a record no longer has one of those purposes, we aim to delete it or change it so it no longer identifies you.

Request changes

You can ask us to access, correct or delete eligible personal data through the account support path. Describe the exact record, such as an old phone number or a QRIS receipt reference, so we can verify the request and respond accurately.

Ask about cuan18 Privacy Policy

These common questions focus on the choices Indonesian account holders usually need before sharing details with us. Each answer relates to the cuan18 Privacy Policy, from wallet references and cookies to account access, correction requests and device security. If your case involves a specific record, contact support with the smallest useful set of details and never include a password or one-time code.

It covers account details, phone-verification status, wallet and bank-transfer references, cookie use, device signals, security activity, retention and privacy requests. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, virtual accounts and bank transfer.

Phone verification helps us confirm that the person requesting account access is connected with the account record. It can also help us investigate an unfamiliar login. We do not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to match an account event, investigate a receipt and answer a payment-status request.

Contact us through the account support path and state whether you want access, correction or deletion of eligible data. Name the relevant record, such as your phone number or a QRIS receipt reference, so we can verify the request without collecting extra details.

Cookies can keep your session active, remember language choices and support security checks between pages. Browser controls let you restrict or remove them. If you block cookies needed for login, some account functions may not work as expected on your phone or desktop.

We retain data while it supports account operation, security checks, dispute handling or a legal requirement. After that purpose ends, we aim to delete the record or make it non-identifying. A specific retention period can depend on the record and local legal requirements.

Yes. Send the approximate time, device type and account identifier through the support route. We can assess the session and explain the next account-security step. Access or eligibility depends on local law, and you should not include your password or one-time code.