Resource
Most “legal transcription software” pages compare accuracy, turnaround, and price, and leave the question bar regulators now ask first to a security page: where does the privileged audio go, and who can use it? Here’s a map of the category — what needs a human, what needs software, what recent ethics opinions require, and what the software’s architecture must look like when the recording is privileged.
Quick answer
Certified transcripts are a human service, not a software feature. When the transcript itself must be evidence — proceedings, certified deposition transcripts — you hire a certified transcriptionist or court reporter. Software can produce a draft, but the certification is a person’s.
Everything else is a software job, and architecture is the buying criterion. Client meetings, dictated memos, interview prep, internal case discussions: software transcribes them instantly. But cloud transcription tools put a third party inside privileged conversations. On-device tools — where audio is transcribed and stored on your own machine — are the only architecture where the transcription step involves no outside party at all.
1. Court-grade transcripts. Human, certified, formatted to jurisdiction rules. Budget for a service; this category isn’t what software is for.
2. Working transcripts of privileged material. Client calls, strategy discussions, dictated case notes. Speed matters, but confidentiality governs: this is where the vendor-in-the-loop question from our privilege analysis applies with full force. ABA Formal Opinion 512 requires understanding a tool’s data handling before client information goes in — an analysis that gets much shorter when the transcription never leaves your machine.
3. Non-privileged volume. Public hearings, recorded CLEs, marketing content. Any decent transcription tool works; pick on price and convenience.
ABA Formal Opinion 512 (July 2024) set the general rule for generative AI: understand the tool, protect client confidences, and check the output. The New York City Bar has since applied it to transcription specifically. Formal Opinion 2025-6 (December 2025) covers AI that records, transcribes, or summarizes client calls: tell the client in advance and get consent, find out where the provider stores recordings, for how long, whether it trains on them, and whether you can delete them, and review the transcript or summary before relying on it. Formal Opinion 2026-2 (August 2026) covers calls with non-clients and advises against recording them by default.
In practice that turns into a short checklist for any tool: where audio is processed, how long audio and transcripts are retained, whether your data trains the vendor’s models and whether you can opt out, which subprocessors touch it, whether you can delete it, and whether the vendor signs a BAA when health information is involved. Read the terms and acceptable use policy, not only the security page; the two do not always say the same thing. This is not legal advice, and other states have their own opinions.
Minutes is built for job #2. It records and transcribes on your own machine with on-device speech models, labels speakers, and stores everything as markdown files on your disk with owner-only permissions — organized, greppable, and readable by your AI assistant straight from local files, with structured action items filled in once you connect one. If that assistant or a summarizer is a cloud service, the meeting context you authorize goes to that provider; use a local model or skip summarization to keep the whole workflow on-device. It’s open source (MIT), so your security review can read the code instead of a vendor questionnaire.
Where it is not the tool: certified transcripts (job #1 — hire a human), jurisdiction-formatted verbatim output, or medical-legal templating. And it doesn’t change your own obligations — recording consent, device encryption, matter-based access control stay with you, where they already live.
Next step
Informational, not legal advice. Certification requirements and consent law vary by jurisdiction — confirm with your ethics counsel.
What disclosure to a vendor does to privilege.
Consent law by state, before the transcript exists.
The clinical parallel to the same confidentiality problem.
On-device options, where nothing is disclosed to a third party.