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.
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
- 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.
Related resources
Screen sharing without exposing sensitive data
Use Screen Privacy Blur before sales calls, investor updates, onboarding sessions, or live debugging where private information can appear unexpectedly.
Blur sensitive information in Google Meet
Blur dashboards, inboxes, internal tools, and private fields before sharing a Chrome tab in Google Meet.
Screen privacy for Zoom demos
Cover sensitive browser fields before sharing a browser window or tab during Zoom calls, customer demos, and recordings.