Screenshot & Log Redactor

Catch and mask sensitive details locally before you share a screenshot or debug log

Problem

When developers file issues, post feature demos, or share screenshots from AI coding assistants, internal project names, emails and internal domains leak into the frame; debug logs often carry auth fields and cookies. Manual checking is slow and error-prone, and uploading screenshots to an online tool is itself a leak.

Solution

A local-only tool: drop in PNG/JPEG screenshots or .log/.txt files, and it flags hits using custom sensitive terms (project names, domains, emails) plus built-in rules for emails, tokens and cookie fields. On images you draw masks visually and save a copy without touching the original; logs show offending lines so you can export a clean version.

Users

Developers who share screenshots and file issues publicly; engineers using AI coding assistants who need to share outputs; open-source maintainers.

MVP

Import images and text files; custom terms plus built-in email/token/cookie rules; highlighted hits and a list view; visual masking with save-as-copy; fully local, no uploads.

Revenue

Open-source core, Pro one-time license (~$19-29) for batch folder scans, shared team term lists and CI CLI checks; enterprise rule packs.

Why now

AI assistants have multiplied screenshot and log output, and sharing has grown with it, while platform-side review tools don't cover personal leakage; a local-only utility is a two-to-three-week solo build with no data or compliance burden.