Reference

cu888 Privacy Policy

The cu888 Privacy Policy explains what we collect when you open an account, use the lobby, or check a DANA or QRIS transaction.

Clear data purposesCookie choicesAccount contact routePayment record controls
cu888 cu888 Privacy Policy
CONTACT ROUTES

Privacy Help Near Your Account

A clear support route matters when a privacy request is connected to login or wallet records.

Account data request From your account support path, ask which personal data is linked to your profile. Include your registered contact detail and the request type, such as access or correction, so we can confirm the account before responding.
Wallet record query For a DANA, OVO, GoPay or QRIS record, send the visible transaction reference rather than a full wallet password or security code. We use the reference to locate the cashier entry while limiting unnecessary personal details.
Security concern If you see an unfamiliar login or device session, use the account support route and state when you noticed it. We may ask for account verification before discussing access history or making a security-related change.
SECURITY PRACTICE

What We Do With Your Data

Our policy work follows the account actions you can actually take: register, verify, sign in, use a wallet route, and contact support.

Account data

We may hold your registration details, verification status and support messages so we can create the account, restore access and respond to requests. We use these fields for the stated account purpose, not as an open-ended record of unrelated activity.

Payment records

Cashier references can show a payment rail, amount status and account link for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use this trail to match a transaction and investigate a status question without requesting your wallet password.

Cookies

Cookies and similar browser storage can keep a session active, remember a selected setting or help us understand page errors. You can manage browser permissions, although removing required storage may sign you out or affect the account path.

Device security

We may record device type, browser signals, login time and session identifiers to identify unusual access. If a new phone signs in after desktop use, these signals help us place an extra verification step before account changes.

Retention period

We retain each category only while it supports the stated account, security, payment or legal purpose. When a record is no longer needed, our process is to remove it, separate it from direct identifiers, or preserve it only when a legal duty applies.

Changes and requests

You can ask us to correct profile data, explain a processing purpose, provide eligible account data, or assess a deletion request. Send the request through account support with enough detail to identify you; we may verify ownership before making a change.

Privacy Policy Answers For cu888

These answers address the searches we hear most often about the cu888 Privacy Policy. They focus on account data, cookies, payment references, device access and request handling, so you can decide what to share before opening an account or contacting support.

It covers data linked to registration, verification, login, lobby use, support contact and cashier activity. The policy explains why we use account details, device signals, cookies and payment references, plus how you can request access, correction or another eligible change.

We may collect registration and verification details, login events, device and browser signals, support messages and transaction references. The exact record depends on the action you take, such as opening an account, signing in, or checking a QRIS status.

Yes. The Privacy Policy covers records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes. These records can include a payment reference, status and account link used to match activity or answer a cashier question.

We use required cookies or browser storage to support sessions and account security, while other signals can help identify page errors or remember a setting. You can change browser permissions, but removing required storage may sign you out or interrupt account access.

Use the account support path and state whether you want access, correction, deletion assessment or a purpose explanation. Include your registered contact detail and a short description. We may verify account ownership before sharing data or applying a change.

Retention depends on the reason the record exists. We keep account, security, payment or legal records while that purpose requires them, then remove or separate them from direct identifiers when permitted. A legal preservation duty can extend a particular record.

Yes. Contact us through account support and provide the approximate time, device type and account contact detail. We can use session and device signals to investigate the event, and we may require verification before discussing access history or changing security settings.