Resource
Privilege has one load-bearing wall: confidentiality. An AI notetaker that streams your client conversations to a vendor’s cloud puts a third party inside that wall, and nobody — not the vendor, not the bar, not yet a court — has given lawyers a clean answer on what that does to privilege. Here is the current state of the analysis, and the architectural choice that makes most of it moot.
Quick answer
Waiver is fact-specific and unsettled — but the risk vector is not. Privilege requires confidentiality; a cloud notetaker is a disclosure to a third party under that vendor’s terms. Whether that disclosure defeats privilege will depend on the vendor’s data handling, your diligence, and a judge — three things you don’t fully control.
On-device transcription removes the third party entirely. A transcript generated and stored on the attorney’s own machine involves no outside disclosure to argue about. The confidentiality question collapses back to the one you already answer daily: is your laptop secure?
The closest authoritative guidance is ABA Formal Opinion 512(July 2024) on generative AI. Its core demand is unglamorous: before client information goes into an AI tool, the lawyer must actually understand the tool’s data handling — who can access inputs, whether they train models, how long they’re retained — and in some cases obtain informed client consent. Competence about the tool is part of the duty of confidentiality, not separate from it.
Applied to meeting notetakers, that means reading the vendor’s terms the way opposing counsel would: Does the vendor’s staff have access to transcripts for “service improvement”? Are recordings used for model training, by them or their subprocessors? What happens to your clients’ conversations under a subpoena served on the vendor? Every “yes” and “unclear” is material you may someday have to defend.
Separately from privilege, recording consent law applies: some states require all-party consent to record a conversation, others one-party. For client meetings, explicit consent is the professional norm regardless of what your state minimally permits — the RCFP guide linked below has the state-by-state map.
If you’re evaluating any cloud notetaker for client work, get written answers to:
Notice what this list is: a due-diligence file you must build and maintain for a vendor whose entire involvement is optional.
Every question above exists because the conversation leaves your machine. Run transcription on-device instead, and the third party disappears: no vendor receives the communication, no terms of service govern it, no subpoena served on a vendor can reach it, and there is no “service improvement” clause to parse. That is the design of Minutes — open source, on-device transcription and diarization, transcripts as markdown files on your own disk with owner-only permissions. The privilege analysis returns to familiar ground: secure the device, control access by matter, and document client consent to recording.
What on-device does notdo: it doesn’t satisfy consent law for you, secure an unencrypted laptop, or make a transcript less discoverable in litigation — your own files are always discoverable. It removes the third-party disclosure question, which is the one you can’t fix after the fact.
Next step
This page is informational, not legal advice. Privilege and consent questions are jurisdiction- and fact-specific — consult your ethics counsel before adopting any recording tool for client work.