Public sector: handle citizens' files without uploading their data
Case files, applications, ID scans, benefit records. Government offices run on PDFs full of citizens' data. reader.me processes them in the browser, so nothing is uploaded to a server.
A public administration holds some of the most sensitive data there is, and it doesn’t get to choose. A benefits application has someone’s full financial situation. A case file might hold an ID scan, a medical certificate, a criminal record check, a child’s details. Citizens don’t opt in to handing this over; they have to, to get a service they’re entitled to. That raises the bar for how their files get handled.
Then a clerk has a perfectly ordinary task to do. Merge the documents in a case file into one PDF. Compress a scanned folder so it fits the email system. Make an old scanned record searchable. The quick way to do each of these is a free online tool, and that quick way is how a citizen’s data ends up on a server the administration never vetted.
A different standard applies here
When a private company is careless with data, it’s a breach. When a public body is careless with citizens’ data, it’s also a breach of trust people couldn’t avoid giving. The data was collected under legal authority, often with no real alternative for the person, and that comes with a duty to protect it that’s higher, not lower, than the private sector’s.
A typical online PDF tool uploads the file to its server, processes it there, and deletes it later on a schedule nobody can verify. For a citizen’s case file, that’s a transfer of personal data to an unknown third party, frequently one in another jurisdiction, governed by terms no one in the office has read. It’s exactly the kind of uncontrolled processing that public-sector data rules exist to prevent. “It was just to merge the PDF” is not something you want in an incident report.
How reader.me fits the public sector
reader.me runs entirely in the browser. There’s no upload because there’s no server doing the work; the engine runs on the office’s own machine, inside the browser tab.
So when a clerk merges a case file, the browser reads the documents into memory on that computer, combines them right there, and produces the result. The citizen’s PDF never travels. For a public body, that’s the difference between routine work and a reportable data transfer. The file stays inside the office the entire time.
And it’s verifiable, which matters when a data protection officer or an auditor asks. Open any reader.me tool, open developer tools (F12), and watch the Network tab while processing a file. Nothing uploads. Disconnect the machine from the internet and it still works, because the data was never going to leave.
The everyday office jobs, kept in-house
- Assemble a case file. Merge the application, the supporting documents, and the correspondence into one PDF, locally.
- Compress for internal systems. Scanned files are heavy and email or document-management limits are real. Compress the PDF without sending the citizen’s documents anywhere first.
- Make an archived record searchable. Old scanned files become searchable after OCR, so staff can actually find what they need. The scan stays on the machine.
- Add an official signature. Sign a decision or a form with the signature tool, no third-party signing service holding the document.
- Protect what you send out. Sending a citizen their own file, or passing one between departments? Lock it with a password and share the key separately.
Accountability built in, not promised
Public bodies have to be able to account for what happens to the data they hold. That’s hard to do honestly when part of the workflow runs through outside servers whose deletion policies you take on faith. Processing in the browser closes that gap: there’s no third party to account for, because there isn’t one. The file goes from the citizen, to the office’s machine, to where it needs to be, and through no PDF service in between.
A clerk also shouldn’t have to choose between getting the work done and protecting the person whose file it is. A tool that runs locally removes the choice. The citizen handed over their data because they had to. Keeping it inside the office, every step of the way, is the least the administration owes them. Open the PDF tools, do the job in the browser, and the data stays where the public trust requires it to.