Terms of Service
Wording here matches the data clauses in our terms. Definitions of account, session and wallet handle are written once and reused so nothing contradicts across pages.
LEGAL REFERENCE
Our Privacy Policy, Written for You
This is the timnas slot privacy policy — the document that tells you what we collect when you open an account, why we hold it, and how long...
Account dataCookiesRetentionYour rightsIndonesia
Policy Posture and Jurisdiction
Where local law permits, we process your account data under the privacy framework applicable to Indonesia residents using timnas slot. We collect identifiers you give us at registration, session signals from your device, and the wallet handle you nominate for top-ups. We do not sell your personal data. We share it only with payment partners and verification providers needed to keep your
account live. Retention follows supported-region rules: active accounts stay on file while open, dormant records are minimised, and you can ask us to close and erase at any time. This policy is reviewed quarterly and updated when the law shifts.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY VISITORS TRUST US
How We Review This Policy
Data Officer
Our named data officer signs off every revision. Nothing on this page ships without their review, and their contact route...
Legal Counsel
External counsel familiar with Indonesia data rules reads the policy before we publish changes. They flag anything that drifts from...
Quarterly Audit
We audit log access, retention windows and third-party processors every quarter. Findings feed straight back into this page so the...
Plain Language
We rewrite legalese into reader-friendly English so you can finish this page in one sitting. If a clause needs a...
Version History
Each update carries a date and a short summary of what moved. You can ask the privacy inbox for prior...
User Feedback
When you tell us a clause is confusing, we log it. Reader questions have shaped roughly a third of the...
BENCHMARKED
Consistency With Our Other Legal Pages
Cookie Notice
Cookie categories listed here align exactly with the toggles on our consent banner. If a tracker exists, it's named in both places — never one without the other.
KYC Statement
Identity checks referenced in this policy follow the same evidence list described in our KYC statement, so you won't be asked for documents not mentioned here first.
Payments Notice
What we share with DANA, OVO, GoPay and QRIS partners is described identically in the payments notice. Same processors, same retention, same disclosure scope.
Complaints Policy
Escalation paths for privacy disputes mirror the steps in our complaints policy. You won't hit a different ladder depending on which page you started reading from.
Marketing Preferences
Opt-in and opt-out language used here is the same wording shown on the preferences panel inside your account, so toggles match the promises on this page.
Account Closure
Erasure timelines in this policy match the closure flow. When you close an account, the deletion clock starts on the day described here — not later.
PLATFORM SNAPSHOT
What This Policy Page Actually Covers
01
Scope Box
A short scope statement at the top tells you which timnas slot surfaces this policy applies to — web lobby, mobile site and account dashboard — so you know what's in and what's out.
02
Data Map
We list every category of data we hold against the reason we hold it. No vague bundles, no catch-all clauses that could mean anything later down the line.
03
Retention Table
Retention windows are spelled out per data type rather than buried in prose. You can find the row, read the number, and know when records drop off our systems.
04
Rights Panel
Your access, correction, portability and erasure rights are grouped in one panel with the exact request channel beside each one. No hunting through paragraphs.
05
Processor List
Third parties that touch your data are named, not hinted at. The list updates when we onboard or drop a vendor, and the change date sits beside the entry.
06
Update Log
A dated changelog at the foot of the page records every meaningful edit. You can see at a glance whether wording has shifted since the last time you visited.
Privacy Questions Readers Send Us
We collect the handle, contact detail and date of birth you submit at sign-up, plus the wallet identifier you link for DANA, OVO, GoPay or QRIS top-ups. Session signals from your device are logged for security.
Active accounts stay on file while open. Once you close, identifying fields are erased within the window listed in our retention table, with a shorter trail kept only where local law obliges us to.
Yes. Email the privacy inbox with your account handle and we'll prepare a structured export. Standard requests from Indonesia accounts are returned inside fourteen days, often much sooner than that.
Only the fields needed to route your top-up or withdrawal — handle, amount, wallet reference. DANA, OVO, GoPay and QRIS partners receive nothing beyond what the transaction itself requires to clear.
Essential cookies keep your session alive. Optional analytics and preference cookies fire only after you accept them on the banner. You can revisit those toggles any time from your account settings.
Open the closure flow inside account settings or message the privacy inbox. We confirm the request, settle any pending balance, and then start the erasure clock described in the retention section above.
We review the wording quarterly and whenever Indonesia rules shift. Each change is dated in the update log at the foot of the page, with a short note explaining what moved and why.