NoCapture
AI privacy and app hiding for screen sharing
3 followers
AI privacy and app hiding for screen sharing
3 followers
Cross-platform desktop privacy tool. Prevent screen recording leaks, streaming exposure, and AI scraper visibility.
Free Options
Launch Team / Built With
Floot MCPBuild and ship web and mobile apps inside Claude or ChatGPT
Promoted
Hey PH 👋
I'm Wasi, solo builder behind NoCapture.
Built this after leaking AWS keys on a Zoom call — twice. Terminal was minimized behind the browser. I "cleaned my desktop" but forgot what was hiding.
NoCapture blocks windows at the OS compositor level. Not minimize. Not monitor two. Actually invisible to capture. Your window stays visible to you. Gone from Zoom, Teams, OBS, and AI agents that screenshot your screen every 2–5 seconds.
Claude Desktop, Copilot Vision — they don't use APIs. They photograph your screen and OCR everything. Password manager, Slack DMs, bank balance. All in frame. Most people have no idea.
While Building NoCapture i found out our app titles are also leaking info so i covered it as well in this launch.
NoCapture blocks that too. Same toggle.
What's the worst thing you've accidentally shared on a call? I need to know I'm not alone.
—
Built with Webview + Typescript. Happy to answer anything.
Spent the morning fighting with Windows Desktop Window Manager (DWM) frame buffers before mapping out the core architecture for NoCapture.
When an AI desktop agent or meeting recorder asks for screen access, Windows treats display output as an all-or-nothing pipeline. There's zero granular isolation built into the OS. You're either exposing your entire workspace—IDE secrets, Slack DMs, browser tabs—or you're stuck closing apps manually.
Putting "surgical, system-level control" on a visual is easy, but under the hood, it's a nightmare of DXGI desktop duplication hooks and process-level buffer interception.
We had to guarantee that when a cloaked window renders, NoCapture strips its pixel data directly out of the OS capture stream before Zoom, Teams, or background scrapers receive the frame—all while keeping that window completely visible and interactive on your actual physical display.
Tuned the DXGI hook listener down to ~16MB RAM with effectively zero CPU overhead so it doesn't drag down GPU-heavy dev setups.
Read the technical breakdown on how system-level window cloaking works
How much actual control do you feel you have over what background AI tools and recording bots are grabbing from your display right now?