Reference

Privacy Policy for hksiang Accounts

hksiang Privacy Policy explains how we use the details connected with your account, wallet activity and access to the lobby.

Account dataWallet referencesCookie choicesAccess requests
hksiang Privacy Policy for hksiang Accounts
PRIVACY HELP DESK

Ask About Your hksiang Privacy Record

A clear support route helps when your account details look wrong or you want to understand a data decision. Contact us through the support path connected with your account and include the email or phone detail used for access, the request you are making, and any relevant wallet reference. We use those details to locate the right record without asking you to send a password or wallet PIN. If access is discussed, it depends on local law and the result may require identity checks.

Team online

Access requests

Ask us for a copy of personal data linked to your account. Include your registered phone or email so we can locate the correct record and confirm that the request comes from you before releasing account details.

Correction requests

If your contact detail or account record is inaccurate, tell us what needs changing and why. We may ask for phone verification before editing the record, helping keep another person from changing your account information.

Wallet questions

For a DANA, OVO, GoPay or QRIS reference that appears unclear, send the account identifier and cashier status shown on your side. Do not send a PIN, password or full wallet login details through support.

DATA CARE ROUTINES

What Privacy Means During Account Use

Privacy work continues each time you sign in, check a wallet status or return to a mobile lobby.

Account security

Phone verification is used before account access and may also help us confirm a privacy request. Keep your password private, sign out on shared devices and contact support if a login record does not match your activity.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to reconcile the account action. These records are not a request for your wallet password or PIN.

Cookies

Session cookies can keep you signed in during an account visit, while preference cookies can remember choices made on the site. Your browser settings can remove or restrict cookies, although some account steps may then need repeating.

Mobile devices

When you move from login to Aviator Mobile Play or Fishing War Mobile Play, device and session details can help us identify a broken access path. We use those signals for support and security rather than asking for unrelated device content.

Retention

We keep personal details only for the operational, security or legal purpose that calls for them, then review whether they are still needed. The period can differ by record type and by local law, so support can explain the applicable request path.

Policy changes

If this Privacy Policy changes in a way that affects account data, we will present the updated wording on the site. Check the policy before opening an account or using the lobby, especially after a phone, browser or wallet-status change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you may have before opening access on hksiang. They explain what we collect, why phone verification appears, how wallet references are handled, and how to request action. If your situation involves a specific account or payment record, use the support path rather than sending sensitive credentials in a message.

The hksiang Privacy Policy covers personal details connected with account creation, phone verification, sign-in activity, device sessions, cookies, support requests and payment references. It also explains retention, security handling and the routes available when you ask to access, correct or remove data.

We use phone verification to connect the correct person with an account and reduce unauthorised access. It can also help us confirm a privacy request before sharing account details. We will not ask you to provide your password or wallet PIN for verification.

Yes. The Privacy Policy covers payment references and status information created when you use DANA, OVO, GoPay or QRIS, as well as bank transfer and virtual account records. We use those details to match a cashier event with the right account and investigate status questions.

Use the support path connected with your account and state that you want an access request. Include the registered phone or email, but do not include a password, wallet PIN or full wallet login. We may verify your identity before providing the matching record.

You can ask us to correct inaccurate account information through support. Describe the field that is wrong and the replacement detail, then complete any phone verification we request. Whether a change can be made depends on local law and the record's operational or legal purpose.

Retention varies by the kind of record and the reason we hold it. Account security logs, wallet references and support records may follow different periods because they serve different operational or legal purposes. Where local law permits, support can explain the request route for a specific record.

You can manage or remove cookies through your browser settings. Session controls may be needed for login, while preference controls can remember choices during a visit. Restricting cookies may cause repeated account steps or make parts of the privacy-request path harder to use.