Reference

Privacy Policy for Your hari88 Account

Our Privacy Policy explains what we collect when you open a hari88 account, use the lobby, connect a device or check wallet status.

Account clarityWallet recordsCookie choicesAccess requests
hari88 Privacy Policy for Your hari88 Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact path helps you ask about the personal data linked to your account without mixing the request with a general lobby question. Use the support channel available after sign-in and include your account phone number, request type and any relevant payment reference. We may ask for an account step to confirm that the request comes from you. This protects records connected with DANA, QRIS, bank transfer or virtual account activity while keeping the request focused on Privacy Policy matters.

Team online

Account access

If you cannot sign in, use the account support route shown on the sign-in page and state that your request concerns personal data. We can ask for phone verification details before discussing account records, including the device path used to reach the lobby.

Wallet records

For a data question tied to DANA, OVO, GoPay or QRIS, include the payment rail and reference visible in your account. We use those details to locate the relevant status record without asking you to send a wallet password or private payment code.

Correction requests

When a name, phone detail or account record needs correction, send the requested change through the available support channel. We may compare the request with your verified account step before updating information or explaining why a record must remain unchanged.

DATA PRACTICES

How We Handle Your Account Data

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Account security

Before account access, we use phone verification and sign-in checks to connect activity with the correct account. Device and session signals can help us identify unusual attempts, protect your account and investigate an access concern without requesting your wallet password.

Payment references

Our records can show that a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event was linked to your account. We use the reference and status to reconcile activity, while payment credentials remain handled by the relevant payment service.

Cookie controls

Cookies can keep your sign-in session and selected page settings available as you move between account pages and the lobby. Your browser can block or remove them, but doing so may require you to repeat sign-in or verification steps.

Mobile devices

When you use a phone or tablet, we may process browser, operating system and session signals needed to display account pages correctly. We do not describe this as a separate mobile application; access follows the browser path from sign-in to the lobby.

Retention checks

We retain account, support and payment-status records for the period needed to provide access, resolve disputes, protect the service and meet applicable duties. After that need ends, we review whether records can be deleted, restricted or kept in a less identifiable form.

Your requests

You can contact us to ask for access, correction, clarification or a restriction concerning your personal data. Include your account phone number and request details; we may verify ownership first and explain any legal or operational reason that limits the requested action.

Privacy Policy Answers For hari88

These Privacy Policy answers address the account and device questions we expect before you open an account. They explain how data connects with phone verification, local wallet references, cookies and support requests. If your situation is not covered, use the signed-in support route and describe the exact record or account step involved. Access depends on local law, so the response may vary according to your location and the type of request.

The Privacy Policy covers account and contact details, phone verification data, sign-in and device signals, session activity, support messages and payment references. It may also cover cookie data used for session continuity. We use these records for access, security, reconciliation and support rather than requesting wallet passwords.

Phone verification helps connect an account request with the person who controls the registered contact detail. It supports sign-in protection and helps us handle access or correction requests safely. We may repeat an ownership check before discussing account data connected with DANA, QRIS or another payment reference.

No. The Privacy Policy describes records such as a payment rail, reference and status that may help reconcile activity with your account. Wallet credentials are handled by the relevant payment service. Do not send a wallet password, one-time code or private payment credential through support.

On a mobile browser, cookies can help keep your sign-in session and page settings available while you move through account pages. Your browser controls can remove or block them. If you do, we may ask you to repeat sign-in or phone verification before access continues.

Use the support channel available after sign-in and state whether you want access, correction, clarification or restriction. Add your account phone number and the record concerned. We may verify ownership first, then confirm the action or explain why a legal or operational limit applies.

We keep records for the period needed to provide account access, investigate security events, reconcile payment status, resolve disputes and meet applicable duties. We review records after those needs end and may delete, restrict or reduce identifiability where allowed. The exact period can depend on the record type.

Yes. You can ask us to clarify the personal data linked to your account through the available support route. Include enough account detail for an ownership check, but do not send wallet credentials. Access and response steps depend on local law and may require identity confirmation.