Reference

666ii Terms & Conditions Before Access

666ii Terms & Conditions set the rules for opening, using and closing your account, with clear steps for identity checks, wallet status and access where local law permits.

Account rulesPayment conditionsPolicy access
666ii 666ii Terms & Conditions Before Access
POLICY HELP

Where To Ask About Terms & Conditions

A clear support route helps when a clause affects your account, wallet status or access request.

Account help Use the account help route when you need clarification about phone verification, permitted access…
Cashier questions If a DANA, OVO, GoPay or QRIS transaction does not match your account record…
Policy changes When you want to question a wording change, ask for a data correction or…
ACCOUNT SAFEGUARDS

What The Policy Says About Your Data

The Terms & Conditions work alongside our account handling practices so you can see what happens to information used for access, payments and support.

Account details

Your registered phone details must remain accurate because phone verification is part of the account access path. If your number or personal details change, contact us before attempting a wallet or withdrawal change so the record can be checked without creating conflicting account data.

Transaction records

We retain transaction references needed to check DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. A receipt reference lets support compare the payment record with your account details and apply the relevant Terms & Conditions without relying on an incomplete screenshot.

Cookies

Cookies can preserve session settings and help the account path work between login and the lobby. You can manage cookies through your browser controls, but changing them may require another login or remove saved settings used during a Terms & Conditions request.

Security checks

We may pause an account action when the phone, payment detail or access pattern needs confirmation. This protects the account record rather than changing the policy. Follow the requested verification step and contact support if the check blocks a legitimate wallet or account request.

Retention requests

You can ask how long account or transaction records are kept and why a record remains available after a request. Send the question through account help with your registered phone details; we will explain the applicable retention rule and any records that must remain for account handling.

Corrections and closure

If a name, phone detail or account entry is wrong, request a correction before using another payment rail. You may also ask to close the account, subject to unresolved transactions and checks required by the Terms & Conditions. Support will outline the next step.

666ii Terms & Conditions Questions

These answers address the policy searches we hear most often before account access. Read the full Terms & Conditions first, then use the account help path if your situation involves a wallet receipt, a phone change, a data request or a local eligibility question. We will apply the current wording to your account record.

You can open the Terms & Conditions from the policy link on the 666ii site before completing account access. Read the clauses on eligibility, phone verification, payments, account closure and data handling. If a section is unclear, contact account help with the exact heading or wording.

Yes. Access depends on local law, and you must check that the service is permitted where you are located before opening or using an account. Our Terms & Conditions do not replace local requirements. If your eligibility is uncertain, ask support before submitting account or payment details.

Phone verification comes before account access, and your registered details should match the account information used for a wallet transaction. When using DANA, OVO, GoPay or QRIS, keep the receipt reference available. A mismatch may require a support check before the transaction can proceed.

Yes. Send a correction request through account help and identify the field that needs changing, such as your registered phone detail. Do not send a password or wallet PIN. We may ask for an account check before updating the record under the Terms & Conditions.

The policy explains how account details, transaction references and cookies support access, payment checks and support replies. Browser cookie controls can change session behaviour. You can ask us about data use or retention through account help, and we will explain the relevant handling rule.

You can request account closure through the support path, but unresolved wallet or bank transfer activity may need checking first. We may also retain records required for transaction handling. Support will confirm the closure steps and explain which account details remain subject to retention.

Keep the payment receipt and contact the cashier support path with the rail used, such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account. State the clause or transaction concern plainly. We can explain how the Terms & Conditions apply to that account record.