Reference

Privacy Policy for Your hokiwin Account

Clear rules for account, wallet and device data are set out in the hokiwin Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet recordsDevice choicesAccess requests
hokiwin Privacy Policy for Your hokiwin Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you ask what data we hold, why it is used, or how a wallet reference appears in your account. Use the support route available from your account when a phone verification record, QRIS reference or device sign-in needs explanation. Include the email or phone detail linked to your account so we can locate the correct record without asking for unnecessary material.

Team online

Account contact

Send a privacy question through the support contact shown after sign-in. We use your account email or verified phone detail to locate the right record, then explain the relevant data purpose without requesting your wallet password or full payment credentials.

Wallet reference

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the date, amount reference and wallet name shown in your account. We can check the matching record while keeping authentication details private and separate from the support message.

Privacy request

For access, correction or deletion questions, state the action you want and the account detail we should check. We may ask for a verification step before changing records, helping prevent another person from receiving or altering your account data.

HANDLING DETAILS

What We Do With Your Data

We keep this policy practical by linking each data use to an account action you recognise. Phone verification supports account access, cookie settings shape browser sessions, and payment references help us investigate…

Account security

Phone verification helps us confirm account access before we discuss private records. Keep your login details private, sign out on shared devices, and contact support if a sign-in or verification event does not match your activity.

Cookie choices

Cookies can remember session settings and help us understand whether a sign-in page works on your device. You can adjust browser cookie controls, although removing necessary cookies may require you to verify your account again.

Payment data

For DANA, OVO, GoPay and QRIS, we use relevant references and status details to connect a payment enquiry with your account. We do not ask you to place a wallet password or full credential inside a support request.

Device signals

Browser type, device details and sign-in signals may be checked for session continuity and unusual access. On mobile, this can help us identify why a verification step repeats without treating the device signal as your wallet password.

Retention period

We retain account, support and transaction records for the period needed for the stated purpose, security checks or legal duties. When a record is no longer needed, our handling follows the deletion or anonymisation process available to us.

Request changes

You can ask to access, correct or delete eligible personal data through the privacy contact route. We may confirm your identity first, explain any legal reason a record must remain, and tell you what action was taken.

Privacy Policy Questions For Indonesia

These answers focus on the questions you may have before opening an account or sending a wallet enquiry. They summarise how the hokiwin Privacy Policy works in everyday situations, including mobile sign-in, payment references, cookie controls and requests about your personal data. If your situation is not covered, use the privacy contact route and include only the account detail needed to identify your request.

The hokiwin Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references linked with DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security steps and how you can request access or correction.

We use phone verification to confirm that the person requesting account access or private support details is connected with the account. It can also help us investigate repeated sign-in checks, while access remains subject to local law and our stated security process.

Yes, it covers the payment references and status details that reach our account records when you use DANA, OVO, GoPay or QRIS. The payment provider has its own privacy terms, so its handling of wallet data may differ from ours.

Use the privacy contact route shown in your account and ask for access to your personal data. Include the account email or verified phone detail, but not a wallet password. We may complete an identity check before releasing eligible records.

You can request a correction when an account detail, phone record or support reference is inaccurate. Tell us which field needs changing and why. We will check the request, confirm your identity when needed, and explain the result or any legal restriction.

Cookies may keep a browser session connected and preserve selected settings during account access. If you block or clear them, the mobile path may ask for verification again. Your browser controls let you manage cookies, subject to essential session functions.

We keep personal data only for the account, support, security or legal purpose that requires it. Retention can differ by record type, including payment references and verification history. You can ask us about a specific record through the privacy contact route.