Security Model & Technical Specifications
Our security model is founded on one simple premise: the safest document is the one that is never transferred over the internet.
Zero-Trust Network Model
By executing all PDF parsing and byte-level manipulation within the browser's JavaScript sandbox, we eliminate man-in-the-middle transmission vulnerabilities.
Ephemeral Memory Lifecycle
Document data is held exclusively in volatile RAM while the active tab is open. No data is written to localStorage, IndexedDB, or browser storage.
Audited Open-Source Dependencies
We rely exclusively on vetted, battle-tested PDF engines: Mozilla's PDF.js and pdf-lib.
Static Edge Delivery
Our frontend website is served purely as static, pre-rendered HTML/JS from global CDN edges, completely eliminating server-side injection vectors.
How to Independently Audit Our Zero-Upload Architecture
You don't have to take our word for it. Any security engineer, compliance auditor, or IT administrator can independently verify that zero document payload data leaves your workstation:
Press F12 or Ctrl+Shift+I in Chrome/Firefox. Open the Network tab and filter by Fetch/XHR.
Drop any PDF into our Merge, Compress, or Sanitize tool and click Process. Observe the network traffic.
You will see exactly 0 POST/PUT requests. Processing completes strictly in browser WebAssembly RAM.
📶 Air-Gapped Test Supported:
Load any tool page, disconnect your Wi-Fi or activate Airplane Mode, and process your files. Every tool runs 100% offline without internet.