Cookies
Browser storage and tracking pixels are described in the cookie notice. This privacy page references that document rather than repeating the cookie inventory, keeping each policy focused on its own scope.
LEGAL REFERENCE
How detikbet Handles Your Account Data
This is the detikbet privacy policy — the document that tells you what we collect when you open an account, why we keep it, and how long it...
Privacy PolicyData HandlingAccount RecordsIndonesiaUpdated 2025
Policy Posture and Jurisdiction Notes
We collect only what your account needs: your contact handle, device fingerprint, payment reference and the wallet rail you choose at checkout. Records linked to DANA, OVO, GoPay or QRIS transactions are stored for the period our compliance obligations require, then purged on schedule. Where local law permits, we share limited fields with payment partners to clear your deposits and withdrawals. We
do not sell your data to advertisers, and your gameplay history sits behind staff access controls. This policy applies across supported regions of Indonesia and updates here when material changes occur.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
REVIEW SIGNALS
Editorial Trust Signals for This Policy
This document is reviewed by named owners on a fixed cadence. The signals below tell you who touches the text, how often, and what evidence sits behind each clause.
Named Policy Owner
A single data protection lead signs off every revision of this page. Their name and contact route are on file with our compliance team, which keeps accountability clear rather than hidden behind a generic inbox.
Quarterly Review
We re-read this policy each quarter against current Indonesia data rules and our payment partner agreements. Any wording drift between the policy and live practice gets corrected in the same review cycle.
Change Log
Material edits are dated at the foot of the page. You can see when a clause was added, when wording was sharpened, and which sections were last touched without having to guess at version history.
Plain-Language Pass
Every draft passes an editor whose job is to remove legalese and replace it with sentences you can read on a phone. The intent is comprehension, not a wall of clauses written for lawyers only.
Payment Partner Alignment
Clauses that mention DANA, OVO, GoPay or QRIS are checked against the data-sharing terms we hold with each rail, so the policy reflects what actually moves between systems at checkout.
Access Logging
Internal access to your account record is logged at the row level. Auditors can trace who viewed which field and when, which keeps the staff-side promises in this policy honest rather than aspirational.
PLATFORM COMPARISON
Consistency With Our Other Policy Pages
The clauses here line up with our cookie notice, terms and account rules. The table below shows where each topic lives so you are not hunting through three pages for the same...
Account Terms
Rules about account creation, verification thresholds and closure live in the terms of service. Privacy here covers the data side of those same events without restating the contractual clauses.
Payment Records
Retention periods for DANA, OVO, GoPay and QRIS transaction records match the timelines published in our payments page, so you see the same number wherever you check.
Marketing Choices
Your opt-in and opt-out controls for email and push messages are set in account preferences. This policy explains the legal basis; the preferences page is where you toggle them.
Complaint Routes
If a privacy issue escalates, the complaint pathway mirrors the one in our dispute policy. Same stages, same response windows, same escalation contacts for consistency.
Data Sharing
Third-party processors named here match the list maintained in our vendor register. Adding or removing a processor triggers an update to both documents in the same release.
Retention Tables
How long we keep each data category is summarised here and detailed in our retention schedule. The categories use identical labels across both pages to avoid mismatched terminology.
What Shapes This Policy Page
These are the visible elements that define how the privacy page itself is laid out and what you can expect to find as you scroll. They...
Section Anchors
Each clause has a jump link in the side rail. You can land directly on retention, sharing or contact without scrolling past sections that are not relevant to your current question.
Last-Updated Stamp
A clear date sits at the top of the policy so you know which version you are reading. Bookmark holders can confirm at a glance whether anything has changed since their last visit.
Definitions Block
Terms like processor, controller and account record are defined once near the start. The rest of the policy uses those words consistently rather than swapping in synonyms that confuse the meaning.
Request Form Link
A direct link to the privacy request form sits beside the contact section. You do not have to draft an email from scratch — the form captures what we need to verify your identity.
Print View
A print-friendly stylesheet renders the policy without the lobby chrome. Keep a copy for your records if you prefer paper documentation of the terms you accepted at sign-up.
Translation Note
The English text is the operative version for our Indonesia rollout. If we publish a translated rendering later, the source language reference stays visible so any wording disputes are resolved against the original.
Privacy Policy Questions
We collect your contact handle, a verification reference and the device details needed to secure your account. Payment identifiers are added only when you link DANA, OVO, GoPay or QRIS to fund your first deposit.
Active account records stay with us while your account is open. After closure, we hold transaction-linked data for the period our compliance obligations require, then remove or anonymise the remaining fields on a scheduled purge cycle.
Yes. Send a request through the privacy inbox or in-app chat with your registered handle. Once we have verified ownership, we return a structured export of the account fields we hold within the response window stated above.
We share the minimum fields needed to clear deposits and withdrawals with the wallet rail you selected. DANA, OVO, GoPay and QRIS each receive only the transaction reference and amount, not your full account record.
Open the account settings panel after signing in to edit contact fields directly. For identifiers tied to verification, contact our privacy desk with the correction and supporting reference so we can update the locked fields on your behalf.
Material changes are dated in the change log at the foot of the page, and we notify active account holders through the in-app message centre. The previous version remains available on request for comparison purposes.
Start with the privacy inbox or in-app chat for routine questions. For formal notices, use the postal address listed in the contact section. Every channel reaches the same named owner who signs off this policy.