Reference

hino99 Privacy Policy For Your Account

Our hino99 Privacy Policy explains what account, device and payment details we collect when you open an account, sign in and use the lobby.

Account dataWallet recordsCookie choicesAccess requests
hino99 hino99 Privacy Policy For Your Account
POLICY HELP DESK

Where To Ask About Your Privacy

A clear contact path matters when a Privacy Policy question affects your account or wallet status. Start from the support route linked to your account area and describe the request in plain English, including the email or phone detail attached to your account. We use that account step to reduce mistaken disclosures. If you are in Makassar and a QRIS receipt does not match the account record, include the transaction reference rather than sending a full wallet password or security code.

Team online

Access request

Ask us which account details, sign-in events and device records are associated with your account. We may ask you to confirm the account step before releasing personal data, so a request reaches the correct account holder rather than another person.

Correction request

Tell our support desk which field is wrong and what it should say. This can cover a contact detail or a payment reference connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Security concern

Report an unfamiliar sign-in, device session or wallet status through the account support route. Do not send your password, one-time code or wallet PIN; we use account verification steps before discussing sensitive records.

DATA CONTROL POINTS

Inside hino99 Privacy Handling

Our Privacy Policy is tied to the way the account actually works, from phone verification before access to the device path that takes you from login into the lobby.

Account collection

When you open an account, we may collect your name or contact route, phone verification result and sign-in details. These records help us connect a support request to the right account before we discuss wallet status or amend personal data.

Device signals

A mobile or desktop session can provide device, browser and connection signals used to recognise repeated access and investigate suspicious activity. We do not ask you to share a device password, and these signals remain part of the Privacy Policy process.

Cookie choices

Cookies may keep your account session working as you move from login to the lobby, including when you check a game area such as Dragon Tiger. Browser controls can limit cookies, although some account functions may then need to be repeated.

Wallet references

We may keep a payment method, amount reference and status linked to an account action, such as a QRIS submission or DANA confirmation. We use these records to trace a stalled step without requesting your wallet PIN or full banking password.

Retention period

We keep personal records only while they serve account support, security checks, dispute handling or a legal requirement where local law permits. When a record is no longer needed, our handling process removes it or separates it from direct account identification.

Change requests

You can ask us to correct account data, explain a processing purpose or remove eligible records through the support route. Include the account contact detail and a specific request; we may verify ownership before making a change.

Privacy Policy Questions About hino99

These Privacy Policy answers address the account questions you may have before opening access or contacting support. They cover data collection, wallet references, cookies, device sessions, retention and the practical route for requesting a change. If your situation is not listed, use the account support path and describe the exact record involved.

The hino99 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies and payment references connected with your account. It also explains retention, security handling and how to request access, correction or removal where local law permits.

We do not ask you to provide a DANA, OVO or GoPay wallet password or PIN through account support. Our records may show a method and transaction status linked to your account, while your wallet credentials remain outside the Privacy Policy request process.

Phone verification helps connect a real account access step with the correct contact route and can help us investigate an unfamiliar session. The result may be retained as an account security record, subject to the retention rules described in our Privacy Policy.

Yes, you can ask which personal records are associated with your account through the support route. State the contact detail used at account opening and the type of data requested. We may confirm account ownership before releasing records to you.

Cookies can help keep your session recognised when you move from login to the lobby on mobile or desktop. You can adjust cookie settings in your browser, but limiting them may require repeated sign-in steps or affect parts of the account path.

You can ask us to check or correct an account-linked QRIS, bank transfer or virtual account reference. Include the account contact detail and transaction reference, but never send a password or PIN. We verify the request before changing the record.

We retain personal data while it supports account administration, security checks, payment tracing, disputes or a legal duty where local law permits. You can ask about a specific record and its purpose; eligible data is removed or separated when retention ends.