Reference

Open hari88 with Legal clarity

hari88 Legal sets out how access, account records, wallet activity and policy questions are handled before you open an account.

Local-law accessPhone verificationPolicy contact pathWallet record clarity
hari88 Open hari88 with Legal clarity
POLICY HELP

Check Legal help for account questions

A clear contact path matters when a Legal question affects your account, phone check or wallet record. Start from the support link inside your account area and include the email or phone detail attached to the request, without sending a password or wallet PIN. We can direct access questions, data requests and correction requests to the relevant team. Your message should state what happened, which account step you reached and whether the issue concerns DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity.

Team online

Account access desk

Use the support link after login when Legal access is unclear. Tell us whether phone verification was completed and include the account detail we can check, so we can separate an eligibility question from a simple sign-in problem.

Wallet record checks

For a DANA, OVO, GoPay or QRIS record, send the transaction reference shown in your account area. We use that reference to locate the relevant entry without asking you to disclose a wallet PIN or full login password.

Policy request route

Ask through the same support route when you want a data copy, correction, retention question or explanation of a Legal decision. Include the requested change in plain English and we will point you to the next account step.

DATA SAFEGUARDS

Protect your Legal choices and records

Legal handling is practical: we identify the account record involved, limit the details shared through support and use account security steps before changing sensitive information.

Data handling

We handle account details, phone verification results and payment references for account administration and policy checks. When you ask about a record, provide only the details needed to locate it; never include your password, wallet PIN or a complete payment credential.

Cookie choices

Cookies can support the sign-in session and remember selected page settings on your device. If you clear them, you may need to complete the account sign-in step again. Contact support if a cookie setting appears to affect a Legal request.

Account security

Phone verification comes before account access, and sensitive changes may require the account detail already attached to your profile. We will not ask for a password or wallet PIN in a policy message, including one about DANA or QRIS.

Record retention

Records are kept only as needed for account administration, payment matching, security checks and policy handling. Ask support which type of record you mean and we can explain the applicable retention position without exposing another account's details.

Correction requests

If your name, phone detail or account record appears wrong, send a correction request through the logged-in support path. State the existing entry and the change you seek; we may ask for an account step before editing sensitive data.

Contact ownership

The account holder should make requests about access, stored data or policy decisions. We use the attached account detail and phone verification context to reduce mistaken changes, then explain the next step through the support route.

Browse Legal answers before opening access

These Legal answers cover the questions we expect you to ask before creating an account with hari88. They explain local-law access, phone verification, payment records, cookies, data requests and correction steps without replacing the rules that apply where you live. If your situation is not covered, use the account support route and describe the exact policy point you need us to check.

Access depends on local law. Before opening an account, you are responsible for checking whether the service is available to you in your location. We may use your phone verification and account details to apply the access position consistently, and support can explain the relevant account step.

Phone verification links the access request to the account detail being used. It helps us handle policy questions, security checks and corrections against the right record. You must complete the verification step before account access, and support should never receive your password or wallet PIN.

DANA and QRIS entries can appear in your account record so we can match a payment reference with the correct account status. If an entry looks wrong, send its reference through support. Do not send a wallet PIN, full credential or another person's payment detail.

Yes. Send a data copy or correction request through the logged-in support route and identify the record clearly. For a correction, state the current entry and the change requested. We may ask for an account step or phone context before changing sensitive information.

Cookies may keep your sign-in session and page preferences working on your device. Clearing them can require another sign-in step, but it does not remove the account records held for policy or payment administration. Ask support if a cookie issue blocks a data request.

Use the support link inside your account and explain the decision, the account step you reached and the location involved. If the question concerns eligibility, we will refer to the local-law position. If it concerns a record, include its reference so it can be checked.

You can ask support which account, security or payment record you mean and how its retention is handled. If you request an account change or closure-related action, we may first confirm the account through its attached phone detail before explaining the next step.