Reference

Privacy Policy for Your chou123 Account

Our Privacy Policy explains how we collect, use, protect and retain your account data when you access chou123 in Indonesia.

Clear data purposesWallet details explainedMobile access covered
chou123 Privacy Policy for Your chou123 Account
HELP WITH DATA

Privacy Policy Support for Account Questions

A clear support route helps you act on this Privacy Policy without guessing which team to contact. Start from the account help path when a phone verification record, wallet status or sign-in event needs checking. Include your account identifier and a short description of the request, but do not send a password or full payment credential. We can then match the request to the relevant account record and explain the next step.

Team online

Account access

If your phone verification blocks access, use our account support path and mention the device, time and step where the issue appeared. We use those details to locate the relevant security event without asking you to disclose your password.

Wallet records

For a DANA, OVO, GoPay or QRIS data question, share the account reference and payment receipt details available to you. We can explain which records we hold and which part belongs to the external wallet or bank.

Policy requests

To ask for a copy, correction or clarification under this Privacy Policy, send the request through account support while signed in when possible. We may ask for an account check before changing or disclosing personal data.

DATA PRACTICES

How chou123 Handles Your Account Data

We keep this Privacy Policy practical: each data practice connects to an account action you can recognise.

Account data

We collect account details needed to create and maintain your access, including contact and verification data. We do not need your wallet password to connect an account request with a DANA, OVO, GoPay or QRIS receipt.

Security records

Login time, device signals and verification events can be used to detect account misuse and investigate a stalled sign-in. These records help us protect your access to casino sections, sports pages and account settings.

Cookies

Cookies and related storage can keep a session active, remember selected settings and help us identify broken steps on mobile. You can manage browser controls, though changing them may affect sign-in or saved preferences.

Payment references

A wallet or bank transaction reference lets support connect a payment question to your account. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may keep separate records under their own privacy terms.

Retention

We retain account, security and transaction records only for operational, dispute, safety or legal needs described by this Privacy Policy. When a record is no longer needed for those purposes, our process addresses its removal or de-identification.

Your request

You can contact account support to ask what personal data we hold, request a correction, ask about deletion or seek a retention explanation. We may verify that the request comes from the account owner before responding.

Privacy Policy Answers for chou123 Accounts

These Privacy Policy answers focus on the account decisions you are likely to make before opening access. They explain what happens around phone verification, local wallets, cookies, device records and requests for changes. If a question depends on your location or a payment provider, the answer will identify that boundary rather than treating every account the same.

The Privacy Policy covers data connected with account creation, phone verification, sign-in, lobby activity, wallet references, support requests, cookies and security checks. It also explains retention and request paths. Access depends on local law, so some rights or processes may vary by your location.

Our Privacy Policy does not require you to give us a wallet password. We may receive or record a transaction reference, status or receipt detail needed to connect a payment question to your account, while DANA, OVO, GoPay and QRIS handle their own account records.

Phone verification helps connect an account to its owner and investigate unusual access. Under the Privacy Policy, verification events can support sign-in protection and account recovery. If the check fails, contact account support with the device and step involved, not your password.

Where local law permits, you can ask account support what personal data we hold and request a copy or explanation. Sign in before sending the request when possible. We may verify ownership, then identify account, security and payment-reference records covered by the request.

Send a correction request through account support and describe the field that is inaccurate. The Privacy Policy allows us to verify the account before changing data. A bank or wallet record may need to be corrected with BCA, BRI, Mandiri, BNI or the relevant provider.

Cookies can remember your session and settings and can help us diagnose a failed mobile login. The Privacy Policy explains their operational use. Browser controls can remove or restrict them, but doing so may require you to sign in again or reset preferences.

We retain records for the operational, security, dispute or legal reasons described in the Privacy Policy. The period depends on the record and applicable rules. You can ask support why a particular account, security or transaction reference remains stored and what removal options apply.