LEGAL REFERENCE

How relaxtoto Handles Your Account Data

This is the relaxtoto privacy policy, written for you in plain language. We explain what we collect when you open an account, why we store it, and how...

Plain-language policyIndonesia-awareAccount-scoped dataUpdated regularlyReader-friendly
Tour the Lobby Read FAQ
relaxtoto How relaxtoto Handles Your Account Data

Our Privacy Posture and Your Rights

relaxtoto processes your personal data only where local law permits and only for supported regions across Indonesia. We collect what's needed to run your account: identity fields you submit at sign-up, device and session signals, and transaction references tied to your e-wallet activity. We don't sell your data to third parties. Where you ask us to correct, export or remove information, we

action the request inside the windows our policy commits to. Data retention follows financial-record rules in your jurisdiction, and any cross-border processing is logged. The chips below show the wallet contexts most often referenced inside your account record.

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

24/7 SUPPORT

Privacy Contact Paths You Can Use

If you have a privacy question, here's how to reach the team that owns this policy. Each channel routes straight to a...

Privacy Inbox Email our privacy desk for access, correction or...
In-Account Form Open your account settings and use the privacy...
Live Chat Escalation Start a chat from the lobby, ask for...
TRUST MARKERS

How We Keep This Policy Honest

Trust signals around this document — who reviews it, when it changes, and how we keep it aligned with the way the lobby actually works.

Quarterly Review

Our compliance team re-reads the privacy policy every quarter against current product behaviour. If the lobby starts collecting a new signal, this document is updated before the change reaches your account.

Versioned Edits

Every edit to the policy is versioned with a date stamp at the foot of the page. You can see exactly when wording changed and what section moved, without digging through archives.

Plain-Language Pledge

We write this policy the way we'd explain it to you in chat. No legal cosplay, no buried clauses — if a sentence is hard to read, we rewrite it at the next review.

Indonesia-Aware Drafting

The policy is drafted with Indonesian data-handling expectations in mind, including how DANA, OVO, GoPay and QRIS references show up inside your account ledger and transaction logs.

Independent Sign-Off

A privacy lead outside the product team signs off each version. That separation keeps marketing pressure away from how we describe data flows on this page.

Reader Feedback Loop

If a clause confuses you, tell us through the privacy inbox. We log every comment and many of our clearer rewrites started as one reader saying a sentence didn't land.

Consistency Across Our Policy Pages

How this privacy policy lines up with our other legal documents so nothing contradicts.

Terms of Service
The terms govern the contract; this policy governs your data. Where the two touch — like account closure — we use the same wording so the rules read as one.
Cookie Policy
Cookies and similar signals are summarised here and detailed in the cookie page. Both documents share a single retention table, updated together at every review.
AML Policy
Anti-money-laundering checks generate data this policy covers. We cross-link the two so you see why an identity field is held and for how long.
KYC Notice
The KYC notice describes verification steps; this policy describes what happens to documents afterwards. Retention windows match exactly across both pages.
Marketing Preferences
Opt-in choices live in your account settings, but the legal basis for sending messages is described here. Withdrawing consent is one click and reflected immediately.
Complaints Procedure
Privacy complaints follow the same escalation tiers as our general complaints page, with a dedicated privacy lead at the second tier instead of a product manager.
Security Statement
Our security page explains controls; this policy explains data scope. Together they describe both what we hold and how it's protected, without overlap or contradiction.
PLATFORM SNAPSHOT

What Defines This Policy Page Layout

The visible elements that shape how you read this privacy policy — designed so the document is scannable on a phone and complete on desktop.

01
Anchored Sections Each policy topic has a stable anchor link, so you can share a direct line to a specific clause with support without forcing the reader to scroll the whole document.
02
Last-Updated Stamp A clear date appears near the top of the policy. You always know which version you're reading and whether the clauses match the screenshots in any earlier conversation.
03
Defined Terms Block Words like account, processing and retention are defined once at the top and used consistently below. Definitions sit in a collapsible block to keep the page light.
04
Inline Examples Where a clause could be abstract, we add a short example tied to the lobby — what data a slot session writes versus what a sportsbook bet writes — so the rule feels concrete.
05
Mobile-First Spacing Paragraphs are sized for one-thumb reading. The policy is the same length on phone and desktop, but the spacing changes so nothing turns into a wall of text.
06
Change Log Footer At the foot of the policy, a short change log lists what moved between versions. You can audit the document's history without contacting us, which keeps the process honest.

Privacy Policy Questions We Hear Often

We collect the identity fields needed for account creation, device and session signals during use, and transaction references tied to your e-wallet activity. Nothing outside that scope is recorded against your profile under this policy.

Retention follows financial-record rules in your jurisdiction, typically several years for transaction logs. Identity copies are removed sooner where law permits. The exact windows are listed in the retention table inside this policy.

Yes. Submit a request through the in-account privacy form or our privacy inbox. We verify your identity, compile the export, and deliver it within the window this policy commits to for access requests.

We don't sell your data. We share it only with processors needed to run the lobby, payments and compliance checks, under contract. Each category of recipient is named in the disclosures section of this policy.

Wallet references appear inside your transaction ledger as identifiers, not as full credentials. We store what's needed to reconcile a deposit or withdrawal and nothing more, in line with payment-processor requirements.

Material changes are announced inside your account and dated on this page. The change log at the foot lists what moved. If a change expands data use, we ask for fresh consent where law requires it.

Escalate through the complaints procedure. A privacy lead outside the product team handles tier-two reviews. If you remain unsatisfied, the policy lists the supervisory authority relevant to supported regions in Indonesia.