Reference

hgo login Privacy Policy for Your Account

Our Privacy Policy explains how hgo login handles the details you provide when opening an account, confirming your phone and entering the lobby.

Account choicesWallet recordsCookie controlsPhone verification
hgo login hgo login Privacy Policy for Your Account
REQUEST PATHS

Get Help With Privacy Requests

A clear contact path helps when you want a copy, correction or explanation of personal data.

Account access If you cannot reach your account after phone verification, contact support through the page route and state whether the issue concerns login records, device data or a privacy request. We will ask only for details needed to locate your account.
Wallet status For a DANA, OVO, GoPay or QRIS record, include the transaction reference and approximate date rather than sending a wallet password. This lets us check the stored payment event while limiting the personal details shared in your message.
Policy changes To request a correction, deletion where available or a copy of your data, use the privacy contact route linked here. Tell us which account detail needs attention, and we will explain any identity check or legal reason for keeping it.
PROTECTION DETAILS

What We Protect Across Your Account

Our handling process follows the account actions you can recognise: registration, phone confirmation, wallet matching, device sign-in and support contact.

Account details

We may store your name or account identifier, phone number, sign-in events and verification status to keep your account connected to the correct person. If a detail changes, use the policy request route so we can check the request against the account record.

Payment references

A cashier action can create a reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use that reference to reconcile status and answer support questions, while avoiding collection of your wallet password or full banking credentials.

Cookies and sessions

Cookies and session data can remember a sign-in state, security preference or consent choice on your browser. Clearing them may require you to confirm your phone again, and it can remove saved preferences without deleting the account records held for legal or security reasons.

Device protection

We may record browser type, device signals, approximate session timing and failed access events to identify unusual account activity. Whether you open Live Roulette Prestige on mobile or view Gaple VIP Table on desktop, these signals support account protection rather than title selection.

Retention decisions

We keep records for as long as they support the account, payment reconciliation, security investigation or a legal requirement. When a record is no longer needed for those purposes, our process is to remove it, aggregate it or restrict access where appropriate.

Your request

You can ask what personal data we hold, request a correction, ask about deletion where available or object to a particular use. Send the request through the policy contact route, and include enough account detail for us to verify ownership safely.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the account steps most likely to raise questions in Indonesia: phone confirmation, wallet references, cookies, device access and requests for changes. If your situation is not covered, use the contact path above and describe the record or action you want us to check.

The hgo login Privacy Policy covers account details, phone verification, wallet and bank references, cookies, device signals, support messages, retention and your available data requests. It also explains why we process records when you move from login to the lobby where local law permits.

No. Our Privacy Policy addresses transaction references and status information for DANA, OVO, GoPay and QRIS, not your wallet password. Bank transfer and virtual account records are used to match an account action, so do not send passwords in a support or policy request.

Phone verification helps us connect a request or sign-in event to the correct account and identify unusual access. Under this Privacy Policy, the verification status can be retained for security and account records, while a correction request can be sent through the policy contact route.

Yes, you can ask for a copy of eligible personal data held for your account. Send the request through the Privacy Policy contact path with your account phone number and the records you want, such as login events, cookie choices or payment references.

Use the policy request route and identify the account detail that is incorrect or the record you want removed. We may verify account ownership first. Deletion can depend on security, payment reconciliation or legal retention needs, so our reply will explain the applicable reason.

Yes. The Privacy Policy covers browser, session and device signals used when you access the account on mobile or desktop. Clearing cookies may end a saved session or trigger phone confirmation again, but it does not automatically erase records that must be retained.

Use the support route linked to this Privacy Policy and describe your request without sending a wallet password. Include your account phone number and, when relevant, a DANA, OVO, GoPay, QRIS or bank reference so we can locate the correct record.