Personal Data in Product Demos
August 25, 2026
Demos are made from real screens, and real screens in a working product contain real people: names, emails, addresses, order histories.
Publishing those is not a technical decision, and it is worth understanding the shape of the obligation even though this is not legal advice and your own counsel is the authority on your situation.
What the obligation attaches to
Not the database — the personal data itself, wherever it ends up. A name in a screenshot on your marketing site is the same category of thing as a name in your production tables, and putting it on a public page is a use of it that whoever it belongs to did not agree to.
That holds regardless of how obscure the demo is or how few people see it. Publication is the act, not readership.
The only reliable answer
- Record against a seeded environment with invented people. Everything else is mitigation.
- Never rely on blur alone. It is a filter over a real image, one missed field is a real disclosure, and an unblurred original may still exist.
- Beware the edges — a browser tab title, an autocomplete dropdown, an email preview, a notification.
- Check exports too. A video or GIF made from the same steps carries whatever the steps carried.
When you must use a real account
Sometimes only production has the data volume that makes a demo credible. Then get explicit permission from the customer whose data it is, in writing, and keep the demo to the screens you agreed.
A customer will usually say yes and appreciate being asked. Discovering their client list in your marketing later is a different conversation entirely.
The internal-tool trap
Demos of internal software are where this goes wrong most often, because the audience is colleagues and it feels private. It is not: a link gets forwarded, ends up in a wiki, and is read by contractors and new joiners for years.
Apply the same rule there. It is the demo most likely to contain salaries and customer records, and the one least likely to be reviewed by anyone.
Frequently asked questions
- Can you put real customer data in a product demo?
- Not safely. A name in a screenshot on a public page is the same category of thing as a name in your production database, and publishing it is a use the person did not agree to. Record against a seeded environment with invented people instead. This is not legal advice.
- Is blurring enough?
- No -- it is mitigation rather than a solution. It is a filter over a real image, one missed field is a real disclosure, and an unblurred original may still exist. Watch the edges too: tab titles, autocomplete dropdowns, email previews and notifications.
- What about demos of internal tools?
- They are where this goes wrong most often, because the audience is colleagues and it feels private. Links get forwarded and end up in wikis read for years -- and internal tools are the ones most likely to hold salaries and customer records.
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 →