Reference

Privacy Policy for hiuslot Accounts

Your hiuslot Privacy Policy explains how we use account details while you move from login to the lobby, check Live Blackjack Table access or manage a DANA wallet.

Account dataWallet detailsDevice securityPolicy access
hiuslot Privacy Policy for hiuslot Accounts
HELP WITH PRIVACY

Privacy Help Beside GoPay Status

A clear support path matters when a privacy request and a wallet check arrive together. From your account help area, tell us whether you need access to stored details, a correction, an explanation of a device record or help matching a GoPay receipt. Include the phone number linked to the account and the relevant date, but never send a password or one-time verification code. We use the details you provide to locate the right record and keep the request connected to your account.

Team online

Account request

Use the account help path for a copy of personal details, a correction request or a question about how your login data is used. We may ask for phone verification before discussing account-specific records.

Wallet record

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date through support. We can explain which payment record is held and why it is connected with your account activity.

Access concern

If a phone or browser shows activity you do not recognise, contact support through your account help area. We can review the access details, protect the session and explain the next privacy step.

DATA CONTROL

How We Handle Account Data

Privacy work is part of the account flow, not a separate promise hidden away from the lobby.

Collected details

We may handle your phone verification status, account identifiers, device signals and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity can be linked to a transaction record.

Cookie choices

Cookies and similar browser storage can keep your session connected and remember necessary access settings. You can manage browser permissions, although removing essential storage may require you to verify your phone again.

Account security

We use login checks, phone verification and session signals to reduce unauthorised access. Never share your password or one-time code; if a device behaves unexpectedly, use the account help route promptly.

Retention period

We keep account, payment and support records only for as long as needed for the stated service, security checks, dispute handling or legal duties. The period can depend on the record and local law.

Your changes

You can ask us to correct inaccurate account details or explain a record connected with your login. Send the request through account help with enough detail for us to locate it without exposing another account.

Policy contact

For a Privacy Policy question, identify your account phone number and describe the data issue in the support request. We may verify ownership before sharing, changing or discussing personal account details.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to ask before opening an account or checking a wallet record. They cover the practical path for data access, device behaviour, cookies, corrections and contact. If your situation involves local eligibility or a particular payment reference, our handling depends on local law and the details connected with your account.

The hiuslot Privacy Policy covers account identifiers, phone verification, device signals, cookies, support messages and payment references. It explains why we use those records for account access, security, transaction matching and support, where local law permits.

Phone verification helps us connect an account request with the correct account before access or support action. It also helps reduce unauthorised changes. We will not ask you to share a password or one-time verification code.

Yes. The Privacy Policy covers transaction references and wallet status connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account records. We use them to match receipts, resolve status questions and handle account support.

We use device and session signals to recognise unusual access, protect your login and investigate an account request. A change from phone to desktop may lead to another security check. These signals are handled for account and security purposes.

Yes. Send a correction request through the account help area, describing the inaccurate detail and the phone number linked to your account. We may verify ownership first, then assess the request against retention needs and local law.

Retention depends on the type of record and its purpose. Account, payment and support details may be kept for security, dispute handling or legal duties, then removed or anonymised when no longer needed where local law permits.

Use the support route inside your account help area and describe the privacy question clearly. Include a relevant date or transaction reference when useful, but do not include your password or one-time code in the request.