Reference

cuan88 Privacy Policy For Your Account

Our Privacy Policy explains how cuan88 handles the details connected with your account, device, wallet status and support requests.

Account dataWallet statusDevice choicesPolicy requests
cuan88 cuan88 Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Privacy Help For Wallet Status

A clear contact path helps when you want to ask what data we hold or why a wallet reference appears in your account record. Use the account help channel after signing in, and include the phone number or account identifier connected with your request. We use those details to locate the right record without asking you to send a wallet password or full payment credential.

Team online

Account help channel

Open account help after sign-in and choose the privacy request route. Add your account identifier, the subject of your request and a safe reply address so we can respond to you.

Payment status request

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the visible reference and date. Never send a wallet PIN, password or complete card credential.

Sign-in access issue

If you cannot reach your account help path, tell us the device type and the sign-in step that stopped. We may ask for phone verification before discussing account-linked data.

DATA HANDLING DETAILS

How We Protect Account Data

Privacy choices work best when you know what happens behind an account request. We separate sign-in records, payment references and support messages for operational handling, while limiting account details to the people…

Account records

We use your registration details and phone verification result to identify the correct account. This reduces mistaken disclosures when two accounts have similar names or payment references.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a status request. We do not ask for your wallet PIN or private wallet password.

Cookies and sessions

Cookies and session records help keep sign-in steps connected on your phone or desktop. You can adjust browser cookie controls, although some account and policy functions may then stop working.

Device security

We may record device type, browser details, approximate session signals and failed sign-in events. These checks help us identify unusual access before discussing account-linked data.

Retention periods

We keep records only for as long as needed for the stated account, security, dispute or legal purpose. When a retention period ends, records are removed or separated from direct account identifiers.

Changes and contact

You can request access, correction or deletion through account help. Include the relevant account step or payment reference, and we may verify your phone before changing or releasing records.

Privacy Policy Answers For cuan88

These Privacy Policy answers cover the requests we expect you to make before opening an account or when checking a record. They explain the practical route for account data, cookies, device signals and Indonesian wallet references, while keeping access wording tied to where local law permits.

It covers account details, phone verification, device and session records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Sign in, open the account help channel and select the privacy request route. State whether you want access, correction or deletion, then provide the account identifier needed to locate your record.

No. A payment reference may help us match a DANA, OVO, GoPay or QRIS status, but we do not ask for or need your wallet PIN, password or private wallet credentials.

Device signals, cookies and session records keep sign-in steps connected and help identify unusual access. For example, opening Bingo or Fish Hunter on a phone can create a session record.

Yes. Send a correction request through account help and identify the field that is wrong. We may complete phone verification before changing account details or confirming the result.

Retention depends on the reason for collection, such as account security, a payment query, a dispute or a legal requirement. Records are removed or separated from direct identifiers when no longer needed.

Yes. Access depends on local law, and some requests may be limited where local law permits retention for security or legal purposes. Contact account help for a request-specific explanation.