Reference

Privacy Policy for Your indrabet Account

indrabet keeps this Privacy Policy focused on the data created when you open an account, verify your phone, use DANA or QRIS, and move through the lobby on…

Account dataWallet recordsCookie choicesPrivacy requests
indrabet Privacy Policy for Your indrabet Account
PRIVACY CONTACTS

Get Help With an indrabet Privacy Request

A clear contact route helps you act on this Privacy Policy without guessing which team to reach.

Access request Ask us for the personal data connected with your account through the support contact displayed after login. We may verify the account step first, so a request is linked to the right person rather than sent to an unknown address.
Correction request If your phone detail or account record is wrong, tell us which field needs changing and why. We compare the request with the verified account details before applying a correction, especially when the record relates to DANA, OVO or another wallet.
Wallet query For a QRIS, GoPay or bank transfer record that does not match your account, contact support from the account path and include the transaction reference. We use that reference to check status without asking for your wallet password or private wallet login.
DATA CONTROL

What We Do With Your Account Data

This Privacy Policy is practical: each data category has a reason connected to account access, security, payment matching or legal duties.

Account details

We use your phone number and account credentials to create the sign-in path, confirm account ownership and respond to privacy requests. If you change a detail, we may ask for another account check before updating the record.

Device signals

When you move from login to the lobby on a phone, tablet or desktop browser, limited device and connection signals can help detect unusual access. These signals support account protection and are not a request for your private device files.

Cookie choices

Cookies can remember a session and selected settings so the privacy controls behave consistently on your browser. You can manage cookies through browser controls, although blocking some types may require you to repeat the login or account step.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event with the correct account. We keep the transaction detail needed for status checks and reconciliation, not your wallet password.

Retention period

We retain account, security and payment records for the period needed to provide access, resolve disputes, prevent misuse or meet legal duties. When a record is no longer needed for those purposes, our handling process addresses its removal or anonymisation.

Your request

You can ask for a copy, correction, restriction or removal of data where the request is available under applicable law. Send it through the account support contact, describe the action clearly, and we will explain any identity check or lawful reason for keeping a record.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. We keep the wording tied to actual account actions: phone verification, browser access, payment references, support requests and the local-law condition. If your question is not covered, use the contact path inside your account and describe the data issue in plain terms.

The Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains why we use those records, how retention works and how you can request access or changes.

We use your phone number to create the account sign-in path, confirm ownership before account access and connect privacy requests with the correct record. Phone verification also helps us investigate unusual login activity. We do not ask you to provide a wallet password through our support contact.

Yes. The Privacy Policy covers the transaction reference and status details needed to match a DANA or QRIS event with your account. The relevant payment provider may have separate terms for its own processing. We keep enough data to check reconciliation, but not your private wallet login.

Use the support contact shown inside your account and ask for a copy of the personal data connected with your phone number. We may verify account ownership before responding. State the request clearly, avoid sending passwords or one-time codes, and expect handling to follow applicable local requirements.

You can request a correction or removal through the account support path. Tell us which record is inaccurate or which data you want addressed. Some account, security or payment records may need to remain for legal duties, dispute handling or fraud prevention, and we will explain that reason.

We retain data for the period needed to provide account access, protect the sign-in path, reconcile wallet events, resolve disputes or meet legal duties. The period depends on the type of record and its purpose. Once retention is no longer needed, the record is removed or anonymised through our handling process.

Yes. The Privacy Policy applies when you sign in through a mobile browser, tablet or desktop. Limited device signals and cookies may support session continuity and account security. You can adjust browser cookie controls, while access to indrabet services remains where local law permits and subject to account checks.