How bakwan4d Handles Your Privacy
This is our privacy policy — the plain-English version of how bakwan4d collects, stores and uses the data tied to your account. We wrote it for Indonesia visitors...
Privacy Posture and Data Scope
Our privacy posture follows the data-protection expectations that apply where local law permits across supported Indonesia regions. We collect what's needed to run your account: your name, contact details, device fingerprint, session logs and the e-wallet references you tie to deposits. We don't sell your data to outside marketers, and we only share with payment partners and licensed processors when a transaction
needs it. Retention periods follow the legal window for financial records, after which entries are anonymised. You can ask us to export, correct or close your account data at any time, and we'll respond inside the windows this policy commits to.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Editorial Trust Signals For This Policy
Reviewed Quarterly
We re-read this privacy policy every quarter and after any platform change that touches data flow. The revision date at the top of the page reflects the most recent sign-off, not a one-time publish.
Legal Sign-Off
Our compliance lead signs each version before it replaces the previous one. Drafts don't go live on bakwan4d until that sign-off is recorded against the document version in our internal log.
Plain-Language Pass
Every clause goes through a plain-language pass so you aren't decoding legalese. If a sentence needs a glossary, we rewrite it until an account holder can read it on a phone screen.
Indonesia Scope
The policy is written against Indonesia data expectations first, not retrofitted from a global template. References to DANA, OVO, GoPay and QRIS reflect how your wallet data actually moves through our system.
Versioned History
Older versions of this policy stay archived so you can compare what changed. We don't quietly edit live text — material updates trigger a notice on your next account session.
Named Owner
This document has a named internal owner inside our compliance team. Questions don't bounce around — they land with the person responsible for keeping the privacy policy current.