How to Hide Sensitive Information When Sharing Your Screen

To hide sensitive information when sharing your screen, layer three habits: share a single window instead of the whole desktop, silence notifications before the call, and blur the data that has to stay on screen — live, with a screen blur tool — so names, emails and numbers are unreadable even while you present the real page.

One habit alone is not enough. Window sharing does nothing about the customer table inside the window; notifications off does nothing about the URL bar. Below are seven measures that stack, roughly in the order of effort, and the honest limits of each.

What actually leaks on a shared screen?

Most leaks are not the document you meant to show. They are the periphery: a message notification sliding in over a client's name, browser tabs whose titles spell out your other customers, the address bar carrying a session token or an internal path, a CRM sidebar with real emails, an autocomplete dropdown remembering a search. Attendees can screenshot anything the moment it renders — there is no undo.

Seven ways to hide sensitive information before you share

1. Share a window, not your desktop

Every meeting tool — Zoom, Google Meet, Microsoft Teams — lets you share one application window instead of the entire screen. This is the single highest-value switch: notifications, your dock and every other app stay invisible. Limit: anything inside the shared window still shows.

2. Use a separate browser profile for presenting

A dedicated Chrome profile with no history, no autocomplete, no logged-in personal accounts and only the tabs you need. Bookmarks bar hidden. It turns 'clean up before the demo' from a 20-minute cleanup into opening the right profile.

3. Silence notifications at the OS level

Do Not Disturb on macOS, Focus Assist on Windows — before the call, not after the first Slack message slides over your slides. Meeting tools cannot suppress another app's toasts; only the OS can.

4. Close or park sensitive tabs

Tab titles leak even when a tab is not active. Move work-in-progress to a different window or profile. If a tab must stay open, at least keep it pinned so its title collapses to an icon.

5. Hide the URL bar

Address bars carry tokens, IDs and internal hostnames. Open the page as an app window or go full screen — the full steps for Chrome, Edge and Firefox are in our URL-bar guide.

6. Blur the data that must stay on screen

Sooner or later you have to show the real dashboard — that is the point of the demo. A real-time screen blur extension hides the sensitive parts of a page while you present it: click an element or drag an area to blur it, and auto-detection catches emails, phone numbers, card numbers and API keys you would miss under pressure. DataBlur does this locally in your browser — no cloud, no editing, and the blur persists while you scroll and navigate.

7. For recordings: blur before you hit record

Editing blurs into a finished recording means tracking every sensitive region frame by frame — and one missed frame publishes the data. Blurring on screen before recording removes the entire editing step; the comparison of both workflows is in our screen-recording guide.

Zoom, Google Meet and Microsoft Teams — where the option lives

All three hide the share behind the same idea: when you click Share, choose a specific window (or a single Chrome tab in Meet and Teams) instead of a full screen. A tab share is the narrowest and safest scope a meeting tool offers — combine it with a blur extension for the data inside the tab, and with OS-level Do Not Disturb for everything outside it.

What these measures don't cover

• Second monitors. Sharing 'Screen 2' while notes live on Screen 1 works until a dialog opens on the wrong display. Window sharing avoids the guesswork.
• Data inside the page you present. Only redaction or live blur covers this — none of the meeting tools can.
• Recovery of weak blurs in recordings. Pixelated text can sometimes be reconstructed; for recordings use a solid redact style for data that must never be recovered — details in our recovery explainer.

Frequently asked questions

Can Zoom or Teams blur part of my shared screen?

No. Meeting tools blur camera backgrounds, not shared content. To blur data on a shared page you need it hidden at the source — a browser extension that blurs elements in real time, or pre-redacted material.

What is the safest way to demo with real customer data?

Share a single tab, present from a clean browser profile, and run a real-time blur with auto-detection on, so emails, numbers and keys are hidden even when you scroll into a view you didn't rehearse. The fail-safe matters: if detection breaks, the tool should blur more, not less.

Does hiding the URL bar protect the page content?

No — it only stops tokens, IDs and internal paths from showing in the address bar. Content on the page needs its own protection: window scope, clean data, or live blur.

Is blurring during a live call reliable enough for compliance-sensitive work?

Treat it as one layer, not the whole answer: narrow the share scope, silence notifications, and blur with a tool that processes everything locally so the data never leaves the device. For hard requirements, rehearse the exact flow once with a colleague watching for leaks.

Present the real thing, safely

Fake demo data convinces nobody, and cleanup-by-vigilance fails exactly when the call matters most. Stack the scope habits above, then let a blur tool guard the page itself: install DataBlur free and run your next screen share with the sensitive fields already gone.