Your image never leaves your browser
Not deleted after an hour. Not encrypted in transit. Not stored securely. Never sent. This page explains why that is true by construction rather than by promise, and then gives you three ways to check it yourself. Two of them hold even if we are lying to you, which is the only kind of assurance worth having.
That is the whole claim, and it is worth being precise, because everyone in this category says something that sounds similar.
We are not saying your photo is deleted quickly. We are not saying it is encrypted while it travels. We are saying it never travels. It is read into memory inside your own browser tab, processed there, and gone when you close it. Nothing about it is ever transmitted to us, or to anyone else.
You should not believe that because we wrote it down. Nobody should take a privacy claim on faith, least of all one this absolute. So the rest of this page is about how you check it yourself, in about thirty seconds.
Verify it yourself
1. Watch your own Network tab
Your browser already keeps a complete record of everything a page sends and receives, and it will show you ours. This is the direct test.
- Open the background remover.
- Open your browser's developer tools. F12 on Windows and Linux, Cmd+Option+I on a Mac.
- Click the Network tab and leave it open.
- Drop in a photo and let it finish.
Read what happened. You will see downloads: the page, its stylesheet, its JavaScript, and one large file, which is the AI model. Every one is a GET, which means "send me this", not "here, take this".
What you will not find is a request carrying your image. Sort by size. Click through them. Look at the payloads. There is no POST anywhere on this site, because there is nothing to POST to.
2. Turn your wifi off
This is the one that settles it, and it takes ten seconds.
Use a tool once, so the model is loaded. Then disconnect from the internet completely, and use it again. It works.
There is no clever way for a tool to secretly send your photo to a server while your machine has no network connection. If it still works offline, the processing is happening on your device. That is not a claim we are making, it is something you can watch, and no amount of our JavaScript can fake it.
(Load the page before you disconnect. The model, once cached, stays cached.)
3. Read the code
Everything that runs is plain, unminified JavaScript. Open the Sources tab and read it. There is no fetch with your image in it, no FormData, no beacon, no analytics call. The only network requests in the whole codebase are the ones pulling code and models down.
A hostile reader needs exactly one counter-example to demolish us. If you find one, tell us and we will fix it that day.
Why it works this way
Every other tool in this category uploads your image to a server, runs a model on a GPU there, and sends the result back. That is not laziness. Until recently it was the only way it was possible.
We do it backwards. The model comes to you. Your browser loads it once, and from then on the work happens on your own processor. Your image has no reason to move, so it does not.
The part that matters is that this is not a policy we could quietly change. There is no upload endpoint on this website: no route that accepts an image, no image-processing library installed on the server, no storage attached to put one in. We could not receive your photo if we decided we wanted to. Changing that would mean rewriting the application and redeploying it, and you would see it in your Network tab the moment it happened.
What does cross the network
Being precise, since "nothing is uploaded" deserves specifics:
| What | Direction | When |
|---|---|---|
| The page, its CSS and its JavaScript | Down | On page load |
| The AI model | Down, from a public CDN | The first time you use a tool, then cached |
| Your image | Never. In any direction. | Never |
| Your result | Never. It is saved straight from your browser to your disk |
One honest note on that middle row. The model is hosted on a public CDN, so that CDN sees a request from your IP address for a file. That is the same exposure as loading a font or a JavaScript library from any CDN, and it reveals nothing about your photo, because your photo is not part of the request. If you would rather not have even that, use a tool once and then work offline: a cached model needs no network at all.
We also run no analytics. None. We genuinely do not know how many people use this site, which is inconvenient for us and is the honest consequence of the position. If that ever changes it will be page-level only, it could not touch your image even if it wanted to, and this page will say so before it ships.
What is stored on your device
The one real cost of this design is that the model has to be loaded once. Your browser keeps it afterwards, which is why the second visit is instant and why the tools work offline.
That is the only thing stored. No tracking cookies, no copies of your photos, no history of what you processed. Here is exactly what this site is holding right now, and a button to delete it:
Checking your browser's storage...
Deleting it costs you nothing except loading the model again next time. You can also clear site data for this domain in your browser settings, which does the same thing.
The part where this is a worse deal
An honest privacy page should include the costs, so here they are.
Running on your device means the first use of each tool loads a model, and on a slow connection that is a real wait. It means speed depends on your hardware rather than a data centre's, so a modern laptop with WebGPU is quick and an old phone is slow. It means very large images can exhaust a browser tab's memory, so we cap input sizes in a way a server-side tool does not have to. And it means we cannot offer you a batch API, because there is no server to run it on.
If those costs matter to you more than the privacy does, that is a completely reasonable conclusion, and our comparison pages say plainly where the paid tools are better. We would rather you picked the right tool than picked ours.
Frequently asked questions
Is it safe to upload photos to an online background remover?
That depends entirely on the tool, and it is worth asking rather than assuming. With a conventional one you are genuinely uploading your photo to a company's computer, and your protection is their privacy policy and their security practices. For a photo of a product on a table, who cares. For a photo of your child, your passport, a medical image, or an unreleased design, the calculus is different. With this site the question does not arise, because there is no upload.
Could you change this later and start uploading photos?
We could rewrite the site, in the same sense that any website could change tomorrow. What we cannot do is change it invisibly. The processing happens in JavaScript you can read, in a tab you can inspect, and any upload would appear in your Network tab the moment it started. A server-side tool can change its behaviour silently, because you can never see what it does with your image once it arrives. Here you can see everything, every time. That asymmetry is the whole point.
Do you use my photos to train your models?
No, and we could not if we wanted to. We did not train these models, we did not fine-tune them, and we never receive your images, so there is nothing to train on. Your photo has no path to us.
Do you have a cookie banner?
No, because we set no cookies and run no analytics or advertising trackers. There is nothing to consent to. If that changes, this page changes first.
Is this actually free, or am I the product?
It is actually free, and the reason is arithmetic rather than generosity. Tools that run the model on their own servers pay for a GPU by the second, so they must meter you with credits, watermarks or sign-up walls. Our cost per image is zero, because your device does the work. There is nothing to recover, so there is no need for your data to be the product. We plan to fund the site with ads placed below the results, which is a worse business than selling data and a much easier one to explain to you.