Reference

horebet Privacy Policy for Your Account

horebet Privacy Policy explains how we handle your account details, device activity and wallet records when you access our lobby.

Account dataCookie choicesWallet recordsSecurity requests
horebet horebet Privacy Policy for Your Account
HELP WITH REQUESTS

Open a Clear Privacy Support Path

If a privacy question appears while you are signing in or checking a wallet status, we keep the request path close to the account support route.

Account access If you cannot reach your account or phone verification stalls, contact our support route…
Wallet records For a DANA, OVO, GoPay or QRIS question, include the payment rail and reference…
Data changes To ask for a correction, access copy or eligible removal, use the same account…
DATA HANDLING

Browse How horebet Handles Privacy

Privacy choices should be understandable before you open the lobby from a phone or desktop. We separate account details, device signals and payment references so each record has a clear operational reason.

Account details

When you open an account, we receive the details you enter and the phone verification result connected with that account. We use them to create access, keep the correct profile attached to activity and respond to a request about your own records.

Cookies and sessions

Cookies and similar session records help keep you signed in, remember a selected setting and identify a broken device path. On mobile, clearing site cookies through your browser settings can sign you out and may remove saved preferences without deleting an account.

Payment references

A DANA, OVO, GoPay or QRIS transaction can provide a reference, amount status and account match needed for payment support. Bank transfer and virtual account records are handled for the same matching purpose, while wallet login credentials stay outside our requested account details.

Account security

We use phone verification, sign-in records and device signals to help identify unusual access. If a login looks different from your usual path, we may ask for an additional account check before discussing private details or changing account data.

Record retention

We keep account, security and payment records only for the period needed for the stated account purpose, operational checks or a legal duty. When a record no longer needs to remain available, our handling follows the applicable deletion or anonymisation process.

Your requests

You can ask for access, correction, clarification or eligible removal through our account support route. We may confirm your identity, narrow a request to a specific record and explain if a legal or security reason means part of that record must remain.

Find Answers About Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access from Indonesia. We keep the wording practical: what we collect, how a device path works, when a wallet reference is used and how to request a change. If your question concerns a particular record, include its account step when you contact us.

The horebet Privacy Policy covers details you submit for an account, phone verification, device and session records, payment references and support conversations. It explains why we use those details, how long operational records may remain and how you can request access, correction or eligible removal.

Yes. Privacy Policy treatment includes the reference and status needed to match DANA, OVO, GoPay or QRIS activity to your account. Bank transfer and virtual account records can be handled in the same way. We do not need your private wallet password for that matching check.

We collect the account details you enter, the phone verification result and records created while your account is accessed. Device and session signals may help us diagnose login problems or unusual access. We use each category for a stated account, security, payment or support purpose.

Where local law permits, you can request access to your account data or ask us to correct an inaccurate detail. Send the request through the account support route and identify the record or account step involved. We may verify ownership before sharing or changing private details.

Cookies can keep a session active and remember browser settings on your phone or desktop. If you clear them, you may need to sign in again and select preferences again. Cookie controls are available through your browser, while account deletion requires a separate request.

We retain payment references, account activity and security records for as long as they serve the stated operational purpose, a support check or a legal duty. The period can differ by record. When continued storage is no longer needed, the record follows our deletion or anonymisation process.

Use the account support path and state that your request concerns the Privacy Policy. Include your account identifier and the relevant subject, such as cookies, phone verification, a QRIS reference or data correction. Do not send a password; we will request only suitable ownership details.