Reference

Privacy Policy for Your csowin Account

Blackjack, Starburst, Aviator and your wallet sit behind one account flow, so this Privacy Policy explains exactly what data we collect before you explore the lobby.

DANA referencesOVO account checksGoPay receiptsQRIS device logs
csowin Privacy Policy for Your csowin Account
PRIVACY HELP

Three Ways to Ask About Privacy

Privacy questions should reach the right team without making you repeat private details in public channels.

Live chat privacy desk Use live chat from the account menu between 09:00 and 23:00 WIB when you…
WhatsApp account confirmation Message our WhatsApp support when a DANA, OVO, GoPay or QRIS receipt needs privacy-safe…
Email privacy request Send correction, access or deletion questions to [email protected].
ACCOUNT CARE

Six Privacy Controls Inside Your Account

We treat privacy as an account operation, not a paragraph hidden at the bottom of the page.

Data we collect

We collect the details you enter during account opening, including username, phone number and wallet references. Game choices such as Aviator or Mega Fishing are recorded only to maintain session history and account security.

Payment privacy

DANA, OVO, GoPay and QRIS records are used to match your payment to your wallet. We store reference codes, timing and account-name checks, not your private app PIN or mobile banking password.

Cookie choices

Cookies help keep you logged in, remember language settings and detect unusual device changes. On Chrome for Android, open Settings, Site settings, Cookies if you want to change browser-level controls.

Account security

We watch for unusual login patterns, repeated password attempts and device changes. If a session looks different, we may ask for confirmation through your registered phone before allowing wallet or profile changes.

Retention periods

We keep account and transaction records only as long as needed for wallet matching, dispute handling, security checks and lawful record duties. When a record is no longer needed, we remove or anonymise it.

Your requests

You can ask us to access, correct or delete eligible personal data. Start in live chat or email [email protected], then confirm your username and registered phone so we can protect the request.

Privacy Questions You May Search

The answers below focus on practical privacy concerns: what we collect, why we keep it, how wallet details are handled and how you can reach us. If your question is linked to a live account step, such as QRIS matching or phone-number correction, contact us with the exact account detail so we can respond without exposing private data.

We collect the details you provide, such as username, phone number, password credentials and wallet references. We also record login device data and session activity so your account can be protected and payment checks can be traced.

We use those payment references to match deposits and withdrawal requests to the correct account. The record normally includes sender name, reference code, amount, timing and status, not your private app PIN.

Yes. Contact live chat or email [email protected] with your username, registered phone number and the detail that needs correction. We may ask for confirmation before changing profile or wallet-related data.

Cookies remember your login session, language choice and security signals. On Android Chrome, go to Settings, Site settings, Cookies to manage browser controls, then sign back in if a session is cleared.

Only support and operations staff who need the message to answer your case can access it. We use chat history to trace account steps, payment references and privacy requests without posting your details publicly.

We keep transaction records while they are needed for wallet matching, dispute checks, security monitoring and lawful record duties. After that, we remove data or anonymise it where deletion is allowed.

Use live chat from 09:00 to 23:00 WIB, WhatsApp support, or email [email protected]. Include your username and the account step involved so we can route your privacy request correctly.