Privacy Policy
Your files never leave your device. This page explains exactly how.
The short version
- Your PDF files are processed entirely in your browser.
- We never upload your files, file names, metadata, or extracted text to any server.
- There is no database and no cloud storage.
- Analytics (if enabled) only receives coarse, non-sensitive event data.
How PDF processing works
When you select a PDF, IXPDF reads the file into your browser's memory and passes it to a Web Worker running on your own device. The PDF engine (currently pdf-lib) performs the operation locally and produces a result that is offered as a download.
At no point does the file content travel over the network. There is no upload API — the code path that would send your file to a server does not exist in IXPDF.
What we never collect
- The contents (bytes) of your PDF.
- Your file name.
- PDF metadata (author, title, creator, dates, etc.).
- Extracted text from your PDF.
- Passwords, tokens, or API keys you enter.
- The result of processing your PDF.
Analytics
IXPDF uses Google Analytics 4 to understand which tools are used and whether they succeed. The Measurement ID is provided via an environment variable; if it is empty, analytics is disabled entirely. We also respect the browser's Do Not Track setting.
Analytics events are limited to coarse, non-sensitive aggregates:
- The name of the tool you used (e.g.
compress-pdf). - The type of operation (e.g.
readMetadata). - Whether the operation succeeded or failed.
- A coarse duration bucket (e.g.
1-2s) — never the exact time. - A coarse file-size bucket (e.g.
1-5MiB) — never the exact size. - A stable error type code (e.g.
INVALID_PDF) — never the raw error message.
These events cannot be used to reconstruct your document or identify its contents.
No databases, no cloud storage
IXPDF is a static website. There is no server-side runtime, no database, and no cloud storage bucket. Nothing about your visit is stored on our infrastructure beyond the aggregate analytics events described above (processed by Google Analytics under their own terms).
Changes to this policy
If we ever change how data is handled, we will update this page so the text always matches the technical implementation. Because the privacy promise is enforced in code, any change that would break it would be rejected in review.