Claude Blurred My Password Out of a Screen Recording

I was recording a screen video for Meta's app review. It is the video where you prove your app actually uses the Instagram permissions you are asking for. Halfway through, I clicked "Show" on the password field. Four seconds of my password sitting in clear text, in a video I was about to hand to Meta.

I did not open a video editor. I did not scrub the timeline looking for the frame. I gave Claude the raw recording and one line, and it found the leak and blurred it.

What actually happened

I was building the Auto DM feature in CueEdit. Meta wants a screen recording for every permission, so I recorded the Instagram connect flow with Screen Studio and dropped the file in my project folder.

Then I typed this into Claude Code:

"I just made a video, can you please prepare it?"

That is the whole prompt. No timestamps, no "there is a password at 0:41". Claude watched the footage, and this is what it came back with:

• It found the four seconds where the password was visible after I clicked Show.
• It found a Chrome saved-logins dropdown that listed other usernames and a phone number.
• It cut an earlier failed attempt out of the clip.
• It placed a blur over both windows and checked every frame of both blur regions before handing the file back.

I was literally building a video editor at the time. Watching this happen made me rethink what an editor even needs to be.

How to do this yourself

You do not need to learn anything technical for this. It is a folder, a file, and a sentence.

1. Install Claude Code

Get it from claude.com/claude-code. It runs on your Mac or Windows machine and can read the files in whatever folder you open it in.

2. Put the recording in a folder

Make a folder, drop the raw screen recording in it, and open Claude Code in that folder. Screen Studio, QuickTime, OBS, Loom exports, all fine. Claude needs ffmpeg to read video frames. If it is missing, Claude will tell you and install it for you when you say yes.

3. Ask in plain English

Use the exact prompt I used, or be more specific if you already know what leaked:

"I just recorded this video for an app review. Find any passwords, emails, phone numbers or account names that show up on screen and blur them. Tell me the timestamps you blurred."

Asking for the timestamps matters. You want to verify, not trust.

4. Check the output

Claude will write a new file next to the original. Open it, jump to the timestamps it reported, and confirm the blur covers the whole region for the whole duration. Also scrub the few seconds before and after each blur, because dropdowns and autofill popups tend to flash briefly.

5. Keep the original private

Delete the raw recording, or move it somewhere that never gets uploaded. The blurred file is the only one that should leave your machine.

Where BlurWeb fits

Claude fixed my mistake after the fact. BlurWeb stops the mistake from happening in the first place.

BlurWeb is a browser extension that blurs sensitive information on the page while you are recording or screen sharing. You pick the elements once, it keeps them blurred every time that page loads, so a password field, an email column, or a revenue number never makes it into the recording at all.

Use both. BlurWeb for the things you know are sensitive before you hit record. Claude for the things you did not notice until after.

About me

I'm Sanskar. I build products solo with AI and teach how to do it.

• Vibe coding: how I build apps by describing them, not by writing every line.
• Vibe testing: how I test what I built the same way.
• Vibe marketing: how I turn a few typed lines into a finished reel from my laptop.

If you want to see the moment Claude placed the blur, the video at the top of this post is the raw reaction I recorded right after it happened.