Last updated: this page reflects the codebase as of the most recent deploy. If you're reading this from a source checkout, you can verify every claim below yourself — none of it depends on trusting us.
Your images never leave your device
Every tool on this site — Encode, Inspect, Preview, Convert, Optimize, Batch — reads the file you choose using the browser's local File API and processes it with Canvas, Web Workers, and WebAssembly, entirely inside your browser. There is no upload step. No image, or any byte of an image, is ever sent to a server, because this app doesn't have one to send it to — it's a static site with no image-processing backend at all.
No accounts, no sign-in
There's nothing to create an account for. Nothing you do here is tied to an identity, a session, or a login of any kind.
What we store on your device
Nothing, currently. As of this deploy, the app does not use localStorage, sessionStorage, indexedDB, or cookies for anything — no saved preferences, no history, no tracking identifiers. Every tool starts fresh on reload.
Fonts
Typefaces (Fraunces, Hanken Grotesk, IBM Plex Mono) are self-hosted at build time via next/font, not loaded from Google Fonts' servers at runtime. Visiting this site doesn't make your browser talk to Google for fonts.
Advertising
Some pages reserve visual space for ads, clearly marked as placeholders in the source. As of this deploy, no ad network script is loaded and no ad is actually served anywhere on the site — the slots render nothing.
Server logs
Like any web server, whatever infrastructure hosts this site may log standard technical request data (IP address, requested path, user agent, timestamp) for operational purposes — this is true of essentially any website and isn't specific to anything Headroom does. This page doesn't claim otherwise, but also can't make promises on behalf of hosting infrastructure it doesn't control.
Questions
There isn't a contact channel set up for this project yet — see the note on the Contact page. If you found this project through a specific deployment, check there for how to reach the people running it.