Screen-share privacy for sales engineers

What should stay private during a sales demo?

Keep other customers’ information, internal deal notes and personal messages outside the shared source. A demo account can still expose private information through its account switcher, search history, browser bookmarks or a connected real inbox.

Decide which requests you can demonstrate in that account before the meeting. If a customer asks to see an admin screen containing real users or billing details, stop sharing while you prepare a safe example. Keeping a second window ready is useful only if its contents are also safe.

A fictional demo rehearsal

This is a rehearsal scenario, not a customer case study. Create an Example Company demo account with a Sample Launch project, a few fictional tasks and a slide explaining the workflow. In a separate notes app, write SAMPLE INTERNAL NOTES so a leak is easy to identify without exposing real information.

Run the sequence you expect to present: slides, the project board, a settings page and back to the slides. Open the search box and the account menu. These controls often display content that is absent from the main page, so inspect them as part of the demo.

Then rehearse an off-script request: “Can you show how another team would configure this?” If answering would require switching to a real customer’s account, practice stopping the share and preparing a fictional example. Screen filtering cannot decide which records a customer is allowed to see inside an otherwise shared app.

Which screen-sharing source should you choose?

Choose the smallest source that contains the demo. A single browser window may be sufficient for a product walkthrough; you do not need a multi-app sharing setup for every call.

When the walkthrough spans slides, a browser and another app, start ScreenVeil, mark the internal apps private, and select the window named Privacy Screen in the meeting app. Your private apps remain usable locally. Sharing the entire display instead bypasses this filtered output.

You can also exclude one whole window through Hide a window or Settings → Sharing → Specific windows. Those choices reset when Privacy Screen stops. A window exclusion cannot hide one tab or a paragraph inside a window you continue to share. Move private browser work to a separate window or browser and verify the resulting feed.

If Privacy Screen is missing from the meeting picker, use Show Privacy Screen and inspect the picker again. Do not substitute a desktop share just to get the call moving.

• Check the supported sharing setup
• Separate private browser tabs

Before the customer joins

ScreenVeil excludes Notification Center banners by default in the tested macOS 26.1 setup, but an app can draw its own popup. Review a Focus mode’s allowed people and apps too. Visual filtering does not silence the microphone, meeting audio or notification sounds.

If another presenter takes over, agree on who stops and starts sharing. A privacy setting on your Mac does not change their source.

• Review Focus exceptions on Mac

What if something private appears mid-demo?

Stop sharing in the meeting app if you cannot confirm the audience view. Cover feed, using the default ⌘⇧B shortcut, covers ScreenVeil’s output while you fix a problem, but it only helps when Privacy Screen is the source being shared.

After changing accounts, displays or the sharing source, check the receiver view again before continuing. Neither covering the feed nor stopping the share removes frames already delivered to the meeting or its recording.