Reference

666i Privacy Policy For Your Account

The 666i Privacy Policy explains what account, wallet, device and support data we use, why we use it, and how you can request changes.

Account dataWallet recordsCookie choicesPolicy requests
666i 666i Privacy Policy For Your Account
POLICY HELP ROUTE

Where To Ask About Privacy

You can ask us about the Privacy Policy without explaining your entire account history. Use the support path beside account access for a data question, a cookie concern or a request to correct your details. If a wallet event needs checking, include the relevant DANA, OVO, GoPay, QRIS or bank transfer reference so we can locate the correct record.

Team online

Policy contact form

Send a direct request through our policy contact form when you want to ask what data we hold, why a record exists, or how to request a correction to your account details.

Account help path

If sign-in or phone verification blocks your request, use the account help route linked near the login step. We use the details you provide to match the request with the right account.

Wallet status query

For a privacy question tied to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, include the transaction reference and avoid sending your password or full security code.

HANDLING YOUR RECORDS

What We Do With Account Data

Our Privacy Policy separates service records from the access credentials that protect your account. We keep collection focused on account operation, wallet reconciliation, device security and support handling rather than asking for…

Account creation

When you open an account, we use the details you submit to create your profile and support phone verification before account access. We do not need your password in a policy contact request.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be connected with your account record to check payment status. We use that trail to resolve mismatched or pending wallet events.

Device signals

We may record browser type, device signals, session time and sign-in events to identify unusual access. A mobile browser and desktop browser can therefore produce different security records without changing your policy rights.

Cookie choices

Cookies can help keep a signed-in session working and remember a preference. You can manage browser cookie settings, although removing required cookies may interrupt account access or return you to the login step.

Security controls

We limit account data access to operational needs, protect sign-in details and ask you to avoid sharing passwords or verification codes. Support may request enough account detail to confirm the correct record.

Retention requests

We retain records only for service, security, dispute handling or legal needs that apply to the request. Ask through the policy contact form to request access, correction or deletion assessment.

Privacy Policy Questions For 666i

These Privacy Policy answers address the searches we expect before you open an account or contact us about stored data. Each answer stays focused on your account, device, wallet and support records, including access where local law permits.

It covers account creation, phone verification, sign-in events, device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your submitted phone number for account creation and phone verification before account access. It also helps us match a policy request with the correct account when you contact support.

Yes. The policy covers payment references and wallet status linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those records are needed for reconciliation or support.

We may record browser type, device signals, session time and sign-in events. These details help identify unusual access and can differ between a mobile browser and a desktop browser.

Use our policy contact form and state whether you want access, correction or another data request. Include the account identifier needed to find your record, but never send your password or security code.

Yes. Use your browser cookie controls to change available preferences. Required cookies may be needed for a signed-in session, so removing them can send you back to the login step.

We retain records for service operation, security, dispute handling or legal needs that apply to the matter. You can ask us to assess deletion or correction through the policy contact form.