Mac screen sharing privacy checklist: what can leak?

The short answer: choose the smallest useful window or tab, clear private clipboard history, close unrelated apps, decide whether the meeting should transmit computer audio, and run a private test in the same app. Treat the visible share and the transmitted audio as separate paths. A clean desktop does not prove the audio path is safe.

Disclosure: I build TeenyApps, including TeenyClip for local clipboard history and TeenySound for per-app volume. My bias is toward small native utilities. The checklist still starts with macOS and the meeting app, because those own the share, permission, and output paths.

This is different from a general meeting privacy checklist. It answers one narrower question: what can appear or be heard when you share or record a Mac screen?

Start with the two exposure paths

01Share the smallest useful surface

Start by choosing the surface. A whole display is convenient, but it also exposes notifications, menu bar status, background windows, and the moment you switch apps to find something. A single window or browser tab is usually safer if the meeting app supports it.

Apple's screen sharing controls and Screen and System Audio Recording permission are separate ideas. Screen sharing lets another person or app see the screen. The privacy permission list controls which apps and websites can record the screen and audio. Check both when a call app, recorder, browser, or support tool has not been used in a while.

If the share is a live workshop rather than a quick review, use the more detailed Mac live workshop checklist for clipboard and audio. It covers teaching flow, copied commands, app audio, and the final dry run. This checklist is the shorter privacy pass before the share starts.

02Clean clipboard history before opening it on screen

On macOS Tahoe 26, Spotlight can show clipboard history if the feature is enabled. Apple says to open Spotlight with Command-Space, choose Clipboard or press Command-4, then use More and Clear History when you need to remove it. Apple also warns that sensitive information may appear there.

A separate clipboard manager can add another history surface. Clearing Spotlight history does not establish that a third-party manager is empty, and clearing the manager does not establish that Spotlight is empty. Review each one privately. On older macOS versions without Spotlight clipboard history, still replace the current clipboard item with harmless text before the share.

TeenyClip is built for local clipboard history. Its homepage says it keeps searchable history for text, images, files, and URLs, supports pins, opens with Option-Shift-V by default, and stores clipboard history locally. The local Swift source confirms pasteboard polling, pinned items, history limits, auto-clear settings, excluded apps, duplicate merging, and a grace period around sensitive apps.

My rule is simple: before sharing, open the history privately. Keep only public commands, public docs, fake sample data, reusable safe snippets, and source links you want the audience to see. Remove the rest. If you often copy from password managers, finance tools, production dashboards, support consoles, or customer records, exclude those apps instead of relying on memory.

03Search copied links as well as text

People clean obvious passwords and forget URLs. URLs can carry private workspace slugs, document IDs, invite tokens, branch names, customer names, staging domains, and internal route names. They are easy to show because they look harmless until somebody reads them closely.

Search clipboard history for your company domain, customer names, "token", "invite", "admin", "staging", private repo hosts, and the meeting client's name. If you would not paste the URL into a public chat, do not leave it visible in a screen-shareable history list.

For the focused cleanup pass, read Mac clipboard history before screen sharing. For the privacy model behind exclusions and history limits, read Clipboard manager privacy on Mac.

04Set output and app audio before sharing

Separate local output from transmitted audio. Apple's Sound settings choose the output device, output level, alert volume, input device, and input level. Those settings shape what you hear. The meeting app's share-audio switch determines whether computer audio enters the remote session.

Then check the app layer. TeenySound is a local per-app mixer for that job. Its homepage says it shows every audio-producing app with its own slider, supports app mute, mute-all with restore, per-app output routing, device-specific volume memory, and customizable shortcuts. The local Swift source confirms Core Audio process discovery, volume clamping, mute state by bundle ID, restore-all behavior, output-device routing, per-device volume storage, and the macOS 14.2 requirement for the tap path.

Current controls differ by meeting app. Zoom exposes a Share sound checkbox. Google Meet shares tab audio by default when you present a tab and offers Also share system audio for a window or the entire screen. Teams desktop uses Include sound and warns that computer audio includes notifications; Teams on the web varies the audio scope with the selected tab, window, or entire screen.

