Privacy checklist before using an online PDF tool

Classify the document first

A public brochure and an employee record do not carry the same consequence if exposed. Look for government identifiers, account numbers, health information, customer lists, signatures, unpublished financials, contracts, credentials, and information covered by an employer or client policy.

If the document is regulated, confidential, under legal hold, or owned by another party, use the approved organizational workflow. A convenient consumer web tool should not override a data-handling agreement or security policy.

Understand where processing occurs

A browser interface can still upload a file to a server. HTTPS protects data in transit but does not describe how the server stores, logs, copies, or deletes it. Look for a concrete statement about processing location, retention period, accounts, analytics, backups, and third-party subprocessors.

This editor sends the PDF to its Cloud Run backend. The file is held in volatile application memory during the active editing session, removed after export, or expires after at most about ten minutes if the workflow is abandoned. It is not intentionally written to persistent document storage. Operational infrastructure may still process request metadata such as time, response status, and network information.

Reduce what you send

If only one non-sensitive page needs correction, create a local copy containing only that page before upload and merge it back with an approved tool afterward. Redact sensitive content only with a true redaction workflow; drawing a black rectangle over text may leave the underlying text extractable.

Remove comments, attachments, form data, and hidden layers locally when they are not needed. Preserve the original separately. Never test a questionable service using a real confidential file when a synthetic sample can verify the workflow.

• Use a made-up sample to test compatibility.
• Upload only the pages required for the task.
• Avoid shared or public computers for sensitive work.
• Do not edit a signed document without understanding signature invalidation.

Evaluate the service claim

Specific, limited language is more credible than “100% secure.” Check whether the actual product limits match the policy, whether the company explains deletion timing, and whether support material acknowledges unsupported files and output limitations.

For this site, input is limited to 10 MB and 50 pages. PDFs with encryption, interactive forms, embedded files, JavaScript, or certain active content are rejected. Rate limits protect the service. These controls reduce attack surface but do not make every document appropriate to upload.

Handle the result safely

Download to a trusted device, open the output with current PDF software, and confirm that only intended content changed. Rename the new file so it cannot be confused with the original. If the document contains sensitive data, store and share it under the same policy as the source.

Close the editing session after export. Clear browser downloads or temporary copies when organizational policy requires it. For material decisions, keep an audit note describing the original, the edited version, who reviewed it, and why the change was authorized.