Privacy Policy

Last updated: 18 July 2026

Your bank statements never leave your computer.
bankstatements-csv parses PDFs with code running in your browser. Your files, the transactions in them, and the CSVs you export are never uploaded to us or anyone else. That's how the product is built, so there's no policy here for us to quietly change later.

What stays on your computer

None of this is transmitted, logged, or stored by us. If a statement fails to parse, we receive only a generic error code, never the text that caused it.

What we collect

We collect the minimum needed to run accounts, subscriptions, and to know whether parsing succeeds in the wild. This is the complete list; if it's not in these tables, we don't collect it.

Your account

DataWhy
Email address and sign-in identity (via Google, Microsoft, or email sign-in)To sign you in and answer support email
Trial start/end dateTo run the 7-day free trial
Subscription status, billing period end, and Paddle customer & subscription IDsTo know whether your subscription is active. We never see your card number, payment details go directly to Paddle
Account created/updated timestampsRecord keeping

Usage events

When you parse a statement or export a CSV, the app sends a small event so we can see whether the parser is working well. Every field is a count, a duration, a yes/no flag, or a code from a fixed list; there is no field that could carry text from your statement. Each event contains some or all of these fields, and nothing else:

FieldExample
Event type"statement parsed" or "CSV exported"
Success or failuresuccess
Failure code, one of a fixed list of four"password protected", "file failed to open", "parser error", or "no transactions found"
Number of pages12
Number of transactions340
How long the parse took0.9 seconds
How many rows the app flagged for review, and the matching confidence score3 rows, 0.99
Whether the statement had a balance columnyes
How many flagged rows were still unreviewed at export1
Time from parse to export45 seconds
Counts of manual fixes made before exporting: column and region adjustments or re-detections, cell edits, row deletes, merges, inserts, and rows marked reviewed2 cell edits, 1 row delete
App version1.0.0
Timestamp7 July 2026, 10:12

These counts tell us that a statement parsed badly and how much fixing it took, never what was in it. Events are linked to your account so we can help when you contact support, and so a future "your activity" view can show you your own history.

Cookies and tracking

The app uses the cookies required to keep you signed in (set by Clerk, our authentication provider). There are no advertising trackers and no third-party analytics scripts on the site or in the app.

Who processes data for us

We don't sell or share your data with anyone else, full stop.

How long we keep it

Account and usage data are kept while your account exists, so trials, subscriptions and support work. Delete your account and we delete the lot (details below).

Deleting your account and data

Email support@bankstatements-csv.com from your account email and ask. We delete your sign-in identity from Clerk and your account row and all usage events from our database, and cancel any active subscription. One caveat: Paddle, as the seller of record, retains the invoices for your past payments to meet its own tax and legal obligations; that retention is governed by Paddle's privacy policy.

Where the data lives

Our database runs on Cloudflare's network; Clerk and Paddle are global services with their own compliance programs (see their privacy policies). We're an Australian business and handle personal information consistent with the Australian Privacy Principles.

Changes

If this policy changes materially, we'll update the date above and flag it in the app. The core promise, that statements never leave your computer, won't change.

Contact

Privacy questions: support@bankstatements-csv.com