A tool that sees your windows, reads your titles, and monitors your screen-sharing state requires an extraordinary level of trust. We do not take that lightly. This post explains exactly what NoCapture does with your data, which is almost nothing.
Everything Happens Locally
NoCapture does not upload screenshots. It does not upload window titles. It does not upload your app list, your process names, or your screen contents to our servers. The capture exclusion happens inside the Windows Desktop Window Manager on your machine. The title masking happens in memory on your machine. The live preview renders on your machine.
The only data that leaves your device is:
- License validation. When you activate Pro or Teams, NoCapture checks your license key against our server. This sends the key hash and a device fingerprint. It does not send your identity, your apps, or your usage.
- Crash reports. If NoCapture crashes and you opt in to sending a report, we receive a stack trace and basic system info. You can disable this entirely in settings.
- Update checks. NoCapture pings our update server to check for new versions. This sends your current version number and OS build.
That is the complete list.
What We Do Not Collect
We do not collect:
- Screenshots or screen recordings
- Window titles or content
- List of installed applications
- Browser history or tabs
- Keystrokes or input
- Network traffic
- File contents
- Usage patterns or behavior analytics
We do not have a "telemetry" toggle because there is no telemetry to toggle. The product is designed to be invisible to us in the same way it is invisible to capture tools.
Why Local Processing Matters
Screen privacy tools that upload data for "AI analysis" or "cloud preview" create the exact risk they claim to solve. Your screen contains passwords, personal messages, financial data, and confidential work. Any tool that sends this to a server is a potential breach vector.
NoCapture's architecture assumes the worst case: our servers could be compromised, our employees could be malicious, and our legal jurisdiction could demand data. The defense against all three is the same. We do not have the data.
Code Signing and Distribution
NoCapture executables are code-signed with a valid EV certificate. This means Windows SmartScreen and most antivirus tools recognize the publisher. Unsigned tools like some open-source alternatives trigger security warnings because Windows cannot verify their origin.
We are also preparing a Microsoft Store submission for additional distribution trust. Store apps undergo review and run in a more restricted environment.
DLL Injection and Security Software
NoCapture uses DLL injection to apply WDA_EXCLUDEFROMCAPTURE to third-party windows. This is the same technique used by Evanesco, CaptureGuard, and WinHider. Security software sometimes flags this behavior because injection is also used by malware.
Our injection is minimal. The DLL is small, signed, and only sets a single window property. It does not hook APIs, log keystrokes, or modify application behavior beyond the capture exclusion flag. If your EDR tool flags NoCapture, you can whitelist it by publisher certificate.
We wrote about antivirus false positives here.
The Open Source Question
NoCapture is not open source. We understand that some users prefer inspectable code. Our reasoning is commercial, not secretive. We publish detailed technical documentation about our architecture and limitations. We do not hide what the tool does or how it does it.
If you require open source, Evanesco and CaptureGuard are excellent alternatives that use the same core mechanism. We recommend them without reservation for users who prioritize code inspection over workflow features.
The Bottom Line
NoCapture is safe because it is designed to know as little as possible. Local processing is not a marketing feature. It is an architectural requirement for a tool that operates in the most sensitive visual space on your computer.
Read our full privacy policy here.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
