Privacy scene guard

Render-time redaction masks secret-shaped strings, but some screens exist specifically to show secrets — pasting an API key into Settings, for example. For those, masking isn’t enough; the audience shouldn’t see the screen at all.

What the guard does

1. You designate a privacy scene in OBS (a “be right back” card, a logo, anything).
2. While Streaming Mode is on and OBS is connected, opening a sensitive surface — the API-keys tab, the license tab, the setup wizard — switches the OBS program scene to that privacy scene automatically.
3. Close the sensitive screen and the previous scene comes right back.

Why both layers exist

Redaction protects against secrets that appear in ordinary content (a terminal cat .env, an agent echoing a token). The scene guard protects against screens designed to show secrets, where masking would defeat the purpose of the screen. Together they make “I opened settings live on stream” a non-event.

Good to know

• The guard requires the OBS connection; without OBS it can’t switch scenes (redaction still protects the window itself).
• Scene changes land in the Audit Log, so you can confirm after the stream that the guard fired.