Demo Videos Without Real Customer Data
Record every demo against a dedicated demo workspace filled with plausible fake data, logged in with a test account that only sees that workspace, and never against your own account or a customer’s. It sounds obvious; it is also how most demo videos end up showing a real email address in the corner. Here is a setup that makes the safe path the easy path.
Why is your own account the wrong one?
Your account has your real projects, your real teammates’ names, the real invoices. A thirty-second demo recorded there has a dozen chances to leak something, and the zoom that makes the demo readable also makes the leak readable. A customer’s account is worse: it is not yours to show.
What goes in the demo workspace?
Create one workspace (organization, team, account, whatever the product calls it) that exists only for demos:
- Plausible names. “Acme Projects”, “Website redesign”, “Q4 launch”. Names that look like a product in use, not “test test 123”. Viewers notice placeholder data and stop trusting the demo.
- Enough content to look alive. Two or three existing items on every list the demo will show, so the new one lands among neighbours.
- No real people. Teammate names and emails invented, avatars generic. If the product shows the signed-in user’s name, make the test user “Ana Demo” or similar.
- Stable state. Demos that create things leave things behind. Either clean up after each recording or make the flow idempotent (create, then delete at the end).
Which login should the recording use?
The recording should start after the login, with an account that can only see the demo workspace. With Klevo, that is a saved secret: a password secret for a plain form, a storage state for single sign-on or two-factor, or a magic link for a staging test-login endpoint. The login runs before recording starts and never appears in the video; the secret is encrypted and referenced by name, so the password is never in the chat. Recording an app behind a login has the setup for each kind.
Give the test account the least access that still makes the demo work. If the flow is “invite a teammate”, the account needs to invite; it does not need to see billing.
What about sensitive fields on screen?
Some demos have to type into a field that is sensitive by nature: a password, an API key, a card number in a test-mode checkout. Klevo blurs these automatically during recording: password fields, and any field whose name or label looks like a password, token, secret, key or card. The blur lives in the page, so every frame carries it. For a field it would not recognize, name the step’s text from a secret rather than typing it, and it is blurred too.
For values that are not fields, such as an API key displayed on a settings page, the honest answer is: do not demo that screen with a real key. Rotate the test account’s key to a throwaway before recording, or record a step that opens the page with the key hidden.
What is the pre-recording checklist?
| Check | Why |
|---|---|
| Logged in as the test account, not you | The header shows a name and avatar |
| Demo workspace selected | Workspace switchers remember the last one |
| Lists have two or three plausible items | Empty states look like a broken product |
| No real emails anywhere on the flow’s screens | Zoom makes them legible |
| Test mode on for payments | A demo must not charge a card |
| Staging, not production, if the flow creates data | Production data is customer data |
What if the demo needs real-looking data?
Sometimes the feature is the data: an analytics product is dull with fake numbers. Make the fake numbers good. Seed the demo workspace with a generated dataset that has the shape of real usage (a weekly rhythm, a few outliers), and keep the seed script in the repo so the workspace can be rebuilt. The time spent on a convincing seed pays for every demo after.
How do you make the AI respect this?
When Claude records a demo through Klevo it operates the account you point it at; it does not pick. Tell it the workspace and the secret in the prompt and it stays there:
Record a demo with Klevo on https://staging.acme.app/projects, logged in with DEMO_LOGIN, in the Acme Projects workspace. Create a project named Q4 launch.
Captions are written from what it did, not from your data, and the intro and outro cards show only the title, brand and call to action you give. Captions that explain a flow covers what goes in them; the AI demo generator guide covers what an AI should never invent.
FAQ
Can a saved secret leak through the chat? No. The secret is stored encrypted on Klevo, referenced by name in the script, and sent only to the recording service for the duration of a session or render.
Can I delete a video with a mistake in it? Yes, from the video page. The files are removed; the row keeps its date for the monthly count.
Does blurring cover text that looks like a key in a table? No; the automatic blur is for input fields. Keep real keys out of the demo workspace.
Can I record on production? Only with a demo workspace that holds no customer data; staging is the safer default for flows that create anything.