Terms of Service
Wording about account ownership and data retention matches what you read inside our terms page, so there's no mismatch between the two documents.
This is where we explain what tt4d togel does with your account data — nothing more, nothing less. We collect what's needed to verify you, fund your lobby...
We process your details under the privacy posture that applies where local law permits, and we follow the data-handling rules common to supported regions for Indonesia. That means we collect identifying fields at sign-up, transaction references when you top up through DANA, OVO, GoPay or QRIS, and session logs that protect your balance. We don't sell your data to third parties. We
share it only with payment partners and verification providers that need it to clear your activity. You can request a copy of what we hold, ask for corrections, or close your account through the channels listed further down. Retention follows the timeline set by the financial rules covering your wallet activity, and we delete personal fields once that window closes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every clause is read by our policy editor before it goes live. We rewrite anything that sounds vague so you can tell what we keep and what we don't.
Our legal contact checks the policy against the rules that apply in supported Indonesia regions. Updates happen when wallet rules shift or when a new partner joins the lobby.
You'll find a revision date at the foot of this page. When we change a clause, the date moves and we flag the section so returning account holders know what's new.
This policy has named owners on our side — a data lead and a privacy editor. They sign off on changes rather than leaving the page to drift between teams.
Where DANA, OVO, GoPay or QRIS need a transaction reference, we name that flow inside the clauses. You're not left guessing which third party touched your data.
If you write in about a clause that reads unclearly, we log it and revisit the wording in the next cycle. Your reading of the policy shapes the next version.
Wording about account ownership and data retention matches what you read inside our terms page, so there's no mismatch between the two documents.
Tracking categories named here line up with the cookie banner choices. If you switch a category off there, this policy reflects what stays stored.
Identity fields collected during verification appear in both the KYC notice and this policy, with the same retention window and the same deletion path.
References to DANA, OVO, GoPay and QRIS share the same partner naming used in our payments disclosure, so the data trail reads the same in either place.
Consent language for promo messages matches the toggles inside your account. Turning them off in one place turns them off everywhere we send messages from.
The privacy escalation path here points to the same desk named on our complaints page, so you don't bounce between teams when raising a data issue.
Closure timing, data wipe and residual-record rules are described identically here and on the account-closure page, so the outcome is the same either way you read it.
A short index sits at the top of every long clause group so you can skip to retention, sharing or consent without scrolling through unrelated paragraphs in a single block.
We've stripped legal filler from clauses you actually act on — consent, deletion, access. The dense legal phrasing only stays where regulators in supported regions require the exact form.
Where a clause is easier to read with an example — like which field we store at top-up — we drop the example beside the clause instead of hiding it in a footnote.
Each clause group carries the date it was last touched. You see at a glance which parts changed since your last visit and which have stayed put for a while.
Buttons next to relevant clauses send you straight to the account panel — for marketing toggles, device sessions, or a data export — without copying URLs.
Privacy contacts appear inside the clauses they relate to, not only at the bottom. If a clause raises a question, the right desk is named beside it.