Your uploaded files are never kept
Zero-retention processing, encrypted transit, SOC 2 compliant infrastructure. We built this for people who care about where their bank data goes.
- No bank login
- Files never kept
- EU-based operator
How we protect your data
Six security practices built into every request.
Zero-retention processing
Encrypted in transit
SOC 2 compliant infrastructure
No third-party data sharing
Minimal data collection
Authentication & access control
What happens to your file
The complete lifecycle of your uploaded bank statement.
- Step 1
Upload (encrypted)
Your file is sent over TLS 1.3. Small files go straight to server memory; larger ones are staged in encrypted R2 storage for the request.
- Step 2
Process
AI reads the text (scans included), extracts transactions and assigns categories.
- Step 3
Extract results
Only structured data is kept: dates, descriptions, amounts, categories. The original file is discarded.
- Step 4
Deliver & delete
Results are shown in your browser or downloaded as a file. The uploaded document is deleted (a one-day automatic expiry catches failed requests).
GDPR aligned
We follow GDPR principles by design — not as an afterthought.
Right to access
View all data we hold about you from your dashboard settings.
Right to erasure
Delete your account and all associated data at any time.
Right to portability
Export your analysis history and transaction data.
Right to rectification
Edit or correct your account information.
Data minimization
We only process and store what is necessary to deliver the service.
Purpose limitation
Your data is used solely for statement analysis — nothing else.
Infrastructure security
Every provider in our stack is independently audited.
- CloudflareSOC 2 Type II, ISO 27001Hosting (Workers), database (D1), file staging (R2) — Western Europe
- Google CloudSOC 2, ISO 27001, SOC 3AI processing & scan reading (Gemini)
- PolarPCI-compliant checkoutPayment processing
- Better Authbcrypt + secure cookiesAuthentication
Third-party data processing
What data leaves our servers, where it goes, and how it's protected.
Google Gemini API
What is sent: Transaction descriptions and amounts are sent for AI categorization; page images of scanned or photographed statements are sent to be read.
Protection: Google API Terms prohibit using API data to train models. Data is processed and discarded — not stored by Google. All requests over TLS.
Polar
What is sent: Payment card details (we never see or store these).
Protection: PCI-compliant checkout. Card data goes directly from your browser to Polar.
Public-site scripts
PostHog measures product usage with privacy controls.
The site uses PostHog for product analytics, attribution, conversion funnels, and privacy-protected session replay. Input values are masked, and replay is disabled on results, dashboard, settings, and claim pages. For the current provider list, see Subprocessors and Trust Center.
Who operates this service
Transparency about who handles your data.
- Operator
- DPmedia
- Founded by
- Dawid P.
- Jurisdiction
- Poland, European Union
- GDPR status
- EU-based operator — fully subject to GDPR
- Contact
- contact@mybankstatementanalysis.com
- Operational docs
- Trust Center, Subprocessors, Data Retention, Responsible AI

Try it on your own statement
Your first upload is free, with no account or card. If a paid report doesn't match your statement, you get your money back within 14 days.





