vs Terms of Service
The Terms cover account conduct and payouts; this policy covers data. Where they overlap on identity checks, the wording is identical so you don't get two different answers.
This is the ya togel privacy policy — the document that tells you what we collect when you open an account, why we hold it, and how long...
Our policy posture is simple: we collect what we need to run your account and nothing extra. That means your registration details, the device you sign in from, the games you open in the lobby, and the payment references you attach. We process this where local law permits and only inside supported regions for Indonesia. Your data isn't sold. We share it
with payment partners and licensed auditors when a transaction or compliance check requires it, and we keep records for the period our regulators ask us to. If you close your account, we retain the minimum required and erase the rest. Questions about a specific field are answered by our policy desk.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If anything in this policy needs clarifying, talk to us directly. Our privacy contacts handle data requests, correction notices and account deletion separately from general support — so your message lands with someone trained to answer it.
Write to our data team for access requests, corrections or deletion. We acknowledge within one business day and follow up with the full response inside the window your regulator requires.
Open the chat widget from any page and ask for the privacy desk. The agent routes your query to the data team rather than answering general account questions, so nothing gets crossed.
For formal data subject requests, our registered postal address is published in the footer. Send signed notices there if your case needs documented delivery rather than email confirmation alone.
This document isn't decoration. It's reviewed, dated and signed off before it goes live, and the people behind it are named below.
Each policy revision is signed off by our compliance lead and legal counsel. Their initials and the publish date sit...
We run an internal data audit every quarter. The findings inform whether the policy needs an update, and material changes...
Wording follows guidance from the regulators that license us, plus Indonesia-facing data norms. Where the two diverge, we apply the...
Old versions of this policy stay accessible on request. If you signed up under an earlier draft, you can compare...
We strip the legalese before publishing. The aim is a policy you can read in five minutes, not one that...
Every contact route on this page reaches a human at our office. No auto-loops, no shell inbox — your privacy...
Our privacy policy lines up with the other legal documents we publish. Here's how they relate.
The Terms cover account conduct and payouts; this policy covers data. Where they overlap on identity checks, the wording is identical so you don't get two different answers.
The cookie notice details browser-side tracking. This policy covers server-side account data. Both reference the same retention windows so the timelines match across documents.
KYC explains the documents we ask for at verification. This policy explains how those documents are stored, who sees them, and when they're purged from our systems.
AML wording governs transaction monitoring. This policy describes the personal fields tied to that monitoring, so reading the two together gives you the full picture.
Bonus terms reference the data we use to detect duplicate accounts. This policy is the source for what that data actually is and how long we hold it on file.
The complaints policy lists escalation routes. This document confirms that complaint correspondence counts as personal data and is retained under the same rules as account records.
Closure rules sit in the account section. This policy specifies what survives closure — usually only the records regulators require us to keep.
Quick orientation to the elements you'll see on this page and how they're laid out.