Use the smallest audio setup that works. If nobody needs computer audio, leave the meeting app's audio-sharing control off. If the audience needs one source, make that source audible and mute the rest locally, then confirm the transmitted result with another device or participant. TeenySound changes the local app mix; it does not turn Zoom, Meet, or Teams audio sharing on. For the focused pass, read Mac app audio before screen sharing.

05Check Screen and System Audio Recording access

Apple's current privacy controls let you decide which apps and websites may record the screen and audio. An app can be allowed to record both or audio only. Permission authorizes capture; it does not choose the window you share or switch computer audio into a meeting.

This permission can be easy to over-approve. A browser used for calls may need it. A screen recorder may need it. A support tool may need it for remote sessions. A random utility should not get it just because a prompt appeared during setup.

TeenySound is a useful example of why wording matters. Its current code requests the narrower System Audio Recording Only permission for Core Audio taps rather than screen capture. The app needs access to outgoing app audio for per-app volume adjustment. Its homepage says the audio is adjusted locally and is not recorded to disk or sent elsewhere.

06Run one private share test

Run the test in the same app you will use live. If you will share in Zoom, test in Zoom. If you will record with Screenshot, test with Screenshot. If you will share a browser tab, test that tab, that profile, and that audio behavior.

The dry run should prove five things: the right window is visible, private clipboard history is not visible, copied links are safe, only intended audio reaches the remote listener, and the app has the permission it needs. Listening through the same Mac proves local output, not the transmitted stream.

After the share, reset the temporary state. Clear throwaway clips, unpin one-time snippets, restore app audio, turn alerts back to your normal level, and close any private windows you opened during the session. A short reset keeps tomorrow's screen share from inheriting today's workaround.

Five-minute pre-share pass

1. Choose the exact display, window, or browser tab to share.
2. Close apps and tabs that do not belong in the session.
3. Open clipboard history privately and remove private temporary clips.
4. Search copied links for customer names, tokens, private repos, and admin URLs.
5. Set macOS output and alert volume, then play the exact source app once.
6. Mute unrelated apps or use a per-app mixer if one source needs to stay audible.
7. Check Screen and System Audio Recording access for the app doing the share.
8. Run one private test with the same app, same window, same audio source, and same copy sequence.

Common questions

What should I check before sharing my Mac screen?

Choose the smallest useful share surface, clear private clipboard history, close unrelated apps, decide whether the meeting should transmit computer audio, verify recording permission, and run one private test in the same app.

Can clipboard history leak during screen sharing?

Yes. On macOS Tahoe 26, Spotlight can show clipboard history if it is enabled. A separate clipboard manager can keep its own history too. Review and clear both privately before opening either panel on a shared screen.

Should I share system audio from my Mac?

Only when the audience needs it. The meeting app controls whether computer audio is transmitted, while Mac output and per-app volume control what you hear locally. Check both paths with a remote listener.

Sources checked

• TeenyClip facts were checked against the TeenyClip homepage and local Swift source for clipboard capture, text/image/file/URL history, pins, search, history limits, auto-clear, excluded apps, duplicate handling, and local storage claims.
• TeenySound facts were checked against the TeenySound homepage and local Swift source for per-app sliders, app mute, mute-all restore, output routing, device volume memory, shortcuts, Core Audio taps, permission handling, and macOS 14.2 requirements.
• Apple Support: Search your clipboard history on Mac.
• Apple Support: Control access to screen and system audio recording on Mac.
• Apple Support: Turn Mac screen sharing on or off.
• Apple Support: Copy and paste between your Mac and other Apple devices.
• Apple Support: Change Sound settings on Mac.
• Apple Support: Change the sound output settings on Mac.
• Zoom Support: Sharing computer sound in a screen share.
• Google Meet Help: Present during a video meeting.
• Microsoft Support: Share sound from your computer in Teams.