Privacy Policy For Your Account
Clear data handling, account privacy controls, and contact paths sit beside the batavia 4d lobby you came to explore. Open your account in seconds and we’ll show you...
How We Handle Your Privacy
This Privacy Policy explains how we collect, use, store, and share data when you access batavia 4d from Indonesia or other supported regions where local law permits. We collect account details you provide, technical records from your device, security logs, and transaction references connected with DANA, OVO, GoPay, QRIS, or related account checks. We use that data to open and maintain your
account, secure the lobby, verify activity, answer support requests, and keep records required for lawful operations. We do not sell your personal data. When service partners help us with hosting, risk checks, wallet references, or customer support, they receive only what they need for that task and must handle it under privacy terms aligned with our policy.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths For You
If you need help with personal data, contact us through the same account channels you use for the lobby. We keep privacy requests separate from promo talk, so your question goes to...
How Our Policy Stays Checked
We keep this policy practical, not hidden in legal language. Our team checks the wording against account screens, support scripts, wallet reference flows, and security prompts, so what...
Plain wording
We write privacy terms in direct English for Indonesia, so you can understand what data we collect, why we need...
Account flow match
Policy wording is compared with sign-in, profile, verification, and lobby screens, so data requests on the site align with the...
Security alignment
Our security checks are mapped to privacy purposes, covering device signals, session records, suspicious access alerts, and account recovery steps...
Partner scope
When service partners support hosting, wallet references, analytics, or help desk work, we limit shared data to the task and...
Retention checks
We assess storage periods for account, support, verification, and transaction reference records, then remove or anonymise data when the purpose...
Change tracking
When this policy changes, we update the page date, adjust related support language, and keep older internal copies for compliance...
Consistency Across Policy Pages
Your privacy should read the same wherever you enter our brand home. We align this page with cookie, terms, support, security, and account pages, so each touchpoint explains...
| Cookie page | Cookie wording explains device identifiers and analytics signals, while this policy connects those signals to account security, session stability, and privacy choices. |
|---|---|
| Terms page | Our terms describe service rules, while this policy explains personal data use behind account creation, access checks, security logs, and support handling. |
| Support page | Support language points you back to privacy channels when your request involves account data, correction, storage, consent, or identity-related checks. |
| Security page | Security content describes protective measures, while this policy explains which technical records support those measures and how they are handled. |
| Promotions page | Promo pages may reference eligibility checks, but this policy explains the personal data used to confirm account status and prevent duplicate claims. |
| Wallet references | Where DANA, OVO, GoPay, or QRIS references appear, this policy explains that transaction data is used for reconciliation, security, and support. |
| Account settings | Profile screens let you manage certain details, while this policy explains correction requests for records that cannot be edited directly inside your account. |
Visible Privacy Cues On Page
This layout is built to make privacy easier to act on before you join or return. Key cues, short blocks, contact cards, and FAQ answers keep...
Short hero promise
The page starts with what privacy means for your account: clear data handling, easy contact paths, and context before you share details.
Context chips
Chips for DANA, OVO, GoPay, and QRIS appear only as privacy context, helping you see where wallet references may touch account data.
Contact cards
Support cards separate routine account help from security and policy requests, so your privacy question reaches the right handling path faster.
Policy comparisons
Comparison blocks show how this page connects with terms, cookies, security, support, and account settings without repeating every clause again.
Readable FAQ
FAQ answers focus on common privacy actions, including access, correction, sharing, storage, consent, and account closure, in compact plain language.
Action-friendly structure
Each section gives you a next step, whether you want to open an account, correct details, ask a privacy question, or check data handling.