Reference

Privacy Policy For Your ciobet Account

Our Privacy Policy explains how ciobet handles the details you provide when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
Explore Our Lobby Read FAQ
ciobet Privacy Policy For Your ciobet Account
CONTACT PATHS

Ask About Privacy Before Account Access

A clear contact path matters when a privacy question is tied to a login or wallet status.

Account privacy request Use the support contact shown after account access when you want a copy, correction or explanation of personal data. Include your registered phone detail and the specific request so our team can separate an account question from a DANA, OVO, GoPay or QRIS status query.
Wallet record question If a payment record looks unfamiliar, mention the rail and reference visible in your cashier history. We use that detail to check DANA, QRIS, bank transfer or virtual account status without asking you to disclose a password, card secret or complete wallet login.
Login and device concern When a phone, browser or account session seems unfamiliar, contact support from the account area and explain what changed. We can direct the privacy request to the access check, while you keep control of your password and any phone verification code.
HANDLING DETAILS

Six Ways We Protect Your Privacy

Privacy work is practical: we limit access to account records, separate payment references from unnecessary profile details and use device signals to help identify unusual sign-in activity.

Account details

We collect details needed to create and maintain your account, including contact information and phone verification status. We use them to match you with your own account flow, respond to a privacy request and prevent records from being assigned to the wrong person.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount, timestamp and status in your account record. Bank transfer and virtual account entries are handled in the same way: enough detail to reconcile a request, not a request for your wallet password.

Cookies and devices

Cookies and device signals help keep a signed-in session working, remember selected settings and flag an unusual access pattern. A mobile browser may create different technical records from desktop, but both remain connected to the account session rather than treated as a new identity.

Account protection

Phone verification before account access helps us check that a sign-in request belongs to you. Keep your password and verification code private. If a device is lost or a session looks unfamiliar, contact support so we can review the access record.

Retention choices

We keep personal data only for the account, payment reconciliation, security checks and legal duties that require it. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identification where appropriate.

Changes and requests

You can ask us to correct inaccurate account details, explain a data use or provide access to information linked to your profile where local law permits. Send the request through the account support path and identify the record without including a password or complete wallet credentials.

Privacy Policy Answers For ciobet

These answers focus on the questions you may have before opening an account or checking a wallet record. They cover the ciobet Privacy Policy, device access, cookies, payment references and requests for data changes. If your situation is specific, use the support path above and include only the details needed to locate your account.

It covers personal data connected with your account, phone verification, device access, cookies and payment records. It also explains why we use those details, how we protect access, how retention works and how you can ask for access or correction where local law permits.

Yes. The policy covers payment references and status details created when you use DANA, OVO, GoPay or QRIS. It can also apply to bank transfer and virtual account records. We use these details to reconcile activity and answer status questions, not to request your wallet password.

Phone verification connects an access request to the account contact you provided. It helps us reduce mistaken access and investigate an unfamiliar session. Keep the code private, and contact support from the account area if your phone is lost or the sign-in activity does not look like yours.

A mobile browser or desktop session can create technical details such as browser type, session signals and access time. We use them to keep a session working, remember settings and identify unusual activity. The device path does not replace the account details used for your privacy request.

You can ask for access to data linked to your account or request a correction where local law permits. Use the support contact shown in the account area, state the requested action and provide your registered phone detail. Do not attach your password or a complete wallet credential.

We retain records for the account, payment reconciliation, security checks and legal duties that apply to the relevant record. Retention can differ by record type and local requirements. You can ask support why a particular record remains connected to your account and what request options apply.

Open the account support area and describe the concern, such as an unfamiliar payment reference, an incorrect profile detail or an unexpected cookie setting. Include only identifying details needed for the check. We will route the request to the relevant privacy or account-access review.

Related Pages

ciobet Indonesia Access guide Account information About Us FAQ