· Updated
How to hide sensitive data in a product demo: blur, redact, and review
Keep private details out of shared demos. Prepare representative data, review every screen, and check what your redaction tool actually changes.
A useful product demo should show the workflow without exposing the customer account behind it. Start with representative data, then review the finished demo before sharing it.
Hiding a name on the screen is only part of that review. Captures may include page content, screenshots, titles, URLs, and exports. Check the surfaces your tool actually records and publishes.
Start with data you can share
Use a demo account with made-up customers, email addresses, and figures whenever possible. Prepare the account before recording so you can focus on explaining the task.
Check the workflow for:
- Names, addresses, avatars, and comment threads.
- Account numbers, internal identifiers, and financial figures.
- Tokens, passwords, one-time codes, and credentials.
- Page titles, URLs, menus, and autocomplete suggestions.
- Notifications or other content that can appear during capture.
Remove secrets from the recording environment instead of relying on a later edit to make them safe.
Choose the control for the detail
Blur can make a busy area less distracting. Do not rely on unreadability as proof that sensitive information is gone.
Redaction covers or replaces selected content. Find out whether your tool changes the published image or page content, or merely draws a layer over the source. Inspect the published result rather than trusting the editor preview alone.
Changing the source data avoids carrying the original detail into the capture. It is the best starting point when you can prepare a representative account.
These controls do not review the rest of the demo for you. A name hidden on one screen may still appear in a title, another step, or a downloaded file.
Review every output before sharing
- Watch the full workflow at a readable size, including menus and temporary states.
- Check selected redactions and look for repeated details elsewhere.
- Read the demo title, captions, step titles, and captured URLs.
- Open the published link with the access a viewer will have.
- Check the embed and every exported file separately.
- Recheck after recapturing, replacing, or republishing a screen.
If the tool stores an original capture, understand who can access it and how long it remains. Publishing a redacted version does not establish that the original has been deleted.
Evaluate privacy controls before buying
Test the control on the exact plan you are considering. Confirm whether it covers screenshots, captured page text, repeated occurrences, exports, and newly recorded steps.
Use the vendor’s current pricing page for availability and commercial terms. A free recording test may not cover the complete publishing workflow. Our demo-software cost worksheet helps you compare the full requirement.
How Demonstratio handles selected content
Demonstratio is in development. Its editor includes manual Blur and Redact tools for selected regions and elements. Published content and video export apply selected redactions; the original workspace data and existing published versions are preserved.
Redaction is deliberate, not automatic detection of private information. Selected text masking can retain word lengths, spacing, and digit positions, and text may reflow. Review titles, captions, URLs, other steps, and unselected duplicates yourself. Start with representative data and keep secrets out of the capture.
Prices and plan inclusions are not set yet. Sign up before launch and you keep early pricing when plans go live.
Related
Make your next explanation a walkthrough
Demonstratio is in development. Capture a browser workflow, edit the useful steps, and share a clickable demo. Prices are not set yet. Sign up before launch and you keep early pricing when plans go live.
More guides for your next demo
How to show your product without getting on camera
Make the product the explanation. Choose a screenshot guide, screen recording, or clickable demo for your page, launch post, and sales follow-up.
How to embed an interactive product demo on your website
A practical guide to embedding an interactive product demo: choose the right page, frame the workflow, write useful surrounding copy, protect accessibility, and give visitors a clear next step.
What should a product demo include? A practical guide
Build a product demo around one buyer question. Use a worked example, a reusable script, and a checklist to show the workflow and make the next step clear.