Reference

Indo Payment Guide Privacy Policy, Clearly Explained

Indo Payment Guide Privacy Policy tells you what account, device and wallet details we use when you open an account or choose DANA, OVO, GoPay or QRIS.

Account clarityWallet detailMobile cookiesLocal-law access
Indo Payment Guide Indo Payment Guide Privacy Policy, Clearly Explained
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route helps when your account record or wallet status needs checking. Use our support contact path from the policy page and include the phone number or email connected to your account, plus the relevant date and payment route. We use those details to locate the right record without asking you to send a full password or wallet PIN.

Team online

Policy contact path

Ask about a Privacy Policy request through our support contact route, stating whether you need access, correction, deletion or an explanation of a specific account record.

Wallet record help

If a DANA, OVO, GoPay or QRIS receipt is attached to the wrong account event, share the reference details and we will check the matching record.

Login detail check

When phone verification or a device login looks unfamiliar, contact us through the same route and describe the device, date and account step involved.

DATA PRACTICE

Six Data Practices We Keep Visible

Our privacy approach follows the actual account journey rather than abstract promises. We separate details needed to identify your account from technical records used to keep a session working, and we consider…

Account details

We use your submitted account details and verified phone step to identify the correct account, protect access and respond to a request about your Privacy Policy rights.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain reference and status details needed to match receipts without requesting your wallet PIN.

Cookies and devices

Cookies can remember a session and your privacy choice. Device and browser records help us investigate an unfamiliar login, whether you use a phone or desktop.

Account protection

Phone verification, login records and unusual-access checks help protect your account. We will not ask you to disclose a password or wallet PIN through support.

Retention period

We keep records only for the period needed for account operation, payment matching, security checks or a lawful request. We assess older records for removal when that purpose ends.

Changes and removal

You can ask us to correct, access or remove eligible details through the policy contact path. We may need account verification before acting on the request.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account from Indonesia. They explain wallet records, device use, cookies, retention and the steps for requesting a copy or change, while access remains subject to local law.

It covers account details, phone verification, wallet and payment references, device records, cookies, support messages and retention practices connected with your use where local law permits.

We may record the payment route, reference and status needed to match an account event. We do not need your DANA or QRIS wallet PIN for that check.

Phone verification helps connect you to the correct account and supports access checks. It also gives us a safer way to handle requests about account details or unusual login activity.

Cookies can keep a session active and remember your privacy choice. Browser and device records may also help us investigate login activity when you open a lobby page on mobile.

Yes. Use the policy contact path, identify the account with its connected phone number or email, and state whether you want access, correction, deletion or clarification.

We retain records for account operation, payment matching, security checks or a lawful need, then assess them for removal when the relevant purpose has ended.

Yes. Privacy rights, account access and eligibility can vary by jurisdiction. Our handling follows applicable requirements, and access depends on local law or where local law permits.