← Back to NilPDF NilPDF

Privacy Policy

Effective date: July 27, 2026

The short version

How PDF processing works

Every NilPDF tool runs entirely inside your browser using Python compiled to WebAssembly (via Pyodide). When you select a file:

1. Your browser reads the file directly from your device's storage into memory.
2. The PDF library (running as WebAssembly inside a Web Worker in your browser) processes it.
3. The result is written back to a file and offered to you as a download, generated by your own browser.

At no point in this process does the file, its filename, its contents, or any data extracted from it travel over the network to NilPDF or to any third party. This is verifiable — see the Security page for instructions on confirming this yourself using your browser's developer tools.

What NilPDF does not do

• NilPDF does not upload your PDF files, images, or any file you select in a tool.
• NilPDF does not intentionally transmit filenames.
• NilPDF does not intentionally transmit extracted text, metadata, or any content read from your files.
• NilPDF does not transmit passwords you enter to unlock encrypted PDFs — they are used only locally, in your browser's memory, to decrypt the file for local processing.
• Generated output files (merged PDFs, extracted images, compressed files, etc.) are created and stay on your device; they are not uploaded anywhere.

Ordinary website traffic

Visiting nilpdf.com itself works like visiting any website: your browser requests the page files (HTML, CSS, JavaScript, the WebAssembly runtime) from NilPDF's hosting provider and any third-party CDNs used to serve libraries. This is separate from PDF processing.

The hosting provider (GitHub Pages) and any content delivery networks used to serve fonts or libraries may process ordinary web request information — such as your IP address, browser type, and the page requested — as part of normal web infrastructure operation. This does not include the contents of any PDF you process, since PDF processing never leaves your browser.

This site uses standard web analytics tools to understand aggregate site traffic (for example, how many people visit a page). These tools operate on ordinary page-visit information and do not have access to file contents, filenames, passwords, or any data from documents you process — that data never leaves your browser in the first place, so there is nothing for an analytics tool to capture.

Cookies and local storage

NilPDF's own application code uses your browser's local storage only to remember a local, on-device counter of how many files you've processed and your light/dark theme preference — this data never leaves your device. Third-party scripts loaded by the page (such as web analytics) may set their own cookies according to their own policies; NilPDF does not control or read those cookies.

Third-party services

NilPDF's static site and libraries (pdf.js, Pyodide, and supporting JavaScript) are served from public CDNs (cdnjs, jsDelivr). Loading these files involves a standard request to those CDNs, the same as loading any web page's assets — it does not include your document data. The optional feedback form (if you choose to submit one) sends only the text you type to a small backend that files a GitHub issue; it is never triggered automatically and never includes file contents.

Data retention

Because your files are never transmitted to NilPDF, there is nothing for NilPDF to retain, store, or delete on your behalf. Your files exist only on your device, for as long as you keep them there.

Changes to this policy

If this policy changes, the effective date at the top of this page will be updated. Material changes will be reflected in the site's version history on request.

Contact

Questions about this policy can be sent through the feedback form available on every page of the site, or via the contact details on the About page.