Reference

Open the hari88 Privacy Policy

hari88 Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record clarityAccount access choices
Browse Lobby Read FAQ
hari88 Open the hari88 Privacy Policy
HELP PATHS

Switch to the right privacy contact

A direct contact path helps you ask about personal data without sending wallet credentials or account passwords. Start with the account details connected to your request, such as your registered phone number and the relevant payment reference. We use that context to locate the correct record while limiting unnecessary disclosure. If your question concerns a sign-in event, device change or QRIS receipt, mention the date and account step so our support team can check the policy issue more precisely.

Team online

Account access

Ask us to clarify data connected to your phone verification, sign-in history or device path. We may request account details to confirm that a privacy request comes from you, but we will not ask for your wallet password or full security code.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the transaction reference and date. We can explain which payment record is held, why it is matched to your account and what correction route applies.

Policy requests

Use the same account help path to ask for a copy, correction or removal request under this Privacy Policy. Tell us which detail is affected and how you want us to respond, without attaching unnecessary identity documents.

DATA PRACTICES

Browse our privacy handling steps

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

Data we collect

We may collect your account name, phone number, verification status, sign-in events, device details and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can be linked to the matching account action.

Cookie use

Session cookies help keep your account connected while you move between policy pages and the lobby on mobile or desktop. Other browser signals may help us identify repeated access, diagnose errors and protect a session from unusual activity.

Account security

Phone verification is used before account access, and sign-in events may be checked when a device changes. Never send a password, wallet PIN or one-time code in a support request; we only need enough detail to confirm the account issue.

Retention choices

We retain records for the operational period needed to reconcile account actions, payment status, security events and support requests. A removal request may be limited when a record is needed for a pending account, transaction or legal obligation.

Correction requests

If your phone number, account name or contact detail is inaccurate, ask us to correct it through the account help path. Include the affected field and a safe way to reach you; we may verify the request before changing the record.

Who to contact

Privacy questions belong with our account support path, including requests about cookies, device records, wallet references or policy access. Share the smallest useful set of details, and identify whether you seek access, correction, deletion or clarification.

Check answers about hari88 privacy

These Privacy Policy answers address the searches we expect before account access: what we collect, how wallet references are used, how cookies work and how to request a change. The same account path can help you identify a record or raise a privacy request, while access remains subject to local law.

The hari88 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and support messages. It explains why we use each category, how records support account operations and how you can ask about access, correction or removal.

No. We use payment references and status details to match DANA, OVO, GoPay or QRIS activity to the correct account step. Do not send a wallet password, PIN or one-time code to support. The Privacy Policy does not require those secrets for a request.

Cookies help maintain a signed-in session as you move between the policy page and the lobby on mobile or desktop. We may also use browser signals to diagnose access errors and protect the session. You can ask support which cookie-related purpose applies to your request.

Yes. Contact the account support path and ask for access to the personal data connected with your account. State your registered phone number and the categories you need, such as sign-in events or wallet references. We may verify your identity before responding.

You can ask us to correct an inaccurate phone number, account name, contact detail or other personal record. Identify the exact field and provide a safe contact route. We may compare the request with your account step before applying a change.

We retain DANA, OVO, GoPay, QRIS, bank transfer and virtual account references for the operational period needed to reconcile account actions, status checks and support requests. A removal request may be limited while a transaction, account issue or legal obligation remains active.

Yes. Access to our services depends on local law, and this Privacy Policy applies where local law permits. If you are unsure whether an account or privacy request can proceed from your location, contact us before sharing extra personal details or payment records.

Related Pages

hari88 Indonesia Access guide pangkaltoto ligaslot88 Account information