Private screen sharing checklist for client calls on Mac

Plan the handoffs before presentation day

Before the call, decide which windows or tabs you will present, where your notes stay and who presents each section. Rehearse the exact change from slides to a dashboard. Sharing one window does not automatically start sharing a different app when you switch focus.

Shortly before joining, prepare sample content, verify the sharing permissions and watch a test from another device. If another participant takes over, agree on the stop-and-start sequence. During an unexpected private lookup, stop or cover the actual shared source first, then choose the public source deliberately before resuming.

• Keep presenter notes separate
• Arrange Zoom participant sharing

Your client-call checklist

A client asks you to show a document, portal or draft. The useful window is ready, but the same Mac also has another client's notes, messages, email and calendar open. For therapists and consultants, a stray window can cross client boundaries: another client's name in a title, session notes in a recent-files menu or appointment details in a calendar preview.

The goal is not to promise perfect secrecy. It is to make the predictable surfaces part of the setup before anyone else can see the screen. This is screen-sharing hygiene, not legal or compliance advice; no screen-sharing utility makes a call, practice or workflow compliant by itself.

Start with the smallest useful sharing boundary

If the client only needs one document, share that document's window. If they only need one web page, use tab sharing when the meeting tool offers it. A smaller boundary reduces what can appear by accident and is usually simpler than adding another tool.

The tradeoff arrives when the conversation moves. A consultant may need to switch from a proposal to a spreadsheet and then a browser. A therapist may need prepared educational material while scheduling or notes stay available privately. Stopping and restarting the share for every switch is safe but disruptive. Sharing the entire display is easier, but every visible app becomes part of the audience view.

Prepare sensitive material before client calls

Private screen sharing starts inside the app you intend to show. ScreenVeil cannot hide one paragraph, one patient or customer name, or one browser tab while the rest of that same app remains public.

Use fictional or redacted records for a demonstration whenever possible. Close unrelated documents and check recent-file menus for client names. Put private browser tabs in a separate window and select it under Hide a window, or use a separate browser marked private. A browser profile can separate accounts and history, but does not automatically exclude a window.

Check the desktop, Dock, window and tab titles, bookmarks bar, autofill suggestions, recent documents, calendar previews and file picker. Those small surfaces are easy to miss because they are not the main document.

Quiet notifications without confusing silence with hiding

Apple's Focus controls can reduce interruptions. Open Control Center on the Mac, choose Focus and turn on the mode you want. Review its allowed people, allowed apps and schedule before relying on it; a Focus can be configured to let selected notifications through.

Focus does not hide an email window, a Messages conversation already on screen, a browser tab title or a client name in a document. ScreenVeil leaves macOS notification banners out of Privacy Screen by default, as documented for the tested macOS 26.1 setup. App-drawn pop-ups and notification sounds need separate checks.

• Apple: Turn a Focus on or off on Mac
• How ScreenVeil differs from Muzzle's notification control

Pick the right sharing source for client calls on Mac

The labels change as meeting apps update, but the decision is the same: choose a window rather than the full screen when you want a narrow boundary. In Zoom, select the prepared app window or Privacy Screen rather than Desktop. In Google Meet, choose Present now, then A window. In Microsoft Teams, choose the relevant window rather than Screen when one app is enough.

Apple requires separate Screen & System Audio Recording permission for apps that record your screen and audio. Giving permission to ScreenVeil does not automatically give it to Zoom or your browser, and vice versa. Review access in System Settings → Privacy & Security → Screen & System Audio Recording.

Do not infer safety from a picker thumbnail. After selecting the source, verify the live audience view.

• Apple: Control access to screen and system audio recording
• Zoom: Sharing your screen or desktop
• Google Meet: Present during a video meeting
• Microsoft Teams: Present content in meetings

When ScreenVeil helps—and what it does not promise

ScreenVeil is useful when one-window sharing is too restrictive. In Privacy Screen mode, it uses Apple's ScreenCaptureKit on your Mac to create a separate window that leaves out apps and windows you marked private. You share that Privacy Screen window in Zoom, Meet, Teams, Loom or OBS. Your private apps remain open on your Mac.

ScreenVeil does not filter a desktop share, stop another recorder, filter sound, identify sensitive text or hide one tab inside a window you are showing. It cannot verify which source you selected in the meeting app. Test again after macOS or meeting-app updates, or after changing displays.

That boundary matters for professional client work: ScreenVeil can reduce accidental exposure in the feed you choose to share, but it does not replace access controls, consent, record-handling policies or your organization's security and compliance process.

Verify the client's view before every session

Run the test with sample content, never with the sensitive material you are trying to protect. A frozen but apparently clean preview is not a successful test. The audience view must stay private and keep updating.

If you use a saved meeting profile, load it before this check and confirm its private-app list. A profile saves choices; it does not prove that the meeting app selected Privacy Screen. Practice ⌘⇧B with sample content so you can cover the feed without searching for a control.

1. 1

   Start the real tool

   Use the same meeting or recording app and the same display arrangement you will use for the call.

2. 2

   Select the source

   Choose the prepared window or Privacy Screen. Read the source name before confirming.

3. 3

   Watch from outside

   Join from a second device, or make a short test recording and play it back.

4. 4

   Exercise the workflow

   Edit or scroll the public document, open a private app, switch public apps, press ⌘⇧B to cover the feed, then resume.

5. 5

   Confirm privacy and motion

   The private app should never appear, and the public feed should keep updating through every switch.

6. 6

   Stop in the right order

   Stop sharing in the meeting app before stopping ScreenVeil or changing the protected-app list.

Use the simplest setup that fits the call

For one document, share one prepared window. For one web page, share a tab. Add ScreenVeil when you need to move between public apps while Slack, Mail, Messages, notes or another private app remains usable on your Mac.

Run the verification steps with sample content before relying on the setup in a real client session. The point is a repeatable boundary you have actually seen from the client's side—not a privacy claim you have to take on faith.

• Complete Mac app-hiding setup
• Current meeting-app compatibility notes
• Why ScreenVeil does not claim to block every recorder
• Download ScreenVeil and test with sample content