Reference

hr89 Privacy Policy for Your Account

Our Privacy Policy explains what account details we collect, why we use them, and how you can ask about changes before opening an account.

Clear data purposesWallet record clarityAccount access requestsMobile and desktop use
hr89 hr89 Privacy Policy for Your Account
CONTACT PATHS

Privacy Questions Around DANA and QRIS

A clear contact path helps when you want to understand a record rather than change a game setting. Use the account help route linked near the cashier area for privacy requests, and include the email or phone detail attached to your account. We can then locate a DANA or QRIS reference without asking you to send a password.

Team online

Account privacy request

Ask which account details we hold, why they are used, or how long they remain stored. Include your registered contact detail so we can identify the correct account before replying.

Wallet record check

For an OVO, GoPay, DANA or QRIS query, share the transaction reference and date, not your wallet password or one-time code. We use those details to trace the relevant record.

Access correction path

If a name, phone detail or account entry needs correction, contact us through account help. We may ask for an account step to confirm that the request comes from you.

DATA PRACTICES

Data Controls Behind Your Account

We handle this policy area through practical controls attached to account access, payment matching and support requests.

Account details

We may hold your registration contact, verification status and selected account settings so we can provide access and answer a request. We do not need your wallet password to discuss a payment reference.

Device activity

Mobile and desktop sessions can produce device and login signals used to protect account access. If a sign-in looks unusual, we may request an account check before discussing private details.

Cookies

Cookies may keep a session active, remember a page choice or help us understand which policy page was opened. Your browser controls can remove or restrict them, though some account steps may change.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help connect a payment request with the correct account. We use the reference for that task, not as a wallet password.

Retention

We retain records only for the account, support, payment, security or legal purpose that requires them. When a record is no longer needed, our handling follows deletion or secure removal procedures.

Your request

You can ask about access, correction, deletion or the purpose of a record through account help. We may verify ownership first, then explain any reason a specific record must remain stored.

Privacy Policy Answers for hr89 Accounts

These Privacy Policy answers address the account and wallet questions you may search before opening access. They focus on the records created by login, verification, payment matching and support, including what you can request from us.

It covers account details, login and device activity, cookies, support messages, payment references and retention. It also explains how you can request access, correction or deletion of relevant records.

We use your registered contact detail to create and protect the account, confirm an account request and respond to privacy questions. A clear contact detail also helps us separate your record from another account.

Yes. The Privacy Policy covers transaction references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These references help us match a payment request with your account.

Use the account help route near the cashier area and state that you want a copy of your account data. Include your registered contact detail; we may verify ownership before responding.

You can request correction or deletion through account help. We assess the request against account security, payment matching and any legal retention duty, then explain what can be changed or removed.

It covers device and login signals created when you open the account on mobile or desktop. We use them to support session security and may ask for an account check after unusual access.

Yes. Access and eligibility depend on local law. We apply the policy to supported Indonesia requests and may limit or adjust a request when a legal, security or payment record must remain.