No processing API
The static application contains no route that accepts document bytes, filenames, extracted text, or passwords.
Verifiable local processing
Privacy is an architectural boundary
PDFPioneer is exported as static files. Application assets may be requested from your own origin, but document content is processed by browser workers and never submitted to a document-processing service.
Outbound guard
Window APIs and the service worker block cross-origin fetches, XHR, WebSockets, and beacons from the editor.
Local revisions
OPFS stores recoverable revision snapshots where supported. An in-memory fallback is used when local persistence is unavailable.
Local metadata
IndexedDB stores small operation records and preferences. Clearing site data removes that local workspace state.
Visible activity
The activity panel exposes allowed and blocked browser requests rather than asking users to trust a marketing claim.
No editor analytics
Do not add third-party analytics, advertising, session replay, or support widgets to app.pdfpioneer.com.
Network activity
Guard active
Requests made after this panel opens will appear here. Blob and local application resources are allowed; cross-origin requests are blocked.
Browser storage controls
Data kept on this device
Revision snapshots use OPFS where available. IndexedDB stores session and operation metadata. Cached application assets enable offline use.
Origin usage
Checking…
Estimated quota
Checking…
Persistence
Checking…
Deployment rule
Serve the editor from an isolated origin such as app.pdfpioneer.com, self-host all core WebAssembly, OCR, and font assets, and apply the included CSP/COOP/COEP headers. Deploy optional add-ons separately. Keep marketing analytics on a separate origin.