Reference

Open qq cuan Privacy Policy Clearly

qq cuan Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Lightning Roulette or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
qq cuan Open qq cuan Privacy Policy Clearly
ASK OUR DESK

Contact Us About Privacy Policy

A privacy question should not be mixed with a lobby question, so we keep a direct route from your account area to our support desk. Tell us whether you need a copy of account data, a correction, a cookie preference change or clarification about a wallet record. Include the phone number or account identifier attached to your request, but never send a password or one-time verification code.

Team online

Account request

Open the support form from your signed-in account and select the privacy subject. We use the account identifier to locate the right record before discussing a data copy, correction or deletion request.

Wallet question

For a DANA, OVO, GoPay or QRIS record, attach the payment reference rather than a full wallet password. This helps us check the matching status without asking you to reveal secret access details.

Login concern

If your phone cannot reach the support form, use the contact route shown beside the sign-in area. Describe the device path and account step that stopped, while keeping your password and verification code private.

DATA CARE DETAILS

Explore Six Privacy Policy Commitments

We keep the Privacy Policy practical by tying each promise to an action you can recognise on qq cuan.

What we collect

We may record your account identifier, phone verification result, sign-in time, device details, support conversation and payment reference. These details help us provide account access, trace a wallet status and respond when you ask about your records.

Cookie controls

Cookies and similar device storage can keep your sign-in path working and remember a preference. You can adjust browser controls or ask our support desk about the cookie categories used on the page you opened.

Account protection

Phone verification is checked before account access, while sign-in and device events may be logged to spot unusual attempts. Keep your password and one-time code private; our support desk will not need either secret.

Payment records

A wallet or bank reference can be retained to match a deposit or withdrawal status with your account. For BCA, BRI, Mandiri or BNI transfers, we use the reference needed for reconciliation rather than unrelated banking details.

Retention choices

We keep records only for the operational, dispute, security or legal purpose that requires them, then remove or separate them when that purpose ends where local law permits. A support request can ask why a record remains.

Change requests

You can ask us to correct an inaccurate account detail, explain a processing purpose, provide available records or address a cookie choice. We may verify account ownership before acting so another person cannot change your data.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover phone verification, wallet references, cookies, device changes and requests for access or correction. If your situation is not listed, use the account support form and describe the exact record or account step you want us to check.

The qq cuan Privacy Policy covers account details, phone verification, sign-in and device logs, cookies, support messages and payment references. It explains why we use each category, how retention works, and how you can request access or correction where local law permits.

Phone verification helps us confirm that the person opening the account controls the stated contact route. We record the verification result and related account event, not your private code. Verification is checked before account access and supports account protection.

Yes. The Privacy Policy covers the payment reference and status connected with DANA, OVO, GoPay and QRIS activity. We use that reference to match a receipt or investigate a status question, while your wallet password and secret code remain yours.

Sign in, open the support form, choose the privacy subject and ask for an account data copy. Include your account identifier and a clear request. We may verify ownership first, then explain what can be provided where local law permits.

You can request a correction through the support form by naming the inaccurate field and supplying the replacement detail. For a wallet or bank reference, include the relevant receipt number. We check the account context before changing a record.

Cookies stored on the old phone do not automatically move to a new device. A new sign-in may create fresh device records, and phone verification can be requested before access. Browser controls and our support route remain available for cookie questions.

Yes. Ask through the account support form and identify the record, such as a sign-in event, support message or bank transfer reference. We will explain the operational, security, dispute or legal reason for retention where local law permits.