Reference

hino99 Privacy Policy For Your Account

Live Baccarat, Rocket Crash and QRIS access each create records that our Privacy Policy explains in plain English.

Account recordsWallet referencesMobile browser dataCookie choices
hino99 hino99 Privacy Policy For Your Account
REQUEST PATHS

Get Help With Privacy Requests

A clear support path helps when a Privacy Policy question concerns your login record, wallet reference or device activity. Start from your account support route and describe the request without sending a wallet password or full payment credentials. We use the account step to match your request safely, then explain what can be accessed, corrected or removed under applicable rules. This same path is available when a QRIS receipt or GoPay status needs privacy clarification.

Team online

Account request

Use the support route connected to your hino99 account and identify the phone number used for verification. We can then locate the relevant Privacy Policy record without asking you to disclose a wallet password.

Wallet record

For DANA, OVO, GoPay or QRIS questions, share the payment reference and date rather than private wallet credentials. We use those limited details to check the account record linked to your request.

Correction request

Tell us which account or device detail needs changing and why. Our support team will explain the next account check, any legal reason for keeping the record, and the outcome of your request.

DATA PRACTICES

Six Ways We Handle Your Data

Privacy is handled through practical account steps rather than vague promises. We separate identity details from payment references where our records allow, limit staff access to work needs, and use account checks…

Account fields

We may hold your account name, phone number, verification result and support messages. These fields help us recognise your account, answer a Privacy Policy request and prevent another person from changing your record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a wallet event with your account. We use the reference and status, not a wallet password, for matching.

Cookie choices

Cookies can keep a session available and help us identify unusual access across a mobile browser. Your browser settings can remove or restrict cookies, although some account steps may then need repeating.

Device security

We may record device type, browser signals, login time and security events to protect account access. If a new mobile browser behaves unusually, we may ask for phone verification before proceeding.

Record retention

We keep account, payment-reference and support records only for as long as needed for the stated purpose, account security or applicable obligations. When retention is no longer needed, we remove or restrict the record.

Policy changes

If you request access, correction or deletion, use the account support path and describe the specific record. We will explain the identity check, available action and any reason a record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain what hino99 may record, how to ask for a change and what happens when access depends on local law. For a case-specific answer, use the support route linked to your account.

The hino99 Privacy Policy covers account details, phone verification, payment references, browser and device signals, cookies, support messages, security events and the reasons we retain or remove those records.

You may provide a name, phone number and verification result when opening an account. We can also receive support messages and account activity needed to handle access, security and your policy request.

Do not send a DANA, OVO, GoPay or QRIS password through support. We use payment references, dates and status details to match an account record, while wallet credentials remain outside that request path.

Use the support route connected to your account, identify the phone number used for verification and ask for a data access request. We may confirm account ownership before explaining which records can be supplied.

Yes. Describe the specific account detail that is wrong and provide the corrected version through support. We will check the request, update the record where appropriate and explain any reason a change cannot be made.

The Privacy Policy explains that we may record browser type, device signals, session activity and security events. These records help protect login access, and cookie restrictions may require you to repeat an account step.

Access or eligibility depends on local law. Where local law permits, you can ask about your records, correction or removal through support, and we will explain any legal reason for retaining specific data.