Reference

666ii Privacy Policy for Your Account

The 666ii Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening an account.

Account clarityWallet data careCookie choicesContact path
666ii 666ii Privacy Policy for Your Account
HELP WITH PRIVACY

Where to Ask About Your Account Data

A clear contact route matters when a wallet status or login question includes personal data.

Privacy questions Ask through the support contact shown on our site when you want to know…
Wallet records For a DANA, OVO, GoPay or QRIS receipt, share the reference details requested by…
Access concerns If your account path stalls before the lobby opens, contact us with the device…
DATA HANDLING

Inside 666ii Privacy Controls

We keep the Privacy Policy practical by linking each data category to an account task. Contact details support verification and account messages; payment references help reconcile wallet activity; device signals help protect…

Account details

When you open an account, we use the details entered in the account path to create access and complete the phone verification step when requested. The Privacy Policy explains the purpose of each requested field, so you can decide what to provide.

Payment references

A wallet name or bank reference can be linked to a deposit or withdrawal status without giving us your wallet PIN. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in a support check when relevant.

Device signals

Browser, device and connection signals help us recognise a session and investigate an unusual login. We use them for access protection and service troubleshooting, not as a reason to request your password or complete wallet credentials.

Cookies

Cookies can keep a session working, remember selected settings or help us understand a page error. Your browser provides controls for cookie storage, although restricting essential cookies may affect the account path or return you to verification.

Retention choices

We keep personal records while they support account operation, security checks, dispute handling or a legal requirement. When a record no longer serves one of those purposes, our retention process assesses it for deletion or removal from active systems.

Change requests

To ask for correction, access or deletion, contact us through the support route shown on 666ii and describe the account detail involved. We may need to verify that the request comes from you before changing or disclosing personal data.

Privacy Policy Answers for 666ii

These Privacy Policy answers cover the questions we expect you to ask before creating an account or checking a wallet record. We keep the wording tied to real account steps, including phone verification, mobile sessions and payment references. If your question is not listed, use the support contact shown on 666ii and tell us which part of your data request needs attention. We will explain the available route without asking for more personal material than the check requires.

The Privacy Policy covers account details, phone verification, device and connection signals, cookies, support messages and payment status references. It explains why we use each category, how long records may be retained and how you can contact us about access, correction or deletion.

Do not send a DANA, OVO or GoPay PIN to us through support. Our payment checks use the transaction or wallet status and the account reference needed to match an event. If a message asks for a PIN, stop and use the support route shown on 666ii.

Phone verification helps connect the account path to the contact detail you provided and can support access protection. The Privacy Policy treats that number as account data. We may ask you to confirm ownership before discussing, changing or releasing account details.

When you use a mobile browser, we may process device, browser and connection signals needed to keep the session working and investigate unusual access. These signals can help separate a cookie or login issue from a personal-data request, and they do not replace your password.

Yes, contact us through the support contact displayed on the site and describe the account data you want to access or correct. We may verify your identity first. Some records can remain where security, dispute handling or a legal duty requires retention.

We retain data while it is needed for account operation, security checks, payment reconciliation, support handling or an applicable legal requirement. The Privacy Policy does not promise one fixed period for every record because retention depends on the purpose and the type of data.

You can send a deletion request through our support route and identify the account detail concerned. We will assess the request under applicable requirements. Data may remain when needed for security, payment dispute handling or legal duties, and access depends on local law.