“No upload” is a claim. Here's the proof.
Every online PDF tool says it cares about privacy. CommandEditor is architecturally incapable of seeing your files — and you don't have to trust us. Three checks, two minutes, no account.
1 · Watch the network tab
- Open your browser's developer tools (F12) → Network tab.
- Drop a PDF into CommandEditor and run any tool — merge, compress, sign.
- Watch: zero requests carry your file. The only traffic is static code and fonts, fetched once.
2 · Pull the plug
Load CommandEditor, then switch off your Wi-Fi. Every tool still works — because the processing never needed a server. (The PWA service worker caches the app; the engines are WebAssembly running on your device.) An upload-based tool dies the moment you go offline. Ours doesn't notice.
3 · Read the code
CommandEditor is open source: github.com/kjelili/commandeditor. There is no upload endpoint to audit around — the architecture has no server-side document processing at all. The built-in Network Audit tool monitors outbound connections from within the app itself.
What we do transmit
Nothing, by default. Optional features that visibly reach out are always initiated by you and labelled: P2P Co-Review (direct browser-to-browser WebRTC, no document server), blockchain notarization (a SHA-256 hash only — never the file), and the on-device AI assistant downloading its open model once from a CDN. Your documents are never part of any request.