For firms in the US and Europe whose staff or clients bring AI note-takers into calls: whose consent the law requires, what the 2026 court decisions changed, and what each tool does unless you change it.
What you'll learn
- Which US states require every participant's consent to record, with the statute for each
- What the court decided in the Otter.ai class action on August 13, 2026, claim by claim
- Why a New York court refused privilege for material prepared with a consumer AI tool
- What the GDPR, Germany's criminal code and the EU AI Act add for European meetings
- Whether 15 note-takers join by themselves, tell participants, train on your meetings, and where they store data
- The settings to change, and what to do when someone else's note-taker joins your call
An AI note-taker is a recorder with a summary attached. The bot, desktop app or built-in meeting feature captures the audio, turns it into a transcript and sends both to the vendor's servers. The law treats that as recording a conversation, so the old rules on consent, confidentiality and evidence apply, and in 2026 the courts began applying them to AI tools.
Below: the consent rules of US states, the Otter.ai lawsuit, what a 2026 ruling means for privileged calls, European data protection with Germany as the worked example, the EU ban on reading employees' emotions, and the out-of-the-box behaviour of 15 note-takers. Court documents, statutes and vendor pages are listed in the Notes. Nothing here replaces advice on your firm's own situation.
Is it legal to use an AI note-taker in meetings?
Yes, in most places, when every participant has been told the meeting is recorded, has agreed where the local rules require consent, and the vendor handles the recording under terms the firm can defend. Federal US law allows recording with one participant's consent, but at least eight states with all-party rules, the GDPR in the EU and Germany's criminal code ask for more. As of November 17, 2026, the legal risk sits in three places: missing notice, a vendor that uses recordings for its own purposes, and confidential calls on consumer plans.[8][21][22]
Each of the three has a 2026 example. The Otter.ai class action is about notice and about a vendor using recordings to train its models.[1] United States v. Heppner is about confidentiality when a consumer AI provider can read and disclose what it is given.[5] And a note-taker that joins every calendar meeting by default, as Fireflies does, turns one person's choice into a recording of everyone in the call.
Where the participants are matters more than which tool records. A call between a firm in New York and a client in California can fall under California's all-party rule. A meeting with a German client adds the GDPR and § 201 of the German Criminal Code. The safe working rule, our reading of the sources below, is to meet the strictest rule that could apply to anyone in the call: tell everyone at the start, and let them say no.
Which US states require everyone's consent to record?
Federal law, 18 U.S.C. § 2511(2)(d), allows a recording when one party to the conversation consents, unless it is made to commit a crime or a tort.[8] As of November 17, 2026, at least eight states require the consent of all parties in the situations their statutes cover, Oregon does for in-person conversations, and Connecticut does for phone calls under civil law. The table gives the condition in each statute.
| State | What the statute requires | Statute |
|---|---|---|
| California | Consent of all parties to record a confidential communication, or to read a communication in transit; civil damages of $5,000 per violation | Penal Code §§ 631, 632, 637.2[9] |
| Florida | All parties must have given prior consent | Fla. Stat. § 934.03[10] |
| Illinois | Consent of all parties to record a private conversation surreptitiously | 720 ILCS 5/14-2[11] |
| Maryland | All parties must have given prior consent | Cts. & Jud. Proc. § 10-402[12] |
| Massachusetts | Secret recording without authority from all parties is an offence; open recording is not | G.L. c. 272 § 99[13] |
| Montana | Recording with a hidden device without the knowledge of all parties; a warning by any party removes the offence | MCA § 45-8-213[14] |
| Pennsylvania | All parties must have given prior consent | 18 Pa.C.S. § 5704[15] |
| Washington | Consent of all parties to record a private communication; an announcement that is itself recorded counts as consent | RCW 9.73.030[16] |
| Oregon | Phone: one party; in person: all participants must be specifically informed | ORS 165.540[17] |
| Connecticut | Phone calls: consent of all parties or a recorded warning (civil liability) | Gen. Stat. § 52-570d[18] |
Three states are contested. Delaware has one statute that requires all parties and another that allows one-party consent.[19] Nevada's phone statute reads as one-party, but commentators report that the Nevada Supreme Court applies an all-party reading; we could not read the decisions.[20] Michigan and New Hampshire are often listed as all-party states, but we could not open their statute texts on November 17, 2026, so they are not in the table. The list is not complete for every state.
Several statutes cover only secret, private or confidential conversations. A recording that everyone was told about at the start is outside the Massachusetts and Montana offences, and Washington treats a recorded announcement as consent.[13][14][16] That is why an announcement at the start of the call, by the host or the tool, removes most of the US exposure.
What does the Otter.ai class action mean for note-takers?
The Otter.ai case shows that a note-taker vendor can be sued as an eavesdropper when it uses meeting recordings for its own purposes. On August 13, 2026, Judge Eumi K. Lee of the US District Court for the Northern District of California let most privacy claims proceed in In re Otter.AI Privacy Litigation, No. 5:25-cv-06911.[1] The plaintiffs allege that Otter's note-taker joined meetings from users' calendars, recorded people who had not agreed and fed the recordings into model training. The ruling decides only that the claims may go forward.
The case began on August 15, 2025 with one plaintiff and was consolidated with others; the consolidated complaint of December 5, 2025 names seven people from California, Illinois and Washington.[48][1][2] Its central allegation is that when an Otter user connects a calendar, the note-taker joins scheduled Google Meet, Zoom and Microsoft Teams meetings automatically, and that participants without an Otter account are not asked.[2] Otter contests the claims in its answer of September 17, 2026.[4]
| Claim | Decision of August 13, 2026 |
|---|---|
| Federal Wiretap Act (ECPA) | Proceeds; the one-party exception does not end the claim at this stage because the alleged purpose, training models, is said to be tortious |
| California Invasion of Privacy Act § 631 | Proceeds for all three California plaintiffs |
| California Invasion of Privacy Act § 632 | Proceeds for one plaintiff, whose call was with a medical provider; dismissed for two others |
| Illinois Biometric Information Privacy Act § 15(a), (b) | Proceeds; voiceprints plausibly alleged |
| Unjust enrichment, California unfair competition law, declaratory relief | Proceed |
| Computer Fraud and Abuse Act, California computer-access law, Washington Privacy Act | Dismissed with leave to amend |
| Standing (Otter's challenge) | Rejected |
The reasoning that matters for any vendor is under § 631. The court held that the plaintiffs had plausibly alleged that "Otter independently collects, retains, and uses communications for its own commercial purposes", so Otter could be treated as a third party listening in, not as a tool in the user's hands.[1] Our reading: a vendor that uses meeting content for its own model training takes on more risk than one that only processes it for the customer, and a firm that picks the second kind takes on less too.
No liability has been found. The schedule of September 16, 2026 sets the motion for class certification for May 13, 2027.[3]
Does an AI note-taker put attorney-client privilege at risk?
No court had ruled on a meeting note-taker and privilege as of November 17, 2026. The closest decision is United States v. Heppner, in which Judge Jed S. Rakoff of the Southern District of New York ruled from the bench on February 10, 2026, with written reasons on February 17, that about 31 documents a criminal defendant prepared with Anthropic's consumer Claude chatbot were neither privileged nor protected work product.[5] Our reading: its reasoning about confidentiality could be applied to any tool whose terms let the provider use or disclose content.
The defendant used the chatbot on his own, after a grand jury subpoena, and later gave the output to his lawyers. The court gave three reasons why privilege failed: Claude is not a lawyer, the exchange was not confidential, and it was not made to get legal advice from Claude.[5] On confidentiality, the court relied not only on the fact that a third party was involved but on the provider's privacy policy, which allowed it to collect inputs, use them for training and disclose them to third parties, including authorities. Sharing the output with counsel later did not cure it. Work product failed because the documents were not prepared by or at the direction of counsel.[5]
The decision has limits. It concerns a chatbot, not a recording; it says nothing about enterprise plans; and the court noted that use directed by counsel might be treated differently.[5] A Florida magistrate judge, comparing Heppner with a Michigan decision that protected a litigant's AI-assisted work, wrote on October 21, 2026 that neither decision sets a categorical rule for AI.[6]
Bar guidance adds a notice duty for recorded client calls. Formal Opinion 2025-6 of the New York City Bar, issued December 22, 2025, deals with AI that records, transcribes and summarises lawyer–client conversations, and expects the client to be told and to agree first.[7] Our reading for any firm with sensitive client calls: run the note-taker on a business plan whose terms stop the vendor training on or handing over the recording, and ask before the bot joins. The wider professional rules sit in our guide to client confidentiality and AI.
What do the GDPR and German law require for AI meeting notes?
In the EU, an AI note-taker processes personal data, so the GDPR applies: the firm needs a legal basis under Article 6 (usually consent or legitimate interests), must tell participants at the time of recording under Article 13, and needs a processing agreement with the vendor under Article 28.[21] A data protection impact assessment under Article 35 is required where the processing is likely to be high-risk.[21] Germany, as one example, adds criminal law and works-council rights.
Germany's criminal code reaches the note-taker itself. Under § 201 StGB, capturing what someone says in a meeting that is not public, without authorisation, or using that capture later, carries up to three years in prison or a fine; prosecutors act only if the person recorded files a complaint.[22] No court has said whether a tool that keeps only text and never stores the audio is caught; we found no ruling. The German data protection association GDD treats transcription tools as covered, because they capture audio at least briefly to transcribe it.[47]
Germany's data protection authorities wrote in their 2020 guidance on video-conferencing systems that recording regularly needs a separate consent, that recording must be switched off by default, and that users should be warned that secret recording can be a criminal offence.[23] We found no German authority guidance specific to AI note-takers as of November 17, 2026.
Staff meetings add a German co-determination step: a note-taker in internal calls needs the works council's agreement under § 87(1) no. 6 BetrVG, because transcripts show who said what and how people work. What counts is whether a device can monitor, not whether the employer intends to; the Federal Labour Court said so on March 8, 2022 (1 ABR 20/21) in an Office 365 case.[24][25] The procedure is in our article on AI and the works council.
Can a note-taker score emotions or engagement in the EU?
Not of employees when the score comes from their voice or faces. Since February 2, 2025, Article 5(1)(f) of the EU AI Act has prohibited AI that infers how people at work feel, with exceptions only for medical or safety reasons.[26] The Act defines emotion recognition by its input, biometric data, and tone of voice counts as such data, so a meeting tool that rates staff mood from the audio of a call falls inside the prohibition.
The European Commission's guidelines on prohibited practices give as an example of a banned use "monitoring the emotional tone" of hybrid work teams from the voice and imagery of video calls.[27] They also say that sentiment analysis of written text is not emotion recognition, because text is not biometric data, and that tracking customers' emotions is not caught by the workplace ban.[27]
For a note-taker, the question is how a sentiment, mood or engagement score is produced. A score drawn from the words in the transcript is outside the ban on the Commission's reading; a score drawn from tone of voice or faces of employees is inside it. Vendors rarely document which method they use, so the safe setting in the EU, our reading, is to switch off any emotion, sentiment or engagement scoring for internal meetings until the vendor states in writing that it works from text only.
What does each AI note-taker do by default?
As of November 2026, Fireflies, MeetGeek and Read AI send their bot to calendar meetings by themselves once a calendar is connected, Otter.ai does so for meetings with a video link where that default is set, and tl;dv's bot asks to join meetings set to record even when its user is absent. Three of the 15 tools we checked, Otter.ai, Fathom and Granola, state that they train their own models on de-identified or anonymised customer data, and Read AI's privacy policy allows training. Tools built into Microsoft Teams, Zoom and Google Meet show a notice to everyone when they start; several desktop tools show none unless the user turns one on. Each cell comes from the vendor's own pages, read on November 17 and 19, 2026.
Yardwork's dataset of 31 meeting and note tools adds data processing agreements, subprocessor lists and EU options for each plan it covers, checked in October 2026.[49]
Bot note-takers: defaults as of November 2026
| Tool | Joins meetings by itself | Tells other participants | Trains on your meetings | Stores data in |
|---|---|---|---|---|
| Otter.ai | Joins calendar meetings with a video link once a calendar is connected; the default shown for Enterprise workspaces[28] | Bot appears as a labelled participant and posts a chat message[29] | Yes, on de-identified audio and transcripts[28] | United States[28] |
| Fireflies.ai | Yes, all calendar meetings by default[30] | Bot visible as "Fireflies.ai Notetaker"; audio notice optional[30] | No[30] | United States; EU storage on Enterprise[30] |
| Fathom | Setting for all, external, internal or no meetings; default not stated[31] | Bot visible in the attendee list; banner and consent email optional[31] | Yes, de-identified; opt-out in settings[31] | United States[31] |
| Read AI | Yes, all calendar meetings by default[32] | Bot visible as a participant and posts a chat message; none with Google Meet native recording[32] | Privacy policy allows training; no opt-in rule confirmed[32] | United States and other countries[32] |
| tl;dv | Bot asks to join calendar meetings set to record, even without you[33] | Bot visible as a participant[33] | No, per tl;dv[33] | European Economic Area, including Germany and Finland; AI processing in the EU or the US, as selected[33] |
| Avoma | Not stated on the pages read | Posts a recording notice in the meeting chat[34] | No[34] | United States[34] |
| Fellow | Only after the user turns on auto-recording[35] | Attendees notified when it joins[35] | No[35] | Canada[35] |
| MeetGeek | Yes, once a calendar is connected[36] | Chat disclaimer optional[36] | No[36] | EU or US, per workspace[36] |
Built-in and botless note-takers: defaults as of November 2026
| Tool | Starts by itself | Tells other participants | Trains on your meetings | Stores data in |
|---|---|---|---|---|
| Microsoft Teams (recording, transcription, Copilot) | Recording allowed by default; automatic start off for meetings[37] | Banner when recording or transcription starts; consent prompt off by default[37][38] | No[39] | Your Microsoft 365 region; recordings expire after 120 days by default[39][40] |
| Zoom AI Companion | Host starts it; automatic start optional[41] | AI icon lit for participants; custom disclaimer optional[41] | No, for audio, video, chat and other communications content[41] | Not confirmed on November 17 |
| Google Meet "Take notes for me" | Automatic option for the organiser; default not stated[42] | Meet informs all participants[42] | Not without the customer's permission[42] | Organiser's Google Drive[42] |
| Granola | Not confirmed: automatic start not documented on the pages read[43] | Chat message and video badge optional[43] | Yes, anonymised, on Free and Business; opt-out in settings[43] | United States[43] |
| jamie | No bot; starts when the user clicks start[44] | No notice unless the user turns on a consent email[44] | No[44] | EEA, Switzerland and UK[44] |
| Bluedot | User starts it from the browser extension[45] | Chat notice per user, default not stated; workspace owners can enforce it[45] | No[45] | EU residency offered; default not confirmed[45] |
| Krisp | No bot by default; user starts it[46] | Only if the user turns on "Notify others"[46] | No[46] | United States[46] |
"Not confirmed" means the vendor's page could not be read or did not say. A blank in a vendor's documentation is itself useful: ask the vendor before staff use the tool on client calls.
Which settings to change before the next client call
Automatic joining, the notice to participants, model training, retention and storage region decide most of the exposure. As of November 17, 2026, Fireflies, Fathom and MeetGeek document a setting for which meetings their bot records automatically, and Microsoft Teams recordings expire after 120 days unless an admin changes it.[30][31][36][40] The eight steps below apply whichever tool your staff use.
- Limit automatic joining to meetings the user hosts, or to internal meetings, and lock the setting for the whole workspace where the tool allows it.
- Turn on the strongest notice the tool offers: a chat message, a spoken announcement, a pre-meeting email or a consent prompt. In Microsoft Teams, an admin can require participant agreement before recording or transcription.[38]
- Turn off training on customer content where the tool trains by default, and confirm the setting covers the whole workspace.
- Set a retention period for recordings, transcripts and summaries instead of keeping them indefinitely.
- Choose the EU region where the tool offers one and your participants are in Europe, and sign the vendor's data processing agreement.
- Switch off emotion, sentiment or engagement scoring for internal meetings in the EU.
- Keep confidential client calls off personal and free plans, and ask the client before recording.
- Write the rule down in two sentences for staff: when the note-taker may run, and what the host says at the start.
Retention defaults vary widely. Granola keeps notes and transcripts until they are deleted or an auto-deletion period is set; Read AI's privacy policy keeps audio and video no longer than two years; Krisp keeps data until the user deletes it; Microsoft Teams expires recordings and transcripts after 120 days.[32][40][43][46] A shorter period means less to disclose, lose or explain later.
The default decides who is recorded. A note-taker set to join every calendar meeting records every participant on the strength of one user's setting, and the vendor's terms then decide what happens to the recording. Change both before the tool reaches a client call.
What to do when someone else's note-taker joins your call
When a client's or supplier's note-taker joins your call, ask who is recording and with which tool, and ask the host to remove it before anything confidential is said. The bot records you under its owner's settings, not yours. As of November 2026, Fireflies does not join if one participant opts out through its consent request, Fathom stops automatic recording when an attendee declines its consent email, and Zoom tells participants they can ask the host to turn AI features off. The first two work only where the tool's owner turned them on.[30][31][41] In every case, the host decides.
If the host keeps the bot, move the confidential part of the call to a separate meeting. In a Microsoft Teams meeting you organise, you can turn off Copilot if your admin's policy lets organisers change it, which also turns off recording and transcription; under Microsoft's default policy organisers cannot.[37] Put your firm's rule on third-party recording in your engagement terms so the question is settled before the call.
Frequently asked questions
Is it illegal to use an AI note-taker without telling people? It can be. Federal US law allows recording with one participant's consent, but California, Florida, Illinois, Maryland, Massachusetts, Montana, Pennsylvania and Washington require the consent of all parties in the situations their statutes cover, and Oregon does for in-person conversations. In the EU, the GDPR requires that people are told about the recording, and Germany's criminal code punishes unauthorised recording of words not spoken in public with up to three years in prison or a fine.
Is Otter.ai being sued? Yes. A class action filed on August 15, 2025 in the US District Court for the Northern District of California, now called In re Otter.AI Privacy Litigation, alleges that Otter's note-taker recorded meetings without the consent of all participants and used the recordings to train its models. On August 13, 2026 the court let claims under the federal Wiretap Act, California's Invasion of Privacy Act and Illinois' biometric privacy law proceed. Otter denies the allegations; nothing has been decided on the merits.
Does an AI note-taker break attorney-client privilege? No court has ruled on a meeting note-taker as of November 2026. In United States v. Heppner, decided in February 2026, a federal court in New York held that documents a defendant prepared with a consumer AI chatbot were neither privileged nor work product, partly because the provider's privacy policy allowed it to use and disclose the data. A recording held by a vendor on similar terms invites the same argument.
Does an AI note-taker use my meetings to train its AI? Some do by default. As of November 17, 2026, Otter.ai, Fathom and Granola state that they use de-identified or anonymised customer data to train their own models; Fathom and Granola describe a setting to opt out. Read AI's privacy policy allows it to use information to train its models. Fireflies, Avoma, Fellow, Microsoft, Zoom, jamie, Bluedot, MeetGeek and Krisp say they do not train AI models on meeting content.
Notes
- US District Court for the Northern District of California, In re Otter.AI Privacy Litigation, No. 5:25-cv-06911-EKL, Order Granting Motion to Dismiss in Part, Dkt. 68, August 13, 2026. courtlistener.com (PDF). Checked November 17, 2026.
- Same case, Consolidated Class Action Complaint, Dkt. 35, December 5, 2025, paragraphs 6 and 40. courtlistener.com (PDF). Checked November 17, 2026.
- Same case, Amended Scheduling Order, Dkt. 79, September 16, 2026. courtlistener.com (PDF). Checked November 17, 2026.
- Same case, Otter.ai's Answer and Affirmative Defenses, Dkt. 80, September 17, 2026. courtlistener.com (PDF). Checked November 17, 2026.
- US District Court for the Southern District of New York, United States v. Heppner, No. 1:25-cr-00503-JSR, Memorandum, ECF No. 27, February 17, 2026. courtlistener.com (PDF). Checked November 17, 2026.
- US District Court for the Southern District of Florida, Fontainebleau Florida Hotel v. Boteach, No. 25-cv-20251, Second Order After Discovery Hearing, ECF No. 289, October 21, 2026, pages 19–21. Copy at damiencharlotin.com (PDF). Checked November 17, 2026.
- New York City Bar Association, Formal Opinion 2025-6, "Ethical Issues Affecting Use of AI to Record, Transcribe, and Summarize Conversations with Clients", December 22, 2025. nycbar.org. Checked November 17, 2026.
- 18 U.S.C. § 2511(2)(d). law.cornell.edu. Checked November 17, 2026.
- California Penal Code §§ 631(a), 632(a) and 637.2(a). leginfo.legislature.ca.gov; text read at FindLaw (§ 632), § 631, § 637.2. Checked November 17, 2026.
- Florida Statutes § 934.03(2)(d). leg.state.fl.us. Checked November 17, 2026.
- 720 ILCS 5/14-2(a). Text read at FindLaw. Checked November 17, 2026.
- Maryland Code, Courts and Judicial Proceedings § 10-402(c)(3). mgaleg.maryland.gov. Checked November 17, 2026.
- Massachusetts General Laws c. 272 § 99, B(4) and C(1). Text read at FindLaw. Checked November 17, 2026.
- Montana Code Annotated § 45-8-213(1)(c) and (2)(a). mca.legmt.gov. Checked November 17, 2026.
- 18 Pa.C.S. § 5704(4). Text read at FindLaw. Checked November 17, 2026.
- Revised Code of Washington 9.73.030(1) and (3). app.leg.wa.gov. Checked November 17, 2026.
- Oregon Revised Statutes 165.540(1)(a) and (1)(c). Text read at oregon.public.law. Checked November 17, 2026.
- Connecticut General Statutes § 52-570d(a). Text read at FindLaw. Checked November 17, 2026.
- Delaware Code, Title 11, § 2402(c)(4) delcode.delaware.gov and § 1335(a)(4), text read at FindLaw. Checked November 17, 2026.
- Nevada Revised Statutes 200.620 and 200.650. Text read at FindLaw (200.620) and FindLaw (200.650). Checked November 17, 2026.
- Regulation (EU) 2016/679 (General Data Protection Regulation), Articles 6(1), 13(1), 28(3) and 35(1). eur-lex.europa.eu (CELEX 32016R0679). Checked November 17, 2026.
- German Criminal Code (StGB), § 201 and § 205(1). Federal Ministry of Justice, gesetze-im-internet.de/stgb/__201.html, __205.html. Checked November 17, 2026.
- Datenschutzkonferenz (DSK), "Orientierungshilfe Videokonferenzsysteme", October 23, 2020, sections 3.4.8 and 4. datenschutzkonferenz-online.de (PDF). Checked November 17, 2026.
- German Works Constitution Act (BetrVG), § 87(1) no. 6. gesetze-im-internet.de/betrvg/__87.html. Checked November 17, 2026.
- Federal Labour Court (BAG), decision of March 8, 2022, 1 ABR 20/21, para. 30. bundesarbeitsgericht.de. Checked November 17, 2026.
- Regulation (EU) 2024/1689 (AI Act), Article 3(39), Article 5(1)(f) and Article 113(a). European Commission AI Act Service Desk, article 5, article 113. Checked November 17, 2026.
- European Commission, Guidelines on prohibited artificial intelligence practices established by Regulation (EU) 2024/1689, C(2025) 5052 final, section 7.2 (paras. 249–254). ec.europa.eu (PDF). Checked November 17, 2026.
- Otter.ai, "Privacy Policy" and "Privacy & Security". otter.ai/privacy-policy, otter.ai/privacy-security. Otter Help Center, "Automatically add Otter Notetaker to your meetings" and "Manage Enterprise Workspace Settings". help.otter.ai (auto-join), (workspace settings). Privacy pages checked November 17, 2026; help pages November 19, 2026.
- Otter.ai blog, "Permission in the age of conversational intelligence", December 22, 2025. otter.ai. Checked November 17, 2026.
- Fireflies.ai, "How to stop Fireflies from auto-joining your meetings", "Responsible and secure meeting notetaking with Fireflies" and "Learn about data storage and transfer". guide.fireflies.ai (auto-join), (notetaking), (storage). Checked November 17, 2026.
- Fathom Help Center, articles on auto-recording, recording consent, the recording banner and data security. help.fathom.video/3239617, 294272, 6150977, 296512. Checked November 17, 2026.
- Read AI, "Privacy Policy". read.ai/privacy-policy. Read AI Support, "How do I add Read to a meeting?" and "How to Stop or Opt Out of a Read AI Recording". support.read.ai (joining), (opt-out). Privacy policy checked November 17, 2026; support pages November 19, 2026.
- tl;dv, "Calendar integration and why it matters" and "AI and privacy". intercom.help/tldv, tldv.io/blog/ai-and-privacy; "Privacy Policy", tldv.io/privacy. Checked November 17, 2026; privacy policy November 19, 2026.
- Avoma Help Center, "Recording consent and compliance" and "Do you use my data to train your models?"; Avoma, "Security". help.avoma.com (consent), (training), avoma.com/security. Checked November 17, 2026.
- Fellow Help Center, "Meet the Fellow AI Note Taker" and "Security and compliance". help.fellow.ai (note taker), (security). Checked November 17, 2026.
- MeetGeek, "Frequently asked questions", "Account preferences" and "Security". support.meetgeek.ai (FAQ), (preferences), meetgeek.ai/security. Checked November 17, 2026.
- Microsoft Learn, "Teams meeting recording and transcription overview" and "Manage Copilot in Teams meetings and events". learn.microsoft.com (recording), (Copilot). Checked November 17, 2026.
- Microsoft Learn, "Require participant agreement for recording and transcription" and "Customize the recording and transcription notification". learn.microsoft.com (agreement), (notification). Checked November 17, 2026.
- Microsoft Learn, "Privacy and intelligent recap" and "Data, privacy and security for Microsoft 365 Copilot". learn.microsoft.com (recap), (Copilot). Checked November 17, 2026.
- Microsoft Learn, "Manage the auto-expiration of Teams meeting recordings and transcripts". learn.microsoft.com. Checked November 17, 2026.
- Zoom Support, "Using Zoom AI Companion meeting summary" (KB0057960), and Zoom AI whitepaper, "User transparency and notice". support.zoom.com, library.zoom.com. Checked November 17, 2026.
- Google Meet Help, "Take notes for me in Google Meet" and "Automatic note taking"; Google Workspace, "Generative AI in Google Workspace Privacy Hub". support.google.com/meet/answer/14754931, 16909639, knowledge.workspace.google.com. Checked November 17, 2026.
- Granola Docs, "Transparency solutions" and "Security, privacy and data FAQs". docs.granola.ai (transparency), (FAQ). Checked November 17, 2026.
- jamie, "Privacy & Security", and jamie blog, "GDPR note-takers in Europe". meetjamie.ai/privacy-security, meetjamie.ai/en/blog/gdpr-note-takers-in-europe. Checked November 17, 2026.
- Bluedot Help, "How to turn off the recording notification", "Recording settings overview" and "Workspace settings overview"; Bluedot, "Security". help.bluedothq.com (notification), (recording), (workspace), bluedothq.com/security. Checked November 17, 2026.
- Krisp Help Center, "Krisp Bot" and "Record your meetings with Krisp AI Note Taker"; Krisp, "Security for AI meeting assistant". help.krisp.ai (bot), (recording), krisp.ai/security-for-ai-meeting-assistant. Checked November 17, 2026.
- Gesellschaft für Datenschutz und Datensicherheit (GDD), "Kurzpapier Nr. 4: Gesprächstranskription", January 2026, section 4. gdd.de (PDF). Checked November 17, 2026.
- Same case, Class Action Complaint, Brewer v. Otter.ai Inc., Dkt. 1, August 15, 2025. courtlistener.com (PDF). Checked November 17, 2026.
- Yardwork, "Meetings and notes: AI training, EU hosting and DPA compared", AI tools dataset, vendor pages checked October 17–20, 2026. yardwork.dev. Checked November 17, 2026.
