Reference

Open api66 Privacy Policy Before Account Access

Your account details, wallet records and mobile access choices are explained clearly in the api66 Privacy Policy.

Account dataWallet recordsCookie choicesAccess requests

Check Wallet Records Under Our Privacy Policy

api66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes how we collect, use, store and disclose details connected with your api66 account. That can include your phone number, verification status, login events, device details, support correspondence and transaction references. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual

1
account, we may retain payment status and reference data needed to match your account activity, investigate a stalled receipt or confirm a wallet action. We do not ask for a wallet password through ordinary support contact. Access and eligibility depends on local law, and the policy
2
applies to account activity where local law permits. We may update this page when our data practices change, with the effective date shown on the policy page. Please read the current wording before opening an account or sending a request.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP DIRECTLY

Contact Us About Privacy Policy Requests

A clear contact path helps you ask about the Privacy Policy without mixing a data request with a wallet-status question. We route account access, privacy questions and receipt concerns through the support contact shown in your account area, so include the phone number linked to your account and the relevant date. For people in Jakarta or elsewhere in Indonesia, the same request path applies where local law permits.

Team online

Account privacy

Ask which account details we hold, why they are used and how phone verification connects to access. Include your registered phone number so we can locate the right account record.

Wallet records

If a DANA, OVO, GoPay or QRIS receipt needs clarification, send its reference and date through the account support path. We use those details to trace status without requesting your wallet password.

Policy changes

Use the same contact route to ask about a revised Privacy Policy, a data correction or an access request. We may ask for account verification before discussing personal records.

DATA HANDLING PRACTICE

Protect Your Data Across api66 Access

We keep the Privacy Policy practical by linking each data category to an account action you recognise.

Account details

We may collect your phone number, account identifiers and verification result when you open an account.

Cookies and devices

Cookies and mobile-browser signals can remember session choices, detect unusual login behaviour and keep the account path working.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount status and timestamp.

Account protection

Phone verification before account access helps us distinguish your login from an unfamiliar attempt.

Retention period

We retain different records for different operational and legal needs rather than keeping every detail forever.

Your requests

You can contact us to ask for access, correction or clarification about personal data linked to your account.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers cover the questions we expect you to ask before creating an account. They focus on account records, mobile access, local wallets, cookies and request handling rather than general lobby features. If your situation is not covered, contact us through the account support path and refer to the current policy wording.

It covers account details, phone verification, login and device events, cookies, support messages, payment references and retention. It also explains how we use, protect, disclose and respond to requests about those records.

Yes. The Privacy Policy explains that DANA and QRIS activity may produce payment status, reference and timestamp records. Similar handling can apply to OVO, GoPay, bank transfer and virtual account payments.

Phone verification helps connect an account access attempt with the correct account record and helps us investigate unusual login activity. We may use the verification result when handling a personal-data request.

You can contact us through the account support route and ask for a correction. Include the phone number linked to your account and explain the field that appears wrong; we may verify your identity first.

Cookies can retain session choices and support mobile-browser access checks. You can adjust cookie settings in your browser, but refusing some cookies may change login behaviour or prevent a requested account function.

Retention depends on the record and the operational or legal reason for keeping it. The Privacy Policy sets out the relevant factors, and you can ask us to clarify a particular payment reference.

Yes, you can request access to personal data linked to your account through the stated contact path. We may require account verification before releasing details, and handling depends on local law.

Open api66 Privacy Policy Before Account Access

Contact Us About Privacy Policy Requests

Account privacy

Wallet records

Policy changes

Protect Your Data Across api66 Access

Account details

Cookies and devices

Payment references

Account protection

Retention period

Your requests

Find Privacy Policy Answers Before Opening

01 What does the api66 Privacy Policy cover?

02 Does the Privacy Policy mention DANA and QRIS data?

03 Why does api66 need phone verification?

04 Can I ask api66 to correct my account data?

05 How do cookies affect Privacy Policy choices?

06 How long does api66 keep payment records?

07 Can I request my personal data from api66?

Related Pages