Screen sharing changes the audience of every visible value on the page. An API key that was visible only to you is suddenly visible to everyone in the call and to any recording, screenshot or meeting transcript that captures the screen.
That makes a screen share a small exposure boundary. It deserves the same kind of preparation as a demo environment or a sanitized log sample.
Threat-model the route through the demo
List the pages you expect to open and the sensitive data each can contain.
| Surface | Common exposure |
|---|---|
| Admin tables | names, emails, phone numbers |
| Settings pages | API keys, tokens, webhook secrets |
| Billing dashboards | balances, revenue, card details |
| Browser URLs | signed links, reset tokens, internal paths |
| Developer tools | headers, environment values, request bodies |
| Notifications | customer names, message previews, internal projects |
Then define what the audience actually needs. If the goal is to explain a configuration flow, the secret value is not part of the demo.
Use deterministic controls where possible
Auto Blur runs as a Chromium extension and covers recognized sensitive text in the page. Its built-in patterns currently include email addresses, phone numbers, API keys, JWTs, AWS credentials, credit-card numbers, private keys, GitHub tokens and passwords. It also includes detectors for Aadhaar, PAN, UPI IDs and IFSC codes.
For organization-specific values, custom regular expressions can cover internal identifiers. Manual blur boxes handle content that is visually sensitive but does not have a useful text pattern, such as graphs, maps, canvases or embedded widgets.
Test rules with both positive and negative cases. You want the employee ID to disappear without hiding every six-digit number in the interface.
Include input fields in the test
Secrets often live in inputs rather than paragraphs. Auto Blur has an input-scanning option that covers supported values while still allowing the active field to be used. Verify the behavior on the settings pages in your own route.
Also test content that loads after the initial page render. Modern dashboards update through client-side navigation and background requests; a privacy control that only scans once at load time is not enough. Auto Blur states that it watches newly added page content, but the responsible test is still the page you plan to show.
Understand the data boundary
According to Auto Blur’s privacy documentation, detection happens on-device and page content is not uploaded for classification. The extension says it has no usage analytics or tracking. Browser storage holds settings and local exceptions; browser sync may copy compatible settings between a user’s devices.
There is one nuance worth keeping: paid-license refresh contacts the product server using a signed code that contains the purchase email. That is different from uploading page content, but it belongs in an accurate security review.
Prepare a failure response
Auto Blur includes a panic shortcut, Option + Shift + B, to cover the entire page. It also offers optional triggers around supported screen sharing, tab switches and idle state.
Do not make an automated trigger your only control. Check what the meeting participants can see before sharing, and have a manual action ready if you need to switch context quickly.
If a credential does appear, treat it as exposed. Stop sharing, revoke or rotate it and review any relevant access logs. Blurring helps prevent disclosure; it cannot undo one.
A five-minute pre-demo test
- Open every planned page in the same browser profile used for the call.
- Confirm expected emails, tokens, credentials and money values are covered.
- Test dynamic content and input fields.
- Check manual blur regions and custom patterns.
- Trigger the panic shortcut once so the response is familiar.
- Verify the useful parts of the interface remain readable.
This is a modest control, not a replacement for access management, demo data or credential hygiene. It is useful because it operates at the point where a private browser page becomes a public presentation.
Review Auto Blur and its security documentation.
Product information checked on 4 October 2026.
Top comments (0)