Scope
Privacy covers account data; terms cover account conduct. We mirror definitions across both so a word means the same thing in either document.
This is the rodaslot privacy policy page, written for the account you open with us in Indonesia. We explain what we collect when you sign up, how we...
We process your data where local law permits and only inside the supported regions our licence covers. When you register, we collect the identifiers needed to run a real-money account: name, contact channel, device fingerprint and the e-wallet reference linked to your deposits. Transaction data is retained for the period our regulator requires, then aged out. We do not sell your records
to third parties, and marketing consent is opt-in at the account level. If a request comes from an authority with jurisdiction over your account, we comply within the bounds of Indonesian data protection rules and notify you where the law allows it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our privacy text is not a copy-paste template. It passes through the checks below before anything reaches your screen.
Indonesian-qualified counsel reviews each clause against current data protection rules before publication. Edits are versioned, dated and stored so we can show you exactly what changed between releases.
Our internal data protection officer signs every revision and owns the response queue. Their name and contact route are recorded on the policy log we keep for regulator inspection.
Third-party penetration testers check the storage layer that holds your KYC documents and wallet identifiers. Findings feed back into the policy when they affect what we tell you about retention.
An editor strips legal jargon so the clauses read the way you actually speak. If a sentence needs a glossary, we rewrite it instead of footnoting it.
Every published edition is archived with a timestamp. You can request the previous version that applied while your account was active and we will send the exact text on file.
Marketing, analytics and personalisation consents each carry their own switch in your account. The ledger records what you toggled and when, so disputes resolve from your record, not ours.
This page sits alongside our terms, cookie notice and KYC clauses. The table below shows how the privacy policy lines up with its siblings so you do not get conflicting wording.
Privacy covers account data; terms cover account conduct. We mirror definitions across both so a word means the same thing in either document.
Retention windows here match the periods named in our KYC notice. If one moves, both move in the same release cycle.
Tracker categories and vendor names align with the cookie banner. Toggling a banner choice updates the consent ledger this policy describes.
The privacy inbox listed here is the same address printed on terms and KYC. One queue, one owner, one response window.
Governing law clauses are identical to those in terms. Disputes route through the same Indonesian forum named in both texts.
Version numbers increment together when a change touches more than one document, so cross-references never point at stale clauses.
All sibling pages are published in the same en-ID register. Translations, when offered, carry the English version as the controlling text.
These are the visible elements that shape how the privacy text is laid out and how you move through it.