Reference

Privacy Policy for your cintawin account

Lightning Roulette, Captain Bounty, E-Sports Arena and QRIS wallet checks all create account data, so our Privacy Policy explains what we collect, why we use it and how…

Account data scopeDANA OVO GoPay QRIS recordsCookie controlsChange requests via support
cintawin Privacy Policy for your cintawin account
CONTACT ROUTES

Ask us about your privacy request

Privacy requests should reach the team that can check account records, not a general inbox that loses context. We ask you to send the mobile number or email linked to your account, the payment rail involved if the issue is DANA, OVO, GoPay or QRIS, and a short description of the change you want. Our support hours are 10:00 to 02:00 WIB, and we use chat history to avoid asking you for the same proof twice.

Team online

Live chat

Use the chat button after login for account-linked privacy questions. We can see your recent session record, device type and wallet reference, then route your request to the privacy queue during 10:00 to 02:00 WIB.

WhatsApp support

Send a short privacy request through our WhatsApp channel with your account email and the payment rail involved. We will never ask for your password or full wallet PIN in a privacy conversation.

Email request

For correction, access or deletion review, email support with the subject Privacy Request. Include your account ID, mobile number, and whether the data relates to games, cookies, QRIS records or customer service chat.

DATA PRACTICE

Our handling of account and cookie data

A privacy policy is useful only if you can see how it works in the account flow. We separate login data from wallet records, keep support access role-based, and use device checks…

Account creation data

When you open an account, we record your chosen username, contact detail, password hash, referral field if used and login timestamps. This helps us secure access and respond when you ask for a privacy change.

Payment record handling

DANA, OVO, GoPay and QRIS activity is stored as transaction references, status codes and wallet-facing amounts. We use these records to trace payment questions, verify withdrawal checks and match support cases to your account.

Cookie and session use

Cookies keep your session active, remember basic language choices and help us spot repeated failed logins. You can clear them in Chrome on Android through Settings, then Site settings, then All sites.

Device security checks

We read device signals such as browser type, IP range and login time to flag unusual access. We do not scan your photos, contacts or private apps when you enter Lightning Roulette or Crash Games.

Retention approach

We keep account and payment records only for operational, legal and dispute needs. When data is no longer needed for those purposes, we remove it from active tools or reduce it to limited audit records.

Change and deletion requests

You can ask us to correct contact details, send a copy of key account records or review deletion where rules allow. We may need identity checks before changing data tied to wallet activity.

Privacy Policy questions you may search

This FAQ explains the parts of our Privacy Policy that usually matter before you open an account: what data is collected, why payment rails are logged, how cookies work and how to reach us for changes. If your question involves a specific wallet transaction, include the DANA, OVO, GoPay or QRIS reference so we can check the right record without exposing unrelated account data.

We collect account details such as username, contact data, password hash, signup time, login records and device signals. If you use DANA, OVO, GoPay or QRIS, we also store transaction references linked to your wallet activity.

We keep payment records to confirm wallet status, trace delayed transactions, verify withdrawal checks and handle support questions. The record usually includes time, amount, payment rail, status and account reference, not your private wallet PIN.

Yes, start from Account, then Profile, and check the email or mobile number shown there. If the field cannot be changed on screen, contact live chat or email support with a privacy request.

Cookies keep you signed in, remember simple preferences and help us detect repeated failed access attempts. On Chrome for Android, you can clear site cookies through Settings, Site settings and All sites.

We keep data while your account is active and for operational, legal or dispute needs after that. Payment and support records may stay longer than simple session cookies because they help resolve wallet and account questions.

Only staff with a work reason can view privacy requests, and access is role-based. Support can see the case, payment references and contact detail needed to respond, while password values remain protected as hashes.

Email support with the subject Privacy Request, then include your account ID, contact detail and the data you want reviewed. We may ask for identity checks before sending records or changing data tied to payments.