A browser demo runbook should include privacy checks as executable steps, not a reminder to “look for secrets.”
Before the run
Use a staging account with invented data. Close unrelated tabs, pause notifications and inspect URLs, recent-item menus, autofill suggestions and developer tools.
During the run
Exercise the surfaces that commonly evade a simple page-load check:
- content inserted after load;
- route changes in a single-page application;
- focused and prefilled inputs;
- charts, maps and canvases;
- manual blur regions after zoom or resize;
- the full-page panic shortcut.
Auto Blur detects several common sensitive patterns in Chromium pages and supports input scanning, custom regex rules, manual blur regions, per-site controls and a panic shortcut. Page detection runs locally.
After export
Scrub through page transitions and menu openings. Check browser chrome and system notifications because page-level redaction does not cover every visible surface. Review audio for spoken private details.
Treat the final video as a release artifact: a second person should inspect it before public distribution. Privacy tooling reduces repeated work; the runbook closes the gaps around it.
Top comments (0)