You cloaked Slack. You masked the title. You verified the live preview. Then a message arrives from your recruiter and the banner draws over your shared PowerPoint deck. The audience sees it. The recording captures it. Your preparation was perfect except for the one layer you forgot.
Notifications are the most common screen-share leak because they are designed to break through every layer of user control. Do Not Disturb, Focus Assist, and Slack's pause notifications all have exceptions. Priority messages break through. Calendar reminders appear regardless. System update banners ignore your settings.
Notification shielding exists to close this gap.
How Notifications Bypass Standard Defenses
Windows Do Not Disturb suppresses most banners but not all. Slack's pause notifications has a "priority" bypass for DMs from specific people. Teams shows its own meeting notifications even when system DND is on. Browser notifications from Gmail, calendar, and banking apps often ignore OS-level settings because they draw through their own rendering paths.
The result is a probabilistic defense. Most notifications are suppressed. The one that matters arrives at the worst moment.
What Notification Shield Does
Notification shield in NoCapture intercepts banner and toast notifications from protected applications before they render on the display surface. If Slack is cloaked, its notifications are also suppressed during active screen shares. If your banking app is cloaked, payment confirmations and OTP codes do not appear as overlays.
The shield is context-aware. It activates when screen sharing is detected or when you manually enable a routine. It does not suppress notifications during normal use. You still see your alerts when you are not sharing your screen.
Why This Is Not the Same as Do Not Disturb
Do Not Disturb is a blanket setting. It suppresses all notifications from all apps. Notification shield is surgical. It suppresses only the notifications from apps you have designated as sensitive. This means:
- You still get calendar reminders from Outlook if Outlook is not cloaked
- You still get build notifications from CI tools if those tools are not protected
- You only lose notifications from apps that should never appear on camera
This selectivity matters because blanket DND creates its own problems. Missing a critical alert because you turned off all notifications is a different kind of failure.
Which Apps to Shield
Common candidates for notification shield:
- Slack and Discord (DMs, channel mentions, thread replies)
- Email clients (Gmail, Outlook — especially subjects and sender names)
- Banking and payment apps (transaction alerts, OTP codes)
- Messaging apps (WhatsApp, Signal, Telegram)
- Password managers (TOTP codes, breach alerts)
- Dating apps (yes, this happens)
- Health apps (appointment reminders, test results)
We documented a HIPAA-level leak caused by a medical notification here.
How to Enable Notification Shield
In NoCapture, notification shield is toggled per app or per routine. When you cloak an app, you can optionally enable notification suppression for that same app. The setting persists across reboots if you save it to a routine.
Verify the shield in live preview. Send yourself a test message from another device. The banner should not appear in the preview pane.
The Limitation
Notification shield operates at the application level. It suppresses banners from protected apps. It does not suppress system-level Windows notifications that originate from the OS itself, such as low battery or security warnings. These are generally less sensitive but still worth monitoring.
We wrote about the three layers of privacy here. Notification shield is layer two: metadata protection.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
