Reference

hero369 Privacy Policy for Your Account

hero369 Privacy Policy explains how we collect, use and protect the account details connected with your lobby access, device, DANA, OVO, GoPay and QRIS records.

Account recordsWallet activityCookie choicesRequest support
hero369 hero369 Privacy Policy for Your Account
DIRECT HELP PATH

Where Privacy Questions Go First

A clear contact path helps you resolve a privacy concern without repeating your account story. Use the support route attached to your account and include the email or phone detail connected with hero369, plus the subject of your request. We may ask for an account step to confirm that the request comes from you before discussing records.

Team online

Account support

Open the support path after signing in and state whether your request concerns access, correction, deletion or a question about the Privacy Policy. We will use your account details to locate the right record.

Payment record check

For a DANA, OVO, GoPay or QRIS privacy query, include the transaction reference and date rather than a wallet password. This lets us check the payment record while limiting unnecessary disclosure.

Identity confirmation

We may ask you to confirm your phone or sign-in detail before releasing account data. That extra account step helps keep a privacy response away from another person using your device.

HANDLING PRACTICES

Six Practical Rules Behind Our Policy

Privacy work is easiest to understand when each action has a defined reason. We separate account access records from payment references, limit internal handling to the task being completed and use security…

Purpose-based collection

We collect account details, phone verification results and sign-in events to provide access, protect the account and answer requests. We do not ask for a wallet password to match a DANA or QRIS receipt.

Cookie controls

Cookies and similar device signals can remember session choices, support security checks and show whether a page loads correctly. You can clear browser data, although a fresh sign-in may then be required.

Mobile device signals

When you use a phone to reach the lobby, we may record device type, browser version, language and security events. These signals help identify unusual access without reading private files stored on your device.

Account protection

Phone confirmation, sign-in records and unusual-session checks help us protect your account. If a request involves changing personal details, we may verify the existing account path before making that change.

Retention decisions

We keep records only for the period needed for the stated purpose, account security, dispute handling or applicable legal duties. When a record is no longer needed, our process moves it toward deletion or anonymisation.

Policy changes

If our Privacy Policy changes in a way that affects your account data, we will place the revised wording on this page and identify the effective date. You can contact support before continuing with an account request.

Privacy Policy Questions About hero369

These answers address the questions we expect you to ask before opening or continuing an account. Each answer stays within the Privacy Policy scope, including account records, cookies, payment references, security checks, retention and requests made from Indonesia.

The hero369 Privacy Policy covers account details, phone verification, device signals, cookies, sign-in events, support messages and payment references linked with DANA, OVO, GoPay, QRIS or bank transfer.

We may collect the details you submit for an account, your phone confirmation result, sign-in history, device and browser signals, support messages and records needed to match an account transaction.

The Privacy Policy treats DANA, OVO, GoPay and QRIS references as transaction records used to match receipts and resolve account questions. We do not request your wallet password for that check.

Cookies or similar signals may keep a session working, support security checks and record technical loading results. Clearing them can remove saved choices and may require you to sign in again.

Use the support path connected with your account and ask for data access under the Privacy Policy. Include your account email or phone detail; we may confirm your identity before responding.

Yes, you can contact us through the account support path to request correction or removal. We may retain records needed for security, disputes or legal duties, and we will explain the relevant reason.

Yes. Account access and the handling of some requests depends on local law. We apply the rules relevant to your region and will explain any restriction when you contact us about the policy.