Reference

hokbet Privacy Policy for your account data

Our Privacy Policy explains how hokbet handles the account details behind DANA, OVO, GoPay and QRIS access, including what we collect, why we use it and how you…

Clear data purposesWallet detail boundariesAccount request path
hokbet hokbet Privacy Policy for your account data
PRIVACY HELP PATH

Get privacy help beside your cashier path

A clear contact route helps when a privacy request meets an account or wallet question.

Account access Tell us which login step stopped you and which account detail you can still…
Wallet status For a QRIS, bank transfer or virtual account question, share the reference shown in…
Data request Ask for access, correction or deletion review through our support route.
DATA CONTROL STEPS

Your data path from login to retention

We keep the Privacy Policy practical by connecting each data use to a real account step.

Account details

We may use your account phone detail and login record to open the correct account view, send an access notice and handle a request about your own data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status questions. They are handled as transaction context, not as wallet passwords.

Cookies

Cookies can keep your selected page state and support account continuity. Browser controls let you remove or restrict them, although some account steps may then need to load again.

Login security

A phone verification step may be requested before account access or a data change. We use this check to reduce the chance that another person receives account details.

Retention period

We retain records for as long as their account, payment, security or legal purpose requires. When that purpose ends, handling follows our deletion and storage process.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page. Check the page before opening an account or sending a request so you can read the current terms.

Privacy Policy answers for hokbet accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account from Indonesia. They explain account data, wallet references, cookies, access requests and the route to contact us, with eligibility depending on local law.

It covers data connected with your hokbet account, including login details, phone verification, payment references, cookies, security records, retention and requests to access, correct or delete data.

No. Our Privacy Policy treats DANA and QRIS details as payment context for status checks. We do not need your wallet password or security code to match a receipt or account reference.

Phone verification helps us confirm that the person requesting account access or a data change is connected with the account. It can also reduce mistaken disclosure during a privacy request.

Yes, where local law permits. Use the support route and identify your account phone detail and request type. We may need an identity check before sharing records connected with your account.

Send a correction request through the account support path, state which detail is wrong and provide the replacement wording. We will explain any verification step and whether a record must remain.

Cookies can preserve page continuity and selected account settings on your device. You can restrict them through browser controls, but some login or policy-page functions may reload or require another step.

You can request deletion where local law permits. Some account, payment, dispute or security records may need to remain for a defined purpose, and our support route will explain the applicable limit.