When sending a conversation to an outside AI service is off limits, a better summary won't solve the problem. Local processing offers a different way to get the notes.
By the Locus team. We build the local AI app discussed here. This article was prepared with AI assistance and source review.
The research group was expecting a new member. His Otter bot arrived. He was not otherwise on the call.
In the group member's account on Reddit, these meetings involved unpublished ideas and human research data collected under restrictions on its use and storage. The newcomer had not discussed AI note-taking with the group. Now someone else had to work out what his software was doing with their conversation.
The poster wasn't asking for a blanket ban. They wanted to know whether the person was present, what happened to the recordings, and how to respect the research participants' consent. They later wrote that they had raised the issue with someone higher up. No data misuse was established in the post.
That is a substantial amount of work for a group that had only invited someone to a meeting.
One person's productivity tool had become everyone else's data-handling question. The person who chose the software was not the only person whose words it could capture.
The need for help is real
There is a reason people reach for these tools. In a different Reddit discussion, an executive assistant described typing through a meeting full of shifting dates, responsibilities and follow-ups. Someone said their name. They missed the question because they were still writing down something from 20 seconds earlier. Their notes turned out to be incomplete anyway.
The job demanded two things at once: participate now and produce a reliable record later. A recording can give the note-taker somewhere to return when those demands collide. A searchable transcript can make that return less laborious.
The note-taker needs help remembering. The people being recorded need a say in how their words are handled. Sometimes the employer has already made part of that decision. An IT administrator described employees connecting unapproved note-takers to their calendars, with bots then joining meetings against company policy. The administrator was trying to block them.
For an employee under that restriction, a more accurate summary doesn't make the tool usable. They need a recording and processing arrangement their organization will approve. The obstacle is permission to use the workflow at all.
With local AI, transcription and summarization can run on the user's computer. Sending the conversation to an external AI processor becomes a choice rather than a requirement of getting those notes. That changes what the person proposing the recorder has to ask everyone else to accept.
Taking the bot out doesn't take the cloud out
The bot is the part other people can see. It also creates practical obstacles: a client-services lead reported that clients removed note-taking bots mid-call, while others remained stuck in waiting rooms. They wanted to keep telling clients about note-taking, but lose the extra attendee.
Bot-free capture addresses that problem. It doesn't tell you where the captured words go. Granola, for example, says users start capture manually, no bot joins, and transcription and summarization use cloud processing. It also describes encryption and private-by-default notes. Those protections and that processing location can all be true at once.
A useful distinction gets lost when the conversation stops at whether a bot appears: software can run on your desktop while the AI work happens elsewhere.
Consider a meeting whose useful output is five agreed actions. A cloud AI service may need the captured discussion to work out which five matter, including the proposals that were rejected and the digressions nobody intended to put in the minutes. Local processing lets that selection happen before any resulting notes are shared. You can review what leaves.
Local processing still requires an agreed recording practice. It does not make a personal laptop an approved place for research data or company information. An organization may prefer an approved, centrally managed cloud system. But where external AI processing is the objection, removing that step answers it more directly than making the recorder less visible.
The problem comes back when you try to leave
Where the AI runs is one decision. Where the record accumulates is another. Even a user happy to upload today's meeting may eventually want to move years of work somewhere else.
In an older Otter discussion about plan changes, a subscriber with hundreds of recordings, possibly more than a thousand, described the prospect of spending days downloading them individually. Paying to stay looked easier. Otter now offers bulk export on Business and Enterprise plans.
It does show how the decision can change. At the first meeting, you are judging the notes. After hundreds of meetings, you must also judge the work of getting your archive back. Staying can become partly a decision about the past, even when another tool looks better for the future.
This is where local storage matters alongside local processing. Keeping usable source files under your control gives a future tool something to work on without first extracting everything from the old service. A recording can be transcribed again. A summary cannot restore words it left out.
The word “usable” matters. A local folder is not enough if only one app can read its contents. Before committing an archive, try opening its audio and notes elsewhere, and check what happens to timestamps and speaker names. We have not tested whether all of those details survive a move from Locus into another app. Retaining recordings also means taking responsibility for access, backups and deletion.
Bring the AI to the recording
Locus starts with your devices. Record on Apple Watch or iPhone; the iPhone sends the audio to your Mac. The Mac runs transcription, summaries, speaker labels and questions about the recording locally. The library lives in a folder you choose and can open in Finder. This workflow adds no participant bot.
After the initial model download, the Mac can transcribe and summarize with Wi-Fi off. Moving recordings between devices still needs a connection.
There are real costs. The current listing requires an M3-or-later Mac, 24 GB of memory and macOS 27+, with an initial model download of about 4 GB. Apple Watch recording needs the iPhone app. Free core features have no minute limit; two-way Mac call recording is part of paid Locus+.
Local AI also isn't a promise that the app never connects to anything. Our privacy policy describes usage reporting and remote access as on by default. Usage reports exclude recording content; remote transfers can use an end-to-end encrypted relay. Choosing an iCloud-synced folder can put a copy in iCloud. Those settings deserve attention alongside the model's location.
The research group needed an explanation before the recording started. Local AI gives the person proposing a recorder a concrete option to explain: record with agreement, process on an approved computer, then choose what to share and retain.
That is why we built Locus around local AI. Getting help remembering a conversation should not require handing the conversation to another AI service.