Privacy Policy
Last updated: 19 Aug 2025
We built Better Bank Statements to be local-first. Your statement files are processed in your browser, not uploaded to our servers. This policy explains what we do—and don’t do— with your data.
Local processing
CSV/XLSX/ODS files are parsed in your browser. We don’t receive or store your files for normal use. You can export results (CSV/JSON) to your device at any time.
What we store on servers
- Account data: if you register (Firebase Auth), we store your email, display name, and auth IDs.
- Credits & usage: your credit balance and usage events (counts). We do not store your statement files.
- Payments: Stripe processes your payment; we receive non-card metadata (product, amount) for fulfilment.
- Anonymous usage gating: hashed anonymous IDs and daily counters to prevent abuse.
- Logs: basic error and security logs for reliability and abuse prevention.
Cookies & local storage
- Auth/session cookies when you sign in.
- Local storage for saved results and an anonymous usage token (hash).
What we don’t do
- No bank connections or screen scraping.
- No selling personal data.
- No server-side parsing of your statement files.
Data retention
Account and billing records are kept as required for operations, support, and tax compliance. Saved results remain in your browser until you clear them. If you share files with support, we keep them only as long as needed to resolve the issue.
Your rights
Depending on your region (e.g., EU/EEA), you may have rights to access, correct, delete, or export your personal data. To make a request, contact us on the Contact page.
Processors
We use Firebase (Google) for authentication/backend services, and Stripe for payments. They act as processors where applicable.
Children
The service is not intended for children under 16.
Changes
We may update this policy to reflect improvements or legal requirements. We’ll update the date above and, when appropriate, provide additional notice.
Contact
Questions or requests? Reach us via the Contact page.