How to Make a Tutorial Video Without Showing Customer Data
A tutorial video should show the real product. The problem is that the real product is full of real people: names in the customer list, emails in the user table, amounts on invoices, phone numbers in the order details. Screen recordings capture everything, and blurring it afterwards by hand is slow and easy to get wrong. This guide shows how to make tutorial videos that show your real screens without showing anyone’s data.
Where customer data slips into tutorial videos
- Lists and tables. The customer list, orders, users, tickets: every row is a person.
- Search suggestions and recent items. The browser or the app shows what was typed before.
- Notifications and the account menu. A pop-up with a customer message, your own email in the corner.
- Dashboards. Revenue, real totals and customer counts you may not want public.
- One frame is enough. A screen that flashes for half a second can be paused and read.
Three layers of protection
| Layer | What it does |
|---|---|
| 1. Test account | The video never signs in as a real user |
| 2. Sample data | Every name, email and amount on screen is invented |
| 3. Blur before capture | Anything still sensitive is hidden before it reaches the video |
Step 1: Use a test account
Create a user only for videos, with the role whose screens the lesson shows. Never use a real customer’s account, and never your own admin account with access to everything. If the product has workspaces or companies, create a separate demo workspace. A test user without a phone code is easiest; if the login does ask for a code, DashCast shows a box on the video page during the render, you type the code, and it continues.
Step 2: Fill it with believable sample data
An empty table teaches nothing, and real data must not appear. Fill the test account with invented but realistic records: names that are clearly fictional, emails on a domain you own or an example domain, round amounts, sample products. Use the same sample data for every lesson, so the numbers on screen stay consistent from one video to the next.
If your product has a staging copy, use it, and keep it on a public address so DashCast can open it. A tool that only opens inside an office network or VPN cannot be reached.
Step 3: Blur before the screen is captured
Most tools blur after recording: you scrub through the video and draw boxes over every frame where data appears. Miss one frame and it is public, and the original file still holds everything.
DashCast works the other way. A blur is a step in the lesson script: it is applied to the element in the browser before it appears in the recording. The unblurred value is never captured, so there is no original to leak.
- Automatically. Turn on Blur personal data in the settings, and the AI writer adds a blur to any element that may show a real name, ID number or email.
- By hand. In the Scene Designer, add a Blur action to a column, a field or a whole panel.
- Check it. Use 🖼 Load preview to see your screens before you render.
Step 4: Check before you publish
- Watch the whole video once at normal speed, and pause on every table and pop-up.
- Look at the corners: the account menu, notifications, the browser address.
- Read the subtitles. The narration should not name a real customer either.
Keep it safe after updates
A new column in a table can show data that the old lesson never blurred. After a product change, press 🔍 Check selectors: it lists every step that no longer finds its element, including blurs whose field moved. Fix them and render again. More in updating video docs without re-recording.
Tips
- Invented, not anonymized. Changing one letter in a real name is not enough.
- Blur whole columns, not single cells, when a list scrolls.
- Hide totals you would not publish, like real revenue on a dashboard.
- Keep the test login private. Never show the password on screen, and change it if the test account has real access.
Making a dashboard lesson? Read how to make a dashboard tutorial video without screen recording.
What it costs. A free account includes 10 minutes of video with no credit card, plus 5 more after your first video. After that, a 100-minute pack costs $5, and plans start at $9 a month. Voice, subtitles, blur and every language are included.
Frequently asked questions
How do I hide customer data in a tutorial video?
The safest way is not to show it at all: record on a test account filled with sample data. For anything that must stay on screen, DashCast blurs the field in the browser before it appears, so the unblurred value is never in the video.
Is blurring after recording safe?
It works, but it is easy to miss one frame, and the original recording still contains the data. Blurring before the screen is captured avoids both problems.
Can the AI blur personal data automatically?
Yes. Turn on Blur personal data in the settings, and the AI writer adds a blur to elements that may show a real name, ID number or email. You can add or remove blurs in the Scene Designer.
Does DashCast store my customers’ data?
DashCast should only ever see your test account. Use a test login and sample data, never a real customer account, and you control exactly what the browser can open.
What if my product only has real data?
Create a separate test workspace or a staging copy, and fill it with believable sample records. It is worth it once, and every future video starts from it.
Real screens, no real customers.
Sign up free and get 10 minutes of video with no credit card. Use a test login, turn on blur, and let the AI write the first lesson.