Short answer: never upload invoices, payslips, bank statements or tax returns to a server-based PDF tool. Most free tools upload your file before doing anything — exposing account numbers, VAT IDs and addresses to transmission, storage, breaches and legal requests. The safe alternative processes the file entirely in your browser, so it never leaves your device. This guide shows the risk, the GDPR angle, and a complete no-upload workflow for everyday accounting documents.
Accounting documents are a uniquely concentrated package of sensitive data. A single invoice carries your client's legal name, address, VAT number and bank details for payment. A payslip carries a national ID number, salary, tax withholdings and home address. A bank statement carries account numbers, balances, transaction history and spending patterns. A tax return carries all of the above. This is exactly the dossier identity thieves and fraudsters assemble — and uploading it to a free web tool hands a complete copy to a third party in one drag-and-drop.
For accountants and bookkeepers the exposure multiplies: you handle dozens or hundreds of clients' documents, and under GDPR you are responsible for every processor you send personal data to. One casual upload of a client file to a server-based tool is a data transfer you now have to justify, document, and defend.
Read the privacy policies and the pattern is consistent:
The key insight: reputable companies have genuine deletion policies — but policy is a promise, and promises are unverifiable. Architecture is verifiable. A tool that never receives your file has nothing to delete, nothing to breach, and nothing to hand over.
| Question | Server-upload tools (iLovePDF, Smallpdf, Adobe online…) | Browser-only tools (this site) |
|---|---|---|
| Where is your file processed? | On the company's servers | On your device, in JavaScript |
| Is the original transmitted? | Yes — the full file uploads first | Never — check the Network tab |
| Deletion after processing? | Promised in 1–24h; backups may persist | Nothing to delete — it never left |
| GDPR processor relationship? | Created — you need a lawful basis + DPA | None — no data transfer occurs |
| Verifiable by you? | No — you must trust the policy | Yes — DevTools shows zero uploads |
| Works offline / behind firewalls? | No | Yes, after the page loads |
Everyday accounting document work maps cleanly onto browser-only tools:
Generate VAT-ready invoices with our invoice generator — line items, tax rates, 17 currencies, real PDF output. Client names and amounts never leave your tab.
Strip account numbers or ID numbers from statements with true redaction — the hidden text is destroyed and re-rendered, not covered with a black layer that copy-paste defeats.
Add your signature to invoices and engagement letters with the in-browser signer.
Author fields often leak your username or full name. Inspect and fix them with the metadata editor, or strip them entirely with remove metadata.
Statements and scanned receipts get huge. Compress them locally before attaching to emails — smaller files, same privacy story.
If you run a practice, make the rule architectural, not brand-based: "Client documents may only be processed by tools that operate entirely in the browser, with zero file upload. Server-upload tools are prohibited for client data." Then verify, don't trust: any team member can confirm a whitelisted tool in one minute with the Network-tab test. Add the 60-second check to your onboarding. Policies based on "reputable brands" fail the day the brand is breached; policies based on architecture hold regardless.
It is the highest-risk thing most people do with PDF tools. Bank statements, invoices, payslips and tax returns contain account numbers, balances, VAT IDs and addresses — exactly the data identity thieves want. Most free tools upload the file to their servers first, exposing it to transmission, storage, breaches and legal requests. Use a browser-only tool that never uploads the file, so the document is never exposed at all.
Most promise deletion after a window — commonly 1 to 24 hours. But 'deleted from the web app' is not the same as 'gone': backups, logs, caches and analytics pipelines can retain copies, and you have no way to verify deletion. A tool that never receives your file has nothing to delete, which is the only verifiable guarantee.
Uploading a document containing personal data to a third-party server is a data transfer under GDPR — the tool becomes your data processor, and you are responsible for a lawful basis, a processing agreement and appropriate safeguards. Browser-only processing sidesteps the question elegantly: if the file never leaves the client device, no transfer occurs and no processor relationship is created.
In under a minute: open your browser's developer tools (F12), go to the Network tab, drop a file into the tool and run the job. If you see large upload requests carrying your document, it uploads. If you see nothing but tiny page assets, it processes locally — like every tool on this site.
Use a tool that (1) never uploads the file and (2) truly destroys the hidden content instead of drawing a black box over it. Our redact tool does both: everything runs in your browser and the pages are re-rendered with the black boxes burned into the output, so the original text no longer exists in the file.
Yes. Author fields often contain your username or full name, and producer/creator fields reveal your software and workflow. Before sharing invoices or statements externally, inspect the metadata — our free metadata editor shows every field — and clear or correct anything you don't want attached to the document.
For the operations accountants actually need — merging, splitting, compressing, rotating, redacting, signing, metadata editing, page numbering — yes: modern JavaScript PDF libraries run entirely in the browser with identical output. Server processing adds nothing for these tasks except the privacy risk.
Ban upload-based tools for client documents, not free tools as a category. The distinction that matters is architectural: tools that process in the browser never create a copy on a third-party server, while tools that upload do. Set the policy on the architecture, then whitelist no-upload tools for everyday document work.