The Notetaker Nobody Invited

Disclosure: I founded Fellowship Intelligence, an AI strategy and governance advisory firm. I have also spent years developing a private system of hieroglyphics for taking notes, which only I can read, and I do not use meeting recorders.

I was hosting a meeting. An attendee tried to bring a notetaker in, and I denied it. Nothing joined, and nothing showed in the participant list for the rest of the call. Afterward I received an automated email carrying a recording, a transcript and a summary of the meeting.

I cannot explain how that happened, and I am not going to guess at it in print. What I can say is denying admission did not keep a record of that meeting from reaching me.

That is the gap this piece is about. Inside the organization holding a meeting, somebody has to be accountable for the conditions under which a third party may capture it. Not the vendor. Not the platform. Someone with a name.

What the court is weighing

On August 13, 2026, a federal judge allowed privacy claims against Otter.ai to proceed while dismissing others. Seven people alleged that its notetaker had captured their conversations without consent, in meetings where somebody else had deployed the tool. Otter has since answered, and the case is in discovery.

Otter had argued that its notetaker functioned as the meeting host’s recording tool. The plaintiffs alleged that Otter also collected and retained conversations for its own purposes, including improving its models. Those allegations were sufficient for the California section 631 claim to proceed. The court was assessing the pleadings, not deciding that Otter had done what the plaintiffs claimed. Its dismissals matter too: two plaintiffs’ section 632 allegations were found insufficient because they described their conversations only as private or sensitive. This was a mixed ruling. Liability remains unresolved.

It is worth understanding why one person’s permission reaches so far in the first place. Federal wiretap law generally permits interception where one participant has given prior consent, subject to exceptions. That is a statement about federal law alone. It does not establish permission under every state’s law, several of which require all parties to agree, and it does not give an account holder authority inside their own organization to decide the question on everyone’s behalf.

Permission to make a record of a meeting also does not settle what the vendor may do with that record afterward.

One account makes the choice for the room

Granola faces a separate suit, first filed on July 30, 2026 and amended in October. Granola has not yet responded to the complaint. Its original complaint concerns a different method of capture: software running on a participant’s device, with no bot joining the call. Those are allegations. Granola’s own documentation is the more useful place to examine the product’s controls.

Granola’s FAQ page, read on November 9th and 10th, says it captures microphone and system audio without adding an attendee. On consent, it is direct: “You are responsible for obtaining consent from participants before using Granola.”

Granola offers two transparency features and they work differently. The video watermark can be enforced by Enterprise administrators from a set date, after which anyone who has not completed setup is blocked from transcribing. The automated chat notice has its own conditions: Granola’s documentation says the message usually appears one to two minutes after the meeting starts, once transcription is already running, and that delivery depends on meeting chat being available. A notice can arrive after capture has begun. On Free and Business plans, individuals configure all of this themselves.

Its model-training documentation draws another distinction. On Free and Business plans, anonymized data may be used by default to improve Granola’s own models, and Business users must opt out individually. Enterprise customers, that page says, are opted out by default and admins can enforce it. Granola separately says its outside AI providers are never permitted to train on customer data.

These are the account holder’s data settings. The people in the meeting who do not have accounts cannot turn anything off. They do not have a setting.

One person operates the account. The consequences reach everyone whose words it captures. The organization has to establish whether that person has authority to make the choice, and on what terms.

The other person did not choose the plan

The plan matters. Granola says HIPAA support requires an Enterprise arrangement and a Business Associate Agreement, currently covering its desktop and laptop apps. It says Free and Business accounts should not process protected health information.

Consider a patient describing a symptom while a clinician captures the conversation through an account outside those arrangements, without asking. The patient did not choose the account or its terms. The organization can correct its arrangements for future appointments. It cannot give the patient back the choice of whether that particular conversation was disclosed to a third party.

That is a hypothetical, not a reported incident involving Granola. It is also why an individual’s account setting should not carry the whole decision.

A notice does not establish control

Notetakers can spare people from dividing their attention between listening and writing. They can make a conversation easier to revisit and search. That usefulness deserves to be taken seriously. So do the controls vendors have built around it.

