Shared definitions
Terms like account data, session record and transaction log mean the same thing across privacy, terms and cookie pages. We keep one glossary internally so writers can't drift.
LEGAL REFERENCE
How hokiwin88 Handles Your Account Data
This is the hokiwin88 privacy policy — the document that explains what we collect when you open an account, how we store it, and the choices you have...
Account dataCookies & sessionsRetention windowsYour data rightsIndonesia scope
Our Privacy Posture in Indonesia
We process your personal data where local law permits and only for the purposes named in this policy: account verification, lobby access, payment routing and fraud checks. Records tied to your DANA, OVO, GoPay or QRIS transactions are stored for the retention window our supported regions require, then archived or removed. We do not sell your contact list, and we share data
with payment partners or auditors only when a transaction or compliance request makes that necessary. You can write to our privacy desk at any time to ask what we hold, request a correction, or close your account and trigger the standard deletion cycle. This policy applies to every hokiwin88 surface — web lobby, mobile pages and email touchpoints.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
SUPPORT
Privacy Contact Paths
Three direct routes reach our privacy desk. Pick whichever fits the request — data export, correction, or account closure — and our team will route it to the reviewer who owns that...
Privacy mailbox
Write to our privacy address for data export requests, correction notes, or deletion. We log every message, acknowledge within one business day, and complete most reviews inside the window local law sets.
In-lobby chat
Open the chat bubble after signing in and ask for the privacy team. The agent flags your ticket as a data request so it skips the general queue and reaches a privacy reviewer directly.
Account settings
Some changes — marketing opt-out, session preferences, contact details — you handle yourself inside account settings. Updates apply instantly and we log the timestamp against your record for audit purposes.
TRUST MARKERS
How We Keep This Policy Honest
Our privacy text is reviewed on a fixed cycle, not left to drift. Here's what sits behind the words on this page.
Named reviewers
A named privacy lead signs off every edit to this policy before it goes live. The version date at the foot of the page reflects that sign-off, not an automated stamp from the publishing tool.
Quarterly review
We re-read the full policy every quarter against changes in Indonesia data rules and our own payment partners. Edits are tracked so you can ask which clause moved and when it moved.
Plain-language rule
We rewrite any clause an outside reader finds unclear. If you email us about a sentence that reads like jargon, we log it and the next review cycle takes a pass at simplifying that section.
Payment partner audits
DANA, OVO, GoPay and QRIS routing partners run their own data audits on us. Findings feed back into this policy so what you read here matches what those partners verify behind the scenes.
Retention discipline
We hold transaction records only as long as supported regions require, then move them to cold archive or delete. Retention windows are documented internally and our reviewer can quote the exact period on request.
Breach protocol
If a data incident touches your account, we follow a written notification protocol with timelines, contact methods and remedial steps. The protocol is rehearsed twice a year, not left as a paper document.
WHY THIS PLATFORM
Consistency Across Our Policy Pages
This privacy text sits beside our terms and cookie notes. Same voice, same review cycle, same reviewer pool — so nothing contradicts when you read across pages.
Single review cycle
All policy pages refresh on the same quarterly cycle. When one updates, the others get a read-through so cross-references stay accurate and dates line up at the foot of each page.
One reviewer pool
The same small reviewer group signs off every policy page. That stops the situation where privacy says one thing and terms quietly says another about the same data point.
Matched retention text
Retention windows quoted here match the windows in our terms. If we shorten a window for one record type, both pages are edited in the same release, not weeks apart.
Aligned contact paths
The privacy mailbox, chat route and settings page are referenced identically on every legal page. You won't find a different email address tucked into the cookie notice.
Versioned footer
Every policy page carries the same footer format: version number, last reviewed date, next review date. Compare two pages side by side and the rhythm is obvious.
Indonesia scope alignment
Where this policy says supported regions, the terms page uses the same phrase. We avoid mixing legal language so you don't have to decode two different vocabularies for one rule.
SERVICE CONTEXT
What This Policy Page Shows You
The layout below mirrors how we present every legal page — same anchors, same rhythm, so you can find a clause without scrolling blindly.
01
Section anchors
Jump links sit at the head of the policy so you can land on data collection, retention or your rights without scrolling. Each anchor matches the heading text exactly for screen-reader clarity.
02
Plain summaries
Every clause opens with a one-line summary in plain language before the formal text. Skim the summaries on mobile; read the full clause on desktop when you have time.
03
Version date
The footer shows the version number and last-reviewed date. If you printed this page last quarter and want to know what changed, the date tells you whether a fresh read is worth your time.
04
Contact block
A persistent contact block stays visible as you scroll. The privacy mailbox, chat route and settings link are one tap away from any clause that prompts a question.
05
Cross-links
Where this policy touches terms or cookie behaviour, an inline link points you to the matching clause on the sibling page so you can read both sides of the same rule.
06
Mobile rhythm
Headings, summaries and clauses are sized for phone reading first. Tap targets stay generous and paragraphs stay short so the policy is readable on the same screen you use the lobby on.
Privacy Questions We Hear Often
We collect the identifiers needed to open and verify your account — name, contact details, date of birth — plus session data once you sign in. Payment routing through DANA, OVO, GoPay or QRIS adds transaction references to that record.
Account records sit live while your account is open and for the retention window supported regions require after closure. Transaction references tied to DANA, OVO, GoPay or QRIS follow the same window, then move to cold archive or deletion.
Yes. Write to the privacy mailbox with your account email and we'll compile an export of the records linked to your account. We acknowledge within one business day and complete most exports inside the local statutory window.
Small corrections — phone number, email, marketing preference — you can edit inside account settings. For identity fields like name or date of birth, message the privacy desk so a reviewer can verify the change before it takes effect.
We share only what a transaction needs. When you route through DANA, OVO, GoPay or QRIS, the partner receives the reference required to settle that payment. We do not pass marketing lists or session behaviour to payment providers.
On closure we deactivate the account immediately and move records into the retention window local law sets. After that window expires, records are deleted or anonymised. You can request earlier deletion where supported regions permit it.
Material changes trigger a notice on the policy page and, where the change affects your account directly, an email to the address on file. The footer version date moves with every edit so you can check at a glance.