Data scope
Privacy policy lists every category we hold; cookies notice narrows down to browser storage; terms reference both without restating them.
LEGAL REFERENCE
How laris888 Handles Your Account Data
This is our privacy policy page, written so you know exactly what we collect when you open an account with laris888 and step into the lobby. We cover...
Account dataSession logsPayment referencesCookiesIndonesia
Our Privacy Posture in Plain Language
We collect what's needed to run your account: your sign-in identifiers, device fingerprints from the sessions you open, and the transaction references your e-wallet sends back to us. Where local law permits, we retain those records for the period Indonesian financial and gaming rules require, then we purge them. We don't sell your data to outside marketers. Sub-processors who help us —
payment routers for DANA, OVO, GoPay and QRIS, hosting partners, fraud screens — see only the slice of data their job needs. You can ask us what we hold, ask us to correct it, or ask us to close the file when your account closes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
TRUST MARKERS
Editorial Checks Behind This Policy
This document is reviewed before it reaches you. Here's who touches it and why we keep that loop tight.
Legal review
Our retained Indonesian counsel reads every change to this policy before it ships. They check it against current personal data...
Quarterly refresh
We re-read the full policy every three months even when nothing has changed, so stale wording doesn't drift past sub-processor...
Version history
Each published version carries a date stamp at the foot of the page. Earlier versions are kept on file and...
Named owner
A single data protection contact owns this page internally. That person signs off on wording, sub-processor lists and retention windows...
Plain wording
We rewrite legal phrasing into sentences you can actually read. If a clause needs jargon to stay accurate, we add...
Reader feedback
When a reader tells us a section is unclear, we log the comment and review it at the next refresh...
WHY THIS PLATFORM
Consistency Across Our Policy Pages
Our privacy policy, cookies notice and terms page all sit in the same family. Here's how they line up so you don't get conflicting answers.
Retention windows
All three pages quote identical retention periods so a closed account behaves the same way regardless of which document you read first.
Sub-processor list
The roster of payment, hosting and fraud partners is mirrored across pages. Adding one updates every document in the same release.
Contact channel
Privacy email, in-app chat and postal address appear consistently so you don't chase a dead inbox quoted on a stale page.
Jurisdiction wording
Each page uses the same 'where local law permits' framing for Indonesia rather than mixing region-specific phrasing that could contradict itself.
Update cadence
Quarterly review touches every legal page in the same sprint, keeping version dates aligned across privacy, cookies and terms.
Reader rights
Access, correction, deletion and portability rights are described identically wherever they appear, with the same response timelines quoted.
AT A GLANCE
What This Policy Page Shows You
These are the building blocks you'll see on this privacy page itself, so you can find what you need without scrolling the whole document.
01
Data table
A clear breakdown of every field we collect at sign-up, during sessions, and at cash-in or cash-out, grouped so you can scan the categories without reading paragraphs.
02
Retention chart
A short timeline showing how long each data category stays with us before it's purged or anonymised, with the legal reason next to each row.
03
Rights panel
A side block listing your access, correction and deletion rights with the exact request channel for each one, so you don't need to read the full policy to act.
04
Sub-processor roster
A named list of the partners that touch your data, what they do for us, and which region their servers sit in, refreshed whenever a partner changes.
05
Change log
A dated entry for every revision of this policy, with a one-line note describing what moved, so returning readers can spot updates fast.
06
Glossary chip
Short definitions for the few legal terms we couldn't avoid, anchored next to the paragraph that uses them so you don't lose your place.
Privacy Questions We Hear Most
We hold your sign-in identifiers, verified contact details, device and session metadata, and the payment references your e-wallet returns. The full category list sits in the data table earlier on this page, grouped by purpose.
Account records are kept for the retention window Indonesian gaming and financial rules require, then anonymised or purged. The exact period for each category appears in the retention chart on this page.
Yes. Email our privacy inbox from your registered address with a short request and we'll send a structured export within seven working days. We'll verify it's you before we release anything.
No. We don't sell or rent your data. The only third parties that see fragments of it are sub-processors helping us run payments, hosting and fraud screens, and they're bound by written terms.
We pass the minimum routing data your e-wallet needs to confirm the transaction, then store the reference number on our side. Card-style numbers and wallet PINs never reach our servers.
We post the new version with a fresh date and log the change in the version history at the foot of the page. Material changes trigger an in-app notice the next time you sign in.
Write to our privacy inbox or open the in-app chat and tag it as a privacy matter. Reader feedback often becomes wording changes at the next quarterly refresh cycle.