Cookie Notice
The cookie notice uses the same retention windows and the same lawful-basis language you'll see in this privacy policy, so the two documents never contradict each other on tracking.
This page is our privacy policy — the plain-English version of how we handle the data you share when you open an account with topanbos88. We cover what...
Our privacy policy applies wherever local law permits us to operate, and it sits alongside the regulations covering supported regions in Indonesia. We collect the basics needed to run your account — name, contact details, device signals, and the payment references you attach when you fund a session. We retain that information only for as long as your account stays active, plus
the window required by local record-keeping rules. You can request a copy, ask us to correct an entry, or close the account entirely. Third-party processors who touch your data are bound by the same confidentiality posture we hold ourselves to, and nothing leaves the pipeline without a lawful basis.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our privacy team reads this page every three months and rewrites anything that no longer matches how we actually handle...
We translate the legal posture into the kind of English you'd hear in conversation. Where a clause has to stay...
A named data protection lead signs off on every revision. That person is reachable through the privacy inbox and answers...
Material changes are logged with a date and a one-line summary at the top of the policy. You can scan...
Indonesian counsel reviews each revision against current local data rules before it goes live, so the wording you read here...
If a clause reads as confusing, you can flag it through the chat bubble. We collect those notes and feed...
The cookie notice uses the same retention windows and the same lawful-basis language you'll see in this privacy policy, so the two documents never contradict each other on tracking.
Where the terms reference data handling, they point straight back to this page. Account closure clauses match the deletion windows we describe here word for word.
Identity verification disclosures echo the retention rules in this policy. Documents you upload during KYC follow the same storage and deletion timeline as the rest of your account record.
Opt-in language for promotional messages mirrors the consent posture in this policy. Withdrawing consent in one place withdraws it everywhere we hold your contact details.
References to DANA, OVO, GoPay and QRIS handling line up with the processor list named here, so you see the same parties whether you're reading payments or privacy.
The complaints page routes privacy escalations to the same data officer named in this policy, keeping a single point of accountability across every channel.
Every policy page on the site shares a synchronised version date strip, making it easy to confirm you're reading the current revision rather than a cached older copy.
A jump menu sits at the top of the policy so you can land on retention, third parties, or your rights without scrolling through clauses that don't apply to the question you came in with.
The header carries the last-updated date and a link to the change log. You'll know at a glance whether the policy has shifted since your previous visit to the page.
Each technical clause is followed by a short grey-box note translating the legal wording into something you can read on a phone screen between rounds.
A dedicated panel lists your access, correction, and deletion rights with the exact buttons and email addresses needed to action each one without hunting through the rest of the page.
Named third-party processors appear in a clean table with their role and jurisdiction. Nothing is hidden behind generic phrases like industry partners or service vendors.
The footer of the policy carries the privacy inbox, the data officer's name, and the chat shortcut, so you never have to leave the page to raise a question.