# Screen recording privacy checklist

Use this checklist before recording a product demo, tutorial, support video,
training clip or internal walkthrough. It is designed to prevent sensitive data
from entering the source recording rather than relying on blur afterward.

Canonical maintained guide: https://cadre.cam/guides/screen-recording-privacy.html

## Before recording

- [ ] Use a dedicated demo account with synthetic names, messages, analytics and
  payment details.
- [ ] Enable Do Not Disturb or a Focus mode on the Mac and any mirrored device.
- [ ] Close email, chat, calendar, password managers, terminals and unrelated
  browser profiles.
- [ ] Remove private filenames from the desktop, Downloads and recent-file menus.
- [ ] Inspect open-tab titles, bookmarks, browser profiles and autofill suggestions.
- [ ] Replace the clipboard with a neutral value before demonstrating paste.
- [ ] Confirm the exact screen or window that will be captured.
- [ ] Make and inspect a ten-second test recording.

## During the take

- [ ] Follow a rehearsed path through inspected demo data.
- [ ] Avoid untested search boxes, file pickers, address fields and recent-item menus.
- [ ] Stop and note the time immediately if private information appears.
- [ ] Retake a clean section when practical instead of depending on a moving mask.
- [ ] Remember that anything visible in pixels can enter the video, even when typed
  keystrokes are not retained separately.

## Before publishing

- [ ] Watch the complete rendered file at normal speed with sound.
- [ ] Watch it again without sound and inspect transitions, menus and notification
  areas.
- [ ] Listen without looking for names or private details in narration or system
  audio.
- [ ] Inspect several frames before and after every blur or mask.
- [ ] Review captions separately for details surfaced by transcription.
- [ ] Check the export filename and metadata for customer, project or employee names.
- [ ] Confirm that the sharing destination and access settings match the audience.

## When an AI agent is connected

- [ ] Keep prompts focused on editorial intent; do not paste secrets into them.
- [ ] Review the agent provider's data controls separately from the editor's local
  processing boundary.
- [ ] Inspect each timeline change and use undo when a result is incorrect.
- [ ] Complete the same final rendered-file review used for a manual edit.

## Incident response

- [ ] Stop distribution if private data is discovered after publication.
- [ ] Remove or restrict the exposed copy at every destination you control.
- [ ] Preserve the affected file and timeline information if your security process
  requires investigation.
- [ ] Follow the organization's notification, legal and security procedures.
- [ ] Replace the source with a clean retake or a fully verified correction.

This template is provided for operational planning, not as legal or compliance
advice. It may be copied and adapted without attribution. Link to the canonical
guide above when you want readers to receive future corrections and product-
specific privacy details.