Reference

hoki bos Privacy Policy, Clearly Explained

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse Blackjack or Rocket Crash, and use DANA or QRIS.

Account dataWallet recordsDevice choicesYour requests
hokibos.click page image
CONTACT YOUR WAY

Get Privacy Help Beside Your Account

A privacy question should not require you to explain your entire account history.

Account request Use the account support path to ask what personal data is connected to your…
Wallet record For DANA, OVO, GoPay or QRIS questions, share the transaction reference and status shown…
Access question If a mobile browser stops at sign-in, tell us your device type, browser path…
DATA CONTROL POINTS

Six Practical Privacy Checks For You

We handle privacy through account actions rather than vague promises. Your choices cover the data you provide during registration, the cookies and session signals used by the browser…

Registration details

We use your submitted account details to create and maintain your profile.

Cookies and sessions

Our browser path may store cookies or session markers so your sign-in state, language preference and requested page remain connected.

Security signals

Device type, browser version, approximate session timing and sign-in events can help us detect unusual account activity.

Wallet retention

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may remain in transaction history after a request closes…

Data access request

Ask us to identify the personal data linked to your account by using the support path inside your profile.

Correction request

If your contact detail or account record is inaccurate, tell us the field to amend and the reason.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and wallet situations you are most likely to meet on a phone or desktop browser in Indonesia. If your question involves a particular record, keep its date and reference ready so our support route can respond with the right context.

It covers account details, phone verification, browser and device signals, cookies, wallet records, support requests, retention and your options to access or correct personal data. Eligibility depends on local law.

We may use your phone number to create the account connection and complete the phone verification step before access. It also helps us distinguish your profile when you ask about account data.

Yes. A DANA or QRIS request can leave a reference, amount, time and status in account history. We use those details to match the cashier event and investigate a missing or unclear receipt.

The mobile or desktop browser may provide device type, browser version, language, session markers and sign-in timing. These details help connect your session and identify unusual access patterns.

Use the support path inside your account and ask for the personal data linked to your profile. Include your connected phone or email and the relevant record; we may verify ownership first.

Yes. Send a correction request through the account support route, name the field that is wrong and explain the change. We check the request against your profile and applicable local requirements.

Retention depends on the record type and the operational, security or legal reason for keeping it. Wallet references may remain for reconciliation, while other session data can leave sooner.