Reference

Privacy Policy For Your hari88 Account

hari88 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and contact our support route.

Account accessWallet recordsCookie choicesRequest changes
hari88 Privacy Policy For Your hari88 Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path helps when you need a Privacy Policy answer rather than a wallet status update.

Account data request Ask us to identify the personal data connected with your account, including the contact…
Wallet record question If a DANA, OVO, GoPay, or QRIS reference looks unfamiliar, send the receipt or…
Cookie choice For questions about cookies or device recognition, tell us whether you used a mobile…
HANDLING DETAILS

What We Do With Your Account Data

Our Privacy Policy follows the account journey rather than treating every visit alike. A sign-in, phone verification step, wallet status check, and support message can create different records, each used for a…

Data we collect

We may receive your account contact details, phone verification result, sign-in time, device or browser signals, support messages, and payment references. For DANA or QRIS activity, the record helps connect a cashier status to the correct account; it does not replace your wallet credentials.

Why we use it

We use account and device details to provide sign-in, detect unusual access, confirm a requested account action, and match a payment status. A reference for GoPay, OVO, bank transfer, or virtual account activity is handled for the related account process and support response.

Cookies and sessions

Cookies or similar session tools may help keep you signed in during a mobile browser visit, remember a session state, or identify repeated security checks. If you clear browser storage, you may need to complete phone verification again before account access continues.

Account protection

We use phone verification, sign-in signals, and account checks to reduce unauthorised access. Never send a password or wallet PIN in a support message. If your device changes, sign out of the old session and contact us through the account support path if access looks unusual.

Retention approach

We retain records for as long as needed for the account purpose, security checks, payment reconciliation, support handling, or a legal requirement that applies where local law permits. When a record is no longer needed for those purposes, our process is to remove or de-identify it.

Changing your details

You can ask us to correct an inaccurate contact detail or clarify how a record is used. Include your account identifier and the requested change through support. We may verify you first, and some data can remain where retention is required for security, payment records, or legal reasons.

Privacy Policy Answers For hari88

These Privacy Policy answers address the searches we hear most often before account access. They cover data requests, payment references, cookies, device changes, and local access wording. If your situation is different, send a focused request through the support path beside the cashier area. We will first confirm which account the question concerns and then explain the relevant handling step.

The hari88 Privacy Policy covers information connected with account creation, phone verification, sign-in events, device or browser activity, support messages, and payment references. It applies when you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account in an account-related process.

Yes, where local law permits, you can request details about personal data connected with your account. Send the request through the support route near the cashier area and include your account identifier. We may confirm account ownership before releasing or describing any records.

The Privacy Policy treats DANA and QRIS details as payment references used to match a cashier status, receipt, or support question with your account. We do not need your wallet password or PIN. If a reference looks wrong, send the receipt detail through support.

Phone verification helps connect account access with the contact detail supplied during registration and supports checks when a device or sign-in pattern changes. It can also help us confirm ownership before discussing account data. Access depends on local law and the applicable account process.

Send a correction request through the account support path and state which detail is inaccurate, such as a contact record or account identifier. We may ask for an ownership check before making the change. Some payment or security records may need to remain for their stated purpose.

Yes. Cookies or session tools may remember a mobile browser session, support sign-in continuity, or reduce repeated security checks. Clearing browser storage can remove that session and lead to another phone verification step. Tell us your device path if you need help identifying a cookie issue.

We keep personal data for the account, security, payment reconciliation, support, or legal purpose that requires it, where local law permits. Retention can differ by record type. You can ask us which purpose applies to a particular account or payment reference through support.