What data does ToPDF collect? (Short answer: your documents, never)

Privacy pages usually take 3,000 words to avoid saying things. Here's the whole inventory in plain language — short, because the honest list is short.

Your documents and scans

Never collected. Photos are processed inside your browser; PDFs are assembled inside your browser; both exist only on your device and wherever you personally save or share them. There is no upload endpoint, no scan history, no cloud library. Airplane-mode scanning works — that's the proof.

Analytics and tracking

None. No analytics scripts, no advertising pixels, no fingerprinting, no cookies used for tracking. The only thing the site stores in your browser is your theme choice (light/dark) and the cached engine files that make offline work.

What serving a website inevitably involves

Like every site on the internet, the files are delivered by a hosting/CDN provider, which processes basic technical request data (IP, user agent) to serve and protect the site — standard web plumbing governed by the host's policies. That's the complete list; the privacy policy says the same with the formal wording.

Frequently asked questions

Do you know how many documents I’ve scanned?

No. Scans produce no telemetry — we genuinely cannot count your scans, see your file names, or know a scan happened.

Will this change with new features?

The on-device architecture is the product. Features are built to run locally; anything that ever required different handling would be explicit and opt-in, not slipped into a policy update.

How is this free without data monetisation?

Static hosting with on-device compute is extremely cheap to operate — there’s no per-scan server bill to recoup. See the funding-models guide for the industry context.