Reference

hoki70 Privacy Policy, Clearly Explained

hoki70 Privacy Policy shows how we collect, use and protect details linked to your account, device and wallet activity.

Account dataWallet referencesCookie choicesAccess requests
hoki70 hoki70 Privacy Policy, Clearly Explained
CONTACT ROUTES

Where To Ask About Privacy

A clear contact path helps you resolve a data question without sending sensitive wallet details into the wrong place. Start from the support or contact route shown in your account area and describe the request in plain English. Include the account phone number only when the form asks for it, and never include a DANA, OVO or GoPay PIN. We use the same account checks for requests from Jakarta and other Indonesian locations.

Team online

Account support route

Use the support link inside your signed-in account for a privacy request tied to your login. We may ask for phone verification before discussing account data or changing contact details.

Contact request

For a question before access, use the contact route displayed on our site. State whether you need access, correction, deletion or cookie help so we can send the request to the right team.

Payment reference check

If your request concerns QRIS, bank transfer or virtual account records, share the transaction reference requested by support. Do not send wallet passwords, PINs or one-time verification codes.

DATA PRACTICES

How We Handle Your Account Data

Privacy controls work best when each account step has a defined purpose. We use information to authenticate access, protect the account, respond to requests and reconcile payment references, not to collect wallet…

Account details

We may store your name, phone number, login events and verification status to connect you with the correct account. Keeping these details accurate helps us respond to access and correction requests.

Wallet references

DANA, OVO, GoPay and QRIS may appear as payment references linked to an account action. We use those references to trace status and do not ask for your wallet PIN.

Device security

Browser type, device signals, IP-related records and login timing can help us detect unusual access. If a sign-in looks unfamiliar, we may request phone verification before restoring account access.

Cookies

Cookies can keep a session active, remember selected settings and show whether a page loads correctly. You can manage cookie permissions through your browser, although some account functions may then need to be repeated.

Retention choices

We retain records only for the period needed for account operation, security checks, dispute handling or legal duties. A deletion request may not remove records that must be preserved for those reasons.

Change requests

Ask us to access, correct or delete eligible personal data through the account support route. We verify the requester first, explain the result, and contact you through the details attached to the account.

Privacy Policy Questions For hoki70

These answers address the searches we most often expect before an account is opened or a wallet status is checked. They explain what the Privacy Policy means in practical terms, including account verification, cookies, payment references, data requests and access conditions. If your situation is not covered, use the contact route shown on the site and avoid sending secret wallet credentials.

It explains how we collect, use, secure and retain account, device, cookie, support and payment-reference data. It also sets out how you can request access, correction or deletion.

Phone verification helps connect a request or login to the right account and helps us respond to unusual access. We may require it before discussing account details or changing contact data.

Yes. The policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use status and reconciliation details, not your wallet PIN.

Use the signed-in account support route and ask for a data access request. We verify your account connection, locate eligible records, and explain any information that cannot be released.

Yes. Send a correction request through account support, identify the field that needs updating, and complete any requested verification. We will confirm the outcome through your account contact details.

Cookies can support login sessions, saved settings and page performance checks. Your browser controls can block or remove them, but account pages may ask you to repeat some steps.

Access and eligibility depend on local law. Before opening an account, check the rules that apply to your location and use the site only where local law permits.