Reference

Privacy Policy For Your hoki189 Account

Our Privacy Policy explains how we collect, use, protect and retain the details connected with your hoki189 account.

Account data explainedWallet details handledSecurity requests supportedCookies made clear
hoki189 Privacy Policy For Your hoki189 Account
HELP WITH REQUESTS

Privacy Questions Reach A Clear Route

A clear support route helps when your Privacy Policy question concerns a phone check, login record or wallet reference. We ask you to contact us from the email or account route connected with your hoki189 profile, so we can reduce mistaken disclosures. Include the subject of your request, the relevant account identifier and a short description of the change or access you need. Do not send a wallet PIN, password or full payment credential. Our support team can explain the next verification step before handling a privacy request.

Team online

Account privacy request

Use the account-linked support route to ask which personal details are held for your profile. We may request a phone verification step before disclosing account data, changing contact details or confirming that a request came from you.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference is attached to the wrong account activity, tell us the date, amount reference and account identifier. We use those details to investigate without asking you to share a wallet PIN.

Access and correction

For a copy, correction or removal request, send the affected field and the reason it needs attention. We check account ownership first, then explain whether the record can be changed, retained or restricted under applicable requirements.

DATA CONTROL

How hoki189 Handles Privacy Details

The Privacy Policy is built around the points where account data is actually created: phone verification, sign-in, wallet matching and support contact.

Account data

We use your account identifier, phone details and verification result to connect you with the correct profile.

Cookies and device signals

Cookies can remember session settings, while device signals help us notice unusual sign-in patterns.

Payment references

A DANA, OVO, GoPay or QRIS reference lets us connect a payment status with your account activity.

Account security

Phone verification before account access helps us distinguish the account holder from an unapproved sign-in.

Retention period

We retain account, security and payment records for the period needed to provide the requested service, resolve disputes, protect accounts…

Your contact route

You can ask what data is linked to your account, request a correction, ask about deletion or question a cookie…

Privacy Policy Questions About hoki189

These Privacy Policy answers address the account questions you are most likely to have before opening access or contacting us. We keep each answer connected to an actual hoki189 step, from phone verification and QRIS matching to cookie settings and correction requests. If your situation is different, use the account-linked support route and avoid sending passwords, PINs or complete wallet credentials. Access or eligibility depends on local law and applies where local law permits.

The Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, how long records may remain and how you can ask for access, correction or clarification.

Phone verification helps us confirm account ownership before access, recovery or a sensitive data request. It also reduces the chance that another person can change your contact details. We do not ask you to send a phone PIN, password or wallet credential through support.

Yes. The Privacy Policy covers payment references linked with DANA, OVO, GoPay and QRIS activity, including bank transfer or virtual account references. We use these records to match status and investigate errors. We do not need your private wallet password to perform that check.

You can ask for a copy or correction through the account-linked support route. State the account identifier, affected field and requested change. We confirm ownership first, then explain the next step and whether a record must remain stored for security, dispute handling or applicable requirements.

Cookies can retain session settings and help the account page recognise an active sign-in. If you block or clear them, you may need to verify your phone or sign in again. Our Privacy Policy explains this browser behaviour; device signals may still support security checks.

We keep personal, security and payment records only for the period needed for account service, investigation, dispute handling, security and applicable requirements. The exact period can differ by record type. You may ask support why a particular record remains and whether it can be removed.

Where local law permits, you can request deletion or restriction through the account-linked support route. We first verify ownership and identify the requested records. Some details may need to remain for security, payment tracing, dispute resolution or applicable requirements, and we explain that outcome.