How OS-level capture exclusion works
On macOS, Lexora sets the overlay window's sharing type to NSWindowSharingNone. Any process that asks the window server for the contents of your screen — Zoom, QuickTime, a screenshot, a recording tool — receives frames composited without that window in them.
On Windows, the equivalent is SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE. The desktop compositor excludes the window from the duplication API that every screen-sharing tool is built on.
This is the same mechanism banking apps and DRM-protected video players use to keep their content out of screenshots. It is a first-class operating-system feature, not a workaround, which is why it does not break when the meeting app updates.
What it covers
Screen sharing in Zoom, Google Meet, Microsoft Teams, Webex and browser-based assessment platforms. Screen recording, whether by the meeting platform or a local recorder. Screenshots, including OS-native capture tools.
It covers full-desktop sharing as well as single-window sharing, because the exclusion happens below the level where that choice is made.
The honest limits
Capture exclusion protects against anything that goes through the screen-capture pipeline. It does not make you invisible to a camera pointed at your monitor, and it does not change where your eyes go.
That second point is the real one. A tool that puts the answer in a panel you have to read line by line will give you away through your eyeline no matter how invisible the window is. Lexora's answers are bullet-first and deliberately short, so a glance is enough — which is why the latency target and the invisibility work together rather than separately.
We verify capture exclusion at runtime and show you the status in the app. If the platform ever reports that it could not apply the protection, you will know before the call, not after.