No. While a call is running, the Windows client holds three things and no more: the one capture source you picked in the share dialog, your microphone while the audio device is open, and your camera while video is on. Files, other windows, the clipboard and browser history sit outside that set, and the host panel has no control that asks for them. Two of those three streams leave a timestamped trail in Windows Settings, so you can check the answer on your own machine in about three minutes instead of believing anybody, including us.
The three streams the Windows client is actually holding
It helps to stop thinking of Zoom as a thing that has access to a computer, and start thinking of it as a thing fed by three taps. Each tap has a switch, each switch is yours, and each one has a visible tell.
1. The capture source you picked, and only that one
Nothing is captured until you click Share Screen, select a tile and confirm. The dialog builds its grid of thumbnails locally so you have something to choose from, and browsing that grid transmits nothing. Once you confirm, the client encodes that single source: one window, or one display, or one browser tab. Pick a window and the viewer sees that window's frames even while you work in another app. Pick Entire Screen and you have picked a display, taskbar, tray icons, notification toasts and all. Multiple monitors appear as separate tiles, so a second display is in the call only if you chose it. A green border marks whichever source is live, and Stop Share ends the capture on the spot.
2. Your microphone, which stays open even while you are muted
This is the part that surprises people. Zoom's mute button is a client control, not an operating system one. The client keeps the microphone device open while you are muted, which is precisely why it can raise the prompt telling you that you are speaking while muted. It is still reading the input locally in order to notice. Zoom states that muted audio is not transmitted, and that claim is about the network rather than about the device. What you can verify on your own machine is the narrower fact that the device stays open, which is why the Windows microphone indicator stays lit through a mute. If you want the mic genuinely off rather than muted, disable the device in Windows sound settings or unplug it.
3. Your camera, only while video is on
Camera capture tracks the Start Video and Stop Video control far more literally. Stop Video releases the camera, and on most laptops the hardware light on the bezel goes out within a second. That light is wired closely to the sensor on many machines, which makes it the cheapest privacy check you own.
Around those three streams sits a thin layer of ordinary meeting data: your display name, join and leave times, mute and video state, reactions, the chat you type, and any file you deliberately attach to chat. On paid accounts an account administrator also sees dashboards with client version, operating system and connection quality. That is telemetry about the Zoom client itself, and your interviewer is not sitting in an admin console during your call.
One checkbox deserves its own sentence, because it is the most commonly missed leak in the whole product. The share dialog carries a Share sound option. Tick it and system playback audio is mixed into the share, so a notification chime, a video playing in another tab, or a voice from a different app travels along with the picture. Leave it unticked and only your microphone carries audio. Look at that checkbox before you press Share, every time.
Verify all three in Windows Settings, about three minutes
Open the permission pages
Press Windows plus I. On Windows 11 go to Privacy and security, then App permissions, then Camera. On Windows 10 the path is Privacy, then Camera. Scroll past the Store apps list to the section for desktop apps. Classic installers such as the Zoom client live in that lower list.
Read the Last accessed timestamps
Each recently active desktop app carries a Last accessed line with a date and a time. That is a log, not a guess. Note what it says for Zoom right now, before you start anything, then do the same on the Microphone page.
Start a meeting with yourself and toggle the two devices
Open a test meeting on the PC and join from your phone as a second participant, both muted to avoid feedback. Turn video on for ten seconds, then off. Unmute for ten seconds, then mute. Go back to the two Settings pages and reload them. Only the taps you opened moved their timestamps.
Watch the taskbar indicator through a mute
Windows 11 shows a small camera or microphone glyph near the clock while a device is in use, and hovering names the app. Mute yourself in Zoom and watch it. Stopping video clears the camera glyph, while mute usually leaves the microphone glyph lit, which is the open device described above, visible in the tray.
Test the share tap against your phone
Windows has no per app screen recording permission list for classic desktop apps the way macOS does, so this check is behavioural rather than in Settings. Share one window, then Alt Tab away: the phone keeps showing the shared window and never sees the app you switched to. Press Escape in the share dialog without picking anything: nothing reaches the phone at all. Then share Entire Screen and watch the taskbar, the toasts and the Alt Tab strip arrive.
A caveat on that last step, because guessing is worse than admitting. Recent Windows 11 builds have added screenshot related entries under App permissions that apply to packaged apps using the newer capture interfaces. If your build shows one and lists Zoom, read it. If it does not list Zoom, that is normal for a classic desktop installer and tells you nothing bad. The green border and a second device remain the honest test.
Line by line: in the call, or not
| In the call? | How you confirm it yourself | |
|---|---|---|
| One window you shared | Yes, that window's frames | Second device shows it while you work elsewhere. |
| Entire Screen you shared | Yes, everything visible on that display | Second device shows your taskbar and your toasts. |
| A display you did not pick | No | Drag a window there and it leaves the shared frame. |
| Microphone | Yes while unmuted, device stays open while muted | Last accessed timestamp plus the tray glyph. |
| Camera | Yes while video is on | Bezel light, and the Camera permission page. |
| Audio from your other apps | Only if Share sound is ticked | Play music and ask the second device if it hears it. |
| Files, folders, browser history | No | No host control requests them and nothing carries them. |
| Clipboard | No, unless you paste into Zoom yourself | Copy some text and watch nothing happen anywhere. |
| Keystrokes outside Zoom | No | Type in Notepad during a window share and watch. |
| Remote control of your PC | Only after you approve a request | A visible request, then a banner the whole time. |
| A recording of the call | Yes if the host records | Recording indicator, plus a spoken or written notice. |
The cases where the answer genuinely changes
Four situations move the line, and not one of them is a hidden feature of an ordinary meeting.
- You approve remote control. During a share, another participant can request control of your mouse and keyboard. It takes your click, and a banner sits on screen the whole time it is active. Decline it if you were not expecting it.
- The host records. A recording captures what was already in the meeting, meaning your camera, your audio and your share. It does not widen the three taps, it keeps a copy of them.
- A separate proctoring client. If an employer asks you to install software before a timed assessment, that software commonly does inventory running applications, and it often refuses to start until you close things. Its consent screen says so. That, and not the meeting app, is the accurate description of what is watching you.
- A company issued or enrolled laptop. A management agent reports installed and running software as routine, call or no call. That situation predates the interview entirely.
Where our own tool is the wrong answer
People often reach this question while weighing an assistant that runs beside a call, so here is our boundary drawn plainly rather than favourably. The OfferPilot AI overlay is excluded from screen capture at the operating system level, so it does not appear in a Zoom share, in Teams, Meet or OBS, or in screenshots, while staying visible on your own monitor. That holds on every plan, including the free tier.
Now the limits. Capture exclusion is about frames. It hides nothing from a webcam, and your face and your eye movement are visible to anyone watching video. It does nothing about a lockdown browser, a proctoring client that enumerates processes, a person in the room, eye tracking, or a phone camera pointed at your desk. It is Windows 10 and 11 only, so a Mac or a Chromebook is out of scope entirely. And on a monitored assessment where you were told to install a proctoring client, it is the wrong tool, which we would rather say than take the subscription. If you want to test the capture behaviour yourself before deciding anything, the free tier on the pricing page gives five minutes a day and asks for no card.
The short version
- Three taps, all yours. One chosen capture source, the microphone, the camera. Nothing else is in the meeting.
- Two of them are logged by Windows. Camera and Microphone under Privacy and security carry a Last accessed timestamp for desktop apps.
- Mute is a client control. The device stays open, which is how Zoom knows to tell you that you are muted.
- Entire Screen is the real exposure. Not a hidden capability, just a tile people click without thinking.
- Check the Share sound box. It is the difference between sending your voice and sending everything your speakers would have played.
Run the three minute check once and the question stops being a worry. It becomes a fact about your own machine, with timestamps to back it.