Reference

cintawin Privacy Policy for Your Account

Your account details, wallet records and device choices have a clear place in the cintawin Privacy Policy.

Clear data purposesWallet record detailsCookie choicesAccount contact path
cintawin cintawin Privacy Policy for Your Account
PRIVACY SUPPORT PATH

Privacy Questions Through Account Support

A direct support route helps when a privacy request, login record or wallet status needs checking.

Access request Ask us to confirm which account data we hold by using the support route inside your account. We may request phone verification before sending details to the matching account holder.
Correction request If your phone, profile or payment reference is inaccurate, tell us the field that needs changing. We check the account record first, then update or explain the available correction path.
Wallet query For DANA, OVO, GoPay or QRIS records, include the transaction date and status shown to you. Do not send a wallet PIN; our team only needs a reference to investigate.
DATA HANDLING DETAILS

How We Handle Privacy and Account Security

We keep this policy practical by linking each data type to an account action: phone verification protects entry, session records help trace unusual access, and payment references help resolve wallet status questions.

Account records

We use your phone number and verification result to create the correct account path. If access fails, the support team can compare the request with the recorded profile instead of asking for unnecessary personal details.

Device signals

A mobile browser opening Crash Games, Super Bingo or Royal Fishing may send device and session signals. These help us detect unusual sign-ins, preserve security checks and investigate access issues.

Cookie controls

Cookies can retain a session choice or help us understand which policy page was opened. You can clear or restrict them in your browser, although some account steps may then need repeating.

Payment references

For bank transfer, virtual account and QRIS activity, we retain matching references rather than wallet passwords. This supports receipt checks and helps separate your transaction from another account record.

Retention period

We retain account, security and transaction records only as long as needed for the stated purpose, account protection or legal duties. When no valid need remains, records are removed or made less identifying.

Change requests

Use the account support route to request a copy, correction or eligible deletion. We verify the request against your account and explain any record that must remain for security or legal reasons.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers address the account actions that matter before you open an account from Indonesia. We cover phone verification, wallet references, cookies, device records, deletion requests and access rules, including what to do when a payment status needs investigation.

The cintawin Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and verify the account path, protect sign-in attempts and match privacy requests to the correct account. We do not need your wallet PIN for this process.

No. Our Privacy Policy describes payment references, timestamps and status results for DANA and QRIS activity. Wallet credentials remain with the relevant payment service, so do not send a PIN through support.

Open the support area from your account and request a data copy. We may ask for phone verification before responding, so the record is sent to the account holder rather than another person.

Yes, you can request a correction or eligible removal through account support. We first check the account record, then explain whether security, transaction matching or legal duties require a record to remain.

Cookies may retain a session choice or measure use of a mobile page. You can clear or restrict them in browser settings, but signing in again or repeating phone verification may be necessary.

Yes. Some account access, retention and data-request rights depend on local law. Where local law permits, we process eligible requests through account support after confirming the requester’s identity.