Reference

hai168 Privacy Policy for Your Account

Our Privacy Policy explains how hai168 handles the data connected with your account, device and wallet activity before you open the lobby.

Clear data purposesWallet record controlsPhone verification contextIndonesia access wording
hai168 hai168 Privacy Policy for Your Account
CONTACT PATHS

Ask About Privacy Beside Support

A direct support route helps you resolve a privacy question without repeating your account story across several messages. From the account area, contact our support desk with the phone number linked to your profile and state whether your request concerns login records, a wallet receipt or device access. We can then check the relevant account step, including a DANA or QRIS status, while limiting the reply to the data needed for your request.

Team online

Account privacy request

Use the support contact inside your account and include your registered phone number. We use that account step to confirm the requester before discussing login records, profile details or a request to change stored data.

Wallet record question

For DANA, OVO, GoPay or QRIS queries, attach the payment receipt reference rather than sending a full wallet password or security code. We check the matching status and explain which payment record is held.

Device access concern

If a phone or desktop session looks unfamiliar, tell us the device path and approximate login time through support. We can review the security event, help protect the account and explain the related data held.

DATA HANDLING

How hai168 Handles Policy Requests

We keep this policy practical by linking each data request to the account action that created it.

Account data

We may hold your phone number, account credentials, verification result and support messages so we can authenticate access and answer account questions. We use these details for the stated account purpose rather than treating every record as general profile data.

Cookies and sessions

Cookies and similar session tools help keep the mobile lobby connected after login, remember security settings and detect unusual access. Your browser may offer controls for cookies, although changing them can affect sign-in or the path from login to the lobby.

Payment matching

When you select DANA, OVO, GoPay or QRIS, we retain the reference and status needed to match the account activity. Bank transfer and virtual account records are handled in the same way when a receipt or cashier status needs checking.

Account security

Phone verification, login records and device signals help us identify an account session that does not fit your usual access pattern. Never send a password or one-time security code to support; use the account contact path for a security concern.

Retention periods

We keep records only for the period needed for account operation, security checks, dispute handling or a legal request. A deletion request may not remove records that must remain for a stated legal or transaction purpose, and support can explain that distinction.

Changes and requests

To ask for a correction, access copy or deletion where available, contact support from the account tied to the request. Include the precise record, such as a phone detail or QRIS reference, so we can confirm scope before responding.

Privacy Policy Answers for hai168

These answers focus on the searches we hear most often about the hai168 Privacy Policy. They explain the account, device and wallet records involved, while keeping eligibility wording clear for Indonesian access. If your case involves a specific receipt, phone number or login event, use the account support path so we can check the correct record.

We use the phone number linked to your account for phone verification, login protection and support identification. It helps us confirm that a privacy request comes from the account holder. Contact support from that account if the number is wrong or needs a formal change.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those records to match account activity and handle receipt or status questions.

A login can create technical records such as device type, browser details, IP address, session time and security events. We use them to maintain the account session and identify unusual access. The mobile and desktop paths may create different technical signals.

Send the request through the support contact inside the account connected with the data. Name the record you want checked, such as a phone detail, login event or QRIS reference. We may confirm identity first, then explain the available action under local requirements.

You can ask support about deletion of eligible account data. Some records may need to remain for security, transaction matching, dispute handling or a legal request. Our reply will identify the relevant category and explain what can be removed or retained.

Yes. The Privacy Policy applies to the mobile path as well as desktop access. Session cookies, device signals and login records may support account security on your phone. If access or eligibility is discussed, it depends on local law and the applicable regional rules.

Use the account support path as soon as you notice an unfamiliar session and provide the approximate time and device type. Do not send your password or one-time code. We can check the security event, explain the related record and help protect the account.