Verify It Yourself

"Your files never leave your device" is an easy claim to make and a hard one to trust from a privacy policy alone — dozens of browser-only PDF tools say the same thing. So don't take our word for it. Every check below takes under a minute and uses nothing but your browser's own built-in tools.

1. Watch the Network tab while you use a tool

This is the most direct check there is: if a request carrying your file existed, it would show up here.

  1. Open your browser's developer tools (F12, or Cmd+Option+I on a Mac) and switch to the Network tab.
  2. Open any tool — Merge, Compress, Redact, whatever you'd actually use — and load a file into it.
  3. Run the operation and download the result.
  4. Scroll through the request list. You'll see the page's own JavaScript and CSS load once, and nothing else — no request whose size matches your file, no request going to a domain other than this one, at any point before, during, or after processing.
2. Turn off your network and use it anyway

Like any website, the first visit needs a connection to download the app itself. After that:

  1. Open a tool once so your browser caches its code (a few hundred KB, shown in the Network tab from step 1).
  2. Turn on airplane mode, or disconnect Wi-Fi entirely.
  3. Reload the page and run the tool again — merge, rotate, sign, redact.
  4. It works exactly the same, because processing your file was never a network operation to begin with.
3. Read the policy that enforces this, not just describes it

Below is the exact Content-Security-Policy response header this page was just served with — fetched live from this request, not copied into this page by hand. It is a browser-enforced allow-list: the four kinds of outside connection below are the only ones any script on this site is permitted to make. Nothing else — no matter what a compromised dependency or a bug tried to do — could ever send your document anywhere, because the browser itself would refuse the connection.

  • Our own Supabase project — account sign-in and Pro status only, never document content.
  • Stripe's domains — the checkout script and payment iframe, loaded only when you open Upgrade to Pro.
  • jsdelivr.net and tessdata.projectnaptha.com — the OCR engine and language data, loaded only the first time you run OCR.
  • This site itself, for everything else, including the optional anonymous page-view counter described in the Privacy Policy.
Fetching the live header…
4. Read the code

Every tool's processing code runs as ordinary JavaScript in your own browser tab, which means it is never hidden from you: open developer tools, find the file in the Sources tab, and read exactly what it does to your document. There is no server-side step to take on faith.

Found something that doesn't match what's described here? Tell us: privacy@getpdfvault.com.