Privacy

Current as of July 3, 2026 — one policy for the detector and its three companions

Your camera and your photos

A camera pointed around your home is about as personal as data gets, so here is the architecture rather than a promise: every frame and every photo is read into a canvas element inside your browser's memory, sampled by JavaScript there, and released. This site is a folder of static files — there is no upload endpoint, no processing server, no place the pixels could go. Load the page, turn on airplane mode, and everything still works; that's the proof.

When the camera is actually on

Only between your tap on "Start the camera" and leaving the mode or the page — your browser shows its recording indicator the whole time, and stopping releases the hardware. We never see the feed; neither does anyone else.

What persists after you leave

The offline copy of the site's own files (a service-worker cache) and nothing else. Picked colors live in page memory and evaporate when the tab closes — export your palette if you want to keep it.

The single number we get

An anonymous count of page views. No cookies, no fingerprints, no session IDs — a tally mark, not a profile.

Who else is in the request log

Google Fonts serves the two typefaces (so Google sees a font request from your IP, the same as on millions of sites), and Cloudflare Pages serves the site itself with its normal infrastructure logs. Pixels never appear in either.

Anything unanswered

The contact page lists the inbox — privacy questions get answered first.