Screen Privacy During Client Meetings

You are presenting a quarterly review to a client over Zoom. The deck is good. You alt-tab to demo a feature, and as your screen transitions, Slack notifies you that "Sarah from $OTHER_CLIENT is asking about renewal pricing" in the corner of the screen. Your client just read it. The renewal is now a different conversation than it was thirty seconds ago.

Client meetings are a strange privacy category. The threat is not a stranger behind you. It is the act of sharing your screen with the person who has the most reason to notice everything on it.

Why client meetings are uniquely risky

Most screen privacy advice is about people behind you. Client meetings invert that. You are voluntarily showing them your screen. Your defense is no longer "make my screen harder to see," it is "make my screen safer to share."

Notifications are the biggest leak. Slack, email, messages, calendar alerts. Every notification banner shows up in the share. The client sees who else is messaging you, what they are asking about, what your team is saying in real time. One badly timed notification can change the deal.

Open tabs are the second leak. You demo something, then close it, and the row of browser tabs becomes visible. Tab titles tell stories: another client's name, a competitor's pricing page, a job board, an unrelated draft document. The client reads the row in two seconds and forms an impression you did not intend.

In-person client meetings have an extra layer. The client sits across the conference table or beside you at a laptop. They see not just what you are sharing on the projector but everything else on your screen: dock items, menu bar icons, the wallpaper that hints at your weekend. Even your file system reveals more than you think when you save or open a file. Background reading: shoulder surfing at work.

What clients actually see

Client A sees Client B's name in a Slack notification. A small leak, but enough to know they are not your only customer (which they knew) and to know that Client B is currently active (which they did not need to know).

They see browser history if you type a URL and autocomplete fires. They see folder names in Finder. They see filenames in your recent documents when you go to attach something. They notice the email subject line at the top of your inbox if you switch apps.

Clients in meetings are paying close attention. Closer than at any other moment. They are listening to every word and reading every pixel. Treat your laptop as a public document for the next forty minutes.

Specific defenses for client meetings

Client meetings reward preparation more than reaction:

• macOS Do Not Disturb on. Five minutes before the meeting, turn it on. Notifications hidden, no banners during the share.
• Close every non-essential app. Slack, mail, messages, browsers with other tabs. Quit them, do not just minimize.
• One browser window with one tab. The tab you need for the demo. Nothing else.
• Use presentation mode in Keynote or PowerPoint. It blocks the system from showing notifications and hides the menu bar.
• Mirror display only when sharing in-person. Use the second display feature so your laptop screen and the projector show the same thing, and your laptop is not showing a different desktop with notifications.
• Sign out of personal accounts. Personal email, personal calendar, personal browser. Use a work profile or work browser.
• Test the share five minutes early. Open the call alone, click "share screen," and look at what is visible. Adjust before the client joins.

Where camera-based detection fits

This is the scenario where Peeker is least directly relevant. The threat in a client meeting is not behind you. It is in front of you, on the other side of the screen share. Camera-based shoulder surfing detection does not help with notifications popping during a Zoom call.

That said, in-person client meetings in your office can have a Peeker use case. If the client is sitting beside you at your desk reviewing a proposal, and a colleague walks past with sensitive context ("Hey, did you see the email from Big Client?"), the camera does not help. But if you step away for two minutes to grab a coffee and leave the laptop open, Peeker shows you who came near it while you were gone.

The main client-meeting defense is software discipline, not detection.

FAQ

What if I have to alt-tab during a demo?

Plan the alt-tab. Know what window you are switching to. Make sure that window is also clean. If you have to look at a calendar, use a fresh calendar tab, not your full inbox.

Can I use a separate user account for client work?

Yes, and many consultants do. A "client work" user on macOS with only the apps you need, no personal accounts, no browser history. Switch users before the meeting. Effective, slightly clunky.

What about the chat sidebar in Zoom or Teams?

Other meeting attendees may DM you during the call. Their messages appear in the chat panel. If you are sharing your full screen, the chat is visible. Either share a single window only, or close the chat panel.

Wrap

Client meetings are about preparation and a clean screen, not about detecting peekers. Turn on DND, close everything, test before they join. For the rest of the office hours, Peeker is the second layer for when you are working alone and the room is not yours.