Security model · v2.0
A small trust boundary, stated precisely.
Local processing reduces document exposure, but it does not turn a browser utility into a malware scanner or signature validator.
01 / 05
Local documents
File and Blob objects are passed only to same-origin application code and dedicated workers. There is no backend document endpoint, automatic link opening, or arbitrary HTML rendering from PDF content.
02 / 05
Technical loading requests
The browser requests HTML, CSS, scripts, workers, PDF engines, icons, and translations. A restrictive Content Security Policy limits scripts, connections, frames, objects, and forms to the intended origins.
03 / 05
Application cache
Only versioned application assets are cached. Blob URLs, chosen files, rendered thumbnails, results, and analytics payloads are excluded.
04 / 05
Limits of protection
The app does not remove malware, validate digital signatures, guarantee archival conformance, repair every damaged PDF, or bypass passwords. Keep originals and inspect every result.
05 / 05
Vulnerability reports
No public security-reporting channel is currently configured. Do not send confidential documents. This page will be updated before a reporting channel is enabled.