Before recording your screen, clean the frame
The recorder sees more than your explanation
A clear tutorial can still expose a customer name, browser tab or notification. Do a short privacy pass before pressing record. The aim is not an empty desktop at any cost. It is a frame containing only the information the viewer needs. Use invented demonstration data whenever the real task does not require personal records.
Choose the smallest useful surface
Browser screen capture can offer a tab, window or screen depending on the browser. Pick the smallest surface that shows the task. A full-screen recording can include other windows when you switch apps. The browser asks you to choose; a website should not be treated as knowing which private window you meant to exclude.
Prepare the demonstration account
Close unrelated tabs, hide bookmarks if they reveal private projects and stop notifications that might appear in the capture. Check autofill suggestions and recent-file lists too. A clean demo account is often easier to inspect than a personal account with years of history. Do not show passwords, recovery codes, payment details or private customer records.
Watch a short test with audio
Record ten seconds, stop and play the file. Check the visible area and listen for private conversation or unexpected system sound. Screen-capture audio support varies by browser and source, so a requested audio option is not proof it was captured. Fix the setup before recording the whole explanation.
Review before sharing, not after
Watch the exported file rather than trusting the preview. If a secret appears, do not share that take; consider whether the exposed credential needs changing. Confirm the intended audience before uploading. Source: MDN, Using the Screen Capture API, https://developer.mozilla.org/en-US/docs/Web/API/Screen_Capture_API/Using_Screen_Capture . This is a capture-safety checklist, not a claim that every browser or Solivid version supports every capture source or audio option.