Reference

hoki178 Privacy Policy, clearly explained

Our Privacy Policy shows how hoki178 handles the account, wallet and device data connected with your lobby access.

Account dataWallet recordsDevice accessCookie choices
hoki178 hoki178 Privacy Policy, clearly explained
CONTACT ROUTES

Open a privacy request from your account

A clear contact route helps you ask about the Privacy Policy without sending sensitive wallet credentials. Start from your logged-in account support path, describe the request, and include the relevant account step or payment receipt reference. We use those details to locate the correct record and may verify your identity before changing or releasing data.

Team online

Account request

Use the support path after login to ask for a copy, correction or explanation of data linked to your account. Include your account identifier, but never send a DANA, OVO or GoPay password.

Wallet query

For a QRIS, bank transfer or virtual account record, attach the payment reference and date rather than full wallet credentials. We check the status against the account record before replying.

Access concern

If an unfamiliar device reaches your account, contact us through the account support route and describe the login time. We can review access records and guide the next account-security step.

DATA PRACTICE

Browse hoki178 data controls and retention

We keep this policy practical: you should know what we collect, why we use it and how to request a change.

Account records

We use your phone number, account identifier and login events to create access, confirm account ownership and respond to account requests. The account step gives us a consistent record to match when you contact support.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account. We use the reference needed for reconciliation, not your wallet password.

Device signals

Browser type, device details, network address and login time can help identify unusual access. These signals support account protection when you switch from a mobile browser to a desktop session.

Cookie settings

Cookies can keep a session active, remember selected preferences and help us understand whether a login request is functioning. You can manage browser cookie controls, although some account steps may then require another login.

Retention approach

We retain records for as long as needed for the stated account, payment, security or legal purpose. When a record is no longer needed, we remove it or separate it from direct account identification.

Change requests

Ask us to access or correct eligible data through the logged-in support path. We may request identity evidence, limit a request where law allows, and explain the next step without asking for wallet credentials.

Check Privacy Policy answers before opening

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They cover the data tied to login, payments, cookies, device access and requests. If your question is specific to a record, use the account support path with its reference rather than sharing a secret credential.

The hoki178 Privacy Policy covers account details, login events, device signals, cookies, support messages and payment references connected with your use of the site. It also explains retention and request routes.

No. Our Privacy Policy describes using the DANA or QRIS payment reference and status needed to match a transaction. Do not send a wallet password, PIN or one-time code through support.

We may record your phone number, account identifier, login time, browser type, device details and network address. The Privacy Policy explains how those records help provide account access and identify unusual activity.

Use the logged-in account support path and state which record needs correction. Include your account identifier or payment reference, then complete any identity check required before we change the data.

Cookies may keep your mobile session active, remember preferences and help diagnose login behaviour. You can adjust browser controls, but turning cookies off may require repeated login during account access.

We keep account and payment records only for the period needed for the stated account, security, reconciliation or legal purpose. The Privacy Policy explains that records may then be removed or de-identified.

Yes. Where local law permits, contact us through the account support path to ask what eligible data is held or to raise a handling concern. We may verify your identity before responding.