Skip to content

Privacy Lab · reproducible evidence

Privacy demonstrated with tests, not promises

We audited all 14 published tools with synthetic documents. The test loads the tool first, disconnects Internet, and only then selects and processes the file.

Audit V2 · 2026-08-30 · production · commit 9a5ebf9

14/14

After disconnecting

14/14 completed the operation and downloaded a valid result.

14/14

Online control

14/14 completed the same flow under network monitoring.

0

Processing requests

0 offline and 0 in the online control.

0

Document transfer

0 requests carrying fixture data and 0 external origins.

What the data support

  • Tools keep processing locally if the connection is lost after they have loaded.
  • No document transfer was detected in the synthetic online control.
  • No external processing origins were detected.
  • No processing network requests occurred in the online control.
  • Offline processing remained completely silent on the network.

Methodology

The sequence avoids a misleading test where the file is selected before the connection is cut.

  1. Open the tool online and wait for its resources.
  2. Take the browser offline.
  3. Select the local synthetic PDF or image after the cut.
  4. Run the real operation and confirm the download.
  5. Repeat online while checking requests, attachments, canaries and external origins.

Result by tool

PASS = completed flow and valid download. PDF Protection was tested in protect mode.

RouteOffline after loadOnline controlProcessing req.
/unirPASSPASS0 / 0
/dividirPASSPASS0 / 0
/extraer-textoPASSPASS0 / 0
/desproteger · protect modePASSPASS0 / 0
/rotarPASSPASS0 / 0
/metadatosPASSPASS0 / 0
/organizar-pdfPASSPASS0 / 0
/marca-de-aguaPASSPASS0 / 0
/comprimirPASSPASS0 / 0
/numerarPASSPASS0 / 0
/imagenes-a-pdfPASSPASS0 / 0
/pdf-a-imagenesPASSPASS0 / 0
/firmar-pdfPASSPASS0 / 0
/recortar-pdfPASSPASS0 / 0

How we interpret “zero transfer”

It does not mean a website never makes requests. During the audited processing phases there were no processing requests, and the synthetic document, its canary and its bytes did not appear as a network body or attachment.

Stats Lite was handled separately: DNT/GPC were simulated and only /__stats-hit was blocked so the audit would not pollute statistics. An anonymous visit signal is not a PDF upload.

What we have NOT tested

  • Cold-starting PDFPrivado with the browser already offline.
  • Every browser, operating system and hardware combination.
  • Real user documents: the audit uses synthetic fixtures.
  • Every possible sub-mode; PDF Protection was exercised in protect mode.

Fully offline cold start: NOT_TESTED.

Public evidence and reproducibility

We publish a sanitized technical summary, hashes and methodology. The raw ZIP is not public because it contains local paths and internal test material.

SHA-256 raw audit ZIP (not public): 8d79f1add93b2735689a17260de39d4eb0d42d7b2658dbfa7113b916438e435f

Representative screenshots

Offline runs with synthetic fixtures. Screenshots are complementary evidence; counters come from the structured report.

Privacy Lab unir offline
/unir · offline
Privacy Lab protection offline
/desproteger · protect mode · offline
Privacy Lab PDF images offline
/pdf-a-imagenes · offline
Privacy Lab crop offline
/recortar-pdf · offline

Equivalent manual test

Load a tool online, wait until ready, turn off Wi‑Fi, choose the file and process it. This is the claim we validated.

PDF privacy observatory · Study V1

Does your PDF tool upload your documents? Reproducible test of 5 online PDF services

We measured one operation only —Merge PDF— with two synthetic documents, the same method, and a second run with network disabled after preloading each tool.

Tests performed on September 5, 2026

Service Was PDF transfer observed? Completed offline after preload? Observed result
UMyPDFNot observedYesLocal processing verified
SmallpdfYesNoRemote document transfer verified
iLovePDFYesNoRemote document transfer verified
PDF24 ToolsYesNoTransfer + remote merge request
Adobe Acrobat OnlineYesNoRemote document transfer verified

How to read this table

We do not label services “safe” or “unsafe”. We publish observed facts for one tool, date and operation. Web telemetry and document transfer are recorded separately.

Study limitations

Only Merge PDF was tested. Results are not extrapolated to other tools or desktop apps. Offline testing started after the web tool was preloaded; a fully offline cold start remains untested.

Evidence summary

UMyPDF

The merge completed online and after network cutoff following preload. We observed no canary PDF transfer and the result was delivered as a local blob.

Smallpdf

We observed two PUT requests to remote storage for .pdf objects. Offline, the interface reported that the files could not be uploaded.

iLovePDF

We observed two POST requests to /v1/upload of about 462.6 KB each, both returning HTTP 200.

PDF24 Tools

We observed two upload POST requests followed by a remote joinPdf request returning HTTP 200.

Adobe Acrobat Online

We observed asset metadata containing canary markers and application/pdf PUT transfers of about 461.3 KB to temporary Adobe storage.

Reproduce the test

Download the same canary PDFs, method, data and sanitized network evidence. They contain no personal data. Signed URLs and temporary tokens are removed from the public dataset.

Control screenshots

UMyPDF — offline after preload
UMyPDF · offline after preload
Smallpdf — offline after preload
Smallpdf · offline after preload
iLovePDF — offline after preload
iLovePDF · offline after preload
PDF24 Tools — offline after preload
PDF24 Tools · offline after preload
Adobe Acrobat Online — offline after preload
Adobe Acrobat Online · offline after preload

Only Merge PDF was tested. Results are not extrapolated to other tools or desktop apps. Offline testing started after the web tool was preloaded; a fully offline cold start remains untested.