How We Handle Your Account Data
This is the rembotogel privacy policy — the page that spells out what we collect when you open an account, why we keep it, and how long it...
Policy Posture and Supported Regions
We collect only what your account actually needs: your sign-in identifier, a hashed password, the wallet reference you use to top up, and session logs tied to fraud checks. Where local law permits, we retain transactional records for the period your jurisdiction requires, then purge them on a rolling schedule. Marketing consent is separate from account consent — you can withdraw one
without closing the other. Payment metadata from DANA, OVO, GoPay and QRIS is tokenised before it touches our analytics layer, and we never store the full instrument on our side.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
Data Requests Inbox
Email our privacy desk to request an export of what we hold on your account. We acknowledge within one business day and return the file inside the window your jurisdiction sets for data access.
In-App Privacy Chat
Open the chat panel from your account header and pick the privacy topic. The handler routes you to a reviewer who can action consent changes, opt-outs and marketing preferences without escalating.
Erasure Hotline
If you want your account closed and personal fields scrubbed, our erasure line handles the request end-to-end. We confirm in writing once retention-locked records have aged out under local law.
Editorial Trust Signals for This Policy
Reviewed Quarterly
Our compliance team revisits this policy every quarter and flags wording that drifted from current practice. Version notes sit at...
Plain-Language Drafting
We strip out boilerplate that doesn't apply to your account and rewrite anything that needs a law degree to parse...
Named Data Owner
A named privacy lead signs off each revision. Internal teams cannot ship changes that touch your personal fields without that...
Tokenised Payment Trail
Wallet references from DANA, OVO, GoPay and QRIS never reach our reporting stack in raw form. Tokens replace the originals...
Retention Clocks
Every personal field has a retention clock attached. When the clock expires under your jurisdiction's rules, the field is purged...
Third-Party Register
We maintain a register of every processor that touches your data and the contractual purpose. You can request the current...
Consistency Across Our Policy Pages
| Privacy vs Terms | This page covers data handling only. Account rules, wagering conditions and dispute steps live on our terms page so each document stays focused on a single subject. |
|---|---|
| Privacy vs Cookies | Cookie behaviour has its own notice with the granular toggles. Here we summarise the categories so you know what feeds back into your account profile. |
| Privacy vs KYC | Identity verification has dedicated wording. This policy explains where verified fields land and how long they sit before retention rules clear them. |
| Privacy vs Marketing | Marketing consent is opt-in and separately logged. Withdrawing it does not affect your ability to keep using the lobby with the same account credentials. |
| Privacy vs Payments | Payment processors hold their own notices. We link to each one rather than restating their wording, so the source of truth stays with the processor. |
| Privacy vs Security | Security controls — encryption, session timeouts, audit logging — are summarised here and detailed in the security note. Both documents cite the same control set. |
| Privacy vs Complaints | If our handling falls short, the complaints flow is in a separate document. This policy points to it but does not duplicate the escalation steps. |