The anxious pre-call ritual is familiar: close the personal inbox, scan the tab strip, clear the autocomplete, move Messages away, and hope no notification lands at the wrong moment. It works—until the demo needs a document you did not expect to open.
The underlying problem is not that people are careless. A physical desktop is a private working surface. A screen share temporarily turns it into a broadcast surface, but most operating systems leave the presenter responsible for reconciling those two roles in real time.
The risk is measurable
A 2025 Journal of Cybersecurity study surveyed 214 US-based people who regularly worked from home. Its data category covered accidental exposure of computer data—emails, files, images, and filenames—and personalized browsing data such as autocomplete, open tabs, and ads.
Ninety-one participants had experienced at least one of those two data scenarios. Fifty-four reported feeling somewhat or very uncomfortable. That is why “just check your tabs” is not a complete product strategy: the protective action has to survive ordinary task switching during the call.
Source: Work from home and privacy challenges: what do workers face and what are they doing about it?
Separate the working surface from the broadcast surface
There are three common sharing choices:
| Choice | Convenient | Protects unrelated apps | Supports switching apps |
|---|---|---|---|
| Share one app window | Sometimes | Yes | No |
| Share the physical display | Yes | No | Yes |
| Share a filtered audience window | Yes | Yes | Yes |
The third model is what ScreenK9 uses. Your actual display remains the place where you work. A separate window becomes the only surface the audience should receive.
That distinction changes the safety question. Instead of asking “did I close every private thing?”, you ask “which apps and browser profiles are eligible for this audience?”
Treat each Chrome profile as a separate trust decision
Chrome profiles are useful precisely because they keep accounts, history, bookmarks, and tabs separate. A privacy workflow should preserve that boundary instead of flattening every Chrome window into one application-level choice.
In ScreenK9’s MVP, the Chrome companion is installed in each profile. You label that profile Work, Personal, or Unclassified. Only a fresh, uniquely matched work window can enter the audience view. Personal, unknown, stale, and ambiguous windows remain excluded.
The extension does not need browsing history or page content for this job. It sends the local Mac helper the active tab title, a Chrome window identifier, a tab count, and a timestamp. Matching still has limits, so ambiguity resolves to hidden—not visible.
A repeatable pre-call setup
- Start with an allow-only profile for client calls.
- Select the work apps this audience may see.
- Mark each Chrome profile once in the companion extension.
- Add redaction zones for predictable private areas.
- Start ScreenK9 and check the audience preview.
- In the meeting tool, share ScreenK9 — Audience View, not the physical display.
The last step is non-negotiable. A direct full-display share bypasses ScreenK9 because the meeting tool receives the display from macOS itself.
What “fail closed” looks like in a live call
A protective share surface should prefer a short interruption to an accidental disclosure. ScreenK9 replaces the audience view with a placeholder when capture stops updating or a privacy state cannot be verified.
That can feel conservative. It is also predictable: if the app cannot prove that a frame satisfies the active profile, the frame does not go out.