How to Blur Sentry During Screen Sharing (Hide Error Data, PII & Your DSN)

To hide error data and PII in Sentry while you screen-share, use a browser blur extension like BlurFirst to region- and element-blur the sensitive parts of an issue — the stack trace, the request and breadcrumb data, and the user context — before you present. Sentry runs in the browser, so BlurFirst covers the Issues stream, the issue detail view, and Settings. The blur is painted into the page as real pixels, so it survives Zoom, Microsoft Teams, Google Meet, Loom, OBS, and screenshots of the shared feed.

What's risky to show in Sentry during a screen share

A single Sentry event is dense with things that are fine for your team but risky on a shared or recorded call — a cross-company debugging session, a vendor screen share, or a Loom that outlives the meeting. Cover these first:

• Stack traces and exception messages — file paths in the frames reveal your internal directory structure and package names, and secrets are sometimes interpolated straight into an error string.
• Request and breadcrumb data — the Request, Headers, Cookies, and Breadcrumbs sections on an event routinely carry user emails, IP addresses, session IDs, and bearer tokens.
• User context — the User card pins a real customer's email, username, or ID to the crash.
• Your DSN and auth tokens — Settings → Client Keys shows the ingest DSN, and Auth Tokens and Integrations expose credentials that let anyone write to your project.
• Release and environment names — build identifiers, branch names, and env labels like prod-eu-2 that hint at your infrastructure.
• Org and project names — the sidebar and breadcrumbs name the company and product you may be under NDA about.
• The Issues list itself — titles in the stream summarize errors in plain language and can name a customer or endpoint before you even open an event.

How to blur Sentry specifically

The Issues stream and the event detail view expose different things, so use two passes: clear pattern-based PII automatically, then hide the structural bits by hand.

1. 1

   Open the exact event you'll discuss

   Navigate to the specific issue and expand the sections you intend to show before the call starts, so nothing new pops into frame mid-share. Start BlurFirst with Ctrl/⌘ ⇧ Y.

2. 2

   Scan for PII first

   Run Scan (a Pro gesture) to find and blur emails, phone numbers, credit-card numbers, SSNs, and API keys locally in one click — this catches the email in the User card and any key-pattern token in the breadcrumbs. Scan matches patterns, not free-text, so it won't catch an IP address or a customer's name; blur those by hand.

3. 3

   Element-blur the User card and DSN

   Click the User context card, or the DSN field in Settings → Client Keys, to frost just that element. Click it again to reveal after the call.

4. 4

   Box-blur the stack trace and request body

   Drag a rectangle over the frames you don't want on camera and over the Request, Headers, and Breadcrumbs panels. The box stays anchored as you scroll through a long trace.

5. 5

   Keep the panic shortcut ready

   If a teammate's alert or a new issue with a customer name in the title appears, press Ctrl/⌘ ⇧ H to blur the whole page instantly, then reveal what's safe.

Blur is one control, not secret rotation

Blurring stops your DSN, an auth token, or a customer's email from being *seen* on the call or in a recording. But if a DSN or token was ever exposed, rotate it in Settings — and if PII is landing in your events at all, the durable fix is server-side scrubbing and data-scrubbing rules so it never reaches Sentry. Treat the in-page blur as protection for the live presentation, not a substitute for those controls.

Save a reusable Sentry profile

If you triage in Sentry on calls often, set the structural blurs once and let them persist. With BlurFirst Pro you can turn on per-site auto-apply for your Sentry domain, so the org and project names in the sidebar and the property-level chrome re-apply automatically each time you open it — even after Sentry re-renders the view. You blur the event-specific bits per session, and the roster-level stuff is always covered.