Your phone used to be a separate device with a separate screen. Then Windows Phone Link — and Intel Unison, and Samsung DeX, and a dozen mirroring apps — merged them. Your text messages render as Windows notifications. Your phone's photos appear in a PC app. Your mobile apps run in windows on your desktop.
Convenient. Also: your phone — the most personal device you own — is now a set of windows inside your capture pipeline.
The Surfaces You Invited In
Notification mirroring. Phone Link pushes SMS, banking alerts, two-factor codes, and app notifications straight into the Windows notification center. Those toasts obey Windows rendering rules — meaning they draw over your game, enter the capture stream, and display your private mobile life with your PC's screen real estate. A text from your doctor has the same delivery mechanism as a Discord ping.
The Phone Link app itself. Message history, contact names, call logs — a complete window of your mobile communications running as a desktop app. It shows up in Alt-Tab. Its window title carries context. It's capturable by everything OBS, clipping tools, and screen shares can do.
App streaming. Run a phone app in a Windows window and it's a window like any other — except it's a window into an account ecosystem you probably never meant to broadcast: your banking app, your dating app, your family group chat.
Photo sync and file access. Thumbnails of your camera roll appearing in Explorer or the Phone Link app. Your camera roll is not content you curated for an audience.
Why This Layer Is Invisible Until It Fails
Nobody audits Phone Link because it's ambient. It installs by default on modern Windows builds, connects quietly, and then just... exists. Gamers who carefully cloaked Discord often discover — mid-incident — that a text message notification has been mirroring to their PC for months.
There's also a scope confusion: people think of the phone as "elsewhere," so its leaks feel impossible. But the leak doesn't happen on the phone. It happens the moment the phone's content renders on your desktop, inside your display session, where every capture API can reach it.
The Audit and the Architecture
Audit (five minutes):
- Open Windows Settings → Bluetooth & devices → Phone Link. Is your phone connected? Is notification mirroring on? Is app streaming enabled?
- Check for other bridges: Intel Unison, manufacturer utilities (Your Phone successors, Samsung apps), scrcpy sessions, third-party mirror tools.
- Look at what these surfaces render: contacts, SMS history, photos, app windows.
Architecture:
- Notification mirroring off during any streaming period — or better, notification shielding that suppresses mirrored mobile toasts without touching the alerts you need. Surgical, not blunt.
- Cloak the Phone Link app and any mirroring windows from capture. Your messages stay usable on your PC and absent from your stream.
- Title masking so the mirrored app's window titles don't narrate who you're talking to.
- Treat camera-roll access as a surface. If photo sync thumbnails can appear on your desktop, they can appear in a capture. Restrict it or keep it off the broadcast machine entirely.
Metadata discipline applies to mobile bridges exactly as it applies to everything else — the phone just made your metadata surface bigger without asking.
The Bottom Line
You secured your PC and then gave your phone a backstage pass. Every mirrored notification, text window, and photo thumbnail is now inside the same capture pipeline as your game. Audit the bridge, cloak the surfaces, and decide deliberately what crosses from your pocket to your stream.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
