You recorded a walkthrough in a real system, and somewhere in it there is probably a customer's email, a phone number, an account ID or an invoice total. Before the video is shared, those details need to be covered. This guide covers what to look for, detection versus human review, moving content, checking the export, and the separate problem of things you said out loud.
1. Know what you're looking for
Sensitive details in business software tend to fall into a few groups:
- Email addresses and phone numbers, in contact records, call logs and user menus.
- ID numbers: account, customer, order and ticket numbers, including ones with letter prefixes.
- Money amounts: balances, prices, invoice totals.
- Names of people and companies, in lists, headers and breadcrumbs.
- Web addresses, which can reveal a customer's internal system name.
- Values next to labels, such as whatever sits beside "Balance" or "Account".
Also check the edges of the screen: browser tabs, the bookmarks bar, notification pop-ups and the account menu.
2. Decide who will see the video
An internal video may keep record IDs readable so colleagues can follow along; a public tutorial should hide nearly everything. Decide this first, because it sets which categories you blur.
3. Let a scan find candidates, then review every one
Going frame by frame by hand is slow and error-prone. A text scan can do the first pass, but treat what it finds as a list for you to review, not a finished job.
Here is how that works in GlideClip:
- Open your recording (record it in Chrome or Edge, or import a video your browser can play, usually MP4 or WebM).
- Go to Make it safe > What to look for.
- Under Who will see this video?, pick a level: Internal: my company only, Partners or customers, Public: anyone, No blurring needed or Custom.
- Open What gets blurred and check the categories: Email addresses, Phone numbers, Web addresses, Long ID numbers (6+ digits), Money amounts and Your own terms.
- Names are not found on their own. Type each one in Names or words to always blur, one per line (for example "Jane Smith" or "Acme Corp"), and keep Your own terms (below) ticked.
- To hide whatever follows a label, add the label to Blur the value next to these labels, one per line.
- Click Prepare video. The scan runs in your browser tab; the recording is not uploaded.
Then review:
- Open Make it safe > Review blurs. Each found value is listed once, with when it first appears and how many times.
- Click an item to jump to where it appears. Untick anything that should stay visible.
- For anything the scan missed, click ＋ Draw a blur box (or press B) and drag over it on the video. Set From and To so the box shows only when it's needed.
- If a demo value should never be blurred, add it to Never blur these, one per line in What to look for.
If you change your lists after preparing, click Prepare video again so the scan picks up the new words.
4. Be honest about what a scan can miss
No scan catches everything, and GlideClip's is no exception:
- It reads English text on screen.
- Small, blurry or fast-scrolling text can be missed.
- Names are only found when you list them.
- Anything that isn't text, such as a face in a profile photo, needs a blur box you draw yourself.
That is why a person reviews every video, even short ones.
5. Watch out for content that moves
Scrolling lists, pop-ups that open and close, and dropdowns are where details slip through. GlideClip reads the screen twice a second, and a blur it found follows its text as the page scrolls or a window moves, covering the path in between. Fast or jumpy motion is still worth a look. When you review:
- Slow down at every scroll and every page change, and watch the preview there.
- Check the first and last frames of each pop-up, where text may be half-drawn.
- On the timeline, each blur shows as a bar. Drag its ends to blur for longer or shorter so it covers the whole time the detail is visible.
- For something the scan didn't catch, a drawn blur box with the right From and To times is often the simplest fix. A drawn box stays exactly where you drew it, so if that part of the screen moves, check the box covers the detail for its whole path.
Better still, record with test data where you can, and scroll slowly.
6. Check the exported file, not just the editor
What matters is the file people will actually watch. After you export:
- In Make it safe > Export safe copy, click Export safe copy to save a blurred MP4. In the free edition it carries a small "Made with GlideClip" mark.
- Or, for a finished training video with callouts and frame, use Studio > Render > Render final video (free up to 2 minutes with a mark; any length with Pro).
- Open the saved file in a normal video player and watch it all the way through, pausing at scrolls and pop-ups.
- Use Download redaction report if someone else approves the video. It lists the sharing level, each blurred item with its times, and anything found but left visible, showing only the first two characters of each item.
7. Don't forget what you said out loud
Blurring is visual. It changes what is on screen, not the sound. If you read a customer's name, phone number or account number aloud while recording, it is still in the narration, and in the transcript too.
Your options:
- Cut it. In Studio > Edit, use Cut from here and …to here to remove that stretch. The final render leaves cut parts out, sound included.
- Say it again. In Studio > Audio, Replace a line lets you record just that sentence again. The new take's volume is matched to your voice around it, and the captions and transcript use the new words.
- Prevent it next time. Narrate what you are doing ("I'll open the contact record") rather than reading values off the screen.
Try it on a sample
The fastest way to see this workflow is on safe, invented data. GlideClip opens a 38-second sample recording of a made-up CRM so you can run Prepare video, review the blurs and export without touching real customer data.
Your recording is processed in your browser and never uploaded. Optional AI features work from text only, with detected details masked.