IT approval

My company blocks AI notetaker bots. What can I use?

Start by asking what the policy forbids. Most bans target bots that join calls and services that keep recordings in a vendor's cloud. A recorder that runs on your computer avoids both, but it still records people, so it needs the same approval and the same notice to participants. Here is what IT should check before saying yes.

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 botRecorder on your computer
Joins the callYes, as a participantNo
Where audio is processedThe vendor's serversYour computer
Account and retentionA vendor account, under the vendor's termsNo account; local files under your settings
Visible to other participantsUsually, by nameNo, so you have to tell them
Visible to meeting adminsYesNo

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:

  1. Where does meeting audio go? With the built-in models, recording, transcription, summaries, and search run on the computer. 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.
  2. 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. On Windows and Linux, the app also downloads a pinned llama.cpp runtime from GitHub once. A server off the computer receives meeting context only after the user approves that exact origin.
  3. Accounts and telemetry. None. There is no sign-in, analytics service, or telemetry backend.
  4. Storage. Recordings, transcripts, and the search index are ordinary files and SQLite under the user's account, so disk encryption (FileVault, BitLocker, or LUKS) 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.
  5. 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.
  6. Ways data can leave. Markdown exports and the Obsidian and Logseq note 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.
  7. Code and builds. The source is public under GPLv3, with Autocomplete code ported from Cotabby under AGPLv3. Mac releases are signed with a Developer ID and notarized by Apple, and install from the DMG or Homebrew. The Windows build (alpha) is a per-user installer or a portable zip, neither code-signed yet, so SmartScreen warns before it runs. The Linux build (alpha) comes as .deb, .rpm and Arch packages or an archive with an install script. On every platform, updates are signed and install only when the user chooses Install and Relaunch. Any version can be built from source.

What it doesn't have

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.

FAQ

Questions about this guide

Will Teams, Zoom, or Meet show that LokalBot is recording?

No. It doesn't join the call, so the meeting app has no participant to show. That is why telling people is up to you.

Is a local recorder allowed if my company bans AI notetakers?

Only if the policy allows it, so ask IT or your manager. A local recorder changes where the data goes, not the fact that people are being recorded.

Can IT confirm that meetings never leave the computer?

Yes. The source code is public, and the network test above shows what the app connects to while it records, transcribes, and summarizes with the built-in models.

Try it locally

Meeting notes that stay on your computer by default.

Free, open source, and no account. For Mac, with Windows and Linux in alpha.

Download for macOS

Apple Silicon · macOS 15+ · or with Homebrew: brew install --cask stevyhacker/tap/lokalbot

macOS · Windows · Linux (alpha) · requirements