How do I hide customer data in a product demo?

Blur it with a tool that rewrites the stored image rather than drawing an overlay, and check every step at full size before publishing. The most common leaks are real names and emails in table rows, toast notifications, browser autofill, and identifiers in URLs.

Is blurring in demo tools actually secure?

It depends on the tool. An overlay drawn on top of the image leaves the original fetchable by anyone who opens the image URL directly. Destructive blurring replaces the pixels in the stored file, so there is nothing left to recover. Verify which one you have by opening a blurred image URL directly.

Should I use a separate demo account for recording?

A demo account with realistic but invented data removes the highest-frequency leak — the customer list — without the maintenance burden of a full demo environment. Combine it with a fresh browser profile that has no extensions or signed-in accounts.

What gets missed most often when redacting a demo?

Table rows, because they are dense and creators skim their own screenshots; toast notifications, which appear briefly and are captured perfectly; and the corners of the screen, where user menus and system notifications live. Window and full-screen capture modes catch far more than tab capture.

← Back to blog

How to Show Your Product Without Leaking Customer Data

August 14, 2026

Recording your real product is the fastest way to make a demo and the easiest way to publish something you should not have. The risk is rarely the screen you were thinking about — it is the notification that appeared in step four, or the customer name in a dropdown you never looked at twice.

This is what to redact, why the method matters more than people assume, and how to check a finished demo in two minutes.

What actually leaks

Real names and email addresses in list views. The most common leak by a wide margin, because tables are dense and nobody reads their own screenshots.
Browser autofill and toast notifications. They appear for a second, and a screenshot catches them perfectly.
Your own account details — the signed-in user menu, an internal admin badge, a Slack notification across the corner.
URLs containing identifiers. A customer id in an address bar is still customer data.
Revenue and usage figures you are not ready to publish, especially in a dashboard demo.
Anything in a second monitor's worth of screen capture. Window and full-screen recording modes catch far more than a tab capture does.

Why an overlay is not redaction

The important question about any blur tool is whether it changes the stored image or draws something on top of it.

An overlay — a black box positioned over the image in the page — hides nothing. The original image is still sitting behind a URL, and anyone who opens that URL directly, or reads the page source, sees the unredacted version. This has caused real incidents in real products.

Destructive blurring replaces the pixels in the stored file. The data is gone; there is no unredacted copy to fetch. This is the behaviour you want, and it is worth verifying in whatever tool you use — open the image URL directly and see what comes back.

The trade-off is that destructive redaction is permanent, which is why a tool that does it properly should also keep an original you can restore from if you blur the wrong thing.

A two-minute pre-publish check

Click through every step at full size. Thumbnails hide exactly the small text that leaks.
Read the tables, not the headlines. Names hide in rows, not titles.
Check the corners. Notifications, user menus and browser chrome all live there.
Open one blurred image URL directly to confirm the redaction is real, once, in whatever tool you use.
Have someone else look. You have seen these screens so many times you no longer read them.

The safer setup, if you have five extra minutes

Record in a fresh browser profile with no extensions, no bookmarks bar, and no signed-in accounts. This removes an entire category of leak before it happens and takes about a minute to set up.

Use a demo account with realistic but invented data where you can. Not a full demo environment — just an account whose rows are fictional. It removes the highest-frequency leak, the customer list, without any maintenance burden.

And close everything else. Screen and window capture modes will faithfully record whatever notification arrives mid-recording, which is how private messages end up in public demos.

Frequently asked questions

How do I hide customer data in a product demo?: Blur it with a tool that rewrites the stored image rather than drawing an overlay, and check every step at full size before publishing. The most common leaks are real names and emails in table rows, toast notifications, browser autofill, and identifiers in URLs.
Is blurring in demo tools actually secure?: It depends on the tool. An overlay drawn on top of the image leaves the original fetchable by anyone who opens the image URL directly. Destructive blurring replaces the pixels in the stored file, so there is nothing left to recover. Verify which one you have by opening a blurred image URL directly.
Should I use a separate demo account for recording?: A demo account with realistic but invented data removes the highest-frequency leak — the customer list — without the maintenance burden of a full demo environment. Combine it with a fresh browser profile that has no extensions or signed-in accounts.
What gets missed most often when redacting a demo?: Table rows, because they are dense and creators skim their own screenshots; toast notifications, which appear briefly and are captured perfectly; and the corners of the screen, where user menus and system notifications live. Window and full-screen capture modes catch far more than tab capture.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →