Definitions Match
Terms like 'account', 'session' and 'wallet reference' carry the same meaning here as on our terms page, so cross-reading never leaves you guessing what we meant.
This is the rayaselot privacy policy — a plain page about what we collect when you open an account, how we keep it, and what stays private. We...
We collect only what your account needs to work: your sign-up details, device fingerprint, lobby session logs, and the wallet reference you link for DANA, OVO, GoPay or QRIS top-ups. Where local law permits, we keep this on encrypted servers, share it strictly with the licensed processors who run our payment rails, and never sell it on. You can ask us to
export or erase your record at any time, and we'll action that request within the windows our jurisdiction sets out. This privacy notice applies across supported regions of Indonesia and updates when our handling practices change — we'll flag the date at the top of the page so you always see the current version.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If anything in this policy needs clarifying, or you want to action a data request, reach us through one of the channels below. We answer privacy queries on the same desk that handles account recovery, so you'll get a human, not a script.
Email our data desk directly with your account handle and we'll respond within two working days. Use this for export, correction or erasure requests tied to your rayaselot profile.
Open the chat bubble inside your account dashboard and ask for the privacy team. The agent will route your ticket and log it against your file so nothing gets lost in handover.
For formal data correspondence we accept letters at our registered processing address, listed in the footer. Include your username so we can match the request to the right account record.
This document isn't static. We re-read it on a schedule and after any change to how the lobby handles your details, so the wording you see matches what actually happens on the...
Our compliance lead re-reads every clause each quarter, checks it against current Indonesia data practice, and signs off the published version before it goes live on the site.
A single data protection contact owns this policy end-to-end. That means your queries land with someone accountable, not a shared mailbox that nobody monitors closely.
We write each clause in second-person English so you can read it without a legal dictionary. Where a technical term is unavoidable, we explain it in the same paragraph.
Every change carries a date stamp at the top of the page. Older revisions stay archived so you can see exactly what shifted and when it took effect.
An external counsel reviews substantive edits before publication. Their notes feed back into the draft so the language reflects current statute, not last year's interpretation.
If you flag a clause as unclear through the privacy inbox, we log it and address it in the next revision. Real reader questions shape how we phrase the tricky bits.
This privacy policy sits alongside our terms, cookie notice and account rules. We keep the wording consistent across all of them so nothing contradicts when you read them side by side.
Terms like 'account', 'session' and 'wallet reference' carry the same meaning here as on our terms page, so cross-reading never leaves you guessing what we meant.
Privacy, terms and cookies all refresh on the same quarterly cadence, which keeps version numbers aligned and avoids gaps where one page lags behind the others.
The inbox handling privacy requests also covers terms queries and account closures, so you don't get bounced between teams when a question touches more than one document.
How long we hold your data here matches the retention windows quoted in the account rules, with no hidden longer storage tucked into a sister page.
Every legal page references the same supported regions and the same governing framework, so enforcement language never drifts between privacy and terms.
Where the cookie notice talks about tracking, this policy uses the identical phrasing, which makes audits cleaner and your reading experience less confusing.
All superseded versions of every legal document live in one archive folder, accessible on request, so historical comparison stays straightforward.
Beyond the clauses themselves, a few design choices define how this page reads and behaves. We've called them out so you know what to expect when you scroll...