Architecture

Stealth sits between the employee’s display and whatever is capturing it. Protected windows are excluded from capture and a frosted stand-in is drawn in their place, all on the device. The employee keeps seeing the real window; Zoom, Teams, Meet, Loom, OBS, and other capture tools record the frost.

A separate path talks to the license and policy service. That path never carries screen contents.

Boundary: screen pixels are never transmitted. Stealth does not read window titles, page contents, or browser addresses. Nothing about what is on screen is stored or uploaded.

Permissions

Permission Why What it can see Leaves the device?
macOS Screen Recording Show the employee their real window while the share receives frost Frames of the protected window, rendered back to the same display in real time — never written to disk No
macOS Input Monitoring (optional) Move the frost before the Dock does on ⌘Tab, Dock clicks and window clicks, so an app switch never flashes to the meeting Modifier-key and mouse-button events only — no keystroke contents No
Windows No permission prompt. Protected windows are excluded from capture with a Windows API Window bounds and process identity No
Network License validation, team policy, updates Email, license key, anonymous device id, policy version Yes — those fields only

Stealth does not ask for Accessibility, Automation, or any other macOS permission. Screen Recording is the one it needs: it is how macOS lets Stealth mirror a protected window back to you while the share receives frost. Those frames stay in memory on the device and are drawn straight back to the screen. macOS 15 re-confirms this grant with a system dialog (“bypass the system private window picker”) after each Stealth update and roughly monthly; that is Apple’s standard cadence for every app that captures the screen, and it is not a new permission.

Network behavior

There is no telemetry about which apps you protect or whether a screen share is in progress.

Data handling

Data Stored? Where
Screen pixels / window titles / message contents / browser addressesNo—
Buyer / member work emailYesLicense KV, Stripe, Resend
License key, anonymous device idYesLicense KV; key also in macOS Keychain / Windows credential store
Team policy (apps, frost settings, locks)YesLicense KV; pushed to enrolled devices
Seat quantity, subscription statusYesStripe + License KV
Billing metadata, invoicesYesStripe
Website analytics (pages, clicks)Yes, anonymized IPGoogle Analytics
Pilot request form fieldsEmail onlySent to support; IP used for short rate-limit

Software supply chain

Subprocessors

Where Stealth fits

Already use data loss prevention (DLP)? Stealth complements your existing security controls by protecting sensitive information that’s accidentally visible during screen sharing and recording. It also works on its own — nothing else to buy or configure first.

What we don’t claim

Stealth is not SOC 2 or HIPAA certified. It is not a DLP suite, CASB, or secure workspace. It does not inspect files, email, USB, or clipboard. Full-display share is protected; sharing a single application window is not. That honesty is deliberate — a security review will find the limit anyway.

Enterprise packet

If you need a security questionnaire, W-9, order form, or DPA discussion, email [email protected]. We will not invent badges we don’t have.

Start with 10 devices

Run the policy on a pilot group before the security review has to cover 500 seats.

Start a 14-day team pilot