Zoom shows participants an illuminated icon when meeting summary or meeting questions are active. Its My Notes feature is covered separately: a banner, a pencil icon beside the user in the participant list, a transcription icon, the ability for a participant to ask the host to stop, and the host’s ability to stop it. A participant can dismiss the banner and later reset it. These are real controls, and the organization is on the hook to know which of them it needs.

Microsoft Teams offers a policy requiring participant agreement to recording and transcription, off by default. When enabled in a meeting that is not recorded automatically, starting recording or transcription mutes the other participants and turns off their cameras and sharing until they answer. Declining does not stop the recording; it leaves that person in the meeting, able to watch but not to speak, share or be seen. Microsoft also lists endpoints that are consented automatically without participant interaction, including its own room systems, which receive a notification rather than a prompt. So a room full of people can be recorded while the decision is made somewhere other than that room.

Otter offers pre-meeting emails to calendar invitees, and Enterprise administrators can enforce them workspace-wide, overriding what individuals have chosen. Otter is clear about what that is and is not: it tells administrators it “always recommend[s] getting consent from users before recording,” and the recording disclaimer inside the email cannot be customized.

It also sells something considerably stronger. On a Microsoft Enterprise license, an Outlook extension generates a meeting link that sends participants to a permissions page where, Otter says, they “must agree to be recorded by Otter to join the Microsoft Teams meeting.” That is agreement before entry, which is more than the platforms’ own notices ask for. It also works only if the organizer leaves the Teams toggle off and circulates the Otter link instead. Otter says so plainly: guests who join through a Teams-generated link will not see the permissions page.

A control that strong, undone by sending the ordinary invitation.

There is also a boundary to their reach. Zoom’s whitepaper states that its transcript settings do not prevent participants or third parties from independently creating, storing or retaining separate transcripts. A meeting platform can control its own features. A participant’s separate recorder sits outside them.

Which brings me back to a room.

The second account concerns a recurring meeting I attended. Before writing this, I asked another participant what they remembered without first telling them what I remembered.

They recalled a notetaker posting a recording notice with instructions for removing it. Someone would remove it. About two minutes later, it would return. The account holder could not stop it. They left the call. Their notetaker did not. In the end, the meeting had to be ended.

That matches what I remember. What I had not held onto was the ending.

I do not know which product it was. Neither account establishes a defect in any vendor named here. The second does establish the practical problem we experienced: the removals did not stick, and the account holder could not make the software stop by leaving.

The tool had announced itself. People had objected. The person operating it had tried to stop it. Notice, objection and control had come apart in the same meeting.

If your rule depends on the host being able to refuse capture, test what that refusal actually stops before relying on it in a conversation that matters.

The recorder can enter on a lapel

The same decision now extends to a device somebody wears. Plaud markets its NotePin S to lawyers for client consultations, witness interviews and in-person depositions. Its legal marketing page sells the absence of a meeting bot and says: “Nothing visible in the room creates friction.”

That is marketing language, not a description of an invisible recorder. Plaud’s operating instructions describe a red indicator light that stays on while recording, with a vibration when it starts and stops. Its legal page tells attorneys to obtain explicit consent and observe their professional obligations. It says audio stays on the device until the user chooses to process it, not that recordings never leave the device.

The same page says a disclosure beep “covers the notification step automatically.” That is Plaud’s claim, and it is worth noting where the claim lives: the beep appears in marketing copy, while the operating instructions describe the light and the vibration.

An unexplained sound does not establish what the people who heard it understood. Who tells them what is being captured, and what happens to the record afterward?

California Penal Code section 632 is a reminder that the question does not disappear when the recorder moves off the call and onto a lapel. It reaches confidential communications carried on among parties “in the presence of one another,” and generally requires all parties’ consent. Whether any particular signal satisfies a particular statute is a question for a court, and it will turn on what people were actually told.

Plaud is not a defendant in either case discussed here. Its product illustrates the limit of a meeting-platform rule: a host cannot deny a wearable recorder admission through a participant list.

Name the person who owns the answer

The wrong default is to let the ability to start recording stand in for authority to decide. An employee can enable a useful feature without having been given responsibility for whose information it captures or how the resulting record may be used.

