1. What Information Do We Collect?
We believe the best way to safeguard user data is to not collect it in the first place. PDFMiniFly does not collect, log, store, or inspect:
- The contents, text, images, or metadata of any files you process.
- Your identity, personal email, or passwords used to lock documents.
- Biometric data, signatures, or drawings you create on signatures.
2. How Does Browser-Based Processing Work?
Traditional PDF websites rely on cloud servers where your PDF is uploaded, saved to temporary disks, processed by a server script, and sent back. Even when servers claim to “delete files after 1 hour”, your private data traverses the public internet and sits in third-party storage.
PDFMiniFly uses high-performance modern web technologies (HTML5 Canvas, PDF-Lib, PDF.js, and Tesseract.js WebAssembly). The entire processing engine runs right inside the tab on your device. You can verify this anytime by inspecting your browser Network tab during file operations—you will notice 0 bytes of document payloads transmitted.
3. Local Activity History
PDFMiniFly includes a convenience “Recent Jobs” counter. This information is saved strictly to your local browser storage (localStorage) and only contains the filename, tool name, and completion timestamp. Document contents are never stored, and you can clear this history anytime with one click.
4. Offline Capability & Data Isolation
Because PDFMiniFly is designed as a Progressive Web App (PWA), the core application bundle is cached in your browser. Supported tools work offline without an active internet connection.
5. Optional Cloud AI Services (PDF Assistant)
While standard tools (Merge, Split, Compress, Organize, Sign, Redact, Booklet, OCR, etc.) execute locally in your browser, advanced generative AI features (such as Cloud AI summarization or Q&A in the PDF Assistant) require external intelligence. To guarantee total user sovereignty, Cloud AI is strictly opt-in: the app will never send document excerpts to an AI endpoint unless you explicitly confirm and consent in the prompt modal. By default, local heuristic analysis is used.