Protect secrets
Use manual blur for known token areas and Smart Auto Blur Pro for common sensitive field patterns where automation can help. Revoke exposed credentials promptly if a secret was ever displayed.
Hide API keys during live debugging
Blur API keys, tokens, emails, and customer IDs before sharing docs, consoles, dashboards, or internal admin tools.
Add to Chrome — Free
Contact supportCompatible with your browser • Free install in 2 clicks • No signup required
Keep the workflow visible
The viewer can still follow your debugging steps while the specific key, token, email, or account field remains unreadable. That preserves technical context without publishing the secret.
- API keys
- Access tokens
- Emails
- Customer IDs
How to prepare before sharing
When setting up Hide API keys during live debugging (Hide API Keys in Live Debugging | 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
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
Blur sensitive data in Microsoft Teams screen sharing
Works with Teams tab & window sharing
ANSWERS BEFORE YOU INSTALL
Frequently asked questions
Does Smart Auto-Blur detect live API keys and tokens automatically?
Yes. Screen Privacy Blur Pro includes built-in local pattern masks for common API keys, tokens, emails, and cards, plus custom regex/mask rules for internal secret formats.
How do Manual Blur, Smart Auto-Blur, and Auto-Replace work for Hide API keys during live debugging?
For Hide API keys during live debugging (Use case), Manual Blur is free forever and lets you click exact DOM elements or draw custom frosted-glass regions (API keys, Access tokens, Emails, Customer IDs). 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 API keys during live debugging, 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 API keys during live debugging rules (API keys, Access tokens, Emails, Customer IDs) 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.