Reference

Privacy Policy for Your cuan 128 Account

Our Privacy Policy explains how cuan 128 handles the details you provide when opening an account, signing in from a mobile device, or using DANA and QRIS.

Account dataCookie choicesAccess requestsIndonesia focus
cuan 128 Privacy Policy for Your cuan 128 Account
CONTACT ROUTES

Ask About Privacy Policy Details

A clear contact path matters when a phone verification record or wallet status needs checking. From your account area, use the support link beside the cashier path and state that your request concerns the Privacy Policy. Include the account phone number and the record or date you want us to locate; do not send a wallet PIN. Our team can route questions about access, correction, deletion, cookies, or a DANA receipt without asking you to repeat the same request across separate channels.

Team online

Account data request

Use the support link beside your account and identify the phone number attached to your cuan 128 profile. We can use that account step to locate sign-in, verification, and wallet records before explaining what may be accessed or changed under local law.

Wallet record question

If a DANA, OVO, GoPay, or QRIS reference appears incorrectly, include the payment name, date, and reference shown in your account. We use those details to separate a wallet-status question from a broader Privacy Policy request.

Cookie or device help

For cookie choices or an unfamiliar mobile sign-in, tell us the device path you used and the approximate time. We can check the related session record and explain the available Privacy Policy action without requesting your password.

HANDLING DETAILS

How We Apply This Privacy Policy

We apply this Privacy Policy at the points where data is created: account opening, phone verification, wallet selection, sign-in, support contact, and lobby access.

Account security

Phone verification is an account-access step, not a public profile. We use the verified account path to distinguish your sign-in from an unfamiliar device and may ask for matching details before discussing private records.

Cookie settings

Cookies can preserve a sign-in preference or help connect a session to the right account. Your request can specify whether you are asking about necessary session cookies or optional measurement records on the device you use.

Wallet references

DANA, OVO, GoPay, and QRIS references help us trace a submitted payment status without treating a wallet number as a public account detail. We review the reference alongside your account record when a mismatch is reported.

Lobby activity

Opening Live Baccarat Prestige, Football Betting Live, or Lombok Lagoon Megaways can create page and session records. We use these details for account continuity, security checks, and support investigations rather than presenting them as a public history.

Retention choices

We keep records for the period needed for the stated operational, security, dispute, or legal purpose. When that purpose ends, our handling may include deletion, restriction, or removal of direct account identifiers where local law permits.

Change requests

To request correction, access, restriction, or deletion, contact support from the account route and name the exact record. We may confirm your phone verification first so a private account request is not disclosed to another person.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and device questions we expect before you open an account from Indonesia. They also explain what to include when contacting us about a wallet reference, cookie choice, or sign-in record. If a rule differs for your location, access depends on local law and that rule will control the request.

It covers account details, phone verification, sign-in and device records, cookie use, support messages, lobby sessions, and payment references. A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record is handled in connection with the account action it describes.

Use the support link in your account area and write that you are making a Privacy Policy data request. Name the phone number on the account, the record date, and the action involved. We may confirm phone verification before releasing account-specific details.

Yes. When you sign in on a phone or tablet, we may record device and session details needed for account continuity and security checks. Tell us the device path and approximate sign-in time if you need us to investigate an unfamiliar session.

Wallet and payment references help us match a submitted request with the correct account and status. We may retain a DANA or QRIS reference for support, dispute, security, or legal reasons, with handling shaped by the purpose and local law.

You can request correction, restriction, or deletion through the account support route. Identify the exact record rather than sending a password or wallet PIN. We will assess the request against security, dispute, operational, and legal needs where local law permits.

Cookies may keep a sign-in preference, connect a session to your account, or help us understand a device path. Contact us with the page and device involved if you want the cookie purpose explained or want to ask about available choices.

Start with the support link beside the account and cashier path, then label your message as a Privacy Policy concern. Include your account phone number and a short description of the record. We can route questions about access, wallets, cookies, or security.