Terms of Service
The terms page covers account conduct and lobby rules; this page covers data only. Cross-references between the two are linked so you don't have to hunt for the matching clause.
This is the prabu99 privacy policy — the page that explains what we collect when you open an account, browse our live tables, scan slot rooms or check...
We collect the details you give us at sign-up — name, contact, date of birth — plus session signals like device type and lobby activity. Where local law permits, we store this data on servers configured for Indonesia traffic and we only share it with payment processors when you choose DANA, OVO, GoPay or QRIS to move funds. We don't sell your
data to third-party marketers. You can ask us to export your record, correct a field, or close the account; we'll action the request inside the window our jurisdiction sets. Cookies are used to keep your session warm and remember the lobby tab you left on. Decline non-essential cookies any time from the footer toggle, and the core lobby still loads.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach our privacy desk through any of the routes below.
Editorial trust signals behind every clause on this page.
Our legal counsel reviews this policy on a rolling schedule and after any change to Indonesia data-handling rules, so the wording you read matches the practice running inside our systems.
A named data protection lead signs off every revision. That person is reachable through the privacy inbox and owns the response when you raise a formal complaint.
Every meaningful edit to this page is dated at the bottom. You can see what moved, when it moved, and whether the change affected your consent or our retention windows.
We rewrite legalese into sentences you can scan in one read. If a clause still feels dense, tell the privacy desk and we'll clarify it in the next published revision.
Payment partners handling DANA, OVO, GoPay and QRIS flows are audited for their own data posture before we connect them. We drop integrations that fail our review.
If a data incident ever touches your account, we follow a documented notification protocol — email first, in-product banner second — within the timeline regulators require.
How this page lines up with our other legal documents.
The terms page covers account conduct and lobby rules; this page covers data only. Cross-references between the two are linked so you don't have to hunt for the matching clause.
The cookie notice expands what we summarise here — exact cookie names, vendors and lifespans — and uses the same consent toggle wired into your account footer.
Our anti-money-laundering statement explains why we verify identity; this privacy policy explains how that verification data is then stored and eventually purged.
The payments notice describes DANA, OVO, GoPay and QRIS flows operationally; here we cover only the personal data those flows generate on our side.
Marketing preferences live in your account panel. This policy explains the legal basis; the panel itself is where the toggles actually save your choice.
The complaints page sets out escalation steps. Privacy complaints follow the same ladder but route to the data protection lead named in this document.
Our retention schedule is published as an appendix. Each data category in this policy maps to a row in that schedule so the window is never ambiguous.
Visible elements that shape how the policy reads on screen.