Privacy

Your files

Your PDF is processed in this browser tab and never uploaded. Files you open with any of the PDF tools on this site are read and processed by code running in your own browser. We do not receive them, so we cannot store them, inspect them, or hand them to a third party.

This includes filenames. A filename is user data and frequently a revealing piece of it, so it is treated the same way the contents are.

Passwords you type are used only inside this browser tab, by the worker that opens or protects the file. The page keeps a password in memory while it is needed: until the operation succeeds, you start over or choose another file, or you close the tab. Browsers decide when that memory is actually reused, so we do not claim it is wiped. Passwords are never written to storage and never uploaded.

Files that Merge and Split produce are new documents: Verso writes its own name as the producer, and Merge titles its result "Merged document". Titles, authors and dates from your source files are not carried over. Rotate, Protect and Unlock keep the document information your file already has, such as its title and author.

Cookies and tracking

This site sets no cookies. It runs no analytics scripts, no advertising scripts, no session replay, no fingerprinting and no third-party embeds. That is why you have not been shown a consent banner — there is nothing to consent to.

The site writes nothing to your browser's local storage. Its light or dark theme follows your device's setting; the page reads a saved theme value only if one is already there, and nothing on the site writes one.

The site does install a service worker, which keeps a copy of its own pages, scripts (including the code that processes PDFs), styles and icons in your browser's cache storage. That cache holds none of your files and none of your passwords, and clearing this site's data in your browser removes it.

What the server sees

The site is a set of static files delivered by a CDN. Requesting a web page necessarily reveals your IP address and browser user-agent string to whoever serves it, exactly as it does for every website — this is how the internet delivers a response to the right place, not a choice we made. Those requests are for the site's own pages, scripts, styles and icons. None of them carry your file.

Once the site is deployed, it is served by Cloudflare, which handles these requests for us as our hosting provider. We see traffic only as totals: the aggregate request statistics Cloudflare provides, such as the number of requests and the countries they come from, and the search statistics Google and Bing report for the site. There are no analytics scripts and no cookies.

Verifying this yourself

You do not have to take any of the above on trust, which is the entire point of building it this way. Open your browser's developer tools, select the network tab, and use any tool on this site. Watch what leaves. Every tool page also shows request-body observations for window fetch, XMLHttpRequest and sendBeacon calls made after observation starts. The counter distinguishes measured supplied bodies, multipart value lower bounds and unknown sizes. It counts attempts, including failed calls; it does not measure delivery or total network bytes. Other APIs, workers, service workers, URLs (including query strings), headers and earlier traffic are outside its scope. The step-by-step guide walks through the network-tab check.

The counter is one limited diagnostic. Checking whether a file leaves the device requires observing the full processing flow and its network activity, including workers and other browser APIs.

If this changes

There are currently no accounts and no paid plans. If those arrive, signing in and billing will require a server, and this page will be updated in the same release that ships them — describing what is collected, why, and for how long. What will not change is the boundary: account details may reach a server, file content never will.

Read why local processing for how that boundary is enforced in the architecture rather than in a policy.