Visible to you.
Invisible to everything else.
InvisiQ doesn’t need to be trusted. Every claim on this page is verifiable, and your screen content never leaves your machine.
A side-by-side proof.
Your screen on the left. What Zoom shares with everyone else on the right.
Four guarantees you can audit yourself.
OS-level capture exclusion
The overlay uses Windows’ native SetWindowDisplayAffinity(WDA_EXCLUDEFROMCAPTURE), a documented privacy API in Windows 10 v2004+ and 11. The flag tells the OS to drop the window from every standard capture pipeline (Zoom, Teams, Meet, OBS, Snipping Tool, Print Screen). Not a kernel hook. Not a driver. The same primitive that Netflix uses to hide protected video.
AES-256-GCM encrypted keys
API keys are encrypted at rest with a machine-derived key (PBKDF2-SHA256, 600K iterations) and stored in an encrypted electron-store file. They never leave your device except as the body of a direct call to the AI provider you chose.
Your screen never leaves your device
Screenshots and screen contents are never stored or uploaded to InvisiQ. An image is recorded only as a yes/no flag. During the beta we do store the text of the prompts you send, to improve the product: keys and obvious personal info are stripped first, it’s deleted after 30 days, and you can wipe it anytime in Settings → Privacy. Full detail here.
Keys, chats & memory stay local
Your API keys, conversations, memory index, and settings are stored encrypted on your machine and decrypted only at the moment of use. AI requests go straight to the provider you chose, InvisiQ never proxies your screenshots or your keys.
Where your data actually goes.
Your screenshots and keys stay on the left. Your prompt text goes two places, and never your screen.
Security & privacy, asked.
The only way to test invisible is… to try it.
Download InvisiQ, open a Zoom meeting with yourself, share your screen, and look at the recording. The overlay isn’t there.