Reference

Privacy Policy for Your hit77 Account

hit77 Privacy Policy explains how we handle your account details, device signals, cookies and payment records when you open an account or enter the lobby.

Account dataCookie choicesPayment recordsAccess requests
Explore Our Lobby Read FAQ
hit77 Privacy Policy for Your hit77 Account
DIRECT POLICY HELP

Get Clear Answers About Your Data

A clear support route matters when a privacy question appears beside a login or wallet issue.

Account privacy request Ask us to locate the account details connected with your phone verification or sign-in path. We may ask for enough account evidence to protect your records before discussing a request.
Payment record check If a DANA, OVO, GoPay or QRIS reference appears unclear, send the transaction reference through the account support route. We use it to separate a wallet status question from unrelated account data.
Policy contact path For a correction, deletion or access request, describe the specific record and the action you want. We review the request under applicable rules and reply through the contact details on file.
DATA HANDLING CHECK

How We Protect Policy Choices

Privacy choices work best when the account process makes them understandable. We separate ordinary account operation from a request to change or remove personal data, then check the account details before acting.

Account details

We use the details you submit during account opening and phone verification to create the account path, respond to requests and connect activity to the correct record. We do not treat an unverified request as proof of ownership.

Device signals

A mobile browser or desktop session can produce device, browser and login-event data. We use these signals to identify unusual access and keep the sign-in path safer, not to replace the account checks required for a privacy request.

Cookie controls

Cookies can preserve session state and help us identify repeated security events. You can review cookie controls in your browser, although changing them may interrupt sign-in or require you to confirm the account path again.

Wallet records

Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes may be retained to reconcile status and investigate disputes. We use the reference for the relevant transaction rather than collecting unrelated wallet details.

Retention requests

When you ask how long a record remains, tell us which account event or payment reference you mean. We assess the request against active account needs, security checks and applicable retention duties before replying.

Correction route

Send a precise correction request through account support, naming the field that appears wrong and the replacement detail. We may request verification before changing it so another person cannot alter your account record.

Privacy Policy Answers Before Access

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. We keep each answer tied to a practical step, from phone verification and cookies to payment references and requests for a copy or correction. Where access or eligibility is discussed, the position depends on local law and the region supported by the service.

It covers account details, phone verification, login events, device and browser signals, cookies, support messages and payment references. It also explains how we use those records for account access, security checks, payment status work and requests to access, correct or remove data.

Phone verification helps us connect an account request to the person who controls the submitted contact detail. It also supports account recovery and privacy checks. We may use the result when you ask us to change account data or discuss a DANA, OVO, GoPay or QRIS record.

Yes. The Privacy Policy covers transaction references and related status records for DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes. We use those details to reconcile a payment question or investigate an account case, without needing unrelated wallet content.

Cookies can keep a browser session active and help us recognise repeated sign-in or security events. Your browser controls can restrict them, but that may interrupt access or require another account check. The Privacy Policy explains the role of these signals in the account path.

You can contact account support with a clear request for the records connected to your account. Include the phone or email detail on file and identify the account path. We verify the request first, then assess what can be supplied under applicable rules.

Tell us which account field is inaccurate and provide the replacement detail through the account contact path. We may ask you to complete phone verification or another ownership check before making a change, so an unrelated person cannot edit your record.

Retention depends on the type of record and the operational, security or legal reason for keeping it. Ask us about a particular account event or payment reference rather than requesting a general date. We assess the request under applicable rules and reply with the result.

Related Pages

hit77 Indonesia FAQ Account information About Us koittoto