Reference

hgo09 Privacy Policy For Your Account

The hgo09 Privacy Policy explains how we collect, use and protect data connected with your account, device access and wallet activity.

Clear data purposesDevice and cookie choicesWallet activity recordsRequest a policy change
hgo09 hgo09 Privacy Policy For Your Account
HELP WITH PRIVACY

Browse Support Paths For Policy Requests

A privacy question should not be mixed with a game or wallet query, so we give you a direct route through account support. Tell us which account step concerns you, such as phone verification, a QRIS receipt or a device sign-in, and we can locate the relevant policy purpose. We may ask for account details to confirm that the request comes from you. In Yogyakarta and elsewhere in Indonesia, the same support route applies when local law permits access.

Team online

Account request

Use the account support route when you want to ask what data we hold, why a phone verification record appears, or how to request a correction. Include the email or phone number attached to your account, but never send your password or wallet PIN.

Wallet record

If a DANA, OVO, GoPay or QRIS event looks unfamiliar, send the date, amount reference shown to you and payment route through support. We check the account event against our records and explain what data was used for the status check.

Device access

For a sign-in or cookie concern, tell us whether you used a phone or desktop and which browser session needs attention. We can help you end an access session, refresh account verification and explain the device data connected with that request.

DATA HANDLING

Explore How We Manage Privacy

We handle Privacy Policy requests as account matters, not as general lobby questions.

Collected data

We may collect your account contact details, phone verification result, sign-in timestamps, device signals, cookie choices and payment references.

Cookie settings

Cookies can remember a selected language, support a secure session and show whether your browser has completed an account step.

Account security

Phone verification helps us distinguish your account from an unfamiliar sign-in.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a payment status with the correct account event.

Retention requests

You may ask how long a particular account, device or payment record is kept and whether a deletion request can…

Policy changes

Contact support when you want to correct contact data, ask for a copy of applicable account data or object to…

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the account questions you are most likely to have before opening access. We explain the practical link between your contact data, device session and local wallet reference, while keeping the request path clear. If your situation is different, contact support with the account step and payment route involved. Any access or eligibility decision depends on local law.

The hgo09 Privacy Policy covers account contact data, phone verification, sign-in and device records, cookies, payment references and support requests. It explains why we use each category, how we protect access, how long records may remain, and how you can ask for correction, access or deletion.

We use phone verification to confirm that an account request belongs to you and to reduce mistaken or unauthorised access. The result is connected with the account security record. We do not need your wallet PIN, and support will not ask you to disclose it.

Yes. The Privacy Policy covers the payment reference and status connected with DANA, OVO, GoPay and QRIS activity. We use those records to match an account event, check a receipt question and explain a pending status. We do not treat your wallet PIN as support data.

You can contact account support and request a copy or explanation of the data linked to your account. Include your account email or phone number so we can verify ownership. We may limit or delay a response where another person's privacy, security needs or local law requires it.

Send a clear request through the account support path and name the field or record you want changed, such as an outdated phone number or device entry. We verify the request, check whether retention is required for security or payment reconciliation, then explain what we can change.

Cookies can keep a secure session active and remember a device choice, so clearing them may send you through phone verification again. You can manage cookies in your browser. If a cookie appears to cause an account issue, tell support whether you used a phone or desktop.

Use the account support route and state that your question concerns the Privacy Policy. Add the relevant account step, such as sign-in, phone verification, DANA status or QRIS receipt. We confirm ownership before discussing account data, and access remains where local law permits.