Screen-share privacy is usually discussed as a single problem: hide the window. But in practice, privacy failures happen at three distinct layers. Most tools address only the first. Understanding all three is the difference between "probably safe" and "deterministically safe."
Layer One: Pixels
This is what most people mean when they say "hide my window." Layer one prevents the visual content of a window from entering the capture stream.
The Windows API for this is SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE. When applied, the DWM compositor removes the window from the frame buffer sent to supported capture tools like Zoom, Teams, OBS, and Snipping Tool.
Tools that cover layer one:
- Evanesco
- CaptureGuard
- WinHider
- Cloakly
- NoCapture
Layer one is table stakes. It is necessary. It is not sufficient.
Layer Two: Metadata
Even when a window is cloaked from capture, it can still leak information through metadata:
- Window titles in the taskbar, Alt-Tab switcher, and window enumeration APIs
- Process names visible to task managers and monitoring tools
- Notification banners that draw over the captured display
- Desktop file and folder names visible during app switching
- Browser tab titles persistent in the tab bar even when inactive
A window titled "Slack — Recruiter: Offer letter" tells a story even if the window content is blacked out. A notification banner from your bank reveals account activity even if the banking app itself is cloaked. A folder named "[Competitor] Acquisition Analysis" on your desktop exposes strategy during a three-second app switch.
Tools that cover layer two:
- NoCapture (title masking, notification shield, Alt-Tab skip)
- WinHider (taskbar and Alt-Tab hiding, but not title rewriting)
We wrote about how AI meeting scrapers harvest window titles and metadata here.
Layer Three: Workflow
This is where privacy becomes sustainable. Layer three ensures that protection happens automatically, consistently, and verifiably — without depending on human memory or discipline.
Elements of layer three:
- Live preview. See the capture stream before sharing. Remove the guesswork.
- Routines and presets. One-click configurations for common scenarios. "Daily Standup" cloaks Slack and email. "Streaming" hides Discord and Spotify.
- Global hotkeys. Toggle protection instantly without navigating a UI.
- Auto-start and persistence. Protection survives reboots. New apps are cloaked automatically based on rules.
- Focus mode. Auto-cloak distracting or sensitive apps when screen sharing begins.
- Team-wide policies. Centralized enforcement so individual users cannot forget or override protection.
Tools that cover layer three:
- NoCapture
Why the Layers Matter Together
A tool that covers layer one but not layer two leaves you exposed to metadata leaks. A tool that covers layers one and two but not layer three leaves you exposed to human error — forgetting to enable protection, missing a notification, or assuming a window is hidden when it is not.
The most expensive screen-share disasters we have documented here were not caused by missing layer one. The windows were often cloaked or closed. The leaks happened through:
- Tab titles visible during browser switching
- Notifications arriving at uncorrelated times
- Desktop folders visible for seconds during app transitions
- Taskbar previews revealing running applications
These are layer two failures. Layer three failures happen when someone simply forgets to apply protection in the first place.
The Honest Limitation of All Three Layers
None of these layers stop a camera pointed at your monitor. None stop a kernel-level capture bypass. Microsoft documents this explicitly.
What the three layers do stop is the accidental leak — the notification, the background window, the forgotten tab title — which is how 99% of professional screen-share damage occurs.
We wrote about why manual preparation keeps failing here.
How to Evaluate Any Tool
Ask three questions:
- Does it hide the pixels? (Layer one)
- Does it hide the metadata? (Layer two)
- Does it remove the dependency on my memory? (Layer three)
If the answer to all three is yes, you have deterministic privacy. If the answer to any is no, you have probabilistic privacy — which is another way of saying you are hoping.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
