Reference

counterwin88 Privacy Policy for Indonesia Accounts

counterwin88 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and browse titles such as Lightning Roulette or Aviator.

Clear data purposesWallet record contextPhone verificationIndonesia account access
counterwin88 counterwin88 Privacy Policy for Indonesia Accounts
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear support route matters when a phone number, wallet status, or account record looks unfamiliar. Start from your signed-in account support path and describe the exact record you want checked; include the payment rail, date, and reference when your question concerns DANA, QRIS, or a bank transfer. We use those details to locate the relevant entry without asking you to send a password.

Team online

Account request

Use the account support path to ask what personal details are attached to your profile, why a phone verification step appeared, or which record needs correction.

Wallet record

For DANA, OVO, GoPay, or QRIS questions, share the payment name and reference shown in your account. We can then check status without requesting your wallet password.

Access concern

If a device or sign-in record does not look familiar, contact us through the account help route and describe the time, device path, and account step you recognise.

HANDLING DETAILS

Six Practical Privacy Controls We Use

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Purpose-based collection

We collect account and payment details for stated needs such as opening access, matching a DANA receipt, checking QRIS status, answering support, and meeting obligations where local law permits.

Cookie choices

Cookies can remember a session and selected settings on your browser. You can review cookie controls in your device or browser path, although removing them may require another sign-in.

Device signals

Browser type, device signals, and sign-in timing help us identify unusual account access. We use these indicators for security checks rather than treating them as a public profile.

Account protection

Phone verification helps connect an account step to you before access continues. Never send us a password or wallet PIN; use the account support path if access appears unfamiliar.

Retention review

We retain records for as long as needed for the purpose collected, account security, dispute handling, and applicable legal duties, then remove or separate them when no longer needed.

Change requests

You can ask us to correct account details, explain a data use, or address a deletion request through support. We may check account ownership before changing or releasing records.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the searches we expect before an Indonesian account is opened or used. They cover payment records, cookies, device access, correction requests, and the account route for privacy questions. If your situation is not listed, send the relevant account step and payment reference through support so we can examine the right record.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone number to support account creation and verification, connect you with the correct account, and investigate access concerns. We do not need your password or wallet PIN for a support request.

Yes. The Privacy Policy includes payment references, status, amount, and timing associated with DANA or QRIS, along with comparable records for OVO, GoPay, bank transfer, and virtual account routes.

You can ask us to correct inaccurate account details through the account support path. We may confirm ownership first, then assess the request against security needs and duties that depend on local law.

Cookies may keep your session and selected settings available while you move between account pages. Browser controls let you remove or restrict them, but a fresh sign-in may be required afterward.

We keep records for the purpose that created them, account protection, disputes, and applicable legal duties. When a record is no longer needed, we remove it or separate it from active account use.

Use the signed-in account support path and describe the request clearly, such as access, correction, deletion, or payment-record context. Include a date or reference when relevant, but never send a password or wallet PIN.