A Chrome profile is not a screen-share boundary
Google recommends Chrome profiles for keeping bookmarks, history, passwords, settings, and signed-in accounts separate. That makes the wrong identity easier to spot and reduces account mixing.
It does not hide a window from an entire-display share. If a personal Chrome window appears on the display you are broadcasting, the audience can see it.
Use this simple rule:
- One fixed page: share that Chrome tab.
- One fixed browser workflow: share that Chrome window.
- Several known windows in Zoom: select those exact windows together.
- A demo that moves across apps or browser identities: use a separate audience window and verify it before the call.
Google Meet exposes tab, window, and entire-screen modes. Zoom can share one or more specific applications. Start with those built-in options whenever they cover the job.
Set up browser identities once
- Create one profile per trust context. Use a separate profile for each client, internal work, and personal browsing when the accounts must not mix.
- Give each profile a plain name and color. “Acme work” and “Personal” are easier to verify under pressure than clever labels.
- Keep each profile in its own window. A tab can move between windows; the window is the surface most meeting tools can share.
- Rehearse the path. Open new tabs, follow a link that creates a new window, and switch profiles before the real call.
If the presentation stays in one tab or window, this is enough. You do not need ScreenK9 for a fixed surface.
For multi-app calls, approve the browser identity
macOS sees every Chrome profile as the same application: Google Chrome. An app allowlist can say “show Chrome,” but it cannot by itself say “show Acme work and hide Personal.”
ScreenK9’s Chrome companion makes each profile a local trust decision. Label a profile Work, Personal, or Unclassified. The companion uses Chrome’s documented Native Messaging mechanism to send a small local snapshot to the Mac helper:
- active tab title;
- Chrome window ID;
- tab count;
- timestamp.
It does not send URLs, history, cookies, form values, or page content. ScreenK9 has no product account or cloud sync. Polar handles purchases and license activation.
ScreenK9 excludes Chrome first, then adds back only a fresh, uniquely matched Work window. Personal or Unclassified windows stay hidden; stale or ambiguous states fail closed until ScreenK9 can verify them again.
The match is conservative, not cryptographic identity. Page titles can change, two windows can share a title, and the companion can stop reporting. ScreenK9 responds to uncertainty by showing less.
Run one useful rehearsal
For a client call, watch ScreenK9 — Audience View while you:
- switch from the Work profile to Personal;
- open a second Work window with the same active-tab title;
- disable or pause the companion;
- move from Chrome into every approved non-browser app.
The goal is not an uninterrupted demo at any cost. The goal is for uncertain browser windows to disappear or for the audience view to fall back safely.
When the preview behaves as expected, share ScreenK9 — Audience View in Zoom, Meet, Teams, Loom, or OBS. Do not share the Chrome window or the physical display by mistake: direct display sharing bypasses ScreenK9.
For a wider demo, use the companion guide to share several Mac apps without sharing your desktop. The ScreenK9 privacy model explains the local data and capture boundary.
The practical rule is: separate browser identities, choose the narrowest share mode, and verify the exact audience surface. ScreenK9 is a screen sharing privacy app for Apple silicon Macs running macOS 14+, with a 7-day free trial.
Sources checked
- Google Chrome Help: Manage Chrome with multiple profiles
- Google Meet Help: Present during a video meeting
- Zoom Support: Sharing your screen or desktop
- Chrome for Developers: Native Messaging
Platform documentation and ScreenK9 app behavior were rechecked on August 29, 2026.