If you've used Otter.ai, Fireflies, or similar tools, you've seen it: mid-meeting, a participant called "Fireflies Notetaker" or "Otter.ai Assistant" appears in your Zoom call. Nobody invited them. Nobody asked if they could record you. They're just there.
This model is called a self-invited bot — and it has an increasingly serious legal and ethical problem.
The lawsuits that change everything
In August 2025, a federal court in California admitted Brewer v. Otter.ai, a class action alleging that Otter.ai's bot recorded participants without their knowledge or consent, violating the California Invasion of Privacy Act (CIPA). The core charge: meeting participants didn't know they were being recorded by a third party.
In December 2025, Cruz v. Fireflies arrived with similar arguments. Fireflies allows any subscriber to invite the bot into a meeting with other participants who have never interacted with Fireflies or agreed to its terms.
Both lawsuits remain open. The amounts claimed are in the tens of millions of dollars.
The core problem: consent isn't yours to give
When you invite a notetaker bot to your Zoom meeting, you have given your consent. But have the other ten people on that call given theirs?
Privacy legislation — CIPA in California, GDPR in Europe, Spain's LOPDGDD — requires that all parties consent to recording when that recording is performed by a third party. The meeting organizer cannot give consent on behalf of everyone else.
The bot model has a structural flaw: it shifts consent responsibility to the end user while the company collects the data.
How AudioMap works
AudioMap has no bot. It never has. There is no "AudioMap Notetaker" that will ever appear in your meeting.
The model is the opposite: you control the recording.
- You record the meeting with your usual tool (Zoom's native recording, Teams, Meet, or directly with AudioMap for in-person meetings).
- You upload the audio or video file to AudioMap.
- The AI processes what you, consciously, have decided to process.
If you record a meeting with multiple participants, the consent responsibility is yours — just as it would be if you recorded a call with any other tool. AudioMap doesn't change that equation: it respects it.
Why this matters even if you're not a lawyer
Your professional reputation. Some people leave meetings the moment they see a notetaker bot. For certain clients or international counterparts, the bot's presence signals distrust. With AudioMap, that problem doesn't exist.
Your legal liability. If your company operates in Europe, using a bot that records third parties without their explicit consent is potentially a GDPR infringement. The fine doesn't go to the tool — it goes to you.
Data control. With the bot model, your meeting data lives on the bot provider's servers from the moment the bot connects. With AudioMap, the file is yours until you choose to upload it.
Does this mean AudioMap has less functionality?
No. It means it has a different model.
What AudioMap does have: accurate transcription in Spanish and English, speaker diarization, structured AI Notes, automatic task detection, and a chat interface that lets you ask your meeting anything.
What AudioMap doesn't have: a visible bot, the legal risk of third-party consent, and exposure of your data at the moment of the meeting.
The trade-off is that you upload the file manually. That's it.
AudioMap's position
We believe privacy isn't a feature. It's an architecture.
We haven't built the bot because we don't want AudioMap to be the mechanism by which someone records other people without their knowledge. That decision is yours. Our tool only processes what you decide to share with it.
If you want to record your next meeting, do it. Tell participants, as the law requires. Upload the audio. And let the AI do its job.