Terms of Service
The data definitions used here match the ones in our terms — same vocabulary for account, session and cashier data so nothing reads differently between pages.
This is the toko4d login privacy policy. We wrote it so you know exactly what we collect when you open an account, what we keep on file while...
We collect the data you give us at sign-up — your name, contact handle, and the wallet reference tied to your cashier — plus the session signals our lobby needs to keep your account secure. Where local law permits, we store this on infrastructure that serves Indonesia and we share it only with the payment partners that move your top-ups. We don't
sell your data, we don't trade it, and we don't pass it to third parties outside the supported regions framework. You can ask us to show you what we hold, correct it, or close your account and have the record purged on the timeline our retention rules allow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our policy team owns this page, not marketing. They review the wording every quarter so what you read here matches...
Counsel familiar with Indonesia data rules signs off on every change before it goes live. Nothing ships to this page...
We keep a changelog of every privacy update. When wording shifts, you'll see the revision date at the top so...
A real person inside our team handles your privacy requests. Escalations don't disappear into a queue — they reach the...
Payment partners and analytics vendors are checked against our data agreement annually. If a vendor can't meet our terms, we...
If something ever goes wrong, our incident plan tells you within the window local law sets. No silence, no spin...
The data definitions used here match the ones in our terms — same vocabulary for account, session and cashier data so nothing reads differently between pages.
What we say about tracking on this page lines up with the cookie banner you saw at first visit. Same categories, same opt-outs, same retention windows.
Identity checks at the cashier follow the data minimisation rules stated here. We collect only what verification needs and nothing extra for marketing.
Promotional contact rules on this page mirror the consent panel inside your account. Toggle off there and the policy here tells you what stops.
When sportsbook markets need extra session data for fair play, the categories listed here cover it. No surprise data fields appear elsewhere.
Slot session telemetry — spin counts, room visits — falls under the gameplay data bucket described here. The slots page doesn't add new categories.
Live dealer rooms record table activity inside the same retention window stated on this policy page. One rule, applied across every product surface.
We wrote this in everyday English, not legalese. If a clause feels heavy, we've added a short explainer next to it so you can act on what you read.
Every section is framed for Indonesia first. Where local law permits is stated explicitly, and supported regions are named so you know what applies to your account.
The header carries the last-reviewed date and the version number. You can tell at a glance whether the policy you're reading is current or has been superseded.
Every right we describe links straight to the control that exercises it — export, correction, deletion — so reading the policy and acting on it happen in one flow.
We list the partner categories your data touches and why. Nothing vague, nothing catch-all — if a vendor isn't in the list, your data isn't with them.
For each data type we state how long we keep it and what triggers deletion. Account closure starts the clock, and the timeline is the same for everyone.