How your privacy works
Most of this page is one sentence: your file is processed on your device and is never sent to our servers. Here's exactly why that's true, tool by tool.
What happens when you choose a file
The file is read directly by your browser using standard web APIs. SubmitReady's code — which runs entirely on your device, the same as any website's JavaScript — reads the bytes locally to compress, merge, rotate, or otherwise transform the PDF. At no point is the file sent over the network to a SubmitReady server, because there is no upload step in any tool on this site today.
The one exception: text recognition (OCR)
The "Make PDF searchable" tool uses on-device optical character recognition to read text out of scanned pages. The recognition engine itself (a generic language model — not your document) is loaded from SubmitReady's own servers the first time you use that tool. Recognition runs locally in your browser; the recognized text and your document content never leave your device.
What we store
Nothing about your file. We don't store your document, its filename, its extracted text, or a copy of it for debugging. There is no document database, no document history, and no account system that could be tied to a file you processed.
Analytics
We use privacy-respecting product analytics to understand which tools are used and whether they succeed — events like "a compression job finished" — without cookies and without any file content, filename, or extracted text attached.
Full technical detail
The complete, engineer-level breakdown of this — including exactly which browser APIs are used and what the fallback behavior is if something fails mid-process — lives in this project's PRIVACY-ARCHITECTURE.md file alongside the source code.