Local file processing
The core editing and conversion workflows are designed to process files in the browser on your device. In normal use, uploaded PDFs, generated files, selected page ranges, passwords entered for compatible lock or unlock flows, and similar workflow data are not sent to a remote document-processing server in order to complete the task.
That local-first design is the main privacy property of the product. It reduces exposure for sensitive files, but it does not replace your responsibility to secure your own device, browser, and downloads folder.
Analytics and consent
Optional analytics and advertising-related scripts are not required for core PDF workflows. They are consent-gated and can be kept disabled. During AdSense remediation or other review periods, ad loading may be disabled entirely so the site can be reviewed as a product rather than an ad surface.
Analytics, when enabled, are intended for broad product measurement rather than document-content inspection. The goal is to understand usage patterns, not the private contents of a visitor’s files.
Cookies and local storage
The site may use local storage or similar browser storage for product settings, consent state, install-banner preferences, cached runtime assets, and offline capability. These are functional product behaviors, not hidden document uploads.
If you clear site data in your browser, preferences and offline assets may be removed. That can require the app to reload assets online before offline use is available again.
Offline caching
When the PWA service worker is active, the app caches the code and assets required to run supported tools offline after a successful online load. This includes scripts, styles, worker files, and other same-origin runtime assets needed by the application.
Offline caching improves availability. It also means application assets remain stored on the device until the browser evicts them or the user clears them.
Contact for privacy questions
If you have a privacy question, contact [email protected]. The best messages are specific about the behavior you want explained: local processing, cached assets, cookies, optional analytics, or offline install behavior.