Reference

cio168 Legal Terms For Your Account

cio168 Legal terms set out how we handle account access, personal data, wallet records and policy requests before you enter the lobby.

Account rulesData choicesPolicy requestsLocal access
Explore Our Lobby Read FAQ
cio168 cio168 Legal Terms For Your Account
CONTACT ROUTES

Get Help With A Legal Request

A clear contact route helps when you need a copy of your account data, want to question a policy decision or need a correction to registration details. Start from the account support path and include your registered phone number, request type and any relevant receipt reference. We use those details to locate the correct record without asking you to send a full wallet password. If your request concerns DANA, QRIS or a bank transfer, keep the transaction reference available so the policy team can separate account rights from payment processing.

Team online

Account support path

Open the support route from your signed-in account and describe the Legal request in plain terms. Include your registered phone number and the affected account step so we can check the correct record without exposing another customer’s details.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, add the payment reference and date to your message. We can then distinguish a data request from a wallet-status question while keeping your payment credentials out of the conversation.

Policy change request

If you believe a Legal term or account detail is inaccurate, tell us the wording you are challenging and the change you seek. We may ask for phone verification before changing protected account information.

DATA PRACTICES

How We Apply cio168 Legal Controls

Legal handling is connected to the way we store account events, wallet references and access checks.

Data handling

We use registration details, phone verification results and relevant account events to operate the requested account service. Payment references from DANA, OVO, GoPay or QRIS are treated as records for checking status, not as permission to request your wallet password.

Cookies and sessions

Necessary cookies help maintain a signed-in session and preserve the account path between pages. You can review browser cookie controls on your device, but blocking required cookies may prevent account verification or return you to the login screen.

Account security

We may require phone verification before changing protected details or responding to a sensitive Legal request. Do not share your password, wallet PIN or one-time code in a support message, even when asking about account access.

Record retention

We retain account and transaction references for the period needed to handle requests, resolve disputes and meet applicable legal duties. The period can differ by record type, so ask us which category applies when requesting removal or restriction.

Correction requests

You can ask us to correct inaccurate registration information by naming the field and supplying the updated value. We may check the request against your verified phone before applying a change to the account record.

Who handles requests

The account support route receives questions about data access, policy wording, cookies, retention and security. Include a specific request rather than sending wallet credentials, and we will route it to the relevant internal handling path.

Common cio168 Legal Questions

These Legal answers cover the practical questions you may have before opening an account or asking us to change a record. They explain what to prepare, how local access wording works and which details help us respond accurately. If your situation is unusual, use the account support path with the smallest amount of personal data needed to identify the request.

cio168 Legal covers account access conditions, phone verification, personal data handling, cookies, retention, policy changes and request routes. It also explains how we treat payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Yes. Access and eligibility depends on local law, and the applicable position can vary by location or current rule. Check the published policy wording before opening an account, and contact support if you need clarification about a specific access question.

Use the signed-in account support path and ask for a copy of your account data. State your registered phone number and the record category, such as registration, verification or payment reference. We may request phone verification before releasing protected details.

Yes, you can request a correction by naming the inaccurate field and supplying the replacement value. Send the request through account support rather than a wallet message. We may verify your phone before changing registration or security-related information.

We use DANA and QRIS references to check the related account event or payment status, not to obtain your wallet password or PIN. If you contact us about a record, provide its reference and date while keeping secret wallet credentials private.

Necessary cookies help keep your signed-in session active and support the phone-verification path between pages. Browser settings can block them, but doing so may interrupt account access or return you to login. Review your device settings if you want to change cookie permissions.

Send a specific retention or account-removal request through support and identify the record type involved. We assess it against applicable legal duties, dispute handling needs and account security requirements. The response may differ for registration records and payment references.

Related Pages

cio168 Indonesia About Us DANA Withdraw Guide Live Blackjack Table Bundesliga Over Under