Translators: work on clients' documents without uploading them

A translator sees documents before almost anyone else does, and they’re often the confidential kind. An unreleased contract being negotiated across borders. A patent application that mustn’t leak before filing. Someone’s medical records, a birth certificate, a court ruling, a financial report. Clients hand these over because the work can’t be done otherwise, and they usually do it under an NDA that makes confidentiality an explicit condition.

Then there’s the practical side. The source file is a scanned PDF you need as text to work with. It’s too big to email back. It needs to go to a client locked. Each of these is a small PDF task, and each is a point where, with the wrong tool, a confidential source document gets uploaded to a server the translator never vetted.

The NDA problem, in plain terms

Translation work runs on trust and, very often, on signed confidentiality agreements. An NDA is a promise about where information goes: not to third parties, not outside the agreed scope. The trouble is that a free online PDF tool is a third party, and uploading a client’s document to it is exactly the kind of transfer the NDA was written to prevent.

A typical such tool uploads your file to its server, processes it, and deletes it later on a schedule you can’t check. For a patent under embargo or a contract mid-negotiation, that’s a confidentiality breach hiding inside a routine task. You can’t honestly tell a client their document stayed confidential if you ran it through a server you don’t control to turn a scan into text.

How reader.me fits translation work

reader.me runs entirely in your browser. There’s no upload because no server does the processing; the engine runs on your own computer, inside the browser tab.

So when you turn a scanned source PDF into text you can work with, your browser does it on your machine, and the document never travels. For a freelancer or an agency bound by NDAs, that’s the difference between keeping your word and breaking it for the sake of convenience. The client’s file stays on your desk from start to finish.

And it’s verifiable, which matters when a client asks how you handle their material. Open any reader.me tool, open developer tools (F12), and watch the Network tab while you work. Nothing uploads. Disconnect from the internet and it still works, because the file was never going to leave.

The everyday jobs, kept confidential

• Turn a scan into usable text. A scanned source document is just an image until you run OCR, which adds a real text layer so you can select and work with the words. The scan never leaves your machine.
• Pull the source text out. Need the exact wording to work from, or a word count? Extract the text instead of retyping, locally.
• Compress for delivery. Scanned source files and finished documents get heavy. Compress a PDF to fit an email without uploading the client’s document first.
• Assemble a deliverable. Merge a multi-part translation, or the source and target side by side, into one clean file.
• Lock what you send back. Returning a sensitive translation? Protect it with a password and share the key separately.

Confidentiality you can actually promise

The value a client gets from a professional translator isn’t just accuracy; it’s discretion. They’re trusting you with information before the world sees it. That trust is hard to honor if part of your workflow quietly sends their documents through outside servers whose deletion promises you take on faith.

Working in the browser closes that gap. The client’s document goes from their hands to yours to the finished translation, and through no PDF service in between. There’s no third-party retention policy to rely on, because nothing was sent. When a client, or an NDA, asks you to confirm their material wasn’t shared, you can say so plainly. Open the PDF tools, do the work locally, and the confidential source you were trusted with stays exactly where it should: with you.