Reference

Privacy Policy for Your cina365 Account

Our Privacy Policy explains what we collect when you open a cina365 account, sign in from a phone or desktop, and use payment paths such as DANA, OVO…

Account data clarityWallet reference handlingCookie choicesAccess depends on local law
Browse Our Lobby Read FAQ
cina365 Privacy Policy for Your cina365 Account
ASK ABOUT YOUR DATA

Three Ways to Reach Policy Support

A clear contact route matters when you want to understand a record, correct an account detail or ask why a device check appeared.

Policy message Send a privacy question through our account support path and identify the email or phone attached to your cina365 account. We can use the account step and message date to locate the relevant record without asking you to share a password.
Payment reference For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate time rather than a wallet PIN. Our support team can compare the reference with the account record and explain what data was used for the status check.
Access concern If a phone or desktop sign-in looks unfamiliar, contact account support before sending further payment details. Tell us the device type, sign-in time and account contact route so we can examine access signals and help secure the account.
HOW WE HANDLE RECORDS

Six Practical Privacy Commitments

Privacy decisions are easier to assess when the handling steps are visible. We connect each data category to an account purpose, such as access, payment matching, fraud prevention or support.

Account details

We collect contact and verification details when you open or maintain an account because those fields support sign-in, account recovery and identity checks. We aim to keep the record relevant to the account service and do not ask for unrelated personal details as part of a normal login.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be linked to your account to identify a payment status. The reference helps us investigate a receipt or mismatch; it is not a request for your wallet password or card secret.

Cookies and devices

Cookies and device signals help keep a session connected, remember basic preferences and identify unusual access. Moving from a mobile browser to desktop may create a new security signal, while clearing cookies can require another login or phone verification before access continues.

Account protection

We use login activity, verification events and device information to investigate suspicious access and protect your account. Keep your password private, sign out on shared devices and contact us if a sign-in or account message does not match your own activity.

Storage and removal

We keep records for as long as they are needed for account operation, payment reconciliation, security checks or a legal request. When a record is no longer needed for those purposes, our handling process considers removal or restriction, subject to applicable requirements.

Change requests

You can ask us to correct contact details, explain a data category or clarify how a payment reference was used. Send the request through support with enough account context for verification, and we may need to confirm that you control the account before making a change.

Privacy Policy Questions for cina365

These questions address the points you are most likely to check before opening an account or using the cina365 lobby. Each answer stays focused on personal data, account access, cookies, payment references and contact rights. If your situation is specific, use the policy support path and avoid sending passwords, wallet PINs or complete payment credentials. Access depends on local law.

The cina365 Privacy Policy explains how we handle account details, verification records, login activity, device signals, cookies, support messages and payment references. It also sets out why we use those records, how you can ask questions or corrections, and what access depends on local law.

We may collect the contact and verification details needed to create, protect and recover your account, along with sign-in and device information. We use these records for account access and security checks. We do not need your wallet PIN to match a DANA, OVO or QRIS reference.

Device and login information helps us recognise normal account activity and investigate access that appears unusual. A switch between mobile browser and desktop can create a new signal, and clearing cookies may require another sign-in or phone verification before your account path continues.

We may receive a payment reference or status detail when you use DANA, OVO, GoPay or QRIS, so we can connect the transaction with the correct account. We use that context for reconciliation and support. Do not send a wallet password, PIN or full credential.

Yes. Contact policy support with the account email or phone, identify the detail that needs correction and explain the requested change. We may confirm account control before editing a record. A clear request helps us distinguish a genuine correction from an unauthorised access attempt.

We retain records while they are needed for account operation, payment reconciliation, security investigation, support handling or applicable legal requirements. Once a record no longer serves those purposes, our process considers removal or restriction. Specific handling can depend on the record and local law.

Use our account support path and include the account contact route, request type and relevant date. For a payment question, use the transaction reference instead of secret wallet details. We can then explain the record, consider a correction request or clarify the access step involved.

Related Pages

cina365 Indonesia Blackjack Account information kafetogel FAQ