PRIVACY VERIFICATION GUIDE
How to verify that a PDF tool never uploads your file
Do not rely only on a privacy badge. Use this repeatable test to inspect network traffic, disconnect from the internet, and confirm that the finished PDF is created by your browser.
Quick test: turn Wi-Fi off
- Open the PDF tool and wait for the page to finish loading.
- Disconnect Wi-Fi or unplug the network cable.
- Select a non-sensitive test PDF and run the tool.
- Confirm that processing and download still complete.
A successful offline job is strong evidence of local processing, but it does not prove that the page made no earlier or later network requests. Complete the network test below as well.
Definitive browser network test
- Open Developer Tools, then select the Network panel.
- Enable “Preserve log” and clear the existing requests.
- Filter by Fetch/XHR, then select and process a harmless sample PDF.
- Inspect every new request, including its method, size, request payload and destination.
- Verify that no request body contains the PDF, filename, extracted text or document pages.
- Repeat once while downloading the output and once after the job finishes.
What network requests are normal?
A site may load JavaScript, fonts, analytics or advertisements without uploading your PDF. The important distinction is whether a request sends document bytes or document-derived content. Analytics should record only operational events such as tool started, completed or failed—not filenames, document text or PDF contents.
How YourPDFJob can be checked
Load a tool, disconnect from the internet, and process a sample document. Core PDF jobs run inside your browser. Your files are not sent to a YourPDFJob processing server. Very large documents remain subject to the memory and capabilities of your device and browser.
Related: Compare privacy tests for PDF tools