Terms of Service
Account-creation language here mirrors the registration clauses in our terms, so the data we describe collecting is exactly what the terms authorise us to process.
This is the privacy policy for nagabet88. We wrote it so you know exactly what we collect when you open an account, browse the slot rooms, place a...
We process your account data where local law permits and only inside supported regions. When you register, we record identifiers needed to verify you, fund your wallet and pay you back: name, contact channel, device fingerprint, session logs and the e-wallet reference tied to your top-ups. We don't sell your data to third parties. We share it only with payment partners that
settle DANA, OVO, GoPay and QRIS movements, and with regulators when a lawful request reaches us. Retention follows the minimum window our jurisdiction requires, after which records are anonymised. You can ask us to export, correct or erase your file, and we'll confirm action within a reasonable response window.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If something in this policy needs clarifying, or you want to exercise a data right, reach us through any of the channels below. Our privacy desk handles these requests separately from general account help, so your message lands with the right person.
Email our data desk directly with your account reference and the request type — export, correction or erasure. We acknowledge within one working day and resolve inside the window our jurisdiction sets.
Open the in-lobby chat and ask for the privacy queue. The agent tags your ticket so it routes past general support and lands with the team that owns data subject responses.
Inside your account panel you can review the contact details we hold, refresh your verification reference and toggle marketing consent without writing to us at all.
This policy isn't a copy-paste from a template. Here's how we keep it honest and current.
Our compliance team re-reads the full policy every quarter and after any product change. If a clause shifts, we date-stamp the section so you can see what moved and when it took effect.
The wording is drafted by the team that actually runs the lobby, not outsourced. That keeps the language matched to how data really flows through registration, deposits and withdrawals on nagabet88.
Clauses about retention, sharing and lawful basis are mapped to the rules covering supported regions in Indonesia. Where local law tightens, the stricter version applies to your record automatically.
We avoid jargon where we can. If a legal term is unavoidable, we explain it inline so you don't need a separate dictionary tab open while reading through the clauses.
Every revision is logged with a version tag and date. Material changes trigger a notice on your next sign-in so you can re-read before continuing to use your account.
An external counsel reviews substantive amendments before they go live. That second pair of eyes catches drift between what we wrote and what our systems actually do day to day.
This page sits alongside our terms, cookie notice and KYC pages. Here's how the wording lines up so nothing contradicts.
Account-creation language here mirrors the registration clauses in our terms, so the data we describe collecting is exactly what the terms authorise us to process.
Tracking technologies sit in the cookie notice; this policy points there rather than duplicating it, keeping each document focused on its own scope.
Verification data described here matches the KYC document categories listed on the identity page, with the same retention windows applied across both.
Lawful-basis references for transaction monitoring align with the AML page, so deposit and withdrawal records are explained the same way in both places.
Opt-in language used here repeats verbatim on the preferences screen, meaning what you tick in-app matches what this policy commits us to.
Retention of payout records noted in this policy matches the timeframe stated on the withdrawal page, including DANA, OVO, GoPay and QRIS settlement logs.
Escalation routes named here are the same ones documented in our complaints flow, so a privacy ticket and a service ticket follow parallel, predictable steps.
To make the policy easy to scan, the page is laid out around fixed elements you can jump between. Here's what you'll find as you scroll.