What we don't do

No uploads. Your PDF and the converted output are never sent to a server. There is no server — the app is static files, and all conversion happens on your device.

No accounts. There's no sign-up, login, or user database. We have no way to link anything you convert to an identity, because we never collect one.

No cookies or storage. The app doesn't set cookies or use localStorage. Nothing about your visit persists after you close the tab.

No analytics or tracking. No Google Analytics, no ad pixels, no fingerprinting. Nothing watches how you use the app.

No outbound requests. The Content-Security-Policy sets connect-src 'none', which makes it impossible for the page to make any network request. This is enforced by your browser, not just promised.

How your file is handled

When you pick a PDF, your browser hands the page a reference to the file in memory. The app reads it, extracts text and structure using a bundled copy of the PDF.js library, builds the output, and hands it to your browser's save mechanism. At no point does the file, or anything derived from it, leave the tab.

Changes to this policy

If how the app handles data ever changes, this page will be updated. Since there's no account system, we can't notify users individually — check back here to confirm current behavior. If an ad network is ever added, it may set its own cookies and make its own requests, and this policy would be updated to say so.

This is a plain-language description of how the app is built, not formal legal advice. If you deploy this publicly and need a legally reviewed policy for your jurisdiction, have it reviewed by counsel.
Back to converting