Software feature launch · Production guide
Redact customer data from screenshots and product demo clips
Record a demo account with fictional data. Track identifiers in menus, tooltips, filenames, subtitles and every transition. The published-format cup edit masks the account corner.
Input and decision
Start the checklist before recording. Use a fictional project and identify account corners, balance fields, browser chrome, menu overlays and file paths that could appear.
Set up the comparison
Inspect the first and last frame of each trim and the frames around cursor or menu changes. Burn-in covers must actually cover the moving region for the entire interval.
Make the comparison
Scrub across each cut one frame at a time. Include any tooltip or project label that enters outside the masked account corner in the second review.
Worked record
The downloadable worksheet includes the records below and a blank row for your own project.
| Time range | Risk area | Mask bounds | Checked frames | Reviewer |
|---|---|---|---|---|
| 3–7 s | Account corner | Fixed rectangle | Start mid end | Second reviewer |
| 7–12 s | Selection change | Inspect cursor path | Cut boundary | Second reviewer |
| 12–17 s | Account corner and project labels | Check active mask | Cut boundary | Second reviewer |
Check the result
Scrub the frames before a cut, after it and during a selection change. Keep a second reviewer for the final exported file; a clean first frame is insufficient.
Hand off the revision
Send the checked public encode with the reviewed time ranges. Retain the private original with its owner.
Review question
Which points in a redacted capture need another person's review?
Have a second person inspect 3–7, 7–12 and 12–17 seconds, including cut boundaries and selection changes. Use the public encode to check the masks.
Use the task on your own brief
Use a copy of the worksheet to keep the project’s source files, reviewed options and decisions together.