Reference

Privacy Policy for Your herobola Account

Our Privacy Policy shows how herobola handles the details connected with your account, from phone verification to DANA, OVO, GoPay and QRIS records.

Clear data purposesWallet record controlsDirect privacy requests
herobola Privacy Policy for Your herobola Account
PRIVACY CONTACT PATH

Where To Send A Privacy Request

A clear contact path helps you correct an account detail without explaining the same issue twice.

Account privacy request Use the account support desk to ask what personal data is linked to your profile, why it is used or which detail needs correction. We may verify your phone before discussing account-specific records.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount shown in your account and the wallet status displayed. Do not send a wallet PIN or full password.
Access and deletion request Ask support to provide, amend or remove eligible account data. We will explain any record we must retain for security, payment reconciliation or a legal request where local law permits access.
DATA HANDLING DETAILS

Six Practical Privacy Controls

Privacy is handled through ordinary account steps rather than hidden settings. We separate login checks from wallet references, limit internal access to records needed for support or security, and use device signals…

Account details

We use your chosen account details and verified phone number to create the profile, confirm sign-in requests and respond to account messages. Keeping your phone current helps us match a privacy request to the right record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may include a reference, status and timestamp. We use those fields to reconcile the account record, while wallet PINs remain outside our request process.

Cookies and browser use

Session cookies can keep you signed in during a mobile browser visit, while measurement cookies help us understand page errors. Your browser settings let you delete or restrict cookies, though some account functions may then need another sign-in.

Device security

We may record browser, device and sign-in signals to spot repeated failed access or an unfamiliar session. If the pattern looks unusual, we can pause an account action and ask for phone verification before continuing.

Retention periods

We keep personal data only for the period needed for account operation, security checks, payment reconciliation or a legal obligation. When a record no longer serves one of those purposes, our process is to remove or separate it.

Changes and requests

You can ask us to correct inaccurate details, explain a use, provide eligible records or consider deletion. Send the request through support with your account phone number; we will confirm what action is possible and why.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you may have before using herobola. Each response describes the practical step we take and the detail you should include when asking for help. Access remains subject to local requirements, and where local law permits access we will explain the available route.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account. It also explains purposes, retention, security steps and how to request access or correction.

We use your phone number to create and protect the account, confirm a sign-in step and match an account-specific privacy request. If you ask us to disclose, amend or remove data, phone verification may be required before we act.

No. Our payment records can show a provider reference, status, timestamp and the account connection, but we do not ask you to send a DANA, OVO, GoPay or QRIS wallet PIN. Never place a wallet PIN in a support message.

Send an account privacy request through the support desk while signed in, or explain that you are locked out. Include the phone number linked to the account and the records you want. We will verify identity and describe any limits on disclosure.

Yes, you can ask us to correct an inaccurate detail or consider removal of eligible data. Some payment, security or legal records may need to remain for a defined purpose. We will state what can change and the reason for any exception.

Session cookies can keep your sign-in active while you move between the lobby and account pages on a mobile browser. Browser controls can delete or restrict them. After that choice, you may need to sign in again or see limited account functions.

Yes. Access, eligibility and some data requests depend on local law. Where local law permits access, we will provide the relevant request path and explain verification, timing or retention limits that apply to your account and payment records.