What we collect (almost nothing)

This page is short on purpose. Most privacy policies hide their answers inside legal boilerplate. We'd rather you understand ours in two minutes.

• ✓ Your PDF files are never uploaded by any in-browser tool — they stay on your device from start to finish.
• ✓ No account or signup is required for any tool on this site.
• ✓ No tracking cookies. Analytics are cookieless and record no personal identifiers.
• ✓ Error reports contain no file data — only the error message, browser version, and tool name.
• ✓ Server tools are clearly labelled. If a tool ever processes your file on a server, it says so on the tool page before you upload.

Your files

Tools tagged "In-browser" don't see your files at all. When you drag a PDF onto a browser-based tool, the bytes go from the file picker straight into a WebAssembly module running in your browser tab. Nothing in that path makes a network call with your file's contents. You can verify this in DevTools → Network.

Tools tagged "Server" (currently none in v1, planned for OCR later) will process files on a server and delete them immediately after the response. We'll never have a server tool without saying so clearly on the tool page, and we'll never quietly switch an in-browser tool to server-side processing.

The reason in-browser tools can make this guarantee is architectural, not just policy. A WebAssembly module running inside a browser tab is subject to the same browser sandbox as any JavaScript on the page. It cannot open a raw TCP socket. It cannot write to disk. The only way it can send data across the network is through the browser's standard fetch or XMLHttpRequest APIs — and any call made through those APIs appears immediately in the browser's DevTools Network panel. If no outbound request containing your file data appears in that panel while you run a conversion, no file data left your device. This is verifiable by anyone, any time, without trusting our word for it.

Analytics we use

We use a privacy-friendly analytics service (Plausible or Cloudflare Web Analytics, depending on the host). It logs page views without cookies, doesn't share data with advertisers, and doesn't fingerprint you. From it we learn things like "which tools are getting used" and "which page is broken in Firefox"; we don't learn who you are.

Privacy-friendly analytics differs from services like Google Analytics in several concrete ways: no cross-site tracking (your activity on this site is not correlated with your activity on other sites), no cookies set in your browser, no storage of IP addresses, and no data sold or shared with advertising networks. The aggregate data we see is page view counts and event counts — numbers, not identities. It is hosted in the EU under GDPR, and we cannot drill down to individual users even if we wanted to. If you use an ad blocker or privacy-focused browser extension, it will likely block the analytics script entirely, which is fine.

The specific events we record about tool usage:

• Tool viewed (just the tool slug, e.g. /fill-pdf).
• File added (your file's MIME type + a size bucket like "5–25MB" — never the file name or contents).
• Tool started / succeeded / failed (with a duration and, if failed, the error reason).
• Download clicked.

None of these include your filename, your file's contents, or any personal identifier.

Errors we track

If a tool crashes, the JavaScript error message is sent to Sentry so we can fix it. The error includes the stack trace, the browser version, and the tool slug. It does not include your file or its contents.

Cookies

We don't set tracking cookies. Your browser may store a few small preferences locally (last-used filename, saved signature shape) — these stay on your device and aren't sent anywhere.

If you contact us

Emails to hello@pdfwox.com land in a regular inbox we read. We keep them for as long as it's useful to keep them and don't share them with anyone.

Changes

If we change this policy in a way that affects users, we'll update the "last updated" date at the top and (for material changes) post a note on the homepage for at least a month.

Questions

Email hello@pdfwox.com. For the architecture story behind all of this, see Why a browser-based PDF tool is safer than an upload site.