The short answer
Usually nothing bad happens. Most statement converters are ordinary businesses with ordinary security, and the overwhelming majority of uploads are processed, returned and forgotten. If that were the whole question, the answer would be a shrug.
But a bank statement is not an ordinary file. It is a list of everybody you paid, what for, when, how much, and what was left afterwards, with your name, your address and your account number at the top. There is almost nothing else on a normal person's computer that says as much about them in as few pages. And converting one to a spreadsheet is a job that never needed a server: it is arithmetic on text that is already in the file. So the question worth asking is not whether the company is trustworthy. It is why the upload is happening at all.
What you are actually handing over
Not “some financial data”. Specifically:
- Your income and its source — salary, who from, how much, and whether it changed.
- Every payee — which is a map of your life. Where you shop, where you travel, your landlord or lender, your pharmacy, your solicitor, your gym, the school, the vet, the subscriptions you forgot about. Payees are more revealing than amounts, and people consistently underestimate this.
- Your balance, which is the single number most useful to somebody deciding whether you are worth defrauding.
- Your account number and sort code, usually in the header of every page.
- Other people, who did not agree to any of this. If you are an accountant or a bookkeeper, that is your client's data, and it is very likely the reason your professional body has an opinion about where it goes.
That combination is worth more to an attacker than a password, because it does not expire and cannot be reset.
What a careful service actually does
It is worth being fair here, because the scary version of this page would be less useful. A well-run converter will process your file, hold it briefly, delete it on a timer, and mean it. Several publish exactly that, and some are audited on it.
What none of them can offer is the thing that would settle the question: proof, checkable by you, that the file was not read, copied or kept. Once the upload completes, everything you know about what happened next is a policy document. That is not an accusation — it is the shape of the arrangement. And the parts of it that are outside anybody's good intentions are the ones worth naming:
- The file exists in more places than you sent it to. Load balancers, request logs, error trackers, temporary directories and backups all touch it on the way through, and a deletion timer set on the primary copy is not always set on those.
- The company can change. Retention policies are not contracts. Acquisitions, new owners and new terms have all retrospectively changed what a service was allowed to do with what it held.
- A breach elsewhere reaches your statement. You are not only trusting their intentions, you are trusting their patching, their staff, their vendors and their vendors' vendors.
- “Free” has to be paid for. Not always by the data — plenty of free tools are advertising-funded or loss-leaders — but it is worth knowing which, and the answer is in the privacy policy rather than on the landing page.
The two questions that actually decide it
This is the same test as everywhere else on this site, and statements make it unusually easy to apply.
Does the work need a server? For converting a statement to CSV, no. The text is already in the PDF. Finding the columns is arithmetic on where that text sits; checking the rows is arithmetic on the balance. There is no model to run, no licence to enforce, no hardware you do not have. A browser can do all of it, which is what the converter here does.
Can you tell the difference? Yes, in about ten seconds, and you do not have to take anybody's word for it. Open the page, then disconnect from the internet, then convert a statement. A tool that needed a server stops. A tool that runs on your machine does not notice. You can also open your browser's developer tools, watch the Network tab and see for yourself whether your file goes anywhere.
The option most people miss
Before converting anything: your bank has probably already done it. Nearly every online banking site will export the same statement as CSV, OFX or QIF directly, usually within a date-range picker a click or two from the statement list. That is more accurate than any conversion of any PDF, because nothing has to be inferred — and it is the only route where the data never leaves the two parties who already have it.
The reason people convert PDFs anyway is that the export only covers the last few months, or the account is closed, or the statement arrived as an attachment from somebody else. Those are good reasons. It is just worth checking first.
If you do upload one
Sometimes it is the only option — a scanned statement needs OCR, and that is a genuinely heavier job. If you are going to:
- Cover what is not needed. The account number and address are rarely required by whatever you are converting for.
- Read the retention line, not the headline. “We take your privacy seriously” is not a retention policy; “files are deleted after one hour” is.
- Prefer a service you pay. Not because paid means careful, but because it answers the question of how the business works.
- Check afterwards whether it was right. This applies to any converter, uploaded or not: if your statement has a running balance, the balance on each row should be the row above plus that row's amount. A converter that quietly misreads one digit produces a spreadsheet that looks perfect. That check is worth doing by hand if the tool does not do it for you.
The thing worth remembering
“Nothing bad has happened yet” is a description of the past, not a property of the arrangement. When a job genuinely needs a server — heavy computation, something only they have — the upload is a real trade and worth making with your eyes open. Turning a statement into a spreadsheet is not one of those jobs. It is arithmetic, it fits in a browser, and the only thing an upload adds is a copy of your account history on somebody else's disk.