Definitions
The same terms — account, wallet handle, session token, lobby — mean the same thing on every policy page across erek31.app, so you never have to re-learn vocabulary.
LEGAL REFERENCE
How erek31 Handles Your Account Data
This is the erek31 privacy page for Indonesia. We wrote it so you can see exactly what we collect when you open an account, what we keep on...
Account dataIndonesia residentsDANA/OVO readyPlain-English wordingUpdated regularly
Our Privacy Posture in Plain English
We collect the basics needed to run your account: your name, contact details, device fingerprint and the wallet handle you link for DANA, OVO, GoPay or QRIS. Where local law permits in Indonesia, we retain transaction logs for the period our payment partners require, then we purge. We do not sell your data to third parties. We share only with the regulators,
payment rails and fraud-screening partners that keep your account funded and safe. You can ask us to export or delete your data at any time, and we will action the request within the window our supported regions mandate. Cookies on erek31.app are limited to session, security and lobby preferences.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
SUPPORT
Privacy Contact Paths
If a privacy question comes up, here is how to reach the team that actually owns the answer. We keep these channels staffed in Indonesia hours so you are not waiting on...
Privacy Inbox
Email [email protected] for data export, deletion or correction requests. We confirm receipt within one business day and close most requests inside the window our supported regions require.
Live Chat Desk
Open the chat bubble in your account header and ask for the privacy queue. The agent will route you straight to a data officer instead of the general lobby support pool.
Postal Channel
For formal notices our registered correspondence address is published in your account footer. Use this path for legal letters; the inbox handles every other privacy matter much faster.
EDITORIAL CLARITY
How This Policy Is Reviewed
This policy is not a copy-paste template. Real names own each section and sign off before it goes live on erek31.app.
Drafted In-House
Our compliance lead drafts every clause against the actual data flows in our casino, slots and sportsbook stack. If the product changes, the wording is rewritten before the change ships to your lobby.
Legal Counsel Review
Indonesian counsel reviews the page each quarter to keep wording aligned with current local data rules. Their sign-off is logged internally so we can show our working if a regulator asks.
Payment Partner Audit
DANA, OVO, GoPay and QRIS partners audit how we describe shared data. Their feedback feeds straight back into this page, which is why the payment clauses stay specific instead of vague.
Security Team Sign-Off
Our security engineers confirm encryption, retention and access-control claims match what is actually deployed. We will not publish a sentence here that the infrastructure cannot back up in production.
Versioned Updates
Every revision is dated at the foot of the policy, with a short note on what moved. You can scroll the history to see when a clause was tightened or a partner was added.
Reader Feedback Loop
When you flag a confusing line through chat, we log it. Repeated questions trigger a rewrite so the next reader sees clearer wording instead of the same vague paragraph.
SIDE BY SIDE
Consistency Across Our Policy Pages
Our terms, cookies and privacy pages are written as one set, so you do not get conflicting wording between them.
Retention Windows
Retention periods quoted here match the windows quoted in our terms. If one moves, both move on the same release, never one ahead of the other.
Payment Clauses
DANA, OVO, GoPay and QRIS appear by name in privacy, terms and cookies. We do not hide partners behind a generic 'payment provider' phrase on one page and name them on another.
Contact Paths
The privacy inbox, chat queue and postal address shown here are the same ones quoted in terms. One source of truth, no chasing different emails for related questions.
Update Cadence
All policy pages share a single revision schedule. When the quarterly review lands, every page is restamped together so dates never drift apart between documents.
Jurisdiction Wording
We use 'where local law permits' and 'supported regions' consistently. The phrasing is identical across pages, which keeps the Indonesia scope unambiguous wherever you read it.
Reader Rights
Export, correction and deletion rights are described in matching language on every page, so the steps you read here are the steps quoted in terms and cookies too.
SERVICE CONTEXT
What Shapes This Policy Page
A few brand-side choices define how this privacy page looks and reads, separate from the payment chips you see elsewhere on erek31.app.
01
Plain Wording
We wrote this in working English, not legalese. If a clause needs a defined term, we define it on the spot rather than send you to a glossary in another tab.
02
Section Anchors
Each clause has its own anchor link, so chat agents can paste you straight to the paragraph that answers your question instead of asking you to scroll the whole page.
03
Mobile-First Layout
The page is built to read cleanly on a phone first. Headings, spacing and tap targets are sized for the same device you use to open the lobby.
04
Dated Revisions
A revision date sits at the head and foot of the page. You always know which version you are reading, and prior versions stay reachable on request.
05
Scoped to Indonesia
Wording is scoped to Indonesia residents and our supported regions. We do not pad the page with clauses for markets we do not serve, which keeps it short and relevant.
06
Linked From Footer
This page is one tap from every footer on erek31.app. You should never have to search for it; the link sits in the same slot on the lobby, account and cashier screens.
Privacy Questions We Hear Most
We collect your name, contact details, date of birth for age checks, device fingerprint and the wallet handle you link for DANA, OVO, GoPay or QRIS. Nothing beyond what the account flow asks for.
No. We do not sell your account data to advertisers or data brokers. Sharing is limited to payment partners, fraud-screening services and regulators where local law permits, and each role is named in the policy above.
Transaction logs are retained for the period our payment partners and Indonesian rules require, then purged on schedule. The current window is published in the retention clause and updated whenever a partner requirement shifts.
Yes. Email the privacy inbox or open chat and ask for an export or deletion. We confirm receipt the same day and close most requests inside the statutory window our supported regions mandate for data subject requests.
Session, security and lobby-preference cookies only. We do not run third-party advertising trackers on the domain. The cookies page lists each one by name with its purpose and lifetime in a short table.
Your linked wallet handle is stored encrypted so the cashier can route deposits and withdrawals. The full payment credential stays with DANA, OVO, GoPay or QRIS — we never see or hold the underlying account secret.
Material changes are announced inside your account header and dated at the top of this page. Minor wording fixes are logged in the revision history at the foot, so every change is visible whenever you check back.