Stop leaking customer data in demo videos: a 3-step pre-flight checklist

2026-04-22 · 6 minute read · Workflow

If you record demo videos for customers — Loom walkthroughs, sales calls, support replies — there's a roughly 60% chance you've leaked another customer's data on at least one video this year. Most of the time you don't notice. Sometimes the customer notices, and then it's an awkward email.

This is the checklist sales engineers, customer success managers, and content creators use to avoid the problem. It takes five minutes to run and saves the once-a-quarter "oh no" of an embarrassing leak.

Why it happens

Customer data leaks in demos happen for three reasons, in roughly this order:

1. Tabs you forgot were open. You're showing the dashboard for Customer A; tab #4 has Customer B's account.
2. Sidebars and recent-items menus. "Recently viewed" sidebars in CRM tools default to showing the last 10 customers. If you fly past them in a recording, they're recoverable from a paused frame.
3. Notifications. A Slack message about Customer C pops up while you're showing Customer A.

None of these are technology problems. They're attention problems. The fix is a checklist that takes the attention out of it.

The 3-step pre-flight

Step 1 · One minute · Close everything you don't need

This is the cheapest, biggest-impact step. Before you hit record:

• Close every Chrome tab except the ones for this demo
• Close Slack, Discord, email, calendar — anything that pops a notification
• Close VPN, password manager, and any other widgets in your menu bar
• Quit any editor / terminal that has unrelated context visible
• Switch your browser to Guest mode or a separate "demo" Chrome profile (no extensions, clean history, clean autocomplete)

If you do nothing else, do this step. It catches 80% of leaks.

Step 2 · Two minutes · Replace real data with demo data, or hide it

You have two paths here, depending on the tool:

If the SaaS has a "demo mode": use it. Stripe, HubSpot, Salesforce, and most modern B2B tools have a sandbox or demo workspace. Switch to it before you start recording.

If it doesn't: you have to hide real data on your real account. Three options, ranked by speed:

• Edit each value manually — slow, breaks if you have to scroll
• Use DevTools to delete elements — fast for one element, breaks page layout, doesn't survive scrolling
• Use a redaction extension — RedactPro covers this. Click an element to blur it, drag a rectangle for arbitrary regions, or press Alt+Shift+E to auto-detect and redact every email, IP, JWT, and credit card on the page in one keystroke. The redaction stays through scrolling and tab switches.

For most B2B SaaS dashboards, the "auto-detect" approach takes about 3 seconds and catches things you'd never have remembered to redact manually — referenced customer IDs in URLs, IPs in audit logs, credit card last-4s in billing tables.

Step 3 · One minute · Test record, watch back, redact again

This is the step everyone skips. Don't.

Record the first 60 seconds of your demo with all the navigation you're going to do — open the menu, switch tabs, scroll the sidebar. Stop the recording, watch it back at 2x speed, and look for anything sensitive that's visible.

You will catch at least one thing 30% of the time. Fix it (more redaction, or close another tab), then start the real recording.

Most leaks happen in the navigation, not the main flow. The "before screen" and "after screen" of every demo step is where customer data lurks.

What about screen sharing instead of recording?

Live screen-sharing on Zoom or Meet is harder because you can't watch yourself back before the customer sees you. The same checklist applies, with one addition: before joining the call, share your screen privately with yourself (start a meeting solo, share, look at the preview). Most leaks are visible from the first frame.

For sales calls especially, build the habit: when the customer joins, you've already redacted the side panels and closed the unrelated tabs.