Censr - Hide secrets on your screen before they hit your stream

by
Censr is a Mac app that automatically blacks out API keys, passwords, and personal data on your screen — before they ever hit your livestream or screen-share. System-wide (terminal, editor, browser, native apps — not just a browser tab), 100% on-device (nothing uploaded), and it shows up as a virtual camera in OBS, Zoom, Meet & Discord. Follow to get notified at launch — the first 100 founding members get it for $19.

Add a comment

Replies

Best
Hey Product Hunt I'm Todd. I build apps live on Twitch — and for two years I streamed with a low-grade dread that one careless cat .env or a paste into the wrong window would flash an API key to everyone watching. Leaked keys are real money and real damage, and they're permanent the second they air. Every "blur my screen" tool I found was a browser extension — useless, because I don't leak secrets in a Chrome tab. I leak them in my terminal, my editor, a .env file, a DB GUI. So I built Censr. Censr watches your whole screen on-device (Apple's Vision engine — nothing is ever uploaded), detects API keys, tokens, passwords and PII the instant they appear, and seals them behind a black bar before the frame reaches your audience. It runs a tiny safety buffer so a freshly-typed key is caught before it airs, and there's a panic hotkey (⌘⇧B) to black everything out instantly. It shows up as a virtual camera, so it works in OBS, Zoom, Meet, Teams & Discord. The thing I'm most careful about: no detector is perfect, so Censr is built as defense in depth — buffer + panic key + an always-blur list — not a magic "100% safe" promise. Free 14-day trial, then a one-time price (first 100 founding members get it for $19). Mac-first; Windows is on the roadmap. I'd love your feedback — especially edge cases where it misses something. Ask me anything!

How does it handle dynamic content like password manager autofill that pops up mid-screen-share? Curious whether the detection keeps up with stuff that wasnt visible when you first set it up.

 Great question and it gets at the core design. Censr doesn't do a one-time "setup scan"; it reads your screen live, a few times a second, so it's always detecting what's on screen right now, not a snapshot from when you started.

So an autofill popup mid-stream is exactly the case it's built for the moment it appears, it's read on the next scan and covered. Two things keep that from being "a beat too late": on a sudden pop-up, the feed holds the last already-scanned frame and only advances once the new content is read + redacted (no uncovered flash), and the output runs on a ~1s delay buffer so detection applies before it reaches viewers.

Two honest notes: if the manager shows the password as dots there's nothing to leak; if it shows a real credential, that's what gets covered. And it's OCR-based: which is what lets it catch dynamic content so an exotic/unreadable format is the edge case, which is why a one-key panic blackout is always there.

The latest build specifically hardened this: better small-text detection for popups on a full display, and that "hold until scanned" logic for sudden reveals.