SafeShot

Every "hide the sensitive stuff" tool works the same way: it tries to detect secrets, covers what it found, and hands you the image. That design has one bad failure mode — a miss ships. You glance at a clean-looking screenshot, trust that the tool caught everything, and paste an account number into a public channel. By default the entire page is covered, and you reveal only what you actually meant to show. Detection still runs as the fast path, but the guarantee doesn't depend on it: - If the detector misses something → nothing happens. It was already covered. - If the detector over-covers → mild annoyance, one click to reveal. The dangerous case simply can't occur. Honest about its blind spots. Cross-origin iframes and <canvas> can't be read by any extension. SafeShot counts them, covers them by default, and tells you — in the toolbar and again on the review screen. "I looked and found nothing" and "I couldn't look" are never shown as the same result. Two buttons that never change. Left click reveals. Right click covers. Switching mode only decides the starting state; everything hidden, or just the auto-detected regions, so a click always does the same thing and you never have to remember which mode you're in. Blue means reveal, amber means cover; the cursor tells you what will happen before you commit. Review before you paste. Every capture opens in a review tab so you look before you use it — that step is the point. It copies itself to your clipboard and offers a PNG download. Private by construction. No host permissions, no standing access to any site. Access is granted by your keystroke or click, for one tab, and expires. No servers, no analytics, no network requests. Nothing is ever sent anywhere. Captures are held in memory only (never written to disk) and deleted the moment the review tab reads them. Shortcuts - ⌘⇧Y / Ctrl+Shift+Y — start with everything covered • - ⌘⇧U / Ctrl+Shift+U — start in auto-detect mode - Space switch mode - R rescan - Z undo - A clear - Enter capture - Esc cancel Detectors are deliberately conservative: vendor-prefixed API keys (sk-ant-, ghp_, AKIA…), Luhn-checked card numbers, structurally valid IBAN / SSN / JWT — patterns that won't fire on every order number and train you to ignore them. Requires Chrome 116+. Captures the visible viewport.