◆ How it’s private

“Runs in your browser” is easy to say. Here’s how to check.

We know a privacy claim is worthless unless you can verify it. So verifying it is built into every page — and takes about ten seconds.

1 · There is no server to upload to

Every tool here is a static page plus JavaScript that runs on your device. When you drop in a file or paste text, the work happens in your browser’s memory. Nothing is sent anywhere because there is nowhere for it to be sent — there is no endpoint that accepts your files or your text.

One deliberate exception, and it is not a tool. The suggestion box sends the message you type to a database, because that is the entire point of a suggestion box. It is the only page here that uploads anything, it says so before you use it, and the uploads badge ticks from 0 to 1 when you press send — the badge doing its job, not a mistake.

2 · The badge in the corner is watching for you

The 0 uploads badge in the nav isn’t decoration. We wrapped this page’s own fetch and XMLHttpRequest so any request that would send your data off-device gets counted, live. Click it to see the readout. It says zero because it is zero.

3 · Don’t take our word for it — use dev tools

Open your browser’s developer tools (F12 or right-click → Inspect), go to the Network tab, clear it, then use the tool. You’ll see the page load its fonts and scripts once — and then nothing more when you process your file. No POST, no upload, no beacon.

4 · No cookies, no cross-site tracking, no fingerprinting

We set no cookies at all, and run no third-party ad networks, no session recording, and no fingerprinting. Preferences you re-enter often — your name, your team, your currency — are saved in localStorage, on your device only. That’s why a tool can “remember you” with no account: the memory never leaves your machine.

The one thing we do measure: an anonymous pageview count, so we know which tools people find useful. We use Cloudflare Web Analytics — cookieless, no personal data, no cross-site profile, and nothing about what you type or the files you open. It cannot see your inputs, and your files still never leave your device.

5 · The AI tools download a model — that is the trade

The background remover, transcription, OCR, face blur and the upscaler each fetch a model file the first time you use them, and some are large: 0.4MB to 42MB, plus a ~13MB runtime shared between them. Every size is stated on the tool before anything downloads, and you press a button to start it.

This is the opposite of the usual arrangement. Everywhere else the model sits on their server and your file travels to it. Here the model travels to you, once, and your file never moves. That is why these tools have no account, no per-image credit and no per-minute meter — there is no per-use cost to charge you for. The model files come from this domain, not a CDN, so no third party sees what you are using.

6 · Cloudflare sits in front of this site

Your request now reaches Cloudflare before it reaches our host. That means Cloudflare terminates the HTTPS connection and can see your IP address and which page you asked for — the same as for a very large share of the web. We did it because the model files are tens of megabytes, and caching them at the edge is what makes them free to serve.

What does not change: your files, your text and your audio are never part of a request, so none of it passes through. We set no cookies, and we keep no logs of our own tying you to anything.

If a tool must make a network call to do its job, it says so on the page, in plain language, before you use it — and none of those calls carry your data.
browse the tools → the manifesto