Otter.ai Review for Lawyers
Otter.ai is one of the best-known meeting notetakers on the market. It transcribes calls, summarizes them, extracts action items, and increasingly layers an AI chat on top of your meeting history. For general business use it is genuinely useful. For law practice, the analysis is more complicated, and the answer turns almost entirely on where your client's words end up living.
This review is written for practicing lawyers evaluating whether to point Otter at client calls, depositions, witness prep sessions, or internal strategy meetings. It focuses on architecture and ethics rather than UI polish.
Disclosure: Basil, which publishes this review library, competes with Otter.ai in the meeting-notetaker category. Basil is a fully on-device notetaker built for lawyers, so we have a point of view. We have tried to keep this review factual and to praise what Otter genuinely does well.
What Otter.ai Actually Does
At its core, Otter is a cloud transcription and meeting-intelligence service. You can record audio directly in the mobile or web app, upload files, or authorize the "Otter Assistant" bot to join Zoom, Google Meet, or Microsoft Teams calls as a participant. The service returns a searchable transcript with speaker labels, an AI-generated summary, and extracted action items. A chat interface lets you query across the corpus of everything Otter has ever transcribed for you.
The strengths are real. Transcription accuracy on clean English audio is competitive with the best in the category. Speaker separation works well once the model has heard a voice a few times. The summaries are readable and the mobile app is fast. If your goal is capturing a product roadmap meeting or a sales call, Otter delivers.
The relevant product tiers, integrations, and features are documented on Otter's pricing page and help center.
The Confidentiality Lens
This is the section that matters. When you record a client meeting in Otter, the audio and resulting transcript travel to Otter's cloud infrastructure, are stored there, and are processed by Otter's models and (per its policies) subprocessors. That is the architectural fact from which every ethics question flows.
Where the data lives. Otter's privacy policy and terms of service describe cloud storage of audio, transcripts, and derived data. Retention is not user-configurable in the same granular way it is in some enterprise legal tools; deletion is available, but the default is indefinite retention on your account.
Model training. Otter has historically used de-identified user content to improve its models. The exact opt-out mechanics have shifted over time, and the current controls are described in its privacy policy. For a lawyer, the important point is architectural: content leaves your device, is stored, and — absent affirmative configuration and, ideally, contractual carve-outs — may be used in ways beyond simply returning your transcript.
Subpoena surface. Because Otter holds the audio and transcript, a subpoena served on Otter can reach the content of your client's meetings. That is not hypothetical: any cloud vendor holding readable client data is a potential third-party discovery target. The mitigations are contractual (a business associate or data processing agreement narrowing use and requiring notice of legal process) and architectural (not sending the data in the first place).
DPA and BAA. Otter offers a Data Processing Addendum for business and enterprise customers. HIPAA BAAs are handled through enterprise sales rather than being available on self-serve plans. If you are on the free or individual Pro plan, you are operating under the standard consumer terms, which is not a posture most bar counsel would recommend for privileged content.
The Brewer litigation. In 2025, a putative class action, Brewer v. Otter.ai, was filed in the Northern District of California alleging that Otter recorded and processed meeting audio in ways that violated state wiretap and privacy statutes, and that meeting participants who never signed up for Otter were captured without adequate consent. The case has been covered by Reuters. Whatever its ultimate merits, the theory of the case — that a bot silently joining a call to record other humans is a legally fraught act — is squarely relevant to lawyers, because you are the person responsible for consent on your calls.
Ethics-Opinion Fit (ABA 512)
ABA Formal Opinion 512 (July 2024) is the current baseline for generative-AI use by lawyers. It does not prohibit cloud AI tools, but it requires the lawyer to understand, at a reasonable level of detail: what the tool does with input data, whether inputs train models, who at the vendor can access content, retention, and the terms governing all of the above. It also reiterates Model Rule 1.6 confidentiality duties and, for meaningful disclosures of client information to a third-party AI vendor, points toward informed client consent.
What that means for Otter specifically:
- Free and individual Pro plans are difficult to square with Opinion 512 for privileged content, because you have neither a negotiated DPA nor enterprise-grade controls.
- Business and Enterprise plans with a signed DPA, training opt-outs affirmatively configured, and a documented retention policy are a more defensible posture, though still cloud-based.
- Client-facing disclosure and consent become important. NYC Bar Formal Opinion 2025-6 (Dec 2025) reinforces this direction for New York practitioners, and other states are moving similarly.
- Consent from other participants on the call is a separate obligation. Two-party-consent jurisdictions (California, Illinois, Massachusetts, Pennsylvania, Washington, and others) make silent bot recording legally risky independent of any privilege question.
None of this means Otter cannot be used ethically. It means the burden of configuration, disclosure, and documentation sits on you, and that burden is non-trivial.
A Note on Privilege in the Age of Cloud AI
In US v. Heppner (S.D.N.Y. Feb 2026), Judge Rakoff held that a litigant's chats with a public AI platform were not privileged. That case involved a party talking to a chatbot, not a lawyer using a transcription vendor, and the doctrine on vendor confidentiality is different — lawyers routinely use cloud vendors without waiving privilege where a proper agreement is in place. Still, the direction of judicial thinking is worth noticing: courts are increasingly willing to treat interactions with AI systems as ordinary third-party disclosures unless the lawyer has done the work to make them otherwise. West Technology Group v. Sundstrom (D. Conn. 2024) similarly signals that courts will scrutinize AI-adjacent practices when they surface in discovery.
The practical takeaway is not that Otter waives privilege — it does not, standing alone — but that the architecture increases the number of places a diligent adversary or regulator can look. For lawyers who prefer to shrink that surface, an on-device option like Basil is worth evaluating alongside Otter for meeting capture specifically.
Pricing and Who It's For
Otter offers a free tier with monthly transcription limits, an individual Pro tier, a Business tier with admin controls and higher limits, and an Enterprise tier that unlocks SSO, advanced security controls, and negotiated agreements. Current numbers are on the pricing page. For a solo or small firm, the individual tiers are attractively priced; for a firm serious about using Otter on client matters, Business or Enterprise with a DPA is really the only defensible entry point.
Otter is a strong fit for: internal firm operations meetings, marketing and BD calls, vendor calls, CLE and training sessions you want transcribed, and other content where client confidences are not at stake. It is a weaker fit for: privileged client conversations, witness interviews, deposition prep, and any recording where opposing parties or third parties are on the line and have not consented to a recording bot.
Verdict
Otter.ai is a well-built general-purpose notetaker with a real accuracy story and a mature product. For lawyers, the question is not whether it works but whether its cloud architecture, retention posture, training-data history, and current litigation exposure are acceptable given what you plan to record. On non-privileged content and with the right plan and configuration, it can be. On the privileged core of legal work, most lawyers will want either a heavily configured enterprise deployment plus client consent, or a different tool entirely.
| Pros | Cons |
|---|---|
| Strong transcription accuracy on clean audio | Cloud storage of audio and transcripts by default |
| Good speaker separation and summaries | Training-data use history requires careful opt-out |
| Mature integrations with Zoom, Meet, Teams | Subpoena surface: vendor holds readable content |
| DPA available on business/enterprise tiers | Pending Brewer class action raises consent questions |
| Reasonable pricing across tiers | Bot-joins-call model is risky in two-party-consent states |
This review is for information only and is not legal advice.
Frequently asked questions
Can I ethically use Otter.ai for client meetings under ABA Opinion 512?
Possibly, but only with meaningful work on your part. Opinion 512 requires you to understand the vendor's data handling, training use, retention, and access. In practice that means a Business or Enterprise plan with a signed DPA, training opt-outs configured, documented retention, and — for meaningful disclosures of client information — informed client consent. Free and individual tiers are difficult to square with Opinion 512 for privileged content.
Does Otter.ai train its models on my meeting data?
Otter has historically used de-identified user content to improve its services, with opt-out mechanisms that have evolved over time. The current controls are described in Otter's privacy policy. Even with opt-out, your audio and transcripts still reside on Otter's cloud infrastructure, so training use is only one of several confidentiality considerations.
What is the Brewer v. Otter.ai lawsuit about?
Brewer v. Otter.ai is a putative class action filed in 2025 in the Northern District of California alleging that Otter's meeting bot recorded and processed audio in ways that violated state wiretap and privacy statutes, particularly as to non-users who were captured on calls without adequate consent. It has been reported on by Reuters and remains pending. Regardless of outcome, it highlights consent obligations that fall on the person deploying the bot.
Can a subpoena to Otter.ai reach my client's meeting content?
Yes, in principle. Because Otter stores audio and transcripts in readable form, a subpoena or other legal process served on Otter can reach that content. Mitigations include a negotiated DPA requiring notice of legal process, minimizing what you record, aggressive retention settings, or choosing an architecture where the vendor never holds the content in the first place.
Is Otter.ai HIPAA compliant for law firms handling PHI?
Otter offers HIPAA support through enterprise agreements that include a Business Associate Agreement; it is not available on free or individual plans. If your practice touches protected health information — for example, in personal injury, medical malpractice, or ERISA disability work — a signed BAA is a prerequisite before pointing Otter at that content.
What are better-fit alternatives for privileged legal calls?
Lawyers concerned about cloud exposure often consider on-device notetakers that process audio locally without uploading it to a vendor, such as Basil. Others rely on their existing videoconferencing platform's built-in recording under an existing enterprise agreement, then transcribe selectively. The right answer depends on your jurisdiction's consent rules, your client agreements, and the sensitivity of the matter.
Meeting notes with no server to subpoena
Basil transcribes and summarizes entirely on-device — privilege-safe by architecture. See Basil for Law →
This review is for information only and is not legal advice.