Is Otter.ai Safe? Class Action, Two-Party Consent & Verdict (2026)

TL;DR: Otter.ai is reasonably safe for non-sensitive meeting transcription if you treat it as a cloud SaaS product with two known structural risks. Otter carries a SOC 2 Type 2 attestation, encrypts data in transit and at rest, and its third-party AI providers do not train on user data per Otter's published statements at otter.ai/privacy-security. Three structural caveats matter:

• A pending federal class action. In re Otter.AI Privacy Litigation (5:25-cv-06911, N.D. Cal.) — consolidated from four separate suits filed August-September 2025 — alleges Otter recorded private conversations and trained AI on meeting data without all-participant consent. The consolidated complaint was filed December 5, 2025. On August 13, 2026, Judge Eumi K. Lee granted Otter's motion to dismiss only in part (order): the federal wiretap claim (ECPA), the California wiretap claim (CIPA § 631), the Illinois biometric claims (BIPA), unjust enrichment and the UCL claim go forward, while the CFAA, California computer-access and Washington Privacy Act claims were dismissed with leave to amend. The case continues.
• Otter trains on your meetings by default. Its privacy policy lists "training our proprietary AI technology on de-identified audio recordings and on transcriptions" as a purpose, and neither the policy nor Otter's Privacy & Security page documents a switch to turn that off: no opt-out found when we checked both on October 8, 2026. Voibe, by contrast, never trains on audio or text, from dictation or from meetings.
• The visible-bot consent model is being litigated. The OtterPilot bot joins meetings as a visible participant, which Otter argues is sufficient notice. Plaintiffs are arguing, with all-party-consent states in mind, that a visible bot is not the same as informed consent. The court's answer to that question will define the legal risk for organizations using OtterPilot in mixed-jurisdiction calls.

If you still need the meeting captured, the safer setup is Voibe Work, a meeting note taker and a dictation app in one plan. No bot joins the call, meeting audio is deleted after processing, the notes are saved on your computer rather than a vendor's servers, and nothing is used to train AI. It costs $149 a year, $94.96 (38.9%) less than Otter Pro plus Wispr Flow Pro ($243.96). Meeting notes run on Mac and Windows and need an internet connection, and consent is still your job: Voibe reminds you to tell everyone you're taking notes. If you only need your own notes after the call, Voibe dictation removes the recording question entirely; on Apple Silicon Macs it runs on-device and nothing leaves the Mac.

Here is what Otter actually does with your meetings, the In re Otter.AI Privacy Litigation in detail, the training default, the visible-bot consent problem, retention quirks the privacy policy preserves, a no-bot setup priced against Otter and Otter-plus-dictation, a five-step decision framework, and the alternatives. Every claim is sourced to Otter's own documentation, court filings, NPR, named law-firm analyses, or peer-reviewed third-party reviewers.

Disclosure: Voibe is our product. We compare Voibe to other tools using verifiable facts — Otter's own privacy policy, Otter's privacy-and-security page, the public court docket on CourtListener, named law-firm case analyses, and NPR. Voibe's dictation app and Otter sit in different product categories (personal dictation vs. meeting transcription), while Voibe Work, launched September 2026, now overlaps with Otter's bot-free desktop capture; we say so plainly, and we frame the comparison around the architectural privacy question rather than feature-parity. Where Otter's posture is stronger than Voibe's on a specific dimension (multi-platform reach, integrations, team-collaboration features), we say so.

Here is each row in detail, then a no-bot setup with its price against Otter, ending with a five-step Otter Safety Audit to make your own call.

Every Otter plan, minute cap and price is broken down in our Otter pricing guide.

Otter.ai is a cloud-first meeting transcription assistant. The mental model that matters for safety analysis: Otter is not a personal dictation tool you press a key on — it is a service that joins your video meetings as a visible bot participant (OtterPilot), runs in the browser, or records from its Mac and Windows desktop app without a bot, capturing the audio of every speaker on the call, transmits all audio to Otter's cloud infrastructure, transcribes it using Otter's transcription models, generates AI summaries and action items using third-party LLM providers, and stores the resulting recording, transcript, and AI artifacts on Otter's servers for collaboration and later retrieval.

What Otter captures in a typical meeting:

• Audio recordings of every speaker on the call — not just the host who initiated OtterPilot. Anyone whose voice is captured by the meeting platform is captured by Otter.
• Speaker identification metadata — Otter trains voiceprint models to identify recurring speakers across meetings.
• Meeting metadata — calendar invites, attendee lists, meeting titles, timestamps, duration, platform (Zoom / Meet / Teams).
• Generated AI artifacts — automatic summaries, action items, chapter breakdowns, and Otter AI Chat conversations about the meeting.
• Account information — name, email, billing info, workspace memberships, integration tokens for connected platforms.

What Otter does with that data:

