Terms of Service
Account rules referenced in the terms point back to the same retention periods and contact channels named here, so the two documents read as one coherent posture.
This is the privacy policy for totosakti. We wrote it for you in plain language so you can see exactly what we collect when you open an account...
We collect what we need to run your account: your name, contact handle, device fingerprint, and the payment references you choose at the cashier. Where local law permits, we hold transaction logs for the period required by Indonesian financial rules, then we let them expire. You can ask us to export your record, correct a field, or close the account entirely —
we action requests inside the windows the policy commits to. Marketing contact is opt-in only; switching it off does not affect lobby access. We do not sell your data to third-party advertisers, and any processor we share with (payment rails, fraud screening, hosting) is bound by contract to the same limits we apply ourselves in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If anything in this policy needs clarifying, our privacy desk is reachable through the same channels as account support — staffed by humans who can read your record and act on it.
This page is reviewed on a fixed cadence so it never falls behind the way we actually run accounts.
Our compliance team re-reads this policy every quarter against the live account flow, the cashier, and the marketing console, so...
The policy is written by the team that owns the account database, not outsourced. If a clause says we delete...
Each revision carries a date stamp at the foot of the page and a short note on what changed, so...
Wording follows Indonesian data-handling expectations and references the retention periods local financial supervisors expect from a cashier that touches DANA...
Every external processor we name — hosting, fraud screening, payment routing — sits under a written agreement we audit annually...
We avoid legalese where we can. If a clause genuinely needs a defined term, we define it in the same...
This privacy policy lines up with the other legal pages on totosakti so nothing contradicts.
Account rules referenced in the terms point back to the same retention periods and contact channels named here, so the two documents read as one coherent posture.
The cookie notice describes the browser-side trackers; this policy describes the server-side record. Together they cover the full data picture without overlap or gaps.
Payment-page disclosures about DANA, OVO, GoPay and QRIS handling repeat the processor list named in this policy, with the same retention windows and the same opt-out path.
The marketing toggle inside your account uses the exact opt-in definition from this page, so flipping it off here removes you from every channel referenced.
Closure flow honours the deletion timelines stated here. Once you confirm closure, the same windows apply whether you triggered it from the app, chat or email.
The export bundle you can request matches the field list disclosed in this policy — no hidden columns, no missing rows, structured the way the policy describes.
If we ever need to send a breach notice, the contact route, timeline and content follow the commitments in this policy rather than a separate ad-hoc process.
A few visible elements define how this policy reads on screen — they are here to make the document usable, not decorative.