How liontoto Handles Your Account Data
This is the liontoto privacy policy — the page that spells out what we collect when you open an account, sign into the live tables, scan a QRIS...
Privacy Posture and Jurisdiction Wording
Our policy applies to you wherever local law permits access to liontoto, with specific handling notes for supported regions in Indonesia. We collect the minimum needed to run your account: identity fields at sign-up, session logs while you browse slots or live tables, and transaction references when you fund via DANA, OVO, GoPay or QRIS. We do not sell your personal data
to third parties. Where processors are involved — payment rails, fraud screening, lobby providers — we bind them to confidentiality terms consistent with this policy. You may request access, correction or deletion of your records by contacting our privacy desk, and we respond within the windows local rules require.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths You Can Use
Privacy Inbox
Write to our privacy desk for data access, correction or deletion requests. We acknowledge within one business day and confirm what identity check is needed before we touch your account record.
In-Lobby Chat
Open the chat bubble inside your account area and tag the message as a privacy matter. Our agents route it to the policy handler instead of the general support queue so nothing gets lost.
Formal Notice
For legal notices tied to this policy, send a written letter to the registered address on file. Include your account reference so we can pair the notice with the right data record quickly.
How We Review This Policy
Quarterly Review
Our policy team re-reads this page every quarter and after any change to how the lobby, sportsbook or payment rails handle your data. Stale wording is replaced before it sits on the site.
Named Owner
A named privacy lead signs off each revision. That person is the one your inbox messages reach, so the desk replying to you is the same desk writing the policy.
Processor Audits
We check our payment processors and lobby providers against the confidentiality terms in this policy. Where a partner falls short, we either fix the gap or remove the integration from the account flow.
Plain Wording
We write the policy in the same English you read across the rest of liontoto. No buried clauses, no nested cross-references that send you chasing definitions across five different pages.
Change Log
Every material edit is dated at the foot of the page. You can see what shifted, when, and decide whether you need to re-read a section before your next session.
Local Counsel
Indonesian-aware counsel reviews the wording for supported regions so the policy reads correctly against the rules that actually apply to your account, not a generic global template.
Consistency Across Our Policy Pages
| Scope | This privacy page covers account and session data only. Cookie handling, terms of service and payout rules live on their own pages and are linked from the footer. |
|---|---|
| Definitions | Terms like account, session, processor and identity field carry the same meaning here as on our terms page. We do not redefine them per document. |
| Retention | Retention windows quoted here match the windows quoted on the account-closure page. If you close your account, the same clock applies in both places. |
| Contact | The privacy inbox listed on this page is the same one referenced in our terms and cookie notices. One desk, one queue, one response timeline. |
| Jurisdiction | Where local law permits language appears identically on every legal page. We do not loosen it for marketing pages and tighten it only on legal pages. |
| Updates | Revision dates roll out together. When this policy is reviewed, the sibling legal pages get the same date check so nothing drifts out of sync. |
| Tone | Plain English on this page, plain English on the others. You should never need to switch reading modes between our privacy, terms and cookie pages. |
What This Policy Page Actually Shows
Scope Block
A short upfront statement of what the policy covers — account creation, lobby sessions, sportsbook activity, transaction references — so you know within ten seconds whether your question belongs on this page.
Data Categories
A clean list of the data we actually hold: identifiers, contact fields, session metadata and payment references. No vague catch-all phrases that could mean anything we feel like collecting later.
Your Rights
A dedicated block on access, correction, deletion and objection rights, plus the exact route to exercise each one. You should not have to dig for the contact path.
Processor Map
Categories of third parties we share data with — payment, fraud, lobby providers — described by function rather than buried as a long company name list you cannot parse.
Retention Notes
How long each data category sits on our side, written in months and years rather than vague phrases like as long as necessary. You can plan around real numbers.
Revision Stamp
A visible last-reviewed date at the foot of the page so you can check whether the version you are reading is current before you act on it.