Prove it's private

Try the live privacy demo

This demo merges two synthetic PDF pages using the real browser processor. It never asks for your documents.

Ready to merge two synthetic pages on this device.

The upload counter counts HTTP requests whose method is not GET or HEAD. It counts methods without recording request bodies, headers, addresses or document contents. A request is a warning to investigate, not proof that a file was sent.

Observation covers this page and the demo worker while active. Asset downloads can increase the request count. Browser extensions, other tabs, earlier requests and service worker traffic are outside its scope. Use the browser Network panel for an independent check.

Check it independently

1. Open your browser developer tools and select Network. Clear the list, then run the demo. Inspect any POST, PUT or other write request.
2. Open Merge PDF once while online so its code is cached. Keep synthetic files on your device and finish a merge.
3. Install the app or visit Offline settings and save that tool for offline use. Switch the browser to offline, reload the saved tool, then merge the same files and download the result.
4. Some tools need a first download of language data or a model. Cache that resource first. Camera access also needs HTTPS and your permission.

What stays on this device

Browser tool files and passwords stay in memory during processing. Downloads are saved where you choose. Recent files are off by default; if you opt in, bounded output copies remain in this browser until cleared or removed on a later visit after expiry.

Server conversions and optional AI paths are different: their upload and consent screens explain where data goes before you continue. The browser demo does not certify those paths or your browser extensions.