Reference

Open Your cro188 Privacy Policy Path

cro188 Privacy Policy shows what we collect, why we use it and how you can ask about your account records before opening access.

Clear data purposesWallet record contextCookie choice stepsAccount request path
cro188 Open Your cro188 Privacy Policy Path
REQUEST SUPPORT

Ask About Privacy Policy Through Support

A clear contact route helps when you need a copy, correction or explanation connected with your Privacy Policy rights.

Account data requests Use our account support path to ask what personal records we hold, why a…
Wallet record questions If a DANA, OVO, GoPay or QRIS reference appears in your account history, provide…
Access and cookie help When a sign-in or cookie choice does not behave as expected, tell us your…
DATA PRACTICES

Browse How cro188 Handles Your Data

Privacy work is part of each account step, from the first phone check to a later wallet status question.

Account data use

We use phone verification and account details to create access, confirm changes and respond to requests.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to the correct account.

Cookies on devices

Cookies may keep a session active, remember a selected setting or show us whether a page loads correctly.

Account security steps

Phone verification comes before account access, and we may ask for matching account details when a request involves private records.

Retention and deletion

We keep personal records for the period needed for account operation, security checks, transaction reconciliation or legal duties described in…

Changes to your records

Ask through account support if your phone detail, profile entry or request history needs correction.

Browse cro188 Privacy Policy Questions

These Privacy Policy answers focus on the records you are most likely to notice while using cro188 from Indonesia. They cover account access, local wallets, cookies, device signals, retention and requests. If your situation is not covered, use the account support path and describe the exact policy question so we can check the relevant record.

It covers account details, phone verification, sign-in and device signals, wallet references, cookies, support requests, retention and available privacy choices. It also explains why a record is used and how to contact us about access, correction or deletion where applicable.

Phone verification helps confirm that the person requesting account access or a privacy change controls the linked account. We may use the result with sign-in and account details to protect private records. Access depends on local law and is available where local law permits.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. These records can help match a receipt or status to your account, while wallet passwords, PINs and one-time codes should not be sent to us.

Use the account support path and state whether you want access, a correction or another Privacy Policy request. Add your linked phone number and the record involved. We may verify identity before discussing details, then explain the next step and any applicable limits.

Cookies can support a login session, remember a setting or help us see whether a mobile page loads correctly. Your browser provides controls for accepting or removing them. Turning some off may require another sign-in or remove a saved preference.

We retain records for the operational, security, reconciliation or legal period described in the Privacy Policy. A DANA receipt reference or bank transfer record may remain after a request if it is needed for one of those stated purposes.

Yes. Tell support the device type, browser path, approximate sign-in time and linked phone number. We can explain what session or security record may exist and check the request after identity verification. Do not include a password or one-time code.