Reference

Privacy Policy for cuanhoki Account Data

Clear handling of your account, device and wallet records starts with our Privacy Policy.

Account dataWallet recordsPolicy access
cuanhoki Privacy Policy for cuanhoki Account Data
PRIVACY HELP PATH

Where To Ask About Your Privacy Policy

Privacy questions should reach the account support path rather than a wallet comment or game message.

Account privacy request Use the support path attached to your account when you want a copy, correction or explanation of personal records. Include your registered phone number so we can check ownership first.
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the payment reference and its displayed status. We compare that reference with account data before discussing the transaction.
Device access concern If a phone or browser appears in your account activity unexpectedly, tell us the device type and approximate access time. We can then check security records without requesting your password.
DATA CONTROL PRACTICE

How We Handle Your Account Records

We keep this Privacy Policy practical by linking each data use to an account action you can recognise, such as phone verification, wallet status or a device login.

Account data

We use the details you provide during account opening to create login access, connect your phone verification and respond to requests made through the account support path.

Device signals

Browser and device signals can be recorded around login activity to help identify unusual access. They are not used as a reason to request your password or wallet PIN.

Cookies

Cookies support session continuity and saved site choices. You can manage cookies through your browser settings, although changing them may affect how your Privacy Policy page or account session appears.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a payment status to the correct account. We use the reference for checking, not for collecting unrelated wallet details.

Retention

We keep account and payment records for account servicing, security checks and applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account identity.

Your requests

You can ask for access, correction or clarification through account support. We may confirm your phone-linked account before changing records so another person cannot alter your Privacy Policy data.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the account steps Indonesian customers ask about most often, from phone verification to wallet references and browser cookies. If your question concerns a record not listed here, use the account support path with enough context for us to locate it. Access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, wallet references, support requests and retention. It explains why each record is used and how you can request access or correction.

Phone verification connects the account to the correct person before access and helps us protect account records. We may use that check when you request a copy, correction or wallet status clarification.

Yes. The policy covers references, timestamps, amounts and status connected with DANA, OVO, GoPay and QRIS activity. These records help us match a wallet event with the correct account.

You can request a correction through the account support path. Include your phone-linked account details and explain the change. We confirm account ownership before editing records, where local law permits.

We retain records while needed for account servicing, security checks, dispute handling and applicable legal duties. When those needs end, we remove or anonymise records where appropriate.

Yes. Cookies can keep a mobile browser session and selected site choices available. Your browser controls cookie settings, and changing them may affect account continuity on your phone.

Use the support path inside your account and describe whether you need access, correction, removal or clarification. Add the relevant wallet reference or device detail, but never send your password or wallet PIN.