Reference

Privacy Policy for Your hit77 Account

Our Privacy Policy explains how hit77 handles the details you provide when you open an account, sign in, use the mobile lobby or check wallet status.

Account dataWallet referencesCookie choicesSecure access
hit77 Privacy Policy for Your hit77 Account
CONTACT OUR TEAM

Privacy Help Through Your Account

A direct support route helps you ask about the Privacy Policy without explaining your full account history in a public channel. Use the support contact shown after login and include the email or phone number linked to your account, plus the exact privacy question. We may ask for a limited account check before discussing personal data. If you are in Bandung or elsewhere in Indonesia, the same account path applies on mobile and desktop. Keep payment receipts private when you contact us.

Team online

Account message

Send a privacy request through the signed-in support path and identify the account detail involved. We use the account email or verified phone reference to route the request, rather than asking you to post DANA, OVO or QRIS receipts in an open channel.

Wallet status check

If your question concerns a wallet record, mention the payment rail and date shown in your account. Our team can compare the stored transaction reference with the DANA, OVO, GoPay or QRIS status without requesting your wallet password or full payment credentials.

Access assistance

When a privacy request follows a login problem, first complete the available phone verification step. This lets us separate an account owner request from an unknown device request while keeping the conversation focused on data access, correction or deletion.

DATA HANDLING DETAILS

What We Keep And Why

Our approach links each data category to a practical account need rather than collecting details without a reason.

Account creation

When you open an account, we use the contact details and verification information you submit to create the profile and protect future sign-ins. A clear account path helps us connect your request to the correct record without exposing another person’s data.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, we retain transaction references and status details needed to reconcile the account. We do not need your wallet password to check whether a payment reference matches your account activity.

Cookies and devices

Cookies can remember session settings and help the lobby load correctly after you sign in. Device and browser signals can support security checks when your access changes from mobile to desktop. You can manage browser cookies, though some account functions may then require another login.

Account security

Phone verification, login event records and unusual-device checks help us protect account access. If you receive a sign-in prompt you did not start, avoid sharing the code and contact support through the account path so we can review the event.

Retention periods

We keep personal data only for as long as it supports the stated account purpose, dispute handling, security checks or a legal duty. When a record is no longer needed for those reasons, we remove it, anonymise it or restrict access according to our internal process.

Changes and requests

You can ask us to correct account details, explain stored data, provide access where available or consider removal where applicable. Send the request through signed-in support, describe the change clearly and complete any identity check needed to protect the account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open access from Indonesia. We explain what may be collected, how wallet references are used, how to request a change and what happens when you switch devices. If your situation is not covered, contact us through the signed-in support path and include only the details needed to locate your account. Access depends on local law and is available where local law permits.

The hit77 Privacy Policy covers data connected with account creation, phone verification, sign-in events, device use, cookies, support messages and payment references. It explains why we use those records, who may handle them for an account task and how you can request access or correction.

We do not need your DANA or QRIS wallet password for account reconciliation. We may retain a payment reference, status, amount and date supplied through the payment flow so we can match activity to your account and respond when a wallet status needs checking.

Use the signed-in support contact and ask for a personal data access request. Include the account email or verified phone reference, explain the records you want addressed and complete a reasonable identity check. We use that step to avoid sending account data to an unknown requester.

Yes, you can ask us to correct inaccurate account details through support. State which field is wrong and provide the replacement clearly. We may verify the request using your account email or phone step, then update the record when the request is confirmed.

Device and cookie data help maintain a signed-in session, remember selected settings and identify unusual access when you move between a phone and desktop. You can adjust browser cookie controls, but turning them off may require repeated sign-ins or limit session functions.

Retention depends on the purpose of each record. We may keep account, security, payment-reference or support data while it is needed for account operations, dispute handling or a legal duty. After that need ends, we remove, anonymise or restrict the record.

The same Privacy Policy applies when you use OVO or GoPay through the account payment flow. We may receive transaction status and reference details, while the wallet provider may separately handle data under its own terms. Your wallet credentials remain with that provider.