Privacy

Your PDF is never uploaded. Every tool on this site reads and writes the file inside the browser tab you have open, so the document itself never reaches a server we run. The site does collect anonymous product analytics, and this page lists exactly what those events carry and what they can never carry.

The whole boundary, on one line each
What Leaves your browser?
The PDF you choose Leaves your browser?Never
Its file name Leaves your browser?Never
The text inside it Leaves your browser?Never
Its metadata Leaves your browser?Never
Thumbnails and previews Leaves your browser?Never
The file the tool produces Leaves your browser?Never
Which tool you opened, and whether the run finished Leaves your browser?Yes, as an anonymous event
How long the run took, how many files, their total size, the page count Leaves your browser?Yes, as numbers with no file attached
A coarse browser, platform and country Leaves your browser?Yes

Your files

Every tool runs in your browser. The file you choose is read by code on this page and never sent anywhere. It is not written to disk by us, not stored in your browser, and not kept after you close the tab. You can check this: open your browser's network panel, run a tool, and look at what leaves. You will see requests for this site's code and anonymous analytics, but not a request containing your document.

What we measure

We use PostHog to measure page visits, navigation, tool choices, input file count and total size, page count, settings, editor actions, progress, run time, verified outcome, errors, retries and downloads. It also measures browser and device details, referrer, page performance, scroll depth, dead clicks and session activity. These records tell us which tools are useful, where people stop and how long real work takes.

Analytics never receives PDF bytes, file names, document text, metadata, thumbnails, previews or output contents. The whole tool workspace is excluded from automatic event and session capture. Text and inputs elsewhere are masked before a session recording leaves the browser. Console logs are not recorded, and URLs are sent without their query string.

Our own usage counter

This site also keeps its own count of tool runs, in a Cloudflare database on this domain, so we can publish usage numbers without going through a third party. One run writes one row: which tool, its page, whether the run finished, failed or was left open, how long it took, how many files went in, their total size in bytes, the page count, the size of the result, and a coarse browser and platform name. The row also records the country, region, continent, Cloudflare location and time zone the request arrived from.

The counter stores no IP address, no file name, no document data and no identifier, so nothing links two rows to the same person or the same visit. It reads the same events described above and can never carry more than they do. A browser that sends Do Not Track is not counted, and turning analytics off with the button below turns the counter off too.

Anonymous browser ID

PostHog stores an anonymous identifier in browser storage and a cookie so separate visits from the same browser can be counted together. No account is needed to use the tools, so the identifier is not attached to one. We do not ask for a name or email address and do not call PostHog's identify function.

Analytics are on in this browser.

What the servers see

Serving a web page means your browser asks Cloudflare for files. The analytics requests go to this domain as well, and this site forwards them to PostHog with your IP address attached, so the country on the visit stays right. Those requests carry an IP address and browser user agent, as web requests do. Cloudflare and PostHog keep data under their own retention and security terms.

No account needed, no email

No tool on the site needs an account. We do not ask for your name or your email address, and nothing we store identifies you.

Third parties

The tool code, fonts and images come from this domain, and so does the analytics script. This site fetches that script from PostHog and forwards your events to PostHog, which receives the data described above. Nothing on the page loads from another company's server. There are no ad networks or third-party widgets.

How to check this yourself

You do not have to take any of this on trust. Open the developer tools in your browser, switch to the network panel, and clear it. Then choose a file and run a tool. Every request that leaves is listed there with its size and its destination. You will see this site's code and the analytics requests described above, and no request carrying your document.

A shorter version of the same test: load a tool page, then disconnect from the network before you choose a file. The tool still runs and still produces a download, because everything it needs is already in the tab. A tool that uploaded your file could not do that. Nothing here asks you to believe a policy statement. The test is written out because a claim you can run yourself is worth more than one you cannot.

Metadata inside your PDF

A PDF can carry your name, your software, your file path and the date you made it, whether or not you meant it to. That data stays inside the file, which stays with you. A tool that finds and strips it runs in this tab as the Privacy scan tool.

Where to go next