What actually happens to a PDF you upload to an online tool

An online PDF tool can work in the browser, on a server, or through a mixture of both. That distinction matters. A local-only tool may keep the document on your device, while a server-side tool must receive a copy before it can process the file.

TryDeputize currently uses server-side processing for Merge PDF and its other file tools. This page explains that path plainly, including the limits of what any privacy promise can prove.

The upload is a copy, not a loan

When you choose a file, your browser sends a copy over HTTPS. The source on your device is unchanged. The server stores the uploaded copy long enough to run the job, and the processed result is another file that must stay available long enough for you to download it.

That is normal server-side processing. The safety question is not simply “Was it uploaded?” It is who can access the storage, what else uses the file, how long both copies remain, and whether the service is suitable for the document.

The three questions worth asking

How long is the file kept? Look for a concrete deletion period. TryDeputize targets about 60 minutes, with a cleanup job that runs every 10 minutes and removes both the upload and result after they pass the cutoff. The exact removal time can therefore be a little later than one hour.

Is an account required? An email address turns an anonymous document into a file associated with a person. An account is not automatically unsafe, but it changes the data relationship and should have a clear purpose. TryDeputize file tools do not require one.

What else touches the file? Some sites use uploads to improve products or train models, while others limit processing to the requested job. Read the service’s privacy terms and check whether subprocessors, analytics, backups, or human review are mentioned. The TryDeputize privacy page states that file contents are not sold or used for model training.

A practical decision before you upload

First classify the document, not the tool. Everyday forms, public reports, and non-sensitive scans may be reasonable candidates for a short-lived online job. Medical records, legal discovery, unreleased financial information, identity documents, and files covered by a workplace policy deserve a stricter check.

Then ask whether the task genuinely needs a server. A small merge may be easy to complete locally. If you do use the site, upload only the necessary pages, download the result promptly, and remove local working copies you no longer need.

The complete Merge PDF guide explains the actual merge limits and deletion window. If a sensitive result also needs encryption before it is shared, read the password protection guide and remember that encryption does not make an inappropriate upload acceptable.

When an online tool is the wrong choice

• Policy requires local processing. Automatic deletion is not permission to ignore a client, employer, school, healthcare, or legal data rule.
• The harm from disclosure is high. If an upload could expose identity, financial, medical, legal, or confidential business information, use an approved system with the required controls.
• You need independent proof of deletion. A published retention period is a promise backed by system design and operations, not a receipt proving that every copy disappeared.
• The job is repeated or automated. A reviewed local script or managed document platform may be faster, more auditable, and easier to keep within policy.