Before recording
Add blur to names, account IDs, emails, API keys, or private roadmap notes that can appear during a walkthrough. This lets viewers follow your steps without exposing the value underneath.
Hide private details before Loom recordings
Record product walkthroughs, bug reports, and async updates with fewer accidental leaks in browser-based workflows.
Add to Chrome — Free
Contact supportCompatible with your browser • Free install in 2 clicks • No signup required
After recording
A clean recording means less manual editing and fewer retakes when you need to share a link quickly with a customer, teammate, or support contact.
- Product walkthroughs
- Bug reports
- Async updates
- Founder demos
How to prepare before sharing
When setting up Hide private details before Loom recordings (Hide Private Details in Loom | Screen Privacy Blur), Screen Privacy Blur runs 100% locally in your Chromium browser so private records, credentials, and financial balances remain hidden or replaced with realistic demo data before any frame is shared.
- Open the browser tab or desktop context you plan to present.
- Place blur overlays over the private fields that can appear during the walkthrough.
- Review the visible area, then start the call or recording.
Compare protection modes for this workflow
| Capability | Manual Blur (Free) | Smart Auto-Blur (Pro) | Auto-Replace Data (Pro) |
|---|---|---|---|
| How it targets data | Click exact DOM element or draw freeform region | Local regex & pattern masks (emails, phones, keys, cards, SSNs) | Local pattern masks + custom CRM/dashboard rules |
| How your screen looks on calls | Customizable frosted glass overlay | Automatic frosted glass over detected PII | Clean, natural UI with realistic synthetic demo data |
| Best for | Quick internal calls & ad-hoc sections | Live debugging, coding streams & support calls | Client sales demos, Loom tutorials & Stripe/CRM walkthroughs |
| Role presets | Per-website saved layouts | Dev / Streamer & PII mask profiles | SaaS Sales Demo, FinTech / Stripe & Dev / Streamer scenarios |
| Data privacy | 100% local in browser | 100% local in browser | 100% local in browser (never alters backend DB) |
Related resources
Hide API keys during live debugging
API keys
Replace customer data during live CRM demos
Fictional customer identities
Hide API keys during screen sharing and coding streams
Local API key masks
Hide balances and customer PII in financial dashboards
Blur account balances
ANSWERS BEFORE YOU INSTALL
Frequently asked questions
Can I blur or replace sensitive data on the free Loom plan?
Yes. Screen Privacy Blur works inside Chrome before Loom captures your tab or screen, so you get free manual blur and saved layouts regardless of your Loom subscription tier.
How do Manual Blur, Smart Auto-Blur, and Auto-Replace work for Hide private details before Loom recordings?
For Hide private details before Loom recordings (Use case), Manual Blur is free forever and lets you click exact DOM elements or draw custom frosted-glass regions (Product walkthroughs, Bug reports, Async updates, Founder demos). Smart Auto-Blur Pro masks detected emails, phones, and API keys locally, while Auto-Replace Pro swaps sensitive text with realistic demo data.
Does any page data leave my browser during Use case sessions?
No. When using Screen Privacy Blur for Hide private details before Loom recordings, all pattern matching and DOM replacement run 100% locally inside the Manifest V3 Chrome extension. Open Chrome DevTools → Network while toggling Use case protection to verify zero page content is uploaded.
Can I save my Use case layout for future calls and recordings?
Yes. Once you configure Hide private details before Loom recordings rules (Product walkthroughs, Bug reports, Async updates, Founder demos) on a domain, Screen Privacy Blur saves that layout locally so your protection is ready automatically before your next Zoom, Google Meet, Microsoft Teams, Loom, or OBS session.