Privacy
What we collect, who else sees it, and how long we keep it.
What we collect
| What | Why we have it | Where it comes from |
|---|---|---|
| The PDF you upload | It is the input. We read the transactions out of it. | You, when you upload |
| Page images rendered from that PDF | Intermediate step — pages are rendered as images so they can be read. | Derived from your PDF |
| The extracted result | The accounts, transactions, balance-check result, and the list of anything we could not read. | Derived from the page images |
| Your email address | Signing in. The free monthly allowance is per person, so it has to be tied to an account. | You, when you sign in |
| One identity cookie | Ties this browser to its free allowance and to anything you have paid for. It is a random string and contains nothing about you. | Our server, the first time you actually use the converter |
| A count of the statements and pages you have converted | Metering the free allowance (one statement a month, with a page cap inside it). | Our server |
| Stripe customer and payment records | Taking payment and issuing refunds. | Stripe |
What we do not collect
We do not ask for your bank login, and we never connect to your bank. The only way a statement reaches us is that you upload the file yourself.
We do not build a profile of you across devices or across sites, and there is no advertising or tracking network embedded in the converter.
We do not ask for a password. Signing in goes through Google, which tells us your email address and nothing else — not your contacts, not your calendar, not your Google password, which we never see and could not store if we wanted to. There is no password of yours here to lose.
The one cookie
There is exactly one: a random identifier that says “this browser”. It is what lets us count your free pages for the month and remember that you have paid. It carries no email address, no name, and nothing derived from your statement.
It is set the first time you actually use the converter — uploading a file or signing in — and not merely for reading these pages. Signing in swaps it for the one belonging to your account, which is how your allowance follows you to another browser. Signing out swaps it back.
Clearing it makes this browser anonymous again. If you had paid, sign in to get your access back.
Who else sees your file
- Our AI model provider. Reading a scanned statement requires a vision model, and the rendered page images are sent to that provider to be read. This is unavoidable for the product to work, and it is the one place your statement contents leave our servers. Their retention terms apply in addition to ours.
- Google, when you sign in. Signing in goes through Google, so Google knows you signed in here and tells us your email address. It never sees your statement, your converted output, or anything else you do on this site.
- Stripe, if you pay. Stripe receives payment details. Stripe does not receive your statement or the converted output.
- Cloudflare Pages, which serves this website. It does not handle uploads.
- Google Analytics and Google Search Console, for site traffic and search statistics. These see page views, not file contents.
How long we keep things
The exact retention periods are on the Security page, which is the authoritative version. In short: uploaded files and converted results are deleted after your conversion is done and in no case kept beyond 24 hours; account and usage records last as long as your account; payment records are kept as long as Stripe and tax rules require.
Your statements are never used to train any model.
What you can do
- Get your data out — every conversion is a download; that is the export.
- Delete a conversion early — deleting it from your history removes the file and the result immediately, rather than waiting for the automatic deletion.
- Close your account — this deletes your email address and usage counters. Payment records are kept where the law requires it.
Any of these, or any question about this page: [email protected].