Reference

Privacy Policy For Your cio168 Account

Our Privacy Policy explains what account details we collect, why we use them and how you can ask about changes.

Clear data purposesWallet record contextAccount access rightsMobile privacy steps

How Privacy Applies To Wallet Records

cio168 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers information connected with your account, including contact details, phone verification, sign-in activity, device signals, support messages and payment records. If you use DANA, OVO, GoPay or QRIS, we may retain the transaction reference and status needed to match a cashier request with

1
your account; we do not need your wallet password for that purpose. Bank transfer and virtual account references may also be checked when a payment status is unclear. We use these records for access checks, account security, service requests and legal duties. Availability and eligibility depends
2
on local law. If you disagree with a policy point, ask us before opening an account or continuing to use the account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact route matters when a privacy question affects your account or wallet status. Start from the account help path and describe the exact record you want us to check, such as a phone verification entry or a QRIS receipt. We will use the details you provide to locate the request and avoid exposing account data to the wrong person. For questions about this Privacy Policy, include your account identifier and the subject of your request.

Team online

Account access request

Ask us to explain the account details linked to your phone verification or sign-in record. We may request an account step before discussing personal data, so the request is connected to the correct cio168 account.

Wallet record check

Send the payment rail and reference you need checked, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We can then separate a wallet status question from a wider Privacy Policy request.

Correction request

Tell us which personal detail appears wrong and what should replace it. We may confirm your phone verification first, then review the account record and explain whether the requested change can be made.

DATA HANDLING

Six Practical Privacy Checks We Apply

We treat privacy as an account process rather than a statement hidden from view. Data handling starts when you create an account and continues through sign-in, wallet matching, support and account closure.

Account details

We use the details you submit, including your phone number and verification information, to identify your account and respond to account requests. We do not ask you to send a wallet password when checking a DANA or QRIS record.

Device signals

A mobile browser or desktop session can create technical records such as device type, browser details and sign-in time. These signals help us detect unusual access and explain why a session may need another account check.

Cookie choices

Cookies may keep a session active, remember basic preferences or help us understand a page request. You can adjust cookie controls in your browser, although removing them may require another sign-in or affect account page functions.

Account security

Phone verification and sign-in checks help us avoid discussing personal records with the wrong person. If your access looks unusual, we may pause a data request until you complete the account step connected with your profile.

Record retention

We keep account, support and payment references only for as long as needed for the purpose described in this Privacy Policy, account security and applicable legal duties. A retention question can be sent with the relevant account reference.

Policy changes

If this Privacy Policy changes, we will update the policy page so you can check the current wording before using your account. Ask us to explain a change, or request a correction when a stored detail no longer matches your account.

Answers About cio168 Privacy Policy

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening an account. They cover the records connected with DANA, OVO, GoPay, QRIS and other supported payment references, along with cookies, device activity and requests for access or correction. If your situation is different, use the account help path and describe the record clearly.

The cio168 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each type of data, how security checks work and how you can ask for access, correction or clarification.

Yes. The Privacy Policy includes transaction references and status information connected with DANA, OVO, GoPay and QRIS. We may also check bank transfer or virtual account references to match a payment with the correct account, but we do not need your wallet password.

Use the account help path and state that you are making a Privacy Policy data request. Include your account identifier and the record you want explained. We may ask you to complete phone verification or another account step before discussing personal details.

Device and cookie records help us keep a sign-in session working, remember basic page choices and identify unusual access. The Privacy Policy describes these purposes. You can change cookie controls in your browser, though this may lead to another sign-in check.

We retain account, support and payment references for the period needed for their stated purpose, account security and applicable legal duties. The exact period can depend on the record type. Ask us about a specific account reference if you need a retention explanation.

You can request a correction by identifying the detail that appears wrong and supplying the replacement wording. We may confirm your phone verification before changing it. The Privacy Policy also explains when a record must remain available for security or legal reasons.

Start with account help and label your message as a Privacy Policy question. Describe whether it concerns account access, cookies, device activity, a wallet reference or retention. Availability and eligibility depends on local law, and we will explain the relevant route for your request.

Privacy Policy For Your cio168 Account

Three Ways To Ask About Your Data

Account access request

Wallet record check

Correction request

Six Practical Privacy Checks We Apply

Account details

Device signals

Cookie choices

Account security

Record retention

Policy changes

Answers About cio168 Privacy Policy

01 What does the cio168 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 How can I request my cio168 account data?

04 Why does cio168 use device and cookie records?

05 How long does the Privacy Policy keep my records?

06 Can I correct details held by cio168?

07 Where can I ask about Privacy Policy access?

Related Pages