Reference

666v Privacy Policy for Your Account

The 666v Privacy Policy explains how we handle your account details, device signals and wallet records when you use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
666v 666v Privacy Policy for Your Account
POLICY HELP

Get Privacy Help Near Your Account Path

A clear support route helps when you want to understand a data field, check a wallet record or ask for an account change. Open the support path from your account area, or use the help link beside the cashier flow when a DANA, OVO, GoPay or QRIS reference needs checking. We will ask for enough account detail to locate the request without asking for your wallet password.

Team online

Account access

Use the account support path if you cannot reach the Privacy Policy or need help confirming which contact detail is attached to your account. We may request an account identifier before discussing private records.

Wallet records

If a DANA, OVO, GoPay or QRIS receipt does not match your account history, send the reference through the cashier support route. We use the reference to check status without requesting your wallet login.

Change requests

Ask our support team to explain correction, access or deletion options through the account help path. We first verify the requester, then record the request and reply using the available account contact.

DATA PRACTICES

How 666v Handles Your Privacy Choices

Our privacy work follows the points you can check in your account journey: what we collect, why we use it, how long records are kept and how you…

Account details

We use your account contact details and verification status to provide access, send account messages and identify the correct record…

Device signals

Browser type, device signals and login time can help us spot unusual access and protect your account.

Cookie controls

Cookies can remember session settings and help us understand whether a page loads correctly.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references used to match a payment status with…

Retention approach

We keep account, security and transaction records for as long as needed for the stated purpose, account support and lawful…

Your requests

You can ask what personal data we hold, request a correction or ask about deletion where applicable.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers cover the searches we expect you to make before opening an account or checking a wallet record. We keep the wording practical, with direct references to account access, mobile devices and Indonesian payment rails.

It covers account details, verification records, login and device signals, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

No. Our Privacy Policy concerns transaction references and status details needed to match an account action. We do not ask for or need your DANA, OVO or GoPay wallet password.

Device type, browser details and login time help us identify unusual account access and investigate a failed session. These signals support security checks on both mobile and desktop without reading unrelated device files.

Use the support path inside your account and state that you want a Privacy Policy data request. We may verify your identity before locating the record and explaining what can be provided under local law.

Yes. Send a correction request through the account help path and identify the field that needs changing. We verify the request, update eligible records and explain any restriction that depends on local law.

We retain payment references for the period needed for account support, status checks, security work and lawful record duties. A receipt may therefore remain after a wallet action is complete, even if the session ends.

Open the Privacy Policy link from the account area before access where local law permits. If the page does not load on your phone, use the support path beside the account or cashier section.