Why the bots get blocked
A notetaker bot is a separate participant. It is often added through calendar access, can join meetings its owner doesn't attend, shows up in client and partner calls, and sends the audio to the vendor's servers, where retention and model-training terms are the vendor's to set. Meeting platforms let admins block or flag these bots, and many companies now do.
What a local recorder changes, and what it doesn't
| Notetaker bot | Recorder on your Mac | |
|---|---|---|
| Joins the call | Yes, as a participant | No |
| Where audio is processed | The vendor's servers | Your Mac |
| Account and retention | A vendor account, under the vendor's terms | No account; local files under your settings |
| Visible to other participants | Usually, by name | No, so you have to tell them |
| Visible to meeting admins | Yes | No |
The last two rows matter. A recorder nobody can see is not a way around a ban, and using one where recording isn't allowed breaks the same rules a bot would. Recording laws and client contracts apply either way. If the policy is about recording itself, no tool changes the answer.
A checklist IT can work through
Using LokalBot as the example:
- Where does meeting audio go? With the built-in models, recording, transcription, summaries, and search run on the Mac. To verify it, download the models, select the built-in backend, turn off automatic update checks, and watch network traffic while you record, transcribe, and summarize.
- What else uses the network? Model downloads from Hugging Face or the model's publisher, update checks against GitHub Releases (which can be turned off), and any remote model server a user configures. A server off the Mac receives meeting context only after the user approves that exact origin.
- Accounts and telemetry. None. There is no sign-in, analytics service, or telemetry backend.
- Storage. Recordings, transcripts, and the search index are ordinary files and SQLite under the user's account, so FileVault and your device policies protect them at rest. Day tracking saves app names and window titles by default; screen text and encrypted screenshots are separate opt-ins that expire after 14 days by default.
- Consent behavior. On a fresh install, LokalBot asks through a notification before it records a detected meeting. Automatic recording is a setting the user has to turn on.
- Ways data can leave. Markdown and Obsidian exports are plain files in a folder the user picks. Agent access through the CLI and MCP server, and the optional Agent Mode, are off by default; once enabled, an agent's own provider receives what the agent reads.
- Code and builds. The source is public under GPLv3. Releases are signed with a Developer ID and notarized by Apple. Install from the DMG or Homebrew, or build from source.
What it doesn't have
- Central administration. There is no admin console, central policy, or documented managed settings. Each user configures their own copy, so control comes from your device management: allow or block the app, require FileVault, and set backup rules.
- Other platforms. It runs only on Apple Silicon Macs with macOS 15 or later.
- A shared workspace. Notes stay on one Mac unless the user exports them.
Asking for approval
Send IT the privacy policy, the source repository, and this checklist, and offer to run the network test together on a short call. Once it's approved, tell people when you record, the same way you would if a bot were in the meeting.