That does not prove a policy was broken. It is the reason the organization needs an answer before the next meeting. Four questions make the gap concrete.

1. Which notetakers are in use, including personal accounts and worn devices?

2. What may each vendor retain or use under the plans your people actually have?

3. Which conversations must stay out of third-party capture, and what happens when someone refuses or asks it to stop?

4. Who owns those answers, including the authority to approve an exception? Name the person, not the department.

A name on its own is not control. The evidence above is mostly about controls that exist and were never selected, or were selected and did not reach far enough. So the test for whoever holds the answer is what they can demonstrate: that permitted uses are defined rather than assumed, that a refusal will be honored and somebody knows how, and that when the available controls cannot support the rule, there is an escalation path rather than a shrug.

That does not mean approving every meeting or banning every tool. It means the authority is delegated deliberately, and the limits of it are written down somewhere other than a vendor’s help page.

Someone decided a third party could capture that meeting. Who?

The free Decision Ownership Check: https://www.fellowshipintelligence.com/decision-ownership-check, offers a directional self-assessment of your organization’s AI governance.

Sources

This piece draws on the August 13 Otter order, the original July 30 Granola complaint, public docket entries and vendor documentation checked November 9th and 10th, 2026. Granola’s first amended complaint, filed in October, is not in the RECAP archive, so this discussion uses the original complaint and does not analyze the amendment. The discussion concerns the identified documents, not a finding that either vendor acted unlawfully.

The two meeting accounts are firsthand recollections. Another participant corroborated the recurring-meeting account. The capture mechanisms and products have not been independently established. The patient example is hypothetical. Vendor documentation describes stated behavior, not testing of those controls. Recording requirements vary by jurisdiction; this is an argument about organizational responsibility, not legal advice.

In re Otter.AI Privacy Litigation, August 13, 2026 order, https://storage.courtlistener.com/recap/gov.uscourts.cand.454675/gov.uscourts.cand.454675.68.0.pdf

Otter’s answer, https://storage.courtlistener.com/recap/gov.uscourts.cand.454675/gov.uscourts.cand.454675.80.0.pdf

Public docket https://www.courtlistener.com/docket/71118721/in-re-otterai-privacy-litigation/

Chamberlain v. Granola, Inc. and Granola Labs Ltd., July 30, 2026 original complaint, https://storage.courtlistener.com/recap/gov.uscourts.cand.475308/gov.uscourts.cand.475308.1.0.pdf

Public docket https://www.courtlistener.com/docket/73698016/chamberlain-v-granola-inc/

Granola Security, Privacy & Data FAQs: https://docs.granola.ai/help-center/consent-security-privacy/security-privacy-data-faqs; Models & training https://docs.granola.ai/help-center/consent-security-privacy/model-training; watermark administration https://docs.granola.ai/help-center/consent-security-privacy/transparency-solutions/for-enterprise-admins/watermark; chat message administration https://docs.granola.ai/help-center/consent-security-privacy/transparency-solutions/for-enterprise-admins/zoom

Zoom AI whitepaper, Administrative Controls: https://library.zoom.com/ai/ai-whitepaper/administrative-controls and User transparency and notice https://library.zoom.com/ai/ai-whitepaper/user-transparency-and-notice

Microsoft Teams participant agreement for recording and transcription https://learn.microsoft.com/en-us/microsoftteams/participant-agreement-recording-transcription

Otter Help Center on enforcing pre-meeting notifications: https://help.otter.ai/hc/en-us/articles/13353091821591-Enforce-pre-meeting-recording-notifications

Otter Help Center, Outlook extension and Microsoft Teams recording permissions: https://help.otter.ai/hc/en-us/articles/35561754307479-Outlook-Extension-Manage-Microsoft-Teams-Recording-Permissions

Plaud AI notetaker for lawyers: https://www.plaud.ai/blogs/articles/ai-note-taker-for-lawyers

NotePin S recording instructions: https://support.plaud.ai/hc/en-us/articles/53639943108761-Start-Recording

18 U.S.C. 2511: https://www.govinfo.gov/content/pkg/USCODE-2024-title18/pdf/USCODE-2024-title18-partI-chap119-sec2511.pdf

California Penal Code section 632: https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=PEN&sectionNum=632