Privacy Policy

Last updated: July 2026

The short version: your files never leave your device, and we don't collect anything. FreshPDF has no accounts, no analytics, no ads, no tracking pixels and no server of its own. This page explains exactly what that means — including the few things that are outside our control.

Your documents

Every FreshPDF tool — the editor and all standalone tools — runs entirely in your web browser using JavaScript. When you open, edit, merge, convert, sign or encrypt a file:

  • The file is never uploaded. There is no upload endpoint. Processing happens in your browser's memory, on your device.
  • We never see it. There is no server-side component that could receive, log or retain your documents.
  • Closing the tab discards it. Unless you explicitly save a download, nothing persists.

You can verify this yourself: load a file, switch your device to airplane mode, and keep working — everything still functions, because nothing depends on a network connection.

What is stored on your device

FreshPDF uses your browser's local storage for small preferences that never leave your device:

  • Theme choice (light or dark mode).
  • Editor conveniences such as saved signatures and recent settings, if you use those features.
  • Offline cache: a service worker stores the app's own files (HTML, CSS, JavaScript) so FreshPDF loads fast and works offline. This cache contains our code, never your documents.

You can clear all of this at any time through your browser's site-data settings. FreshPDF sets no cookies and uses no fingerprinting.

Analytics and third parties

There are none. No analytics scripts, no advertising networks, no social-media pixels, no external fonts, no CDN-loaded code. Every script FreshPDF runs is served from this site itself.

What we can't control: hosting

FreshPDF is a static site served by GitHub Pages. Like virtually every web host, GitHub's servers may record standard technical logs (such as IP addresses) when your browser fetches the site's files. That happens before our code ever runs, applies to any website you visit, and is governed by GitHub's privacy statement. We never receive or see those logs' contents tied to your usage of the tools — and your documents are never part of any request.

Encryption features

When you password-protect a PDF, the encryption (AES-256) is performed in your browser using the Web Crypto API built into your browser. Passwords are used in-memory for the operation and are not stored or transmitted.

Children's privacy

FreshPDF collects no personal information from anyone, including children.

Changes to this policy

If we ever change how FreshPDF works in a way that affects privacy, we will update this page and change the date at the top. Given the architecture — no server, no accounts — meaningful changes would require rebuilding the product's foundations, which is not the plan. The privacy model is the product.

Contact

Questions about this policy? Open an issue on GitHub and we'll respond there.