← StatementLift

Why convert bank statements without uploading them

"Upload your statement" sounds convenient. Here's what actually happens after you click that button — and why StatementLift never asks you to.

What upload-based converters actually do

When a tool says "upload your PDF," your statement — account number, balance, every transaction, your name and address on the header — travels to a server you don't control. From there:

None of this makes a tool malicious. It's just what "upload" means: your financial document exists, however briefly, on hardware that's not yours.

What client-side parsing means

StatementLift reads your PDF using pdf.js — the same open-source library Firefox uses to render PDFs — running entirely inside your browser tab. The bytes of your file never get put on the wire. There's nothing to retain, because nothing was ever sent.

How to verify it yourself (don't take our word for it)

Open your browser's DevTools (F12, or right-click → Inspect), go to the Network tab, and convert a statement. Watch the requests: you'll see page assets, an anonymous analytics event or two, a license check if you're on a subscription — and no request carrying your file, its name, or anything derived from it. This isn't a claim you have to trust; it's one you can watch happen. The full breakdown of what our server does and doesn't see is on the privacy page.

Who this matters most for

Bookkeepers and accountants working under client confidentiality — sending a client's bank statement to a third-party server for conversion is a decision worth thinking about, not a default. Freelancers and small business owners who'd rather not create a copy of their bank statement sitting on someone else's infrastructure. Anyone converting a statement with someone else's name on it, where "trust me" isn't really their call to make.