LEGAL REFERENCE

Your Privacy at batik4d, Plain and Direct

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...

Account dataConsent controlsData retentionIndonesia-awareUpdated regularly
batik4d Your Privacy at batik4d, Plain and Direct

Policy Posture and Jurisdiction Wording

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PLAYER SUPPORT

Reaching Us About Your Data

If you want to review, edit or erase what we hold, these are the policy-specific contact paths. Use the one that suits...

Privacy Inbox Email our data team for access requests, deletion...
In-App Chat Open the chat bubble inside your account area...
Account Hotline For urgent privacy issues like a suspected unauthorised...
WHY VISITORS TRUST US

How We Keep This Policy Honest

Editorial trust signals you can check before you trust us with your details.

Named Reviewer

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.

Change Log

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.

Plain Language

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.

Vendor Audits

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.

Local Counsel

Indonesian counsel reviews wording against current local law before each release, so the jurisdictional phrasing reflects what's actually enforceable in your region.

Security Posture

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.

WHY THIS PLATFORM

Consistency Across Our Policy Pages

How this privacy policy lines up with the cookie, terms and account-closure pages so nothing contradicts.

01

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.

02

Retention Windows

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.

03

Consent Toggles

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.

04

Third Parties

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.

05

Contact Paths

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.

06

Jurisdiction

"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.

07

Update Cadence

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.

What Sits On This Policy Page

The visible elements that shape this privacy page so you can navigate it quickly without scrolling blind.

Section Anchors

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.

Plain-English Summaries

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.

Version Stamp

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.

Consent Recap

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.

Glossary Link

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.

Print View

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.

Privacy Questions We Hear Often

We collect your name, contact handle, date of birth and a payment reference for DANA, OVO, GoPay or QRIS. Device and session data is captured automatically so we can secure your login and load the right lobby.

Yes. Open your account settings, head to the privacy panel and switch off marketing or analytics consent at any time. Changes take effect on your next session and don't affect lobby access where local law permits.

Active account data stays while your account is open. After closure, identity records sit for the period local law requires, then we delete or anonymise them. Payment references follow shorter, payment-specific windows.

Only the fields each provider needs to run their slot, live-table or sportsbook product. They can't reuse your data for their own marketing, and contracts forbid onward sharing outside our supported regions.

We store a tokenised reference, not your wallet credentials. The actual authorisation happens with DANA, OVO, GoPay or QRIS directly, and those providers hold the sensitive parts under their own privacy policies.

Material changes trigger an account-inbox notice and a banner in the lobby before they take effect. Minor edits show up in the change log at the foot of the page with the new version date.

Email our privacy inbox from the address tied to your account. We verify your identity, action the request within thirty days where local law permits, and confirm in writing once the records are removed.