DEV Community

Cover image for The 5-Minute Demo Privacy Routine I Wish I Used Earlier
gong junhao
gong junhao

Posted on

The 5-Minute Demo Privacy Routine I Wish I Used Earlier

I used to think privacy leaks in screen recordings were rare edge cases.

They are not.
Most of the leaks happen in ordinary moments:

  • autofill dropdowns
  • internal tab names
  • random notifications
  • customer identifiers in widgets

So I moved to a simple workflow before every recording:

  1. Open a dedicated browser profile for demos.
  2. Turn on Do Not Disturb.
  3. Close chat/email/password-manager overlays.
  4. Run a 30-second dry walkthrough.
  5. Blur sensitive zones before recording.
  6. Rewatch the first 10-15 seconds before sharing.

This process is short enough to use every time, and it cuts accidental exposure risk significantly.

For the blur step, I use BlurMate, a lightweight Chrome extension that lets me place movable blur overlays quickly.

Website: https://blurmate.devstorex.top

If you record tutorials or client demos, what step in your process catches the most hidden leaks?

Top comments (0)