All posts

Why local, client-side PDF parsers are safer for sensitive financial data

5 November 2026

A bank statement is one of the most revealing documents a person or a business has: the account number, the balance, who pays them, who they pay and when. Most online PDF converters ask you to upload it to someone else's server first. A client-side parser does the same job without the upload, and that one difference is most of what privacy means here.

What an upload means

When you upload a statement to a server-based converter, a copy of the file leaves your computer. What happens to it next is up to the service: how long it is kept, who can reach the server, which other companies process it on the service's behalf, which country the server sits in, and what happens if it is ever breached. A privacy policy answers some of that. None of it is something you can check.

On an accounts desk the statement is usually not even yours. It belongs to a client, and handing it to a third party is a decision you may have to account for under data protection rules such as Malaysia's Personal Data Protection Act 2010.

What client-side means

A client-side parser is a web page that brings its own PDF reader. Your browser downloads that code and runs it. The statement is opened from your disk into the page, read there, turned into a workbook there, and saved back to your disk. No copy exists on a server, because no step of the conversion happens on one. Close the tab and what the page held is gone.

That changes the question you have to answer. Instead of "do I trust this company with my client's file", it becomes "does this page send the file anywhere", and that one you can test.

How to check for yourself

• The airplane mode test. Open the page, convert any statement once so the page has loaded everything it needs, switch on airplane mode, then convert your real statement. If it finishes with no connection, the file had nowhere to go.
• The network tab. Press F12, open the Network tab and convert a statement. You can watch every request the page makes, and none of them should carry your file.

What still crosses the network on Parserje

Client-side does not mean the page never talks to the internet, and it is fair to say exactly when Parserje does:

• Loading the page. The page and the libraries it uses, the PDF reader, the OCR engine and the Excel writer, are downloaded when you open it. That is why the airplane mode test says to convert once first.
• Anonymous usage counts. Parserje uses cookieless analytics to count events such as a conversion starting or a file failing. What is sent is limited to fixed labels: the bank's name, whether the file was text or a scan, and rough ranges such as "26-100 rows". Never a file name, an amount, a date, a description or an account number. Anything not on that fixed list is dropped before it is sent.
• The feedback form. Whatever you type there is sent to us. Describe the problem, but do not paste account numbers or statement contents into it.

Parserje has not been independently audited, and we will not pretend otherwise while it is in beta. That is why the airplane mode test is worth more than this page: it asks you to trust nobody.

What client-side does not fix

• The Excel file lands in your Downloads folder. Store it the way you store the PDF.
• A browser extension allowed to read every site can read this one too. Keep extensions to the ones you need.
• A shared or public computer is still shared. Convert client statements on your own machine.
• Emailing the workbook to a client, or putting it in a shared drive, is an upload of its own.

More on how Parserje works is in what Parserje does. Ready to try it? Convert a statement in five steps.