Privacy

Privacy

How FileFlow handles browser-based PDF processing and temporary in-memory data.

Browser-first by design

For the tools in this release, FileFlow does not implement a server endpoint that receives your document bytes. Processing happens in your browser. Some tools load pinned open-source JavaScript libraries from jsDelivr so the browser can perform PDF operations and rendering.

What we do not store

This version has no user account database, document history, or cloud document storage. Closing or refreshing the page clears the in-memory job state.

Third-party delivery

Loading third-party library files can expose ordinary network metadata such as an IP address to the CDN provider. Before commercial launch, the production privacy policy should be reviewed for the final analytics, advertising, payment, support, and hosting setup.

Important files

Always keep your original document. Browser processing can fail on damaged, encrypted, unusually large, or complex PDFs.