It depends on where the photo goes. An upload-based remover processes your photo on its servers and keeps it for as long as its policy says. An in-browser remover never receives it. For a product shot, either is usually fine. For portraits, children, signatures, or client work, choose one that does not upload, and check that claim yourself.
The question that matters: does the photo leave your device?
Background removers work in one of two ways. Some send your photo to a server, run the AI model there, and send the cutout back. Others send the model to your browser and run it on your own computer, so the photo never travels.
That split decides most of the risk. Retention periods and deletion promises only matter once a copy of your photo sits on someone else’s machine. If the photo never leaves your device, there is nothing for a service to keep, log, or lose.
What happens to a photo on an upload-based service
When you drop a photo into an upload-based remover, it goes through these steps:
- The file travels over the network to the operator’s servers, usually encrypted with HTTPS.
- A server decodes the image and runs the model on it.
- The result is kept at least long enough for you to download it.
- After that, the files are deleted on the schedule the policy states. Copies can also exist in logs and backups, which may follow their own schedules.
- While any copy exists, it can be reached by the operator’s staff and contractors as the policy allows, and by an attacker if the service is breached.
Some services publish their retention times. remove.bg’s security page, updated August 28, 2025, says: “Your uploaded images are deleted typically within 60 minutes, guaranteeing no retrieval of any past data after 90 days.” Photoroom’s data security page (checked September 23, 2026) lists separate periods for logs: “Operational logs are deleted after 15 days. API access logs are retained for one year, available to support security investigations and audit requests.”
Statements like these are what you want to find: a stated time, and a note on logs. Keep in mind that you cannot check them from your side of the connection. You are trusting the operator to do what the page says.
Do background removers train on your photos?
Policies differ, and the wording matters more than the headline. Photoroom’s privacy policy, updated March 2026, says: “By using Photoroom, you acknowledge that Photoroom processes and uses the images you upload to improve, train and develop Photoroom’s products, services and models. You can opt-out of this at any time by changing the settings on your account.” The next sentence adds: “This opt out shall not have retroactive effect on processing activities already carried out.”
Terms can also change with the plan, and sometimes a service’s own pages disagree. Photoroom’s security page says: “Enterprise contracts don’t train by default; self-serve API plans do, with opt-out in settings.” Its privacy policy, on the other hand, says: “For clarity, our model improvement does not apply to the images processed through our Application Programming Interface (API).” If you use the API, ask which of the two applies to your contract.
When you read any service’s policy, look for these phrases and questions:
- “Improve our services”, “develop our models”, “machine learning”. These are the usual places a training clause sits.
- Opt-in or opt-out. Opt-in means nothing is used unless you agree. Opt-out means it is used until you find the setting.
- Whether an opt-out reaches back. If it only covers future uploads, turn it off before your first photo, not after.
- Feedback buttons. Some tools ask you to rate a result or contribute an image. Read what a click on that button allows.
- Different terms per plan. Free, paid, app, and API customers can be covered by different rules.
Is HTTPS enough?
No. HTTPS encrypts the connection between your browser and the server, as MDN’s overview of Transport Layer Security explains, so nobody on the network in between can read your photo on its way. It says nothing about what happens once the photo arrives: the server decrypts it to process it. The padlock in the address bar means the connection is private, not that the service is.
How an in-browser remover differs
An in-browser remover turns the transfer around: the model comes to your device instead of your photo going to a server. The browser downloads the AI model and an engine, then runs them in your tab with WebAssembly (a fast, sandboxed format for compiled code), using your graphics card through WebGPU (the browser’s interface to it) when the browser makes one available. This is how on-device background removal works on this site.
The trade is real. The first image waits for the model to download (about 176 MB on Backgrounds Remover, which your browser then keeps in its cache while it can), and your own device does the work, so it needs time and enough free memory: in our measurement in desktop Chromium on a computer with 4 virtual CPUs, the browser tab used about 1.2 GB of memory for a typical photo and up to about 1.6 GB for a 16-megapixel photo. In return, no copy of your photo exists anywhere but your own device.
Backgrounds Remover works this way. The site has no endpoint that accepts an image, its security headers only let the page connect back to its own address, and an automated test checks that no request carries a file. Our privacy and security page lists what stays on your device, what your browser keeps, and how to check it yourself, and the privacy policy states what the site receives. For the steps, see how to remove a background without uploading the photo.
A checklist to vet any background remover
You do not have to take any site’s word for it, including ours. Before you give a tool a photo that matters, run through these checks:
- Does it say where processing happens? Look for a plain statement such as “in your browser” or “on our servers”. If the site does not say, assume the photo is uploaded until you have checked.
- Watch the Network tab. Open your browser’s developer tools (F12, or Cmd+Option+I on a Mac), choose Network, then add a photo. An upload is a POST or PUT request about the size of your photo. A tool that works locally only fetches files, with GET or HEAD requests (this site can also send a small error report when something fails, described on the page linked next). Our step-by-step Network tab check shows what to expect on this site.
- Is a retention period stated? A stated time, including one for logs, is easier to hold a company to than a general promise to respect your privacy.
- Is training use stated? Check whether it is opt-in or opt-out, and whether an opt-out covers photos you already uploaded.
- Does it need an account just to download? An account usually ties your uploads to your name or email address.
- Does it want you to install something? A browser extension or a desktop program can reach far more than one photo. A simple cutout should not need either.
- Is the privacy policy specific and readable? It should name what is collected, how long it is kept, and how to ask for deletion.
- Are you on the real site? Lookalike sites exist. remove.bg’s help center (checked September 23, 2026) warns of “unauthorized websites impersonating remove.bg and misleading customers with fraudulent charges and subscriptions”. Type the address yourself or use a bookmark instead of clicking an ad.
Upload-based and in-browser, side by side
| Upload-based service | In-browser tool | |
|---|---|---|
| Where the photo goes | To the operator’s servers | Stays on your device |
| Who can access it | The operator, whoever its policy allows, and anyone who breaches it | You, and any browser extension you allowed to read pages |
| After processing | Kept as long as the policy says, possibly in logs and backups | Nothing to keep, because it was never sent |
| What you must trust | The operator’s policy and security | The page’s code, whose requests you can watch in the Network tab |
| Speed and device | Runs on the operator’s hardware, so an older device is no obstacle; services may also offer large batches, photo backgrounds, and brushes | Runs on your processor or graphics card, after the model download, and needs enough free memory |
| Connection | Needed for every image | Needed to open the page, and to download the model the first time or after the browser has cleared it |
When an upload service is a reasonable choice
Uploading can be the sensible choice when:
- The photo is not sensitive, such as a product on a plain table that will be public on a listing anyway.
- You have hundreds of images to process in one run (Backgrounds Remover takes up to 20 at a time).
- You want a photo as the new background, not a plain color.
- You need manual brushes to paint back a strand of hair or erase a stray shadow.
- Your device is short on memory, for example a phone without enough free memory for a large model.
Backgrounds Remover does not cover the last four cases. For those jobs, pick a service, read its policy first, and keep sensitive photos out of it.
Photos that deserve extra care
Some pictures carry more than their subject. Think twice before uploading:
- Portraits, especially of people who did not agree to have their photo processed by a third party.
- Children, who cannot weigh in on where their pictures end up.
- Home interiors, which can show your layout, your belongings, and clues to where you live.
- Signatures, which someone else could reuse.
- Unreleased products and designs, which may be under a confidentiality agreement.
- Client material, since a contract or company policy may forbid sending it to third-party services.
Photos can also carry hidden metadata, such as the place where they were taken. An upload usually sends the whole file, metadata included.
Questions
Is a free background remover less safe than a paid one?
Not by itself. Price does not tell you where the photo goes; the policy and the Network tab do. A paid plan can come with different terms, as Photoroom’s pages on training for Enterprise contracts and for the API show, so read the terms for the plan you actually use.
Can an in-browser tool still see my photo?
Yes. Its code runs in your tab and has to read the image to process it. What matters is whether anything sends the photo out, and the Network tab shows that. A careful tool also limits itself: this site’s headers only allow the page to connect back to its own address.
If the photo is one you would rather keep to yourself, remove the background in your browser and download the result. The photo is never uploaded.