Cookie Notice
Same definitions, same retention windows. The cookie page expands the categories; this Privacy Policy is the parent document everything else points back to.
This is the toto12 link Privacy Policy page. We've written it so you can see exactly what account details we collect when you open a lobby session, why...
Our policy applies wherever local law permits you to hold a toto12 link account. We collect the basics needed to run your lobby — name, contact handle, payment reference for QRIS, DANA, OVO or GoPay top-ups, and the device fingerprint that keeps your session yours. We don't sell your data, and we don't pass it to marketing networks outside our brand. Retention
follows the supported-regions rule: identity records are kept for the period local Indonesian regulation requires, transaction logs sit for audit windows tied to your wallet provider, and inactive accounts are pruned on the schedule published below. If a clause conflicts with Indonesian statutory rules, the statutory rule wins.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Each policy revision is signed off by a named editor on our compliance side, not a generic legal box. You'll see the revision date at the foot of the page change whenever real wording shifts.
We re-read the policy every quarter against fresh Indonesian guidance. If wallet rules around QRIS, DANA, OVO or GoPay shift, the relevant clause is rewritten and dated, never silently patched.
Product, payments and support all sign off before we publish a policy change. That stops a clause from making sense to lawyers but breaking the actual lobby flow you experience.
After legal drafts a clause, our copy team rewrites it in the same voice you're reading now. The legal meaning is preserved; the sentence stops sounding like a contract.
We keep a simple change log so you can see what moved between versions. Older versions stay accessible on request through the privacy inbox for at least twelve months.
An external reviewer checks our data handling against the policy text once a year. Findings that affect you are summarised in plain English and added to this page.
Same definitions, same retention windows. The cookie page expands the categories; this Privacy Policy is the parent document everything else points back to.
Where Terms mention your data, the wording mirrors this policy exactly. We don't run two definitions of account data across the brand.
KYC describes which documents we ask for; this policy explains how long we hold them and who inside the team can open them.
Per-wallet notes for DANA, OVO, GoPay and QRIS reference this policy for retention and deletion rules rather than redefining them locally.
Your opt-in choices live in account settings; this policy defines what those toggles actually change behind the scenes.
The complaints page sends privacy-tagged tickets straight to the desk named here, so escalation paths stay consistent.
Any sibling property under our umbrella publishes a policy with the same backbone. Local clauses change; the data-handling spine does not.