A Background Remover That Never Uploads Your Photos

How cloud background removers actually work

The standard pipeline: you select a photo → it's uploaded to the service's servers → a GPU runs the segmentation model → the result is sent back. Your image, at full resolution, transits and at least temporarily resides on infrastructure you don't control. Most reputable services delete uploads after some window and say so in their privacy policy — but “trust our retention policy” is still the security model, and policies allow more than people assume (quality review, abuse detection, sometimes model improvement).

For a beach photo, that trade is usually fine. It's a different calculation for:

• Unreleased products under NDA — leaking via a third-party tool is still a breach;
• IDs, passports, and documents — the photos most often edited and most dangerous to scatter;
• Photos of your kids — many parents simply prefer these never to touch a server;
• Legal, medical, and HR material — where confidentiality is an obligation, not a preference.

How on-device removal works instead

Modern browsers can run real neural networks via WebAssembly and WebGPU. Cutaway downloads the segmentation model itself (~40 MB, one time, cached by your browser) and then runs inference inside your browser tab, on your hardware. The pipeline has no upload step — not encrypted upload, not anonymized upload, no upload. After the engine is cached, the tool works with your network cable unplugged.

The same architecture explains why it can be free and unlimited: there's no server GPU bill scaling with every image, which is the cost cloud services meter you for.

Don't trust the claim — test it

“Your photos never leave your device” is exactly the kind of claim anyone can type. Three ways to check it on Cutaway, hardest evidence first:

• Airplane-mode test. Load the page once, process one image so the engine caches, then disconnect from the internet entirely. Process another photo. It works — which is only possible if the computation is local.
• Your browser's network tab. Open DevTools → Network, then process a photo. You'll see the one-time engine download and nothing outbound carrying your image.
• The built-in privacy monitor. Cutaway ships a live panel that hooks every network API on the page and counts outgoing bytes. It reads zero — and it's wired to turn red, publicly, if any script on the page ever uploads anything.

The honest trade-offs

On-device isn't magic. The first visit downloads ~40 MB; older phones process more slowly than a datacenter GPU; and on the hardest edge cases — flyaway hair against busy backgrounds — the big commercial models still hold an edge. For clear subjects, products, and people, current open models are effectively at parity. You're trading a few seconds of patience for a structural guarantee no cloud service can offer: your photo physically cannot leak from a server it never reached.