Plain-language privacy
Privacy, without the fine-print fog.
kompressPDF is a static website with client-side tools. This page explains exactly what happens to a file when you use it — and the small amount of standard web plumbing that sits outside the app itself.
Last updated · November 18, 2026
What happens to your files
When you choose a file, the browser reads it into this tab’s memory using the local File API. Every operation — compressing, splitting, merging, editing, encrypting, converting — is performed by JavaScript running on your own device. The result is assembled as an in-memory Blob and handed to your browser’s download mechanism.
Nothing is sent to a server, because the app has no server endpoints for file data. There is no storage bucket, no processing queue and no account system. Closing or reloading the tab discards the file from memory. Generated download links are revoked shortly after you click them.
What we collect
Nothing. kompressPDF does not run analytics, advertising pixels, session recording or A/B testing. It sets no cookies and writes nothing to local storage. There is no account, email capture or newsletter form.
- No cookies
- No analytics
- No file uploads
- No accounts
Hosting and standard request metadata
The site is served as static files by Cloudflare Pages. Like any web host, Cloudflare may log standard request metadata — such as IP address, user agent, requested URL and timestamp — for delivery, security and abuse prevention. That is ordinary web-server plumbing and applies to the page itself.
Your file contents are never part of any request. They do not leave the browser tab, so they cannot appear in hosting logs. No custom server logic is deployed alongside the static site.
Fonts and third parties
Typefaces are self-hosted variable WOFF2 files served from this domain — no Google Fonts, no font CDN. The site loads no third-party scripts, iframes, trackers or remote images. Heavy processing libraries are bundled with the site and fetched only from this origin when a tool runs.
What this policy cannot promise
Client-side processing removes the biggest risk — handing your document to a stranger’s server — but it cannot protect a device that is already compromised, or a browser extension that can read page content. Use a trusted browser and keep your own backups of important files, especially before destructive edits.
Changes to this page
If the way the site works changes in a way that affects this policy, the “last updated” date above will move with it. There is no mailing list to notify — the page itself is the record.