PDF Protect Plus
FR EN

Need to merge two PDFs, shrink a scan or add a password? A quick search turns up dozens of websites that will do it in the browser, often in less time than it takes to install anything. For a lot of tasks, that's a perfectly reasonable choice. For client documents, it's worth pausing on one question first: where does the file go while the work is being done?

This article doesn't argue that online tools are bad. It explains what actually changes between an online tool and software that runs on your own device, so you can decide document by document.

What happens when you use an online PDF tool

Most browser-based PDF tools follow the same pattern:

  1. You select a file, and your browser uploads a copy to the provider's servers.
  2. The servers process it: merge, compress, convert, encrypt.
  3. You download the result.
  4. The copies on the server, the one you sent and the one produced, are deleted at some point, according to the provider's own rules.

Some tools do part or all of the work inside the browser itself, without sending the file anywhere. From the outside, the two approaches can look identical. The only reliable way to know is the provider's own documentation.

The key point is step 1. The moment a file is uploaded, a copy of it exists outside your device, on infrastructure you don't control, governed by terms you may not have read. That isn't a sign of bad intent. It's simply how a server-side service works.

What to read before uploading a client document

If you do use an online tool for anything sensitive, its privacy policy and terms of service should answer a few concrete questions:

If the answers are vague or missing, treat that as information too. And keep in mind that you're relying on the provider to do what its policy says; you can't verify it yourself.

What changes with local software

With software that processes files on your own computer or phone, the sequence is shorter: you open the file, the work happens on the device, the result is saved next to the original. No copy of the document is sent anywhere as part of the process.

That removes a whole category of questions. There's no retention period to check, because there's nothing retained elsewhere. There's no server location, because there's no server in the loop for the document. What remains is your own responsibility: keeping your device secure, backed up and up to date, which you already have to do since the documents live there anyway.

Local software has its own trade-offs, and it's fair to list them:

“PDF protected successfully!” confirmation with the prompt to keep the password
The protected copy is saved on your computer, and the original stays as it was: the file never left the machine — Actual PDF Protect Plus interface · fictional documents

When local really matters

For a restaurant menu, a public brochure or a document you'd happily post on your website, an online tool is fine. The calculation changes when the PDF contains information that belongs to someone else and that you've promised, or are required, to keep confidential:

For those documents, the question isn't whether a given online service is trustworthy. It's whether you need a copy to leave your device at all. If the work can be done locally, not uploading is the simplest answer, and the easiest one to explain to a client who asks how their documents are handled.

A simple rule of thumb many practices adopt: if you wouldn't email the document to a stranger, don't upload it to a service whose terms you haven't read. Then decide case by case.

Bank statement with the IBAN and BIC covered by black boxes
Bank details can be redacted on your own computer before the document goes anywhere — Actual PDF Protect Plus interface · fictional documents

An example

Picture Ortega & Lin, a fictional two-person accounting practice. For marketing flyers and public forms, they use whatever online tool is handy. For client files, they've set a rule: compressing, merging, cleaning metadata and protecting all happen on their own computers. When a client asks how their tax documents are handled, the answer is short: they stay on the firm's machines until they're sent, encrypted, to the client.

How PDF Protect Plus fits in

PDF Protect Plus was built for the second category. Documents are processed on your device, on Windows, macOS or Android. The app talks to our server only for account sign-in, licence checks and the subscription; your PDFs are not sent to it.

The local toolset covers the tasks people most often go online for:

Every result is saved as a new file, so the original stays untouched. More detail on what stays on the device is on the local processing page and in our privacy policy.

Batch protection screen: drop zone for the PDFs and the three password modes
A whole batch is processed on the same computer, with one password per client if needed — Actual PDF Protect Plus interface · fictional documents

The short version

To see how this works for a specific task, read how to merge PDF files without uploading them. You can also download PDF Protect Plus and try it on your own documents during the 7-day trial; plans are listed on the pricing page.

Related reading