LEGAL REFERENCE

How We Handle Your Account Data

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...

Account dataCookie useIndonesia-alignedPlain wordingLast updated
rayaselot How We Handle Your Account Data

Our Privacy Posture & Data Scope

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

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.

Team online

Privacy Inbox

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.

Live Chat Desk

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.

Postal Notice

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.

REVIEW SIGNALS

How We Review This Policy

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...

Quarterly Review

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.

Named Owner

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.

Plain Wording

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.

Versioned Edits

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.

Independent Check

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.

Reader Feedback

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.

WHY THIS PLATFORM

Consistency Across Our Legal Pages

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.

01

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.

02

Same Update Cycle

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.

03

Shared Contact Desk

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.

04

Aligned Retention

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.

05

Unified Jurisdiction

Every legal page references the same supported regions and the same governing framework, so enforcement language never drifts between privacy and terms.

06

Mirror Language

Where the cookie notice talks about tracking, this policy uses the identical phrasing, which makes audits cleaner and your reading experience less confusing.

07

Single Archive

All superseded versions of every legal document live in one archive folder, accessible on request, so historical comparison stays straightforward.

QUICK SIGNAL

What Shapes This Policy Page

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...

Date Stamp Header The current revision date sits at the top of the...
Section Anchors Each clause has a deep link, which means you can...
Mobile Scannability We've kept paragraphs short and headings frequent so the policy...
Search-Friendly Layout Use your browser's find function and key terms like 'retention'...
Change Log Link A footer link opens the archive of past versions, so...
Indonesia Framing References, examples and timelines are written for Indonesia-based account holders...

Privacy Questions We Hear Often

We hold your sign-up name, email, phone, device fingerprint, session logs and the linked wallet reference for DANA, OVO, GoPay or QRIS. Nothing beyond what your lobby session and payouts strictly need.

Yes. Send an erasure request from the email tied to your account and we'll action it within the window our jurisdiction allows, keeping only the minimum records statute requires us to retain.

Only with the licensed processors who run our payment rails and identity checks. They sign data agreements with us, use your details strictly for that task, and never receive your data for marketing.

Active account data stays while your profile is open. After closure we retain the minimum legal record for the period our jurisdiction specifies, then purge the rest from live and backup systems.

Cookie handling has its own dedicated notice, but this policy explains how the data those cookies generate flows into your account record. Read the two together for the full picture of tracking.

The revision date at the top of the page updates whenever we edit a clause. For substantive changes we also email registered account holders before the new version takes effect.

Start with our privacy inbox so we can try to resolve it directly. If you're not satisfied, you can escalate to the relevant data authority for your supported region within Indonesia.