Definitions
The same terms — account, session, payment reference, marketing consent — carry identical meanings across every legal page on batik4d, so a clause here matches the cookie and terms pages exactly.
This is the batik4d privacy policy, written for our Indonesia account holders in everyday English. We explain what we collect when you open an account, why we keep...
We process your personal data where local law permits and only inside supported regions for Indonesia. That covers the basics you give us at sign-up — name, contact handle, date of birth — plus the technical signals your device sends when you open the lobby. Payment references tied to DANA, OVO, GoPay and QRIS are stored separately from your gameplay history, with
shorter retention windows. We don't sell your data. We share it only with the providers running our slot rooms, live tables and sportsbook markets, and only with the fields each one actually needs. If a regulator in your jurisdiction asks us to disclose, we follow the law and notify you where we're allowed to.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Editorial trust signals you can check before you trust us with your details.
Each policy revision is signed off by a named data officer on our team, not an anonymous template. Their initials and the date sit at the foot of every published version.
We keep a visible change log so you can see what shifted between versions. Material changes get a notice in your account inbox before they take effect on the lobby.
We rewrite every clause into everyday English instead of leaning on legal jargon. If a sentence needs a lawyer to decode, it doesn't belong in a policy you actually read.
Our slot, live-dealer and sportsbook providers are reviewed annually against the data-handling clauses in their contracts. Failed audits trigger remediation or removal from the lobby.
Indonesian counsel reviews wording against current local law before each release, so the jurisdictional phrasing reflects what's actually enforceable in your region.
Encryption at rest, encryption in transit, role-based access for staff and quarterly penetration tests on the account database. Incidents trigger user notice within the windows local law sets.
How this privacy policy lines up with the cookie, terms and account-closure pages so nothing contradicts.
The same terms — account, session, payment reference, marketing consent — carry identical meanings across every legal page on batik4d, so a clause here matches the cookie and terms pages exactly.
Retention periods quoted here match the figures on the account-closure page. Close your account and the clock starts on the same day, with the same end date applied.
The marketing and analytics switches described in this policy are the literal toggles inside your account settings — same labels, same defaults, no hidden second layer.
Vendor lists referenced here are kept in sync with the cookie page roster. When a provider drops off one list, it drops off the other in the same release.
Email, chat and hotline routes shown above are the same routes printed on the contact and complaints pages. One inbox, one ticketing system, one audit trail.
"Where local law permits" and "supported regions" are used identically here and on the terms page. No page widens or narrows access compared to another.
Policy reviews happen on a fixed quarterly schedule alongside terms and cookie updates, so all four pages share a version date and change-log entry.
The visible elements that shape this privacy page so you can navigate it quickly without scrolling blind.
Sticky anchors at the top jump you straight to retention, consent, contact or change log. Useful when you've come here for one specific clause and don't want to read the whole page.
Every dense clause carries a short summary in everyday language sitting right above it, so you can decide whether to read the full paragraph or move on.
The footer shows the current version number, publish date and the initials of the data officer who signed it off. Earlier versions stay reachable through the archive link.
A boxed recap near the end lists every consent we ask for and the default state, so you can audit what you've agreed to without digging through your account settings.
Technical terms like processor, controller and pseudonymisation link to a short glossary in a side panel rather than forcing you to a separate page mid-read.
A print-friendly view strips the navigation chrome so you can save a clean PDF copy for your own records before agreeing to any updated version.