• Stores it on Otter's cloud infrastructure until you manually delete it (with 30-day trash retention before auto-purge).
• Trains Otter's transcription and summarization models on de-identified user data by default. Otter documents no switch to turn this off.
• Sends transcript excerpts to third-party LLM providers for AI features like Otter AI Chat, summaries, and action items. Per Otter, those third-party providers do not train on the data they receive.
• Makes the recording and transcript available to anyone with the share link if the user enables link sharing, and to all members of the workspace if shared internally.

Otter encrypts data in transit (HTTPS/TLS) and at rest (AES-256), maintains a SOC 2 Type 2 attestation, and publishes a Privacy & Security page that documents the encryption posture and the de-identified training. The platform-level security posture is at industry baseline for cloud SaaS. The privacy questions that matter most — what consent the recording requires, what training default applies, how durable deletion really is, and what the pending class action might change — are not addressed by the encryption layer.

The legal context most Otter users have not absorbed is that Otter is the named defendant in a consolidated federal class action that is the most material AI-meeting-recorder case currently being litigated. The case began as Brewer v. Otter.ai Inc., filed August 15, 2025 in the Northern District of California by Justin Brewer, a California resident.

The factual claim in the original complaint:

• Brewer had never signed up for Otter.
• In February 2025, he participated in a sales call where another participant had OtterPilot running.
• Brewer alleges he was not informed that the call was being recorded by Otter, did not consent to the recording, and did not consent to his voice and conversation being used to train Otter's AI models.
• Otter recorded the call, generated a transcript, and (under default settings) used the de-identified data in training.

The legal claims in the original complaint were the federal Electronic Communications Privacy Act (ECPA), the Computer Fraud and Abuse Act (CFAA), the California Invasion of Privacy Act (CIPA) (California's all-party-consent recording statute, with statutory damages of $5,000 per violation), California's Comprehensive Computer Data Access and Fraud Act, and the California Unfair Competition Law. The consolidated complaint added plaintiffs from other states and more counts, including Illinois Biometric Information Privacy Act (BIPA) claims over voiceprints and a Washington Privacy Act claim.

The procedural history:

• Aug-Sep 2025: Four separate suits filed against Otter alleging similar fact patterns.
• Oct 22, 2025: Judge Eumi K. Lee consolidated all four cases into In re Otter.AI Privacy Litigation, 5:25-cv-06911 (N.D. Cal.).
• Dec 5, 2025: Consolidated complaint filed.
• April 2026: Otter filed its reply brief on the motion to dismiss, denying any interception occurred.
• Aug 13, 2026: Judge Lee granted the motion only in part and denied it "in all other respects." Going forward: ECPA, CIPA § 631, BIPA §§ 15(a) and 15(b), unjust enrichment, declaratory judgment and the UCL claim. Dismissed with leave to amend: the CFAA, the California computer-access claim (CDAFA), the Washington Privacy Act claim, and some plaintiffs' intrusion-upon-seclusion and California constitutional privacy claims. Plaintiffs were given 14 days to amend.

Why this matters for the safety analysis:

• The core claims survived. The wiretap and biometric claims go forward, with Otter treated as a possible third-party eavesdropper because of its alleged use of recordings to train its models. That is a pleading-stage ruling, not a finding of liability: no court has held that Otter broke the law. Class certification and the merits come next.
• The visible-bot consent argument is the core legal question. If the court finds that a visible bot is insufficient notice to satisfy all-party-consent statutes such as CIPA, every organization using OtterPilot in mixed-jurisdiction calls without explicit verbal consent inherits a CIPA-style risk. Statutory damages per violation are not nominal.
• Training is part of the alleged harm. Otter's training-by-default design is why the court treated it as a possible third party to the conversation. A ruling that training on participants' speech requires their consent would have product-design implications for Otter and every peer notetaker with similar defaults.

For the public reporting and source documents:

• NPR's contemporaneous coverage: Class-action suit claims Otter AI secretly records private work conversations (Aug 15, 2025).
• The consolidated docket on CourtListener: In re Otter.AI Privacy Litigation, 5:25-cv-06911.
• The original Brewer complaint PDF: Class Action Complaint (filed N.D. Cal.).
• The August 13, 2026 order on the motion to dismiss: In re Otter.AI Privacy Litigation, No. 25-cv-06911-EKL (FindLaw).
• Jackson Lewis case analysis: We Get AI for Work — Analyzing Brewer v. Otter.ai.

The honest framing: the case is not a breach allegation, a security-control failure, or evidence that Otter is acting in bad faith. It is a litigation of whether the product's consent model meets the statutory bar for all-party-consent jurisdictions, and whether training on participants' speech by default is defensible. Both questions are genuinely contested, and both matter for how an organization weighs Otter against alternatives.

Yes. Otter trains its own AI models on your meeting recordings and transcripts after de-identifying them, and that is the default. Otter's privacy policy (effective June 16, 2026) lists "training our proprietary AI technology on de-identified audio recordings and on transcriptions" as a purpose of processing, with "Consent or Legitimate interests" as the legal basis. Its Privacy & Security page says: "Otter uses a proprietary method to de-identify user data before training our models."

What Otter's own documents say, checked October 8, 2026:

• Training is automatic. "This training method is automatic and as such audio recordings and transcripts are not manually reviewed by a human."
• No opt-out found. Neither page describes a setting that switches training off. The privacy policy gives general rights to "object to our processing of your Personal Information" and to "withdraw any consent you previously applied to us," which is the closest thing to an opt-out it offers. Third-party guides disagree on whether an in-app control exists, so check your own account's settings, and if you can't find one, object in writing.
• De-identification. Training data is de-identified through a proprietary process before being used. De-identification reduces the privacy risk if it is robust, but de-identification is not deletion: the underlying meeting content still informs the model's parameters.
• Encryption. "Additionally our training data is encrypted."
• Third-party AI providers. "No customer data will be used to train or improve our AI Service Provider(s)' artificial intelligence models/algorithms." That covers the LLM vendors behind summaries and Otter Chat, not Otter's own models.
• Imported documents. Files imported from sources such as Google Workspace are excluded from training, per the same page.

Why training by default is a bigger problem in a meeting recorder than in a dictation app:

• The person who agreed is not the person who was recorded. When OtterPilot joins a five-person call, the host accepted Otter's terms. The other four participants never saw them, and their de-identified speech enters the same training pipeline with no practical way for them to object.
• De-identification is not deletion. Even if de-identification clears GDPR's anonymization bar (a high bar that most de-identification misses), the meeting content still shapes the model's weights. For M&A talks, NDA-bound topics or sensitive personal conversations, de-identified training is still training.
• There's no switch to flip. With no opt-out found, the only control is a written objection, which few users will ever send.

How peers compare:

• Wispr Flow: its help center says the "Improve the model for everyone" setting, which covers dictation and Notetaker content, is on by default for Free and Pro, while its launch posts say meeting data is never used to train. (See Is Wispr Flow Safe? and Wispr Flow Notetaker vs Voibe Work.)
• Superwhisper: "Not used for training AI models or any other machine learning purposes." (See Is Superwhisper Safe?.)
• Aqua Voice: Silent on training. (See Is Aqua Voice Safe? for why silence is a signal.)
• Voibe: never trains on audio or text: not in on-device mode, not in the zero-retention cloud, and not on Voibe Work meeting notes.

If Otter is in your stack, the highest-leverage privacy step is to check your account's data settings for a training control and, if there isn't one, send Otter a written objection under the privacy policy's right to object, then keep the reply. Make it part of onboarding for any workspace where Otter is approved.

The single most material legal question about Otter is whether the OtterPilot visible-bot pattern satisfies two-party-consent (also called "all-party-consent") recording statutes in the states that require consent from every party before a private conversation can be lawfully recorded.

The all-party-consent US states and the ones with important nuances, per Justia's 50-state survey:

• California — California Invasion of Privacy Act (CIPA), statutory damages of $5,000 per violation.
• Connecticut — one-party for criminal liability, but civil liability for recording phone calls without all-party consent.
• Delaware — arguably all-party; the law is ambiguous.
• Florida.
• Illinois — Eavesdropping Act; generally all-party.
• Maryland.
• Massachusetts.
• Michigan — technically all-party, though courts have held that participants in a conversation can record it.
• Montana — an all-party "knowledge" state.
• Nevada — all-party for phone calls, one-party in person.
• New Hampshire.
• Oregon — one-party for phone calls; in person, everyone must be told they're being recorded (notice, not consent).
• Pennsylvania.
• Washington — generally all-party.

Every state's rule, including calls that cross state lines, is in our 50-state AI notetaker consent guide.

Otter's stated consent model treats the visible OtterPilot bot in the participant list, plus a notification when the bot joins, as constituting notice that the meeting is being recorded — and treats continued participation in the call as implicit consent. This is the model the Brewer plaintiffs are challenging. The legal questions the court will need to answer:

• Is a visible bot in a Zoom participant list "notice" sufficient for CIPA? CIPA requires consent, not just notice. A participant who sees the bot but does not understand what it is or what it does has been given a label, not informed consent.
• Is silence-as-consent compatible with the affirmative-consent reading of CIPA? Several California courts have read CIPA to require an affirmative act of consent, not the absence of objection.
• How does the analysis change for participants who join late, miss the bot announcement, or come from a one-party-consent jurisdiction that does not match the host's?

The operational risk for organizations using OtterPilot in mixed-jurisdiction calls is straightforward even before the court rules: any single participant in a CIPA state who later objects to the recording or training can file a private right of action under CIPA seeking $5,000 statutory damages per violation. The arithmetic on a recurring meeting with even a handful of CIPA-resident participants over a year escalates quickly.

The defensive workflow regardless of what the court rules:

1. Establish a verbal-consent script. At the start of every recorded call, the host reads: "This call is being recorded and transcribed by Otter.ai. Otter is in our participant list as a visible bot. Do you all consent to recording and transcription?" Wait for verbal acknowledgment from every participant. Document the consent in the transcript itself.
2. Offer a clear opt-out path. Any participant who objects can request the recording be stopped, the bot removed, or themselves removed from the recording.
3. Distinguish internal vs. external meetings. Internal team meetings where all participants are on the same workspace and have agreed to workplace recording policies are easier than client calls, candidate interviews, or partner discussions where the consent baseline is unclear.
4. Have a written policy listing call types that do not get recorded. Privileged legal conversations, HIPAA-bound healthcare conversations without BAA, M&A discussions, candidate interviews where local employment law restricts recording, NDA-bound third-party conversations.

The architectural alternative for the host who is mostly interested in capturing their own contributions, action items, and follow-ups: dictate after the call rather than recording the call. Voibe does the dictation step on-device on Apple Silicon Macs, which removes the recording, the consent question, and the lawsuit-risk profile from the workflow.

Switching to a no-bot notetaker doesn't remove the consent question if you still capture the meeting. A bot in the participant list is at least visible; capture from your own computer is not, which is why bot-free tools are being sued too (see the Granola lawsuit). Voibe Work reminds you to tell everyone you're taking notes when recording starts, but following the rules for every participant's state is still your responsibility.

Otter's user-facing deletion flow is straightforward: a recording moves from your main account to a trash folder, sits in trash for 30 days, then auto-purges. Once auto-purged, Otter states that “no record of the User Content is retained and the User Content cannot be recreated by the service.”

The harder question is what Otter does with copies of your data outside the user-facing deletion flow. Otter's privacy policy reserves the right to retain data “for as long as necessary to fulfill the purposes set out in this Policy, or for as long as it is required to do so by law or in order to comply with a regulatory obligation.” That is broad language with several practical consequences:

• Backup retention. Standard SaaS practice is to keep encrypted backups for a defined window after primary deletion. Otter does not publish the backup-retention window in the public privacy policy.
• Training-corpus retention of de-identified copies. Once a meeting transcript has contributed to a model-training pass under the training default, the de-identified contribution to model weights is durable. Deleting the original recording does not unwind the training contribution.
• Legal-hold retention. If Otter receives a litigation hold or regulatory request that covers your data, the deletion timeline pauses indefinitely.
• Analytics and operational retention. Metadata about your account, your usage patterns, and your meeting cadence is typically retained separately from the content itself.

Independent privacy reviewers analyzing Otter's policy have flagged the broad-purpose retention language as preserving Otter's right to retain copies of user data even after the user clicks delete, if Otter determines retention serves a "legitimate business purpose." This is not unique to Otter — many cloud SaaS privacy policies use similar language — but the combination of a meeting-recording product with broad-purpose retention language deserves explicit attention from anyone storing sensitive conversations.

The practical read for the compliance team:

• Treat the recording as durable for compliance-audit and litigation-discovery purposes. If a meeting is recorded by Otter, assume the recording exists in some form that could be reached by a subpoena or regulatory request even after user-facing deletion.
• Set a retention policy at the org level if you can. On Business and Enterprise tiers, admins can configure shorter retention windows than the default.
• Audit the trash folder. Set a recurring calendar reminder to empty the trash on a defined cadence. The 30-day auto-purge is a floor, not a ceiling — actively empty rather than wait.
• For genuinely sensitive content, do not record in the first place. The architectural answer is upstream of the deletion flow.

Voibe's architectural choice is to keep nothing on its side. Dictation audio either never leaves an Apple Silicon Mac (on-device mode) or is deleted the moment transcription completes (zero-retention cloud). With Voibe Work, meeting audio is deleted once processing completes and the transcript and summary are saved on your computer, not on Voibe's servers, so there is no vendor-side copy for a backup window, a training pass or a legal hold to reach. What sits on your computer is yours to keep or delete under your own retention policy.

Otter sits squarely on the cloud side of the dictation-and-transcription privacy landscape. It is well-supported on the audit and platform-security dimensions and structurally exposed on the architecture and consent dimensions.

What Otter has:

• SOC 2 Type 2 attestation. Independent attestation that security controls have been designed and tested over a defined window. Procurement-clearing for many enterprises.
• Encryption at industry baseline. HTTPS/TLS in transit, AES-256 at rest.
• Third-party LLM no-training contracts. The downstream LLM providers Otter uses for AI Chat, summaries, and action items are contractually prohibited from training on Otter data.
• HIPAA BAA availability on Enterprise. Enables healthcare deployments with the standard caveats about cloud routing.
• Admin controls on Business and Enterprise. Activity logs and usage analytics on Business; SSO, SCIM and domain capture on Enterprise.
• A ten-year operational track record (founded 2016) with no publicly reported data breach that we found.
• Multi-platform reach. Web, iOS, Android, a Mac and Windows desktop app that can record without a bot, and OtterPilot for Zoom / Google Meet / Microsoft Teams.

What Otter does not have:

• On-device transcription as an option. No path to transcribe a meeting without sending audio to Otter's cloud.
• Opt-in training, or a documented way to turn it off. Training on de-identified recordings and transcripts is the default, and no self-serve toggle is documented.
• An explicit consent flow at the meeting level. The visible-bot model relies on implicit-consent reasoning that is being challenged in court.
• A resolved legal posture. The In re Otter.AI Privacy Litigation is ongoing, and its core wiretap and biometric claims survived the August 2026 motion to dismiss. The legal cloud is no longer Otter-specific either. Fireflies faces a voiceprint class action under Illinois' BIPA (Fricker v. Fireflies, N.D. Ill.; our Fireflies safety review tracks it), and in July 2026 Granola was sued in Chamberlain v. Granola, Inc. (No. 3:26-cv-07926, N.D. Cal.) — a wiretap class action alleging its bot-free system-audio capture records meeting participants without any notice at all and trains AI on their communications by default. The entire notetaker category now operates under consent litigation.
• A privacy policy that addresses backup-retention windows or training-contribution-deletion procedures with specific timelines. The broad-purpose retention language preserves rights the user cannot independently verify.

For non-sensitive meeting transcription where all participants are inside the same organization, on the same SaaS contract, in the same jurisdiction, with workplace recording policies that cover the use case — Otter is functional and the security baseline is reasonable. For client calls, mixed-jurisdiction meetings, regulated industries, or any conversation where two-party-consent statutes might apply, the cloud-only architecture plus the visible-bot consent model plus the pending litigation compound into a real risk profile.

For the broader architectural framing, see our cloud vs. local dictation guide and our voice data privacy guide. For a continuously-updated cross-product reference covering Otter, Fireflies, Granola, and the rest of the meeting-transcription peer set on training, retention, and on-device support, see our AI Tool Privacy Tracker.

Otter's default training on de-identified data is a textbook case of the de-identified-data carve-out — one of six clauses that let a company keep and use your audio without breaching its own terms. All six are set out in zero data retention explained.

Most of the risk above traces back to two design choices: Otter keeps the recording and transcript on its servers, and it trains on them by default. Change those two and most of the risk list goes with them. That's the setup we built Voibe Work around. (Voibe is our product, so weigh this section accordingly; every limit below is real.)

Voibe Work is a meeting note taker and a dictation app in one plan. Here's what changes when it replaces Otter:

• No bot in the call. Voibe Work captures Zoom, Microsoft Teams, Google Meet, Webex, Slack huddles or any other meeting app from your Mac or Windows PC. Nothing joins the participant list, and nobody has to admit a notetaker. (Otter's own desktop app can also record without a bot, but the recording still lands on Otter's servers under the same training default.)
• Audio deleted after processing. Meeting audio is processed by open-source models on zero-retention cloud providers and deleted as soon as processing completes. There's no trash folder and no 30-day purge window, because Voibe keeps no copy.
• Notes saved on your computer, not on Voibe's servers. The transcript and summary live on your computer, so the retention question from earlier becomes your own file-management decision.
• Never used to train AI. There's no default to discover and no objection to file, for you or for anyone else on the call.
• The rest of the meeting workflow. AI summaries with templates for each type of meeting (client intake, investment committee and others), chat with your meetings on the same zero-retention cloud with nothing you ask stored, and one-click copy and PDF export.
• Dictation included. Every Voibe Work seat includes Voibe Dictation on Mac and Windows, on-device on Apple Silicon Macs or in the zero-retention cloud. The follow-up email, the CRM note and the memo after the call get dictated in the same app.

What doesn't change: consent. No bot in the call doesn't mean no recording. When recording starts, Voibe reminds you to tell everyone you're taking notes, and you're responsible for the consent rules wherever you and the other participants are. The all-party states listed above apply to Voibe Work exactly as they apply to Otter.

Where Otter still wins. Know the limits before you switch:

• Meeting notes need an internet connection. They are not offline or on-device; on-device processing is a dictation feature on Apple Silicon Macs.
• Voibe Work labels speakers, but it doesn't list calendar auto-join, CRM or Slack integrations, or shared team workspaces, and it has no iPhone or Android app. Otter has all of those. If you need a speaker-attributed record or notes that flow into Salesforce, Otter or a tool from our Otter AI alternatives list is the better fit.

The animation shows the same four-person call through three setups. With a meeting bot (Otter, Fireflies, Fathom), a bot joins and the recording and transcript stay in the vendor's cloud. With a bot-free cloud notetaker (Granola), nothing joins, but the notes stay in Granola's cloud and training is on by default with an opt-out. With Voibe Work, nothing joins, the audio is deleted after processing, the notes are stored on your computer, and nothing is trained on.

What It Costs Against Otter, and Against Otter Plus a Dictation App

Otter has no dictation app, so most people who use it for meetings pay for a second tool to write with. Prices below were checked at otter.ai/pricing, wisprflow.ai/pricing and getvoibe.com/pricing on October 8, 2026 (US prices; Otter shows lower promotional prices to India-issued cards).

The maths:

• Against Otter Pro plus Wispr Flow Pro: $243.96 − $149 = $94.96 a year less (38.9%). Paying monthly, $31.99 − $19 = $12.99 a month less (40.6%). Over three years, the $399 lifetime costs $332.88 less than $731.88 (45.5%).
• Against Otter Business alone: $239.88 − $149 = $90.88 a year less (37.9%), with the dictation app included.
• Against Otter Business plus Wispr Flow Pro: $383.88 − $149 = $234.88 a year less (61.2%).
• Against Otter Pro alone: Otter Pro is $49.04 a year cheaper ($99.96 vs $149). The difference buys the dictation app, no vendor-side copy of your meetings, and no training.

Voibe Work comes with a 7-day free trial of every feature, no credit card and no automatic charge, plus a 30-day money-back guarantee. For every bot-free option side by side, see our best no-bot meeting note takers roundup; if you're weighing Wispr Flow's own notetaker, see Wispr Flow Notetaker vs Voibe Work.

Fathom is the other big bot-first note taker; our Fathom safety audit walks through its default training on de-identified data, US storage and the opt-out settings.

Read AI is bot-first too, but its training is opt-in. Its catch is spread: its bot can join through any colleague who has it connected. Our Is Read AI safe? review covers that and why six universities block it.

Leaving Otter? Turn off Otter Notetaker's auto-join and disconnect your calendar first; how to stop meeting bots joining your calls walks through each Otter setting.

Use the Otter Safety Decision Tree to decide whether Otter is safe enough for your specific situation. The five questions, in order, take you from the lowest-risk use case to the highest. Stop at the first question where you cannot accept the answer Otter currently provides.

1. Are all meeting participants on the same workspace with workplace recording policies that explicitly cover Otter? If yes — internal team meeting use is reasonable, assuming the org has dealt with training (question 3). If no, continue to question 2.
2. Are all meeting participants in one-party-consent jurisdictions, or have you established explicit verbal consent at the start of each call? If yes — the CIPA-class risk is mitigated. Continue to question 3. If no, accept that any single CIPA-state participant can later file a private action seeking statutory damages.
3. Have you dealt with training? Otter documents no training toggle, so check your account's data settings and, if there's no control, object in writing under the privacy policy and keep the reply. If done — continue to question 4. If not, assume every meeting is contributing to Otter's training corpus in de-identified form.
4. Is the content covered by HIPAA, attorney-client privilege, or specific NDA terms restricting third-party processing? If no — Otter on opted-out training with consent established is workable. If yes — confirm a signed BAA on Enterprise, verify the specific NDA language permits cloud transcription, and consult counsel for privileged calls. For PHI without a BAA, Otter is the wrong tool regardless of plan.
5. Are you comfortable with the pending In re Otter.AI Privacy Litigation, the visible-bot consent model, and the broad-purpose retention language in the privacy policy? If yes — Otter is workable with the configurations above. If no, change the architecture and pick by what you need. Meeting notes with no bot and no vendor-side copy, on Mac or Windows: Voibe Work (audio deleted after processing, notes saved on your computer, never trained on, dictation included; you still handle consent). Only your own notes after the call: Voibe dictation, on-device on Apple Silicon Macs. A speaker-attributed record or a BAA-backed meeting tool: see our Otter alternatives roundup.

The pattern: the further you progress through the tree, the more Otter's defaults rub against the use case. By question 4, the absence of an Enterprise BAA blocks regulated workflows. By question 5, the pending litigation becomes the dispositive factor for risk-averse organizations.

Quick Routing: Which Setup Fits Your Meetings

The right alternative to Otter depends on whether you actually need a meeting recording, or whether you only need notes about the meeting. These are two different product categories, and confusing them is why many users default to Otter when their actual need is dictation after the call.

If you need a meeting recording — for legal deposition, multi-party interview, sales-call review, training, or transcribed-for-record events — the safer alternatives have explicit all-party consent flows, signed BAAs where applicable, and documented retention timelines. See our Otter AI alternatives roundup for the meeting-tool comparison. And if your actual question is Otter versus Dragon — meeting capture versus document dictation — our Dragon vs Otter comparison untangles the two jobs. The relevant axes are:

• Consent flow. Does the product require explicit consent from each participant, or rely on visible-bot-as-notice?
• Training default. Opt-in, opt-out, or no-training-period?
• Compliance attestations. SOC 2 (Type 1 or Type 2), HIPAA BAA availability, ISO 27001, regional data residency.
• Retention transparency. Specific timelines for backups, training-contribution durability, and legal-hold pause behavior.
• Architecture. Cloud-only, hybrid, or on-device options.

If you only need notes about the meeting — your own action items, follow-ups, summaries, decisions — the architectural alternative is to skip the cloud meeting bot entirely and dictate your own summary directly after the call using an on-device tool. The benefits compound:

• No consent question. You are dictating your own notes; you are not recording other participants.
• No training question. On-device dictation has no cloud surface and no training corpus.
• No retention question. Voibe keeps no copy; dictation audio is discarded after transcription.
• No subpoena exposure. Audio that never leaves your Mac cannot be subpoenaed from a third party.
• No bot in the participant list. Calls feel natural; no one is wondering what OtterPilot is.

For the cross-tool roundup with feature-level detail, see best offline dictation apps. For the comparison-with-Otter framing, see Otter vs. Wispr Flow.

Speakers and Summaries Without the Meeting Bot

Voibe started as a dictation app, a different category from Otter — but that is no longer the whole picture. Voibe's speech-to-text API now returns the substance of what a meeting-transcription tool sells: a diarized transcript with speaker labels and per-segment timestamps, plus a summary you steer with your own prompt. In Claude Cowork, Claude desktop or Claude web, add it under Customize › Connectors › Add custom connector, paste https://api.getvoibe.com/mcp and sign in once — no terminal, no code. Developers connect the same server in Claude Code with one claude mcp add command, or call the REST endpoints directly from a script or cron job.

Meeting notes, without the bot. In September 2026 Voibe added Voibe Work, a plan that takes meeting notes from your Mac or Windows PC with no bot in the call. Meeting audio is processed by open-source models on zero-retention providers and deleted when processing completes, and the transcript and summary are saved on your computer. It doesn't list calendar integration or auto-join, so it replaces Otter's desktop capture, not a bot that shows up on its own. Because every Voibe Work seat includes the dictation app, it also replaces the second subscription most Otter users carry; the safer-setup section above has the prices. Our Granola alternatives and best no-bot meeting note takers guides compare it. Separately, the API takes a recording you already have — a local Zoom file, a voice memo, an interview — and gives you speakers, timestamps and a summary without uploading it to a service that retains it. If you already have the file, you no longer need to hand it to Otter to get that. If you need something to attend the meeting for you, Otter and its notetaker peers remain the category that does it.

The privacy contrast is the sharp part. Otter trains by default and its deletion promises carry the caveats set out above; Voibe's API deletes the audio the moment the transcript exists, never trains on it, and applies that on every tier with no flag to remember. See how to transcribe a Zoom recording for the full walkthrough.

Voibe is a dictation app for Mac and Windows built around a durable promise: your audio and text are never stored, never sold, and never used to train any AI model. It offers two user-selectable modes. In on-device mode, Voibe runs OpenAI Whisper on Apple Silicon's Neural Engine — when you press your hotkey, audio is captured into memory, transcribed by the local Whisper model, written into the active text field, and discarded; nothing leaves the Mac. In zero-retention cloud mode, audio is encrypted in transit to zero-retention providers running open-source models (Whisper Large Turbo on Groq or Cloudflare) and deleted the moment transcription completes. No participant consent question, no training-corpus contribution in either mode.

Mapped against the safety questions raised by the Otter story:

• Audio routing. In on-device mode Voibe processes audio on the Apple Silicon Neural Engine and nothing leaves the Mac; in zero-retention cloud mode audio is encrypted in transit and deleted the moment transcription completes.
• Consent question. Not applicable. You are dictating your own notes after the call — you are not recording any other participants.
• Training default. Not applicable. Voibe never uses your dictation to train any AI model, in either mode.
• Retention. Not applicable. Your audio and text are never stored; on-device mode writes no recording files to disk.
• Class-action exposure. Not applicable. The product category is different (personal dictation, not meeting recording); the consent litigation does not apply.
• Privacy policy. Voibe's privacy policy and cloud AI privacy page commit that your audio and text are never stored, never sold, and never used to train any AI model — with a fully on-device mode available when you want nothing to leave the Mac at all.
• Permissions. Voibe requests microphone access and macOS accessibility permission — the minimum surface required to capture audio and paste text into the active field. No screen recording, no camera, no full-disk access.
• Network monitor. Run Little Snitch during a Voibe on-device dictation session. Outbound traffic from Voibe during transcription is zero.

What Voibe is not: Voibe does not send a bot into Zoom, Google Meet, or Microsoft Teams, and it doesn't list calendar auto-join. Its dictation app captures only your own voice. The Voibe Work plan (Mac and Windows) captures meetings from your computer and saves the notes there, so the consent question applies to it as it does to any no-bot note taker. If you already have the recording — a Zoom local recording, for instance — Voibe’s transcription API will turn that file into a speaker-labelled transcript without any bot joining anything; see how to transcribe a Zoom recording. Voibe Work's transcripts label each speaker with a time on every line. If you need a certified record of a legal deposition, that still takes a court reporter, and our Otter alternatives roundup covers the other tools in that category. But for the most common Otter use case — capturing your own notes, summaries, action items, and follow-ups after a call — Voibe handles the dictation step on-device and removes the entire recording question.

Pricing: Voibe Dictation is $9.90/month, $99/year, or $199 lifetime on Mac and Windows (on-device mode requires an Apple Silicon Mac, M1 or later). Voibe Work, which adds meeting notes with no bot on Mac and Windows, is $19/month, $149/year or $399 lifetime. Both include Developer Mode, which resolves file names, folder paths and variable names in Cursor, VS Code and Windsurf.

Try Voibe for Free — install, grant microphone and accessibility permissions, and dictate. The 7-day free trial covers every Voibe Work feature, with no credit card and no automatic charge.

Otter.ai is reasonably safe for non-sensitive meeting transcription if you treat it as a cloud SaaS product with two known structural risks, deal with the training default (no toggle is documented, so object in writing), establish explicit verbal consent at the start of every recorded call, and have a written policy listing the call types that bypass Otter entirely. The platform-level security posture — SOC 2 Type 2, AES-256 at rest, HTTPS/TLS in transit — is at industry baseline. For internal team meetings on a single workspace with workplace recording policies that cover the use case, Otter is functional.

It is not the right tool if you need an explicit all-party consent flow rather than visible-bot-as-notice, cannot accept training by default on participants who never agreed to Otter's terms, are uncomfortable with the pending In re Otter.AI Privacy Litigation, need HIPAA coverage without an Enterprise BAA, or require a privacy policy that addresses backup-retention and training-contribution-deletion timelines specifically. None of these gaps are breaches or security failures — they are product-design choices and unresolved legal questions that compound risk in specific deployments.

The pattern this represents is broader than Otter. Fireflies faces a BIPA voiceprint class action in Illinois, and in July 2026 Granola — the best-known bot-free notetaker — was sued in Chamberlain v. Granola, Inc. (N.D. Cal.) for recording meeting participants without their knowledge or consent through its system-audio capture and using their communications for AI training by default. Cloud meeting transcription tools sit at the intersection of recording statutes (which require consent from every speaker), training-data law (which is still being defined), and litigation-discovery rules (which can reach data that the user has "deleted"). For non-sensitive internal use, the cloud meeting bot is a reasonable convenience. For mixed-jurisdiction, regulated, privileged, or NDA-bound calls, the architectural answer is explicit consent with a BAA-anchored tool, capture with no bot and no vendor-side copy, or skipping the recording entirely and dictating the notes after the call on-device.

If Otter is on your shortlist, run the Otter Safety Audit: map your jurisdictions, establish a verbal-consent script, object to training in writing, define call types that bypass Otter, and on Enterprise tiers request the SOC 2 Type 2 report and verify the signed BAA. If those steps feel like more diligence than you want to spend per recorded call, Voibe Work captures the meeting from your Mac or Windows PC with no bot, keeps no copy on Voibe's servers, never trains on it, and includes dictation for $149 a year, $94.96 less than Otter Pro plus Wispr Flow Pro. You still owe everyone on the call a heads-up, and Voibe reminds you when recording starts. If you only need your own notes after the call, on-device dictation on Apple Silicon handles that step with no recording at all.

For further reading, see our Otter AI alternatives roundup, best no-bot meeting note takers, Otter vs. Wispr Flow comparison, and the broader dictation privacy hub. For the sibling "is X safe?" investigations, see Is Wispr Flow Safe?, Is Superwhisper Safe?, Is Aqua Voice Safe?, Is Willow Voice Safe?, Is Dragon Safe?, Is Claude Code Safe? (developer-tool parallel covering Anthropic's Consumer-vs-Commercial Terms split), Is Blip AI Safe?, Is VoiceDash Safe?, Is Voicy Safe? (the Groq-routed cloud peer whose no-training promise lives on marketing pages, not in policy), Is Wisprtype Safe? (local-by-default but closed-source, with a telemetry default that contradicted its policy), Is VoiceInk Safe? (the open-source GPL v3 on-device peer — zero telemetry, verified in source), Is Handy Safe? (the free MIT-licensed local tool with no cloud transcription path at all), and the TurboScribe alternatives guide (whose safety section covers a cloud file-transcription peer that is well-encrypted but stores your uploads until you delete them). For the cross-product privacy reference covering Otter, Fireflies, Granola, and the rest of the meeting-transcription peer set, see our AI Tool Privacy Tracker. For the architectural framing, see the voice data privacy guide, the cloud vs. local dictation guide, the offline dictation privacy on Mac explainer, and our dictation and HIPAA guide. For regulated-industry framing, see Rev alternatives for lawyers and Rev alternatives for journalists.

Decided to leave? Otter subscriptions are non-refundable, so switching from Otter to Voibe Work covers the time left on your paid plan with free Voibe Work, plus a bonus month, up to 12 months.