Reference

Privacy Policy for Your hoki62 Account

Your account setup, DANA, OVO, GoPay and QRIS wallet records, cookies and device checks are covered in this Privacy Policy before you open the lobby.

Account data scopeDANA OVO GoPay QRISCookie choicesDevice security logs
hoki62 Privacy Policy for Your hoki62 Account
CONTACT ROUTES

Three Privacy Contact Paths

Privacy requests work better when they arrive through a channel we can attach to your account record. We give you live chat, a Help Center privacy form and an account ticket path, so you can ask for access, correction, deletion or cookie help without sharing wallet secrets. Our team handles these requests daily from 09:00 to 01:00 WIB and may ask for account ID plus one safe verification step.

Team online

Live chat

Use live chat from 09:00 to 01:00 WIB when a privacy question is tied to a login, device alert or wallet record. We may ask for your account ID before discussing DANA, OVO, GoPay or QRIS entries.

Privacy form

Send a message through the privacy form inside Help Center when you want a copy, correction or deletion request recorded. Include the phone number on your account, not your full wallet PIN.

Account ticket

Open an account ticket from Profile > Help when you need a dated trail for a privacy case. We keep the ticket thread connected to your account so the next agent sees the same request history.

ACCOUNT SAFETY

Six Ways We Protect Your Data

We treat the Privacy Policy as an operating rule, not a footer link. Your data moves through account creation, wallet checks, cookies, game-session records and support messages, so…

Account collection

When you open an account, we collect the phone number, username, password hash, verification status and referral source needed to…

Payment records

DANA, OVO, GoPay and QRIS entries are stored as masked references, timestamps, status codes and amount fields.

Cookie choices

Cookies help keep you signed in, remember language settings and measure session errors.

Device access

We log device type, browser, IP range and sign-in time so we can flag unusual access.

Game-session records

Session records may show that you opened Live Roulette, Aviator or Aztec Gems, plus time, stake reference and result status.

Retention requests

Some records must stay while a withdrawal check, dispute or legal duty is active.

Privacy Questions You May Ask

These answers cover the privacy points we hear most from Indonesia account holders before and after sign-in. They explain what we collect, how payment and device records are handled, how to make a request, and when data may stay in our systems because of security, wallet checks or legal duties.

We collect your phone number, username, password hash, sign-up time, device type and verification status. If you add wallet activity later, we store masked DANA, OVO, GoPay or QRIS references linked to your account.

No. We do not need your full wallet PIN to check a payment record. We store transaction references, status results and timestamps, while support may ask for a receipt image with sensitive parts hidden.

Sign in, open Profile > Help, and choose the privacy request option. We may confirm your phone number or recent login detail before sending account data, because we must make sure the request is yours.

Yes. Send the correction request through live chat or the privacy form and state the field that needs fixing. For payment-related fields, we may compare your request with DANA, OVO, GoPay or QRIS records.

Device and IP logs help us detect unusual access, failed sign-in patterns and account sharing risks. You can view device activity from Profile > Security > Devices and remove a session you do not recognise.

You can request deletion, and we will remove eligible data after account checks are complete. Some records may stay longer where local law permits, especially payment records, dispute trails and security logs.

Only trained support and account-security staff should handle privacy cases. Your ticket is linked to your account history, and we mask wallet details so the team can answer without seeing full payment credentials.