Reference

indoheboh Privacy Policy For Your Account

indoheboh Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the mobile lobby and account settings.

Clear collection purposesDANA and QRIS recordsPhone verification contextMobile account controls
indoheboh indoheboh Privacy Policy For Your Account
CONTACT THE TEAM

Ask About Privacy Before You Open

A clear contact route matters when you want to understand a record rather than simply remove it. From your account support area, tell us whether your question concerns phone verification, a DANA receipt, a QRIS status, a cookie choice or a device login. Include the email or phone detail attached to your account, but never send a wallet password or one-time code. We use the supplied details to locate the relevant record and answer the privacy request without asking you to repeat unrelated account data.

Team online

Account privacy request

Use the account support path to ask what personal details we hold, why a phone check appears, or which record relates to your login. We may ask you to confirm the account detail already on file before discussing private information.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date shown in your account. This lets us trace the payment record without requesting your wallet password, card secret, or one-time verification code.

Correction or deletion

Tell us which field needs correction or which account record you want reviewed. We first check identity and any open transaction or security obligation, then explain what can be changed or retained under this Privacy Policy.

DATA HANDLING DETAILS

What We Do With Your Account Data

Privacy controls work best when they match real account steps. We separate login signals from payment references, restrict access to staff who need a record for support or security, and retain records…

Collection

We collect details you enter for an account, the phone verification result, login timestamps, device and session signals, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookies

Cookies and local storage help keep your session active, remember selected settings and support security checks. You can manage browser storage, but removing it may sign you out or require phone verification again.

Account security

We use phone verification and sign-in signals to reduce unauthorised access. Keep your password and one-time code private; our support team does not need either item to discuss a general Privacy Policy question.

Payment matching

A payment reference helps us match a wallet or bank transfer to the correct account. We record the status needed for reconciliation, including QRIS or virtual account details, rather than asking for your wallet login credentials.

Retention

We keep personal data only as long as needed for account operation, fraud prevention, payment reconciliation, dispute handling or a legal obligation. When a period ends, records are deleted, anonymised or securely restricted.

Your request

You can ask for access, correction, deletion or clarification through the account support path. Include the affected account field and a safe contact detail so we can verify the request and explain any necessary retention.

Privacy Policy Answers For Indonesian Accounts

These answers address the privacy searches we hear most often before account access. They cover payment references, mobile sessions, cookies, correction requests and the checks we may need before sharing private account details. If your situation is different, use the account support path and describe the exact record involved.

It covers account details, phone verification, login and device signals, cookies, payment references and support requests. The Privacy Policy also explains why we use each category, how long records may remain, and how you can request access or correction.

No. We use the payment reference, amount status and related account detail needed to match DANA, OVO or GoPay activity. Your wallet password and one-time code should remain private and should never be sent through support.

A QRIS reference lets us connect a payment status to the account that initiated it. We retain that operational record for reconciliation and support, while avoiding requests for your QRIS access credentials or unrelated wallet details.

Cookies and local storage help preserve your session, selected settings and security checks on a phone or browser. Clearing them may sign you out, remove preferences or trigger phone verification when you return to the account.

Yes. Send a correction request through the account support path and identify the field that is wrong, such as a phone number or contact detail. We verify the request against your account before changing the record.

We keep payment records for the period needed for account operation, reconciliation, disputes, security and applicable legal duties. After that period, we delete, anonymise or restrict the record according to our retention process.

You can ask us to review deletion of personal data through account support. We check identity and whether a record must remain for an open transaction, security matter or legal duty, then explain the result and any remaining data.