Do AI notetakers work in end-to-end encrypted meetings?
Mostly no, with one exception that matters. End-to-end encryption means the platform's servers relay the call without being able to decrypt it, so every feature that needs the server to hear the meeting switches off: the built-in AI (Zoom AI Companion, Teams Copilot, Meet's Gemini notes, Webex AI Assistant), cloud recording, and cloud transcription. Meeting bots often can't join, because E2EE modes restrict which kinds of client may connect, and a bot that is admitted gets the keys like any participant and uploads the decrypted call to its vendor. The exception is capture on your own computer. A tool listening to your system audio still works, because the call has to be decrypted for you to hear it. That calls for more care, not less. E2EE is usually switched on because a conversation is sensitive, and a cloud notetaker on your device carries the words outside the boundary everyone in the call was promised. Ask the host first, or use fully on-device transcription.
Last updated September 22, 2026
Mostly no. The one kind that does work is the kind that deserves the most thought. End-to-end encryption decides who can hear a call while it travels between devices. It has nothing to say about what a participant’s device does once the call arrives. With that in mind, every notetaker falls into place. The ones that listen from a server stop working. The ones that join as a participant are mostly turned away at the door. The ones that listen on your own computer carry on exactly as before, because the audio has to be decrypted for you to hear it.
What end-to-end encryption actually changes
Almost every meeting is encrypted. Very few are end-to-end encrypted, and the difference is who holds the keys.
- Default encryption is what Zoom, Teams, Google Meet and Webex use unless someone changes it. It protects the call in transit, but the platform manages the keys. The platform’s servers can decrypt the media, and that’s what lets them record it to the cloud, caption it, transcribe it, and pass it to a built-in AI.
- End-to-end encryption (E2EE) moves the keys to the participants’ devices. The platform’s servers still relay the call, but what passes through them is ciphertext they can’t read. Nothing on the server side can listen.
That’s the trade E2EE makes, and the platforms are open about it. At the time of writing:
- Zoom: E2EE is an option the host turns on per meeting. The default is Zoom’s standard “enhanced” encryption, where Zoom manages the keys. With E2EE on, cloud recording and live transcription switch off, and participants have to join from Zoom’s own desktop or mobile apps rather than the web client or a phone line.
- Teams: Microsoft offers E2EE for one-to-one calls and, on Teams Premium, for meetings. Recording, live captions and transcription are unavailable in both.
- Google Meet and Webex: Meet’s client-side encryption (on some Workspace editions) and Webex’s end-to-end encrypted meetings make the same exchange.
Feature lists change between releases, so check your platform’s current documentation. The overall pattern can’t change, because it follows from what E2EE is.
E2EE is also almost always something somebody chose. It’s off by default on the major platforms, and it costs features. Hosts and administrators switch it on for a reason: a board meeting, a legal or HR matter, a patient, a deal. If you find yourself in one, that tells you something about the conversation.
What happens to each kind of notetaker
The four ways AI notetakers capture a call split cleanly under E2EE, by where each one does its listening:
| How it captures | Where it hears the call | In an E2EE meeting | Where the words end up |
|---|---|---|---|
| Platform-native AI (Zoom AI Companion, Teams Copilot and recap, Meet’s Gemini notes, Webex AI Assistant) | On the platform’s servers | Off. The server can’t summarize audio it can’t decrypt | Nowhere; the feature isn’t available |
| Cloud recording, captions and transcription | On the platform’s servers | Off, for the same reason | Nowhere |
| Meeting bot (Otter, Fireflies, Fathom, tl;dv) | As a participant, running in the vendor’s cloud | Often can’t join, because E2EE modes restrict which clients may connect. If admitted, it gets the keys like anyone else | Decrypted and uploaded to the vendor |
| Caption-scraping extension (Tactiq) | Reads the platform’s captions in your browser tab | Usually nothing to read. Captions generated in the cloud switch off, and some E2EE modes exclude the web client | Nowhere |
| Bot-free desktop app with cloud processing (Canary, Granola) | Your computer’s system audio, after decryption | Works, technically | Streamed to the vendor’s speech-to-text and language-model providers |
| Fully local transcription (a local Whisper model, OS on-device captions) | Your computer, after decryption | Works | Stays on your device |
Three things in that table are worth drawing out.
The platform’s own AI is the first casualty. This is the one row with no nuance. Zoom AI Companion, Teams Copilot, Gemini in Meet, and Webex’s assistant all do their work on the provider’s servers. So they’re unavailable in exactly the meetings where the provider has been told it may not listen. If your organization relies on platform-native AI for recaps, E2EE meetings are the gap, and that’s by design. Canary vs Zoom AI Companion and Canary vs Microsoft Copilot cover what those tools do the rest of the time.
A bot that gets in defeats the point. E2EE hands the keys to every participant, and a meeting bot is a participant. Whether a given bot can connect to a given E2EE meeting depends on how it joins. Many can’t, and the vendor is the one to ask. Where one is admitted, it decrypts the call like anyone else and sends it to a server the platform itself was kept out of. The encryption holds, but the promise it made doesn’t. To the bot’s credit, it’s visible. It sits in the participant list, where the host can see it and remove it.
Capture on your own computer is unaffected, and that’s the uncomfortable part. Your meeting app has to decrypt the call to play it through your speakers. Any tool that listens to your computer’s output hears the same decrypted audio you do. On Windows that’s loopback capture; on a Mac it’s the system-audio permission. No platform setting can block that without also stopping you from hearing the meeting. A microphone can hear the call too if you’re using speakers. With headphones on, it hears only you, as the headphones answer explains.
The question flips
For bots and platform AI, “does it work in an E2EE meeting?” has a technical answer: mostly no. For capture on your own device the technical answer is yes, and that’s what makes it the wrong question.
Everyone in an E2EE meeting has been told, implicitly, that only the people in it can read the conversation. A notetaker on your laptop doesn’t break the encryption. But suppose it sends the audio to a cloud speech-to-text service and the transcript to a language model. Now two or three more companies can read the call. That’s what a bot does, minus the name in the participant list. The encryption did its job, and your device is where the call leaves it.
So the useful question isn’t “will it work?” It’s “does using it here keep the promise the host made when they turned E2EE on?” Sometimes the answer is fine: E2EE is the org default, the content is routine, and everyone’s happy for you to take notes. Sometimes it plainly isn’t. You won’t know without asking.
One phrase to watch for. When a notetaker vendor calls itself “end-to-end encrypted”, it usually means your data is encrypted on the way to its servers and while stored there. The vendor then decrypts it to transcribe and summarize. That’s good practice and worth having, but it isn’t the property the meeting had. On-device transcription covers the difference between encryption and keeping data on your device, and are AI meeting notetakers safe covers what to check instead.
If you need notes in an E2EE meeting
- Ask the host. They turned it on, so they know why. Something like “I’d normally run a notetaker. Is that OK here, or should I take notes by hand?” takes five seconds and settles it.
- If the answer is yes and cloud processing is acceptable, a bot-free tool on your own computer works where bots and platform AI don’t. Say at the start that you’re running it. How to tell participants has wording you can use.
- If nothing should leave anyone’s device, the only capture that fits is fully local. Run a transcription model on your own machine, and accept a transcript rather than a live summary. Canary vs Whisper is an honest guide to what that takes. Or take notes by hand. An encrypted meeting is one place where the old method is still the right one.
- Check your organization’s policy. Many companies restrict capture in exactly the meetings they encrypt, whatever the tool. It’s the same permission question as using a notetaker when your company blocks bots.
- Mind the law. Consent rules for capturing a conversation apply regardless of encryption, and they vary by region. See is it legal to record a meeting.
Consumer calling apps like FaceTime, Signal and WhatsApp are end-to-end encrypted by default, and the same logic applies. Nothing on the server can take notes, and anything on a participant’s device can.
Where Canary sits
Canary is a real-time, bot-free meeting summarizer. It captures your computer’s system audio (no bot in the call, no plugin) and shows a live, multi-resolution rolling summary — from what’s being said right now to the whole call — so you can catch up the instant your name is called.
In an E2EE meeting, Canary works in the plain technical sense. It hears what your computer plays, whatever the platform and however the call was encrypted on the way. We’d rather be precise about what that means than let it read as a feature:
- Canary is not end-to-end encrypted and doesn’t preserve a meeting’s E2EE. Audio is streamed in short chunks to a speech-to-text provider, and the transcript goes to a language-model provider. Both are named in the privacy policy. Audio isn’t written to disk and is gone once transcribed. What’s kept is the text transcript and the summaries. That’s a sound design for most meetings, but it isn’t “only the people in the call can read this.”
- It isn’t a way around E2EE, and we don’t pitch it as one. If the host enabled E2EE because no third party should hear the conversation, Canary doesn’t meet that requirement. Fully local transcription does. The honest move is to leave Canary off, or ask.
- No bot means no visible cue. A bot at least announces itself in the participant list. Canary shows nothing to anyone, so telling people is entirely your job, in an encrypted meeting more than anywhere. The complete guide to bot-free meeting notes explains how it works, and who can see my AI meeting notes covers where the record ends up.
End-to-end encryption keeps the platform out of the room. It was never meant to decide what the people in the room do with what they hear. In an encrypted meeting, that’s the decision to make out loud.
Frequently asked questions
Does Zoom AI Companion work in an end-to-end encrypted meeting?
No. With end-to-end encryption on, Zoom's servers relay the meeting without being able to decrypt it, and AI Companion does its work on those servers, so there's nothing for it to summarize. At the time of writing, Zoom also switches off cloud recording and live transcription in E2EE meetings. Its default setting is standard encryption, where Zoom manages the keys, and that's the mode in which the cloud and AI features work. Feature lists change between releases, so check Zoom's current documentation if a specific feature matters to you.
Can a notetaker bot join an end-to-end encrypted meeting?
Often not. E2EE modes tend to restrict which kinds of client may join (Zoom's, for example, requires its own desktop or mobile apps rather than the web client or a phone line), and many bot services connect in ways that are excluded. Whether a particular bot can get in depends on how it joins, so ask the vendor. If one is admitted, it receives the keys like any participant, decrypts the call, and uploads it to the vendor's servers, which is exactly the access E2EE exists to deny. It does at least show up in the participant list, where the host can see and remove it.
How do I know if my meeting is end-to-end encrypted?
Assume it isn't unless someone turned it on. Zoom, Teams, Google Meet and Webex all encrypt meetings in transit by default, but with keys the provider manages. That's what lets them record, caption and summarize in the cloud. End-to-end encryption is generally an option a host or administrator enables, it costs features, and platforms that support it usually show an indicator in the meeting window. A quick check is whether cloud recording and the built-in AI are available. If they've disappeared, E2EE is probably on. If you're not sure, ask the host. They'll know why they enabled it.