Prepare a narrow view, test with harmless content, and stop explicitly.
An encrypted conversation can still become visible when you share your screen. The message does not have to be intercepted or decrypted by an attacker: your device has already opened it for you, and a screen-sharing session may send that readable view to someone else.
The practical question is not just “Is this chat encrypted?” It is “Which part of my device am I showing, to whom, and for how long?” Choose the smallest useful sharing area, prepare it, and check what the other person actually receives. These are general precautions, not a claim that Livara provides a particular screen-sharing feature.
1. Choose a tab or window before the whole display
Sharing options differ. A browser tab, one application window and an entire display are not interchangeable. Google Meet documents all three choices on computers. Signal Desktop documents sharing a screen or a separate window during a call. Look at the actual picker rather than assuming every app offers the same controls.
For one document, prefer a narrow option when available. A shared browser window can still reveal another tab if you switch within that window. A selected messaging app can reveal another conversation you open inside it. Narrowing the area reduces accidental exposure; it does not make everything inside that area safe.
If a demonstration genuinely requires the whole display, close unrelated windows first. Check desktop filenames, recent-document lists and the material you intend to open. A clean sample is often more useful than demonstrating with real private messages.
2. Do not assume notifications behave the same everywhere
Some sharing modes deliberately exclude notifications. Android's MediaProjection documentation says its app-window sharing, introduced in Android 14, excludes notifications and other system interface elements. That describes app-only capture, not every full-display session on every phone.
Apple likewise says incoming notifications are not visible to the other person during FaceTime screen sharing. Microsoft’s Teams mobile guidance, by contrast, warns that sharing the entire screen includes notifications and other activity.
Those differences matter more than a blanket rule such as “screen sharing always exposes notifications” or “notifications are always hidden.” Check your app, operating system and selected mode. Even when banners are excluded, opening the message itself within the shared area can expose its contents.
Do Not Disturb can help, but inspect its exceptions and visual settings. Pixel documentation allows exceptions for people and apps and notes that critical system notifications can still appear. A silenced alert is not necessarily proof that nothing can be shown.
3. Prepare a small, harmless demonstration
Before starting, use this short checklist:
- Open only the document, page or sample conversation needed for the task.
- Replace real names, account details and private messages with harmless examples where possible.
- Close unrelated chats, email, password managers and recovery information.
- Review notification previews and interruption settings, including allowed exceptions.
- Inspect the selected sharing area and identify the control that stops it.
- Check microphone and shared-audio settings separately from the picture.
Audio deserves its own decision. Depending on the service, browser and operating system, the chooser may offer tab or system audio. Read the actual toggle; do not enable it merely because you need to show a document. Unneeded audio can disclose material that is not visible in the selected picture.
Preparation does not mean disabling security protections or granting broader permissions to make a demonstration work. If an app blocks capture of sensitive content, use a sanitized explanation instead of trying to defeat that restriction.
4. Test the receiver's view, not just your preview
For an unfamiliar setup, rehearse with a trusted participant and nonsensitive material. Ask which window they can see. Move between harmless windows or tabs and confirm whether the view follows. If notification behavior matters, test with a deliberately bland message rather than waiting for a private one to arrive.
Check sound independently: can the other person hear your microphone, the shared application's audio, both or neither? Then stop sharing and confirm that the other person no longer receives live updates.
This rehearsal is a practical check of that setup, not a permanent security guarantee. An application update, a different sharing choice or a different device may change the result. Repeat the useful parts when the configuration changes.
5. Screen viewing and remote control are different permissions
Showing your screen does not automatically mean giving someone control. Read any additional request carefully. In FaceTime, for example, a viewer can request remote control, and you can allow or decline it. Apple documents that an allowed controller can perform actions such as opening apps, changing settings, deleting items and sending messages.
A pointer, drawing or annotation is not by itself evidence that control has been granted. Conversely, do not approve control just because someone already sees the screen. A demonstration may require viewing only.
Keep genuine passwords, recovery phrases and one-time codes out of the demonstration. If unexpected instructions ask you to expose secrets or grant access, stop and verify the person's identity and purpose through a channel you already trust.
6. Stop before opening something private
During the session, treat the shared area as visible to the participants. Stop sharing before switching to an unrelated private task, rather than relying on a quick window change. Check the app's sharing indicator and the receiver's view when practical.
Do not assume that muting the microphone, hiding your camera or minimizing the call has stopped the shared picture. Use the specific stop-sharing control. Apple documents that ending a FaceTime call ends sharing, but that is not a reason to assume identical behavior in every service.
Stopping limits further exposure. It cannot retract information already read, noted, photographed or recorded. The related guide on encrypted chats and screenshots explains why encryption does not give you control over another person's copies.
7. If you accidentally show private information
Stop sharing first. Work out what was visible, for how long and to which participants; do not assume that your entire device was exposed. If appropriate, ask the recipient not to retain or redistribute the material, while recognizing that you cannot verify deletion of every copy.
For an exposed reusable password or recovery secret, use the relevant service's official security controls to replace or revoke it where supported. If someone had remote control, separately review actions they could have taken; mere viewing and interactive access are different incidents.
The lasting habit is simple: prepare a narrow view, test with harmless content, and stop explicitly. Encryption remains valuable, but it cannot make a readable screen private from the people you choose to show it to.
