A privileged conversation, sent to a server neither party chose.

That is the actual trade a general-purpose meeting notetaker asks a law practice to accept: a client call gets transcribed and summarised somewhere the client never agreed to and the practice doesn't control, in exchange for not having to type notes while the call runs. For most meetings that trade is a reasonable one. For a client consultation, a deposition prep call, or any conversation where confidentiality is the actual job, it's worth asking whether the recording needs to leave the room at all.

What a cloud notetaker asks the practice to accept

Otter and Fireflies both join a call as a named participant to build their transcript, and both do the transcription and summarising on a server the vendor operates — a real convenience for a firm that never minds a bot on the roster of an internal meeting, and a harder thing to accept for a client call specifically. Granola doesn't put a participant in the call, but the recording still leaves the Mac to be transcribed and summarised in the cloud. Neither answers the actual question a confidentiality-conscious practice is asking, which isn't "does a bot join" but "where does the recording go."

Recording that never leaves the machine that made it

Coii AudioNotes records the microphone and the system audio the Mac is already carrying, as two separate tracks, and transcribes and summarises entirely on that same Mac. Nothing about the call — the audio, the transcript, the summary — is sent anywhere to produce any of it.

A summary written on the same machine as the call

A language model bundled inside the app turns the transcript into a short recap — a decision, an action, an open question — right after the call ends, on the same Mac that recorded it. Nothing about that step depends on a server being reachable, and nothing about it is sent anywhere either.

What this page is careful not to claim

Whether a recording made this way is privileged, or admissible, or how it should be handled under a specific jurisdiction's rules of evidence, is a real question this page is not in a position to answer — it depends on facts a search result can't know, and belongs with the practitioner's own professional judgment and counsel. What this page can state plainly is what the tool itself does: the recording, the transcript and the summary are produced on the Mac and none of the three is uploaded anywhere to get there.

What it deliberately doesn't do

There is no integration with a matter management system, a document management platform or a billing tool — nothing here files a call against a matter number automatically. There is no shared workspace an associate can browse without being sent the recording directly; each one lives on the Mac that made it, across up to three machines on one licence. It is not a certified court-reporting product, and it makes no claim to replace a stenographer for a deposition or a hearing. And it runs on macOS only, so a firm with paralegals or associates on Windows machines won't get the same tool across the whole team from this one alone.

The question a client call actually raises

A client rarely asks where a recording is stored, but the concern sits underneath the relationship whether it's voiced or not — the same reason attorney-client privilege exists as a doctrine in the first place. A cloud vendor's privacy policy can describe who can reach a recording and under what circumstances, but that document lives somewhere neither attorney nor client reads before the call starts. Recording, transcribing and summarising on the Mac that made the call sidesteps the question rather than needing a reassuring answer to it: there is no third server in the chain to describe.

Who this genuinely isn't built for

A larger firm running case management through a shared system, where a partner needs to pull up an associate's call notes without being sent the file, has a real workflow this tool doesn't attempt to replace — that kind of shared access is exactly what a practice management platform is for. This is written for the version of practice where the call is mostly one attorney's, and where the client's confidence that nothing about the conversation went to a third party matters more than a shared dashboard.

Setting it up is smaller than the decision to switch

The first launch asks for two macOS permissions — microphone access and permission to record system audio — the same prompt any Mac app requesting audio capture triggers, and that's the whole of it. No account to register, no workspace to configure, nothing to connect before the first client consultation can be recorded. The larger part of adopting this in a practice is usually not the software itself but the practice's own decision about which calls get recorded and how that's communicated to a client, which is a judgment call this page leaves entirely to the attorney.

Recording is a decision made call by call

Nothing here records automatically the way a bot logs into a scheduled meeting on its own. Recording a client call is a deliberate action taken for that specific call, which means a practice that wants some consultations recorded and others not gets that simply by choosing not to start it — not by configuring an exception into a calendar integration that was going to record everything by default otherwise.

Why a transcript is worth having, beyond the notes taken live

Notes taken by hand during a client call capture what the attorney thought was important in the moment, which is not always the same thing the client actually said, or the exact way they said it. A transcript sitting alongside those notes affords a chance to check the two against each other afterward — useful on the calls where a precise date, a specific figure or an exact phrase turns out to matter more on review than it seemed to during the call itself.

Why a transcript settles more than a memory does

A dispute over what a client agreed to on a call three weeks ago is a weak argument when it comes down to one side's recollection against the other's. "The transcript shows this at this timestamp" is a stronger position than "my notes say," and it only exists if the call was actually recorded rather than summarised from memory in the minutes after it ended. That's a small advantage on most calls and occasionally the reason a disagreement about scope or instructions gets resolved without it turning into something larger.

What a full caseload makes visible over time

A single call's recap is useful that afternoon; a searchable archive of them becomes useful differently months into a matter, when the question is what a client said in an early call that's since become relevant again, or whether a detail mentioned once six weeks ago was ever followed up on. Reconstructing that from memory across a full caseload isn't realistic past a handful of active matters; a transcript sitting on the attorney's own Mac, searchable by keyword, turns that into a question with an actual answer.

What actually changes across a full matter

Nothing about how a client call runs changes — same conversation, same platform. What changes is what's available months into a matter, when opposing counsel or a client references something said on an early call and the accuracy of the response depends on whether that call is still just a memory or an actual transcript, searchable on the attorney's own Mac rather than reconstructed from whatever handwritten notes survived.

Who this genuinely isn't built for, said a second way

A solo practitioner or a small firm where the attorney handling the call is also the one who needs the record of it is exactly who this is built for. A larger firm with associates, paralegals and a shared matter management system has a real reason to stay with tools built around that infrastructure — not because a single call is handled worse here, but because the value of a shared system comes specifically from the sharing this tool deliberately doesn't do.

The first weeks after switching

The first few client calls after moving off a bot-based tool tend to feel slightly unfamiliar for one specific reason: the habit of checking the participant list to confirm the bot joined before the conversation starts. That habit fades within a couple of weeks, and what replaces it is simpler — press record, run the call, and find the transcript and recap waiting on the attorney's own Mac once it ends, the same outputs a bot-based tool used to produce, without anything having joined to produce them.

What a client remembers about the call

A client rarely remembers the exact terms discussed, but they do remember whether the attorney seemed present in the conversation or distracted by typing. Recording instead of transcribing live keeps the attorney's attention on the client rather than on a notepad, which matters as much for the relationship as it does for the accuracy of the eventual file note.

Who this is written for, plainly

Not a large firm standardising matter documentation across dozens of attorneys and paralegals — that's a practice management decision, not a single app's job. This is written for the solo practitioner or small firm whose client calls currently get either typed live, at the cost of attention the client can hear in the pauses, or reconstructed from memory afterward, and who wants a transcript worth trusting without a recording that has to leave the Mac to produce it.

What it costs, what it runs on

Coii AudioNotes is $19, paid once, for three of an attorney's own Macs, with a 30-day trial needing no card and no account, and every feature unlocked from the first launch rather than gated behind a tier a solo practice would have to justify upgrading into. It runs on macOS 13 Ventura or later, Apple Silicon or Intel. Against Otter's $8.33–$19.99-a-month tiers, Fireflies' comparable subscription, or Granola's $14-a-month Business tier, the $19 is a one-time cost rather than a recurring one for as long as the practice keeps recording calls. Full comparisons here and here. A wider round-up of meeting notes apps for regulated work covers legal practice alongside the other professions with the same confidentiality requirement and is worth reading before a firm settles on a single tool for client calls, and a round-up of private meeting recorders covers the broader field a confidentiality-first search turns up. The broader case for a Mac-native meeting notes app, what an AI notetaker without the bot and a meeting recorder without a bot change about a client call, and what happens when a call takes place somewhere without a reliable connection, in offline transcription for Mac, all cover ground this page doesn't repeat, and each is worth a look before a firm settles on a single tool for recording client calls.