Privacy Policy

The Short Version

We don't have a server that receives your files. We don't have a database with your documents. We don't know what files you process, how many pages they have, or what's inside them. This is not a policy we can change later — it is a technical reality of how the app is built.

What Data We Collect

How File Processing Works

When you open a PDF in PDF Tools Pro, here is what happens technically:

• Your browser reads the file from your local disk into memory (RAM)
• The file is passed to pdf-lib and/or PDF.js — JavaScript libraries running entirely in your browser tab
• All operations (merge, split, compress, rotate, convert) happen inside that browser tab
• The output file is written back to your local disk via a standard browser download
• When you close the tab or navigate away, the in-memory data is immediately freed by the browser

At no point does any file data leave your device. There is no network request containing your file content. You can verify this yourself by running the app with your network connection disabled — it will work identically.

Third-Party Libraries

PDF Tools Pro uses the following open-source libraries, loaded from public CDNs on first launch and then cached locally by the service worker for offline use:

• pdf-lib (MIT License) — PDF creation, editing, and manipulation
• PDF.js (Apache 2.0, Mozilla) — PDF rendering and page previews
• JSZip (MIT License) — Creating ZIP archives for batch exports
• Google Fonts — Typography (Syne, DM Mono, Instrument Sans)

These libraries are fetched from CDN servers on first use (standard browser cache headers apply). After the first load, the service worker serves them from local cache. None of these libraries receive your file data — they run as code inside your browser, not as external services.

Local Storage & Caching

PDF Tools Pro uses the browser's Cache API (via the service worker) to store the app shell and library files locally. This enables offline use after the first load. The following is stored in your browser's cache:

• The app HTML, CSS, and JavaScript
• The PDF processing library files (pdf-lib, PDF.js, JSZip)
• Font files

Your PDF files are never written to the browser cache or any persistent storage. They exist only in RAM while you're using them and are discarded when you're done.

You can clear this cached data at any time through your browser's settings (Settings → Privacy → Clear browsing data → Cached images and files).

Microsoft Store & Licensing

PDF Tools Pro is distributed through the Microsoft Store as a one-time purchase Progressive Web App. The purchase, licensing, and payment processing is handled entirely by Microsoft under their privacy policy and terms of service.

We receive no personally identifiable information from Microsoft as part of the license verification process. The Microsoft Store handles all billing, receipts, and refunds.

For questions about your purchase, refund requests, or billing issues, please contact Microsoft Store support directly.

Children's Privacy

Because PDF Tools Pro collects no personal data whatsoever, there are no specific age restrictions from a data privacy standpoint. The app does not knowingly collect information from anyone, including children under 13.

Changes to This Policy

If we ever change our privacy practices, we will update this policy and revise the "Last updated" date at the top of this page. Any meaningful change — especially one that involves newly collecting data — will be communicated prominently in the app itself before taking effect.

The commitment to never uploading your files is fundamental to the product and will not change. If we were ever unable to honor that commitment, we would disclose it clearly rather than quietly update a policy.