What we do not upload during a cutout
Easy Background Remover is designed so the image you open, its pixels, the generated cutout, and your recent editing history are not uploaded to our servers for background-removal inference. Decoding, mask generation, refinement, and export happen in the extension’s browser environment.
That precise statement matters more than an absolute “no network” slogan. The extension may download its on-device model on first use, receive updates, or use product-quality reporting in a build. The product website also has its own website analytics. Those network activities are not the same as sending your photo to a remote cutout API.
The source image stays in the browser workflow
When you drop, paste, or choose a supported file, the extension reads that image so it can display and process it. When you deliberately start from a page image, the extension attempts to load the image you selected.
In the intended cutout path, the source pixels are handled by the editor and its worker. They are not packaged as an inference request to an Easy Background Remover server. If a page blocks access to its image, the extension may fail to load it; saving the image and opening the local file is the practical fallback.
This distinction covers the image used for the job. It does not mean the file never existed elsewhere. A photo may already be in a cloud-synchronized folder, messaging app, website, or operating-system backup before you open it. Those services have their own data paths and policies.
The cutout result is not sent away for processing
The generated mask, transparent result, and brush refinements are produced in the browser. Download PNG writes the exported result through the browser’s download flow. Copy places a result on the clipboard after your action.
What happens after export depends on you and the destination. Pasting into an online document, attaching the PNG to email, or saving into a synchronized folder can upload the exported file to that separate service. Local cutout processing cannot control the next application you choose.
For a clean privacy boundary, save to a local folder first and decide where the file should go afterward.
Recent history is local data, not a remote project
The extension can retain a short history of recent originals and results in browser storage such as IndexedDB. This is why a recent job may still appear when you reopen the editor.
That history is not presented as a remote account or cloud project. It is local browser data tied to the browser profile. Clearing the extension’s data removes the cache like other local storage. Because browsers can reclaim storage and files can be cleared, history should never be treated as your only copy.
Local does not mean invisible to everyone. A person using the same unlocked browser profile may be able to see recent jobs. Clear the data after working with a private image on a shared device.
What can still use the network
Several ordinary events can create network traffic without carrying your image pixels to a cutout service:
First-run model download
The first launch may fetch the model needed for on-device processing. The browser caches that model for later sessions. A product or model update may trigger another download.
Extension updates
The browser checks for and installs extension updates through its distribution system. Those requests concern software delivery, not the contents of the photo you opened.
Website analytics
Pages on the product website load high-level Umami analytics. Website analytics can include the page visited, referrer, browser and device type, approximate country, and labeled page interactions. They do not receive extension image pixels, cutout results, or the local editing history described above.
Product-quality reporting
If analytics or crash reporting are enabled in a particular extension build, they support product quality. They are not the inference path for the cutout. Because builds can change, the current Privacy and local processing page is the controlling public explanation.
Claims we intentionally avoid
We do not describe the product as “never online,” because initial setup and updates can require a connection. We do not say that an image can never leave your device under any circumstances, because you can export it into another service, start from an image already hosted online, or use a device with separate synchronization software.
We also do not equate local processing with automatic secrecy. Device security, browser-profile access, clipboard history, downloaded files, backups, and the apps you use afterward remain part of your privacy boundary.
The useful promise is operational and testable: the normal Easy Background Remover cutout path does not need to upload your photo pixels to our servers for inference.
How to verify your own workflow
Use a low-risk test image first. Then follow the same route you expect to use later:
- Complete first-run model setup.
- Open the test image from a local folder.
- Process and refine it in the extension.
- Download the PNG to a local, non-synchronized folder.
- Check recent history and learn how to clear extension data.
- Decide separately whether the exported result should enter an online service.
Advanced users can inspect the browser’s extension details and developer tools, but a network log requires interpretation. Seeing a request does not by itself mean pixels were uploaded; identify the destination, timing, and payload rather than guessing from activity alone.
A useful boundary for sensitive images
For confidential, regulated, or high-impact material, follow the rules of the organization that owns the data. A local-processing design may reduce exposure, but it does not replace consent, device policy, access controls, retention rules, or a formal security review.
Do not use someone else’s private image merely because a tool runs locally. Obtain permission, crop unnecessary details before editing, and delete local working copies when the task is complete.
Short answer
During the intended cutout workflow, we do not upload your selected source pixels, generated mask, transparent result, or local recent-job history to our servers to perform background removal. The browser can still connect for model delivery, software updates, website analytics, or build-dependent product-quality reporting.
That is the same scoped claim used across the privacy and product documentation: local image processing, with honest limits around setup, storage, and the rest of your device workflow.