Reference

api 66 Privacy Policy For Your Account

api 66 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet contextDevice controlsPolicy requests
api 66 api 66 Privacy Policy For Your Account
REACH OUR TEAM

Get Privacy Help Beside Account Support

A clear contact route helps you question a record, correct a detail or ask how your account data is used.

Account contact Use the account support route when your request concerns registration details, phone verification or…
Wallet question For a DANA, OVO, GoPay or QRIS privacy question, provide the payment reference and…
Policy request Ask us to explain, correct or remove eligible account data through the policy contact…
DATA HANDLING

What We Do With Your Account Data

Privacy controls matter most during ordinary account actions, so we describe them in practical terms.

Registration records

When you open an account, we collect the details needed to create and maintain that account, including your contact information…

Device signals

A sign-in from a mobile browser or desktop can create technical signals such as browser type, device details and connection…

Cookie choices

Cookies can remember session settings and help us understand whether a page path works after you move from login to…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction can produce a reference, amount and status record.

Account protection

Phone verification, sign-in records and device checks help us distinguish your account activity from an unfamiliar attempt.

Retention requests

We retain records for as long as needed for account operation, support history, payment reconciliation and legal duties.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an api 66 account. They cover registration, device access, local wallets, cookies, retention and requests for changes. If your situation is not listed, use the account support path and describe the record or payment reference involved.

The api 66 Privacy Policy covers data linked to your account, phone verification, sign-in activity, device signals, cookies, support requests and payment references. It applies when you access the website, browse the lobby or use DANA, OVO, GoPay, QRIS, bank transfer or virtual account paths.

We use phone verification to connect registration details to the correct account and reduce confusion during sign-in or account support. The verification result can also help us investigate an unfamiliar access attempt. Eligibility and access depend on local law, and we handle the record under this Privacy Policy.

Yes. The Privacy Policy covers technical details created when you sign in through a mobile browser or desktop, such as browser type, device signals and connection data. We use them for session operation and account protection, not to read private files, photos or messages on your device.

We may keep a payment reference, amount, timestamp and status for a DANA or QRIS request so we can match it to your account and check a receipt. We do not need your wallet password. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

You can request a correction through the account support path by naming the detail that appears wrong and giving the contact method linked to your account. We may verify account control before changing it, then check whether payment or legal records require the original entry to remain.

We keep account, support and payment records for the period needed to operate the account, reconcile a transaction, investigate a security issue or meet a legal duty. If you ask about removal, we will check the specific record and explain what can be deleted or retained.

Send your Privacy Policy question through the account support route and describe the record involved, such as phone verification, a cookie setting or a QRIS receipt. Do not send a wallet password. We will verify the request where needed and explain the next available step.