Terms of Service
The data definitions used here match the ones on our terms page. If you see a term like 'session data' there, it means the same thing on this privacy page.
This is the bakmibet privacy policy — written plainly so you know what we collect when you open an account, what we keep, and what stays under your...
We collect the account data we need to keep your bakmibet login, lobby sessions and e-wallet transfers working — nothing more. That includes your registered phone number, display name, device fingerprint for session safety, and the wallet references tied to your DANA, OVO, GoPay or QRIS activity. Where local law permits in supported regions across Indonesia, we retain transactional records for the
period required by applicable financial rules, then schedule them for deletion. We don't sell your personal data to advertisers. Marketing messages from us are opt-in at sign-up and you can switch them off inside your account screen at any time. If a regulator with jurisdiction over your account requests records, we'll comply within the scope they ask for.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you need to ask about your data, reach us through any of these channels. Privacy questions go straight to the team that handles account records, not general lobby support.
Every wording change here passes through counsel familiar with Indonesia data rules before it goes live. We don't push silent edits to the privacy page that haven't been reviewed.
The retention schedules and access logs behind this policy get audited every quarter. If something drifts from what we promise here, the audit flags it and we correct course immediately.
We keep dated versions of this policy so you can compare what changed between visits. Material changes are surfaced inside your account, not buried at the bottom of the page.
A named privacy owner inside bakmibet signs off on this page. That person reviews escalations, answers regulator queries, and owns the response time for your data requests.
Any partner that touches your account data — payments, fraud checks, hosting — is contractually held to the same handling rules we describe here. We vet them before integration and on renewal.
We deliberately avoid lawyer-speak where everyday English does the job. If a clause sounds vague to you, that's a problem we want to hear about so we can rewrite it.
The data definitions used here match the ones on our terms page. If you see a term like 'session data' there, it means the same thing on this privacy page.
Cookies and trackers are covered in their own notice, but the consent choices you make there feed directly into the data scope described on this privacy page.
Identity checks live in a separate KYC page. The retention windows quoted here align with what KYC keeps, so there's no gap between the two documents.
Wallet handling for DANA, OVO, GoPay and QRIS is described in the payments policy. We reference the same transactional record set both pages depend on.
When you close your account, the closure policy points back here for what gets deleted, what gets retained, and how long the residual record window lasts.
Opt-in choices made at sign-up are governed by the same consent framework this privacy page sets out, so toggling one channel doesn't contradict another.
The complaints page sends privacy-specific disputes back to the inbox listed in our support section, keeping one route for any data-handling concern you raise.