Security and privacy — and how to check we are telling the truth

The short version: for text-layer and password-protected PDFs, which are the large majority of bank statements, your file is read inside your own browser and never transmitted anywhere. There is no upload step, no retention window and no deletion policy, because there is no copy.

How to verify that, in five seconds

1. Turn your Wi-Fi off.
2. Convert a statement.
3. It still works.

Nothing that depends on a server can work offline. You can also open your browser’s developer tools, watch the Network tab while you convert, and see that no request carries your file.

The one exception, stated plainly

A scanned or photographed statement has no text to read, only a picture of text. Recognising that needs a model your browser cannot run well, so those pages would have to be sent to a server. We will tell you when that is the case and wait for you to agree. It never happens silently, and it never happens to a statement that has a text layer.

Passwords

Encrypted statements are decrypted in your browser. The password is typed into the page and used there. It is not transmitted, not stored, and not logged.

What we do collect

Aggregate, non-identifying usage counts — page views, which formats get chosen, whether a conversion succeeded — so we know what to fix. No statement content ever touches analytics or advertising. We do not build audience segments from anything in your file, and we do not put any parsed value into a URL, a data layer or an ad request.

What we are not

We are not a bank, an accountant or a financial adviser, and we do not conduct identity checks, so we are not subject to the record-retention duties those businesses carry. Statements contain no card numbers, so payment-card rules do not apply either. That is why we are able to keep nothing at all — and keeping nothing is the strongest privacy guarantee available.