Privacy
This page describes exactly what Fold does and doesn't do with your files. We'd rather under-promise than make a claim our architecture doesn't actually back up.
Your files
Every tool on this site processes your file entirely inside your browser, using a Web Worker. Your file is read locally, transformed locally, and handed back to you as a download — it is never transmitted to a server. You can verify this yourself: open your browser's network inspector while using any tool here and you'll see no request carrying your file.
Because processing happens on-device, we have no server-side copy of your file to lose, leak, or be compelled to hand over — there is no copy to begin with.
| Tool | Processing |
|---|---|
| Compress PDF | local |
| Merge PDF | local |
| Split PDF | local |
| PDF to JPG | local |
| PDF to PNG | local |
| PDF to WebP | local |
| JPG to PDF | local |
| PNG to PDF | local |
| WebP to PDF | local |
| Images to PDF | local |
| Rotate PDF | local |
| Delete Pages | local |
| Extract Pages | local |
| Reorder Pages | local |
| PDF Metadata | local |
| Protect PDF | local |
| Unlock PDF | local |
| Compress Image | local |
| Resize Image | local |
| Convert Image Format | local |
| HTML to PDF | local |
What we store locally
We use your browser's localStorage for exactly two things: your theme preference, and the IDs of the last few tools you used (so the command palette can show "Recent"). Neither of these ever contains a filename, file content, or anything derived from a document you've processed.
Cookies
We don't set any cookies. Nothing on this site requires them.
Analytics
The site can optionally report anonymous, product-level events — such as which tool was opened, completed, or failed — to help us understand what's useful. This is disabled by default and only activates if an analytics endpoint is explicitly configured for a given deployment. The event payload is restricted at the type level to plain strings/numbers/booleans and a fixed set of event names: it is not possible for a file, filename, or document content to be included, by construction, not just by policy.
Third parties
This site loads no third-party scripts, fonts, or trackers. The PDF and image processing libraries it uses run entirely as local code inside your browser — they do not make network requests.
What we don't claim
We don't claim formal compliance with GDPR, SOC 2, HIPAA, or similar frameworks — those require processes and audits beyond what's described here. If your use case requires a formal compliance claim, please get in touch before relying on this site for it.
Questions
If anything here is unclear, or you find behavior that doesn't match this page, please open an issue on our GitHub repository.