There is no retention window
No uploads, no buckets, no deletion jobs: what FernPDF’s no-server model means in practice.
Most PDF websites need a careful privacy policy for your documents because, at some point, they hold them. FernPDF never does. When you drop a file onto any of our tools, your browser opens it with the File API and processes it right there, on your device. There is no upload step, which means there is no server copy of your document at any moment, for any duration.
It helps to list what simply doesn’t exist here. FernPDF has no upload endpoint to receive your files, no storage bucket to keep them in, no processing queue where they wait, no retention schedule, and no deletion job. We aren’t promising to delete your documents quickly. We never have them at all.
You don’t have to take that on faith. Open your browser’s developer tools, switch to the Network tab, and use any tool with a real file. You’ll see the page’s own assets load, and then nothing: no upload request, no storage traffic, no polling. The absence of traffic is the proof.
Here’s what does live on your machine: preferences, your recent-activity list, and anything a tool saves for convenience sit in your browser’s local storage, on your device, and clearing site data removes them completely. The result of every tool is a download that goes straight from your browser’s memory to your Downloads folder.
If you’re evaluating any PDF tool, ours included, the question that matters is simple: does my file leave this device? With FernPDF the answer is no, and it’s a property of how the product is built, not a clause in a policy.
Try it yourself. Every FernPDF tool runs in your browser. Open one and watch the network tab.
Open Compress PDF