Local image processing
Images you choose, drop, paste, or load as project samples are decoded and processed in your browser. Color sampling, preview generation, tolerance matching, connected-area calculations, and PNG export run on your device.
RemoveColor does not provide an image-upload endpoint. Your image pixels, file contents, selected color, Blob URLs, and generated PNG are not sent to RemoveColor servers.
Storage and file lifecycle
The editor does not store image content in Local Storage, IndexedDB, a database, or a cloud account. Temporary browser memory, Canvas surfaces, ImageBitmap objects, and object URLs exist only to support the active edit and download.
Replacing an image or closing the page releases those temporary resources. Downloads are saved by your browser to the location you choose; RemoveColor does not receive or retain the exported file.
Technical request data
Like any static website host, the hosting network may receive ordinary web request information needed to deliver HTML, CSS, JavaScript, and fonts. This can include an IP address, browser user agent, requested URL, timestamp, and security or cache information.
That delivery data is separate from your image. Image bytes are read by the browser editor and are not included in page requests, error messages, or structured metadata generated by the site.
Analytics and cookies
RemoveColor does not use advertising trackers or account cookies. A deployment may enable Plausible, a privacy-focused analytics service, by providing its site-specific script during the production build. When that setting is absent, no analytics script or product event is sent.
When enabled, analytics is limited to page views and a closed list of named product actions such as upload started, color selected, mode changed, and download succeeded. The event interface accepts no custom properties, so it does not send file names, image content, Blob URLs, pixel data, selected color values, dimensions, or image metadata. Like other web requests, the analytics provider may receive request data such as the page URL, IP address, and browser user agent needed to deliver and count the event.
Browser features and permissions
File selection, drag and drop, clipboard paste, Web Workers, Canvas, and the browser download system are used only when you invoke them. Clipboard image data is handled after a paste action; the site does not continuously read or monitor your clipboard.
External links and policy changes
Links to external services are governed by their own privacy practices. A revised date will appear above if the processing model, hosting setup, or data practices described here change.
For the operating rules that accompany the tool, read the Terms of Use.