A meeting participant called “Notetaker” tells you surprisingly little. It might be a calendar guest, a built-in feature of the call platform, or a separate recorder that never appears in the participant list. Those cases require different controls. A name match is a starting point for review.
We published a dataset of 90 meeting notetakers at Meetful. The records describe how each tool joins and link to the vendor instructions. You can download the JSON or CSV.
Check how a tool joins
If it joins as a participant, start with the participant list and the calendar invite. Removing it from the call and changing future auto-join settings are separate actions.
If it’s built into the platform, look for the relevant recording, transcription, or assistant controls for your role and account.
If it records locally, the participant list may offer no signal. Ask how notes are being captured and agree on what can be shared before the conversation starts.
Pull the records into a review tool
curl -fsSL https://fliclabs.github.io/ai-notetakers/notetakers.json | jq -r '.notetakers[] | [.name, .kind, .page] | @tsv' For an internal directory, keep the source URLs next to each entry. Treat a missing value as unknown. If you flag a participant by name, make the alert reviewable by a human: names can change, and some recording methods never show up as a participant.
I build Meetful. The browser directory includes the per-tool instructions and vendor sources for checking individual cases.
AI assistance was used to draft this article.
