Privacy
Your PDFs stay on your device.
PagePilot's core tools process PDF files locally inside your browser. Your PDF content is not uploaded to PagePilot, stored in an account, or sent to an AI service.
Core PDF processing
- Files are selected through your browser and read into browser memory.
- Previews and PDF operations run locally, including browser workers.
- Finished PDFs are downloaded with a temporary local Blob URL.
- Document contents are not stored in cookies, persistent browser storage, an offline database, or a service-worker cache.
- Closing or refreshing the page clears the current in-memory workspace.
Minimal product analytics
PagePilot uses cookieless Vercel Web Analytics for a small set of product events. Automatic browsing pageviews are discarded. Allowed actions are counted with event-only paths containing an event name and, for tool events, only the tool name. The analytics service also receives ordinary technical request information needed to deliver the event, such as browser, device, and approximate region.
Events we measure
- Tool opened
- File selected
- Operation started
- Operation completed
- Export completed
- Workflow started or completed
- Feedback link clicked
Never included
- PDF content or page text
- File names, document titles, or author metadata
- File hashes, file sizes, or page counts
- Typed notes, form text, or signature text
- Student names or assignment names
External links
Feedback and optional support links open external services. Their privacy practices apply after you leave PagePilot. PagePilot never attaches your PDF to those links automatically.
Future cloud features
If a future OCR, conversion, compression, or cloud feature requires an upload, PagePilot will disclose that clearly and ask you to start the upload explicitly. Those features are not part of this public beta.
Effective: 16 August 2026