bg0.dev
482

Privacy

Last updated September 29, 2026

BG0 removes image backgrounds on your own device. This page explains exactly what leaves your browser when you use bg0.dev, which is very little.

Your images

Images you drop, paste, or open are read into your browser's memory, processed by a model running on your device, and turned into a PNG in the same place. Image bytes are never uploaded to us or to anyone else. We do not receive pixels, thumbnails, masks, file names, file sizes, or image URLs. Close the tab and the image is gone.

What the site loads

Cookies and tracking

bg0.dev uses PostHog for anonymous, first-party product and web analytics. We record page routes and a small set of actions: choosing an image, whether local removal succeeded, the browser engine used, roughly how long removal took (such as "5-15s"), downloading or copying a result, and using result views. If the page reloads during a removal, usually because the browser ran out of memory, the next visit reports only the step it reached and the browser engine. We never send image contents or image metadata to PostHog. Session recording, advertising, fingerprinting, and automatic click capture are disabled.

We also use PostHog to collect survey answers you choose to submit and to report app errors. Surveys are multiple choice, plus one optional short text answer that only appears after you rate a result poorly. Before that text is sent, your browser shortens it to 500 characters and replaces email addresses, links, image filenames and sizes, and long numbers such as phone numbers. Please don't include personal details. One question asks what kind of image you used, such as a product or a pet. That is the category you pick; we never work it out from the image. Error reports include a controlled error category and safe application code locations, without the original error text, image URLs, image contents, or image metadata. Survey responses and error reports use the same anonymous identifier as the analytics above.

PostHog stores a random anonymous identifier in local storage so visits can be counted without an account. The model cache also uses browser storage and only holds model files. While a removal runs, the tab keeps a small note in session storage with the step, the browser engine, the start time, and a random ID, so it can explain a reload. It is deleted when the removal ends or you leave the page.

Changes

If this policy changes, the date at the top of this page changes with it. The full history is in the public repository on GitHub.