Reference

hero123 Privacy Policy For Your Account

Our Privacy Policy explains how hero123 handles the details connected with your account, including phone verification, DANA and QRIS payment records, device access and support requests.

Account dataPayment recordsCookie choicesContact path
hero123 hero123 Privacy Policy For Your Account
CONTACT THE POLICY TEAM

Get Privacy Policy Help Beside Account Support

Questions about our Privacy Policy should be handled through the account help path, where we can match your request to the right account record. Include the phone number linked to your account and describe whether your question concerns a cookie, payment record, device sign-in or data change. We will use the details needed to locate the request and avoid asking you to send unnecessary payment credentials.

Team online

Account help path

Use the account help route when you need to ask about stored profile details, phone verification or a correction under our Privacy Policy. We can check the request against the account step without asking for your DANA, OVO or GoPay PIN.

Cashier status question

If your Privacy Policy question concerns a QRIS, bank transfer or virtual account record, mention the transaction reference and date. Our support path can separate a payment-status question from a request to change personal data.

Device access concern

Tell us when an unfamiliar device appears during sign-in, and describe the phone or browser involved. We use that context to investigate account access while keeping the Privacy Policy request tied to your own profile.

HOW WE HANDLE DATA

Privacy Choices Across Your hero123 Account

The Privacy Policy is practical at each account stage: we explain what is collected at phone verification, what appears in payment records and how a support request is handled.

Phone verification

When you open an account, we use the phone detail you submit to support sign-in and account matching. Our Privacy Policy connects that step to access control, so a request about the number can be checked without exposing another account.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can show a reference, amount and status needed for reconciliation. We use those fields to resolve a cashier question, not to request your wallet password or PIN.

Cookies

Cookies and related browser signals help remember an account session and identify when a new device needs an additional check. The Privacy Policy explains their purpose, while your browser settings provide a separate way to manage them.

Account security

A clear phone verification step helps us connect sign-in activity with the correct account. If access looks unusual, we may ask you to confirm account details before discussing records, which reduces the chance of disclosure to someone else.

Retention timing

We keep personal and payment records only for the account, security and support purposes described in the Privacy Policy. When a record is no longer needed for those purposes, we remove it or retain it in a form that does not identify you.

Data requests

To request access, correction or an eligible deletion, contact the account help path with your linked phone number and the request type. We may verify ownership first, then explain the result and any local-law reason a record must remain.

Privacy Policy Questions About hero123 Access

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. They explain the practical path for account records, cookies, payment references, device checks and data requests. If your situation is not listed, use the account help path and include only the details needed to identify your request.

The hero123 Privacy Policy covers account creation, phone verification, sign-in activity, cookies, device signals, payment references and support requests. It also explains retention, security checks and how to ask for access, correction or an eligible deletion of your personal data.

DANA and QRIS records can contain a payment reference, date, amount and status used to match a cashier event with your account. Our Privacy Policy explains that we use these details for reconciliation and support, without asking for your wallet PIN.

Use the account help path and state that you are requesting access under the Privacy Policy. Include the phone number linked to your account and the data category you want checked. We may verify ownership before sharing records connected with your profile.

Yes, you can ask us to correct eligible account details through the support path. Identify the field that is wrong, such as a phone detail, and explain the requested change. We may ask for an account check before applying it.

Cookies can keep a sign-in session working and help us notice when a new browser or device needs an extra check. The Privacy Policy explains their purpose. You can also manage cookies through your browser, although some account functions may then behave differently.

Contact the account help path promptly and describe the device, browser and approximate sign-in time. We may verify account ownership before discussing activity. Our Privacy Policy permits security checks designed to reduce disclosure of your account data to another person.

Access depends on local law, so the result of a data request can vary by the applicable rules and the record involved. Contact us through account help with your request type, and we will explain whether access, correction or removal is available.