Reference

Open cro168 With Privacy Policy Clarity

cro168 Privacy Policy explains what we collect when you open an account, verify your phone, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet referencesDevice controlsCookie choices
cro168 Open cro168 With Privacy Policy Clarity
CONTACT ROUTE

Reach Us About Privacy Policy

A clear contact path matters when your account record or wallet reference needs attention. Use the support route shown after sign-in for a privacy request, or use the contact option displayed on the cro168 policy page if you cannot enter your account. Tell us whether your request concerns phone verification, a DANA or QRIS reference, a cookie choice, or a device sign-in. Our support hours and available channel are shown on that contact screen so you can send the request through the active route.

Team online

Account desk

After sign-in, open the account help path and select privacy support. Include your registered phone number in masked form and the request type so we can locate the correct record.

Wallet check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference rather than a wallet password. We use that reference to check the matching account event.

Access fallback

If phone verification blocks entry, use the contact route visible on the policy page. State your device type and last successful sign-in without sending a password or private wallet credential.

DATA PRACTICE

Explore cro168 Data Handling Choices

We separate the records needed to operate your account from optional signals used to remember a device or understand a page visit.

Account records

When you open an account, we use the details needed for sign-in and phone verification.

Cookie controls

Cookies can keep a session active or remember a setting on your browser.

Device signals

A browser and device can provide session, security and language signals when you sign in.

Wallet matching

DANA, OVO, GoPay and QRIS references help us trace a payment status without requesting your wallet password.

Retention timing

We retain account, support and payment records for the period needed for the stated purpose, dispute handling and applicable legal…

Change requests

To request a copy, correction or removal, contact us through the account privacy path and describe the record involved.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the searches we hear most often from people considering a cro168 account in Indonesia. They cover the practical points: what is recorded during sign-in, how local wallet references are handled, what happens on a phone or desktop browser, and how to send a request. If your question concerns a specific account event, use the contact route and quote its reference without sharing a password.

It covers data connected with your account, phone verification, sign-in sessions, cookies, device signals, support requests and payment references. It also explains purposes, retention, request routes and the local-law condition that applies when access or eligibility is discussed.

No. Our Privacy Policy describes the use of payment references, timestamps and status details for DANA, OVO, GoPay and QRIS reconciliation. Never send a wallet password to support. A reference lets us check the matching account event without that credential.

Sign in, open the account help path and select the privacy request option. Describe whether you want a copy, correction or removal, and include a masked phone number or transaction reference. We may verify account ownership before releasing or changing records.

A mobile browser may hold a session marker, cookie choice and device security signal when you sign in. The same Privacy Policy applies on the mobile path from login to the lobby. A new device can prompt phone verification before account areas appear.

We keep payment records only for the stated operational purpose, dispute handling and applicable legal duties. This can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. After the relevant period, records are removed or separated from active use.

Yes, where the cookie prompt or browser controls provide that option. Optional cookies can be changed through those controls, while required session cookies may remain necessary for sign-in and account security. The policy explains which purpose each category supports.

Yes. Account access and eligibility depends on local law, and where local law permits, we apply this Privacy Policy to your account activity. If you need help understanding a request or access issue, contact us through the route shown on the policy page.