How We Handle Your Account Data
This privacy policy explains what tancap4d login collects when you open an account, how we store it on our casino and sportsbook lobby, and the choices you have...
Our Privacy Posture and Your Rights
We collect only what your account actually needs: your registered name, contact handle, device fingerprint for fraud checks, and the wallet reference you link for DANA, OVO, GoPay or QRIS top-ups. Session logs sit on encrypted servers and we retain them only while your account is active, plus the window local law in supported regions requires. You can request a copy of
your record, ask us to correct a field, or close the account and have it purged where local law permits. We don't sell your data to advertisers, and marketing pings only go out to handles that have opted in through the account panel. Third-party processors who touch your record — payment rails, KYC partners, hosting — are bound by the same posture
and are listed in the data-processor schedule we keep current on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Us About Your Privacy Record
Privacy Inbox
Write to our privacy desk for data exports, deletion requests, or to correct a field on your account. We aim to acknowledge inside one business day in Indonesia hours.
Live Chat
Open the chat bubble in the lobby footer and ask for the privacy team. The agent will route your query and log a reference number you can quote later.
Account Panel
Most data requests — download a copy, edit your contact handle, switch off marketing pings — can be done directly inside your account panel without writing to us first.
Editorial Trust Behind This Policy
Reviewed Quarterly
Our policy team revisits this page every quarter, checking that the wording still matches how the casino, slots and sportsbook lobby actually handles your account data on the day you read it.
Named Authors
The privacy posture is signed off by our data lead and legal counsel, not a faceless template. Their initials sit on the change log at the foot of this page.
Encrypted Storage
Account records and session logs live on encrypted servers with access tied to named staff roles. We log every internal lookup so audit trails stay intact for supported regions.
Processor Schedule
Every third party that touches your record — KYC, payment rails, hosting — is named in the data-processor schedule we keep current on this same policy page.
Change Log
Material edits to this policy show up in a dated change log so you can see what shifted and when, instead of having to re-read the whole document each visit.
Indonesia Focus
We write for Indonesia first, which means examples lean on DANA, OVO, GoPay and QRIS flows rather than generic wallet language pulled from a global template.
Consistency Across Our Policy Pages
| Account Data | The fields listed here match the ones on our terms page and our KYC notice — same names, same retention windows, no surprise extras tucked away on a sibling document. |
|---|---|
| Retention Windows | How long we hold a closed account aligns with the figure on our terms page and our anti-fraud notice, so you only need to remember one number. |
| Third Parties | The processor list here matches the one referenced on our security page, with the same vendor names and the same scope of access spelled out. |
| Marketing Opt-Outs | The opt-out method described here is the same one our promo terms point to: a single toggle inside the account panel, mirrored by a link in every email we send. |
| Cookie Scope | Cookies named here line up with our cookie notice — session, preference and fraud cookies only, with the same expiry windows quoted on both pages. |
| Payment Records | References to DANA, OVO, GoPay and QRIS data follow the same shape as on our deposit help page, so your wallet handle is treated identically wherever it appears. |
| Contact Routes | The privacy inbox and chat path mentioned here match the support page, meaning one address handles policy queries no matter which document brought you in. |