vs Terms of Service
The terms reference this policy for any account-data clause. If a definition appears in both, this privacy document is the controlling text for data handling specifically.
This is the hola88 privacy policy. We wrote it so you can see, in plain language, what account information we collect when you open a lobby session with...
We collect only what's needed to run your hola88 account: identity fields you submit at signup, device and session signals, transaction references tied to your wallet top-ups, and the lobby actions you take with us. Where local law permits in Indonesia, we process this data to verify you, prevent fraud on your account, and keep balances accurate. We don't sell your information
to third parties. You can ask us to export, correct or delete the records we hold, and we'll respond inside the windows our supported regions require. Wallet identifiers tied to DANA, OVO, GoPay or QRIS are encrypted at rest and shared only with the payment processor handling that specific transaction.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This policy isn't a static document we forgot about. We review it on a fixed cadence and whenever the lobby, our payment rails, or Indonesian data rules shift. Here's how the editorial...
Our compliance team re-reads every clause each quarter and dates the page when anything changes. If we adjust how we handle wallet identifiers or session logs, you'll see it reflected at the top of the document.
Counsel familiar with Indonesian data protection signs off before any policy edit goes live. We don't ship privacy changes through marketing alone — they pass through the same review your account agreements do.
Every revision goes through a plain-language pass so the policy stays readable. If a clause needs a glossary term, we add the explanation inline rather than burying it in a separate annex.
We keep a visible change log at the foot of this page. You can scan what shifted between versions without diffing the whole document, which matters when you're tracking how your data flows.
Twice a year we audit the actual data map against this policy text. If reality has drifted from the document, the document gets corrected the same week — not the policy stretched to fit.
Every processor we share data with — payment rails, KYC providers, hosting — gets reviewed annually. Their handling of your hola88 account information must match the commitments we make to you here.
We publish several legal pages — terms, cookie notice, KYC policy, complaints procedure. They need to agree with each other. Here's how this privacy policy lines up with its siblings so you...
The terms reference this policy for any account-data clause. If a definition appears in both, this privacy document is the controlling text for data handling specifically.
Cookies and similar trackers are scoped in the cookie notice. This policy covers the broader account data; together they describe the full picture of what we observe in a session.
KYC details which identity documents we collect at verification. This page covers what happens to those documents afterwards — retention, access, deletion windows.
If you escalate a privacy issue, the complaints page lists the timeline. This policy lists the substance of the right you're exercising. They're meant to be read side by side.
Promotion-specific data — eligibility flags, opt-in records — is mentioned in promo terms. This policy explains the underlying handling of those flags on your account.
Wallet-side disclosures cover how DANA, OVO, GoPay and QRIS process payment data on their end. This policy covers our slice — what we receive, store and reference.
Marketing settings live in your account dashboard. This policy explains the legal basis for each channel and how withdrawing consent flows through to our systems.
This page is structured so you can find a clause without reading the whole thing. Here are the elements we deliberately built into the privacy-side layout, and why...