P
PDFtools

Privacy Policy

PDFtools was built with a simple principle: your files are yours. We can't see them, we don't want them, and we built our architecture to make it impossible for us to access them.

Zero-Knowledge Architecture

We process zero files on our servers. We collect zero personal data. We use zero cookies. We run zero analytics.

No Server Uploads

Your files are never sent to any server. All PDF processing happens locally in your browser using JavaScript and WebAssembly. We physically cannot access your files.

No Tracking

We don't use Google Analytics, Facebook Pixel, or any tracking scripts. We don't track which tools you use, how often, or what files you process.

No Cookies

We don't set any cookies. The only local storage used is your theme preference (dark/light mode), which stays on your device.

No Data Collection

We don't collect email addresses, names, IP addresses, or any personal information. There are no accounts, no sign-ups, no forms.

Open Source

Our entire codebase is open source on GitHub. You can inspect every line of code to verify our privacy claims. Transparency is our policy.

No Third-Party Access

Since we never receive your files, no third party can access them either. There is no data to breach, sell, or share.

Technical Details

For the technically curious — here's exactly how it works under the hood.

How does file processing work?

When you select a file, the browser reads it into memory using the File API. We then use JavaScript libraries (pdf-lib, PDF.js) to process the file directly in your browser's memory. The result is generated as a Blob and downloaded to your device. At no point does any data leave your browser.

What about the PDF.js worker file loaded from a CDN?

The PDF.js worker is a JavaScript file that helps render PDF pages. It's loaded from Cloudflare's CDN (cdnjs). This is a static script file — no data is sent to the CDN. Your PDF files are never transmitted.

Do you use any analytics?

No. We have zero analytics, zero telemetry, and zero tracking. We don't know how many users we have, and that's by design.

What about hosting?

The site is hosted as static files on Vercel. The hosting provider serves HTML, CSS, and JavaScript files to your browser. All PDF processing happens after these files are loaded — entirely on your device.

Can you see my files if I report a bug?

No. Bug reports go through GitHub Issues. We never ask for or accept user files. If you encounter a bug, describe the steps to reproduce it and we'll investigate using test files.

This privacy policy is effective as of February 2026. Since we don't collect data, there's nothing to update — but if our architecture changes, this page will be updated and the change will be visible in our open-source repository.