Is it safe to upload your bank statements to a converter?

It's the right question to ask. A bank statement shows balances, income, who you pay, where you shop, and an account number — and uploading one to a website means trusting a company you may have found ten minutes ago. The honest answer isn't "never"; bookkeepers email statements to each other all day, which is worse than most converters. The answer is "check these nine things first." For each, here's what a good answer looks like, and ours.

1. What happens to the original PDF, and when?

The file you upload is the most sensitive artefact in the whole process — it's the complete statement, account number and all. A good converter deletes it automatically, soon, and says so in plain language. Be wary of "retained to improve our services" or no statement at all.

Ours: the uploaded PDF is deleted from storage the moment processing reaches a final state — success or failure — on every plan, including the free one. There is no setting that keeps originals longer, because there's no reason to.

2. How long is the converted data kept?

After conversion there's a spreadsheet of your transactions sitting somewhere. The question is who decides how long. Good: you do, with a short default.

Ours: you choose, from 30 minutes to 30 days, and you can delete a conversion by hand at any time. The details are in data retention settings and what happens to your files.

3. Is it encrypted — in transit and at rest?

Both matter. TLS on the connection is table stakes (look for the padlock; any site without it is disqualified). Encryption at rest is what protects stored files if a disk or backup goes astray.

Ours: TLS in transit, 256-bit encryption at rest.

4. Does a person ever look at it?

Some services route hard documents to human reviewers. That may be acceptable for invoices; it's a harder sell for bank statements. Ask whether processing is automated end to end and under what circumstances staff can access files.

Ours: conversion is fully automated — no one reads your statement to convert it. Support can't open your files either; if you want us to look at a problem conversion, you share it with us deliberately.

5. Is an AI model involved, and is your data used to train it?

Most modern converters use a large language model somewhere in extraction. That's fine — it's why scans and odd layouts work now — but it raises two questions: which provider, and is your data used for training? A good answer names the provider and has a contractual no-training term.

Ours: extracted statement text is sent to OpenAI solely to structure the transactions, under an agreement that excludes training on it. We never use your documents to train anything, ours or anyone else's.

6. What happens to the password on a protected statement?

Many banks send password-protected PDFs. To open one, a converter needs the password — so ask whether it's stored.

Ours: the password is used once to open the file and is never stored. Password-protected PDFs explains the flow.

7. Which law covers it?

Where a company is based and which regime it operates under determines what you can demand — access, deletion, breach notification. For UK and EU users, GDPR is the bar.

Ours: GDPR compliant, with the specifics in our privacy policy. Deletion requests are honoured promptly, and the retention controls above mean there's usually nothing left to delete.

8. Do you have to hand over more than the statement?

A converter needs a PDF. It does not need your online banking login. Any tool that asks you to connect your bank account in order to "convert statements" is doing something else entirely, and you should understand exactly what before continuing. Likewise, be suspicious of a card requirement just to try the service.

Ours: you upload a file. The free plan needs no card. Your first conversion doesn't even need an account.

9. Can you verify the output without trusting the tool?

This is the question nobody asks and everyone should. Safety isn't only about leaks; it's about whether the numbers that land in your books are right. A converter that hands you rows with no way to check them is asking for faith.

Ours: every conversion is checked against the statement's own declared opening and closing balances, and carries the verdict — balanced or needs review. How that works is public, and you can do the same arithmetic yourself on any output.

Compared with what you do now

The alternatives aren't risk-free either. A statement emailed to an accountant lives in two inboxes, two sent folders and two backups, indefinitely. One sent over WhatsApp is on two phones. A shared-drive folder of client statements outlives the client. Desktop software keeps everything on a laptop that can be left on a train. The question was never cloud versus not-cloud; it's retention and control — who holds the data, for how long, and whether you can make it go away.

Red flags, briefly

• No privacy policy, or one that doesn't mention retention.
• "We may use your data to improve our services."
• No way to delete a conversion yourself.
• Originals kept indefinitely "for your convenience".
• A request for your online banking credentials.
• No HTTPS.

If a converter passes the nine questions, uploading a statement to it is safer than most of the things already done with that statement on an ordinary Tuesday. If it doesn't, the cost of a bad answer is your client's bank account history, so walk away. Try ours on the free plan and hold it to every one of the above.