Guide for law firms

AI meeting transcription and client confidentiality

By Josef Long, founder of VaultScribe. Published October 17, 2026. This is general information, not legal advice.

A lawyer's duty to protect client information is broader than attorney-client privilege, and AI meeting tools touch it in ways that are easy to miss. This guide explains the duty in plain language, where AI transcription can put it at risk, and a checklist a firm can adapt.

The duty is about more than privilege

The ABA's Formal Opinion 512 (July 29, 2024) reminds lawyers that under Model Rule 1.6 they must keep confidential all information relating to the representation of a client, regardless of its source, unless the client gives informed consent or another exception applies. Privilege is a narrower rule about what can be forced out in a proceeding. A recording of a client call can raise both questions at once. Read the opinion. State rules vary, so check yours.

Where AI transcription can put confidentiality at risk

• Audio and transcripts stored by a vendor. Anything held on a third party's servers is information the firm no longer fully controls.
• A bot in the meeting. Participants outside the firm may not know a recording tool is present. Lawsuits have alleged that some notetakers recorded people without consent. These are allegations, not findings.
• Use for training. Opinion 512 notes that when a tool learns from what lawyers put into it, information from one client could influence output for others. Ask whether your content is used for training.
• Voiceprints. Speaker identification by voice can create biometric data, and an Illinois lawsuit alleges exactly that against one vendor. See the National Law Review, January 8, 2026, "Illinois BIPA Suit Targets AI Note-Takers- Practical Lessons for Meeting Transcription." Read the article.
• Broad access inside the firm. A shared tool without matter-level walls can show a lawyer information from a matter they are screened from.

A checklist a firm can adapt

1. Keep an approved list of tools. Decide which AI tools may touch client information, and who approves additions.
2. Decide where recordings may live. On firm machines, on a firm server, or with a vendor under a written agreement.
3. Write down consent practice. Recording-consent laws differ by state, and some require every participant's agreement. Say how the firm tells participants, on every call.
4. Set retention and legal holds. Know how long recordings and transcripts are kept, and who can place a hold.
5. Review output. Treat machine transcripts and summaries as drafts. A lawyer checks anything relied on, and quotes are checked against the recording.
6. Talk to the client. Opinion 512 discusses informed consent and says generic boilerplate in an engagement letter is not enough in many cases.

How VaultScribe approaches it

VaultScribe is pre-release and not yet available to buy or download. It is designed so recordings stay on the firm's own machines, no bot joins the call, matter walls apply to every person and tool, and every outside request is in a log. I am looking for founding design partners, with a non-binding letter of intent and terms agreed on a call.

Become a design partner

This page is general information and is not legal advice. Transcripts from any tool are machine transcripts and are not certified. VaultScribe has not yet had an independent security audit.