recordist

Guide · for reviewers

An AI notetaker privacy checklist for IT, security and legal reviewers

Use this checklist to review any AI meeting notetaker before people at your organisation use it, whether it joins calls as a bot, records on a laptop or comes built into your meeting platform. Each section has the questions to send the vendor, what a complete answer covers and where vendors usually publish it.

Some organisations have already decided. Case Western Reserve University blocked third-party AI note-taker apps in its Zoom, Teams and Meet meetings from 12 September 2025. It said these apps often try to join future meetings by default, without the other attendees' consent, and that meeting content can go to third parties outside the university's systems (its notice, read 8 October 2026).

Tick each question as the vendor answers it. 56 questions. Your ticks stay in this browser only, if it allows that.

How to use it

  1. Decide the scope first: who will use the tool, and for which calls. Internal meetings, customer calls and interviews can need different answers.
  2. Send the questions in writing and keep the answers with the date. A published document, such as a DPA or a subprocessor list, counts for more than a sales call.
  3. Try the defaults on a trial account with a colleague who agrees to be recorded: what joins, what the others see, and who receives the notes.
  4. Review again at renewal, and when the vendor changes its terms or its AI providers.
  1. Where audio, video and transcripts go

    Start here, because every other answer depends on it. A notetaker may join the call as a participant, record on the user's own computer, or run inside the meeting platform, and each of these sends the conversation to a different place.

    Ask

    A complete answer
    A list of every place a recording, transcript or summary is written, with the company that runs it and the country it is in.
    Where to look
    The vendor's security or trust page, its data processing agreement (DPA) and any architecture paper.
  2. Retention

    Recordings and transcripts tend to outlive the reason they were made. Find out how long each kind of content is kept and who can change that.

    Ask

    A complete answer
    A table with each kind of content, its default period, the setting that changes it and who is allowed to change it.
    Where to look
    Help articles on retention, the admin guide and the deletion clause of the DPA.
  3. Who can see the recordings and notes

    Many notetakers send a summary to people after the call. Check who receives it by default, because a default that suits an internal stand-up may not suit a call with a customer or a candidate.

    Ask

    A complete answer
    The default sharing settings, the admin setting that restricts them, and the vendor's written policy on its own staff's access.
    Where to look
    Help articles on sharing, the admin guide, and the confidentiality and personnel sections of the DPA.
  4. Model training and AI providers

    An AI notetaker usually sends transcripts to a language model, and the model may be run by another company. Ask whether anyone trains on that content, and get the answer in the contract.

    Ask

    A complete answer
    The contract wording on training, and a list of the model providers with what each one keeps and for how long.
    Where to look
    The vendor's AI or privacy page, its terms of service, the DPA and its list of subprocessors.
  5. Bots that join calls

    A notetaker that joins from a person's calendar can arrive in meetings that person doesn't host, including meetings at other organisations, and keep coming back to a recurring series.

    Ask

    A complete answer
    The default joining behaviour, the admin control that limits it, and the steps a host takes to remove it.
    Where to look
    Help articles on automatic joining and calendar connections.

    If you run Zoom, Microsoft Teams or Google Meet, Keep notetaker bots out lists the settings each platform documents.

  6. Admin controls

    A tool IT can't manage tends to be used anyway, on personal sign-ups. Check what an admin can set centrally and what each user can override.

    Ask

    A complete answer
    A list of admin settings with their defaults, marked with the ones users can override.
    Where to look
    The admin guide and the page for business or enterprise plans.
  7. Deletion

    Deletion is only as good as the last copy. A request to remove someone's data has to reach the recording, the transcript, the notes and every copy made from them.

    Ask

    A complete answer
    The steps to delete each copy, and how long it takes to disappear from backups.
    Where to look
    Help articles on deleting, and the deletion and return clause of the DPA.
  8. Subprocessors

    The companies a vendor relies on handle your data too. Meeting content and billing details often go to different ones.

    Ask

    A complete answer
    A list with each subprocessor's purpose and location, marked with the ones that handle meeting content.
    Where to look
    The vendor's subprocessor page and its DPA.
  9. Security and incident history

    Past incidents, and how the vendor handled them, say more than a list of badges. Ask for both.

    Ask

    A complete answer
    Dates and short accounts of past incidents, the notification period in the contract, and the latest audit report with the period it covers.
    Where to look
    The trust or security page, the status page, the DPA, and a news search for the vendor's name with "breach" or "incident".
  10. Accuracy and how the notes are used

    Notes written by AI can leave things out or credit words to the wrong person. That matters most when the notes feed a decision about someone.

    Ask

    A complete answer
    The product's own guidance on checking notes, and your organisation's rule on using them in decisions.
    Where to look
    The vendor's help on accuracy and speaker labels, and your own HR and AI policies.

Questions

What should an AI notetaker policy cover?
Which tools are approved, which meetings may be recorded, how people on the call are told, how long recordings and notes are kept, who may share them, and whether notes may be used in decisions about people. The ten areas on this page are the questions to settle with each vendor before a tool goes on the approved list.
Do the notes built into Zoom, Teams or Meet need the same review?
They need a shorter one. They run under the agreement and admin settings your organisation already has with that platform, so start with the questions on retention, sharing, consent and model training for the AI features. The guide to built-in meeting notes sets out what each platform documents.
Do notetakers that record on the user’s own computer need a review?
Yes. Nothing appears in the participant list, so telling the others is up to the user, and the meeting platform’s settings can’t see the recorder. Ask where the transcript is processed and stored, because some of these apps upload to the vendor’s servers and some keep everything on the device, and ask whether IT can enforce settings on the computers it manages.
Who is responsible for getting consent to record?
Read the vendor’s terms to see whom they make responsible. Recording laws differ by place: some need everyone on the call to agree, and some need only one person. Recording law by place has general information, and your lawyer can tell you what applies to your calls.
How often should we review a notetaker again?
At each renewal, and whenever the vendor changes its terms, adds a subprocessor or AI provider, or ships a feature that changes who receives the notes or when the notetaker joins. Ask the vendor how it announces those changes.
Can I send these questions to a vendor?
Yes. The button at the top copies every question as plain text, ready for an email or a security questionnaire. This page sends nothing anywhere, and the ticks you make are kept only in this browser, if it allows that.

How Recordist answers it

We make Recordist, so here are its answers to the same questions, for version 0.3.10. The summary for reviewers has the longer version, written to be forwarded, and the managed settings page has what IT can enforce on the Mac computers it manages.

Where audio and transcripts go
Recordist is a Mac app. It records the Mac's microphone and sound output into a data folder on that Mac, transcribes there with Whisper and, with the built-in engine, writes the notes there too. Audio never leaves the Mac. Recordist doesn't encrypt these files itself, so they are encrypted at rest when FileVault is on.
Retention
Audio is kept 30 days by default, and each person can choose Forever, 90, 30 or 7 days, or deletion right after transcription. Delete meetings after removes whole meetings and is off by default. On managed Mac computers, MaxRetentionDays caps both.
Who can see them
The person using the Mac, and programs running under that macOS account. There is no account, no shared library and no link sharing, and the company that makes Recordist receives no audio, transcripts or notes. Exports are copies the person makes and sends.
Model training
Recordist receives no meeting content, so it has none to train on. The built-in engine runs open models on the Mac. If a person connects their own Anthropic or OpenAI-compatible key, the transcript goes to that provider under their account and its terms, and the Privacy Ledger records each request.
Bots
Recordist never joins a call, so nothing is added to the participant list.
Consent
When a call is detected, a card asks the person using Recordist "Record this meeting?", and nothing is recorded until they answer, unless they added that app to the auto-record list, which is empty by default. The Record now button in the main window starts at once. Recordist doesn't tell the other people on the call or ask them, so the user has to.
Admin controls
IT can enforce nine managed settings with a configuration profile from its MDM, such as keeping notes on the Mac, turning off cloud AI keys and capping retention. There is no admin console, single sign-on or account, and Recordist reports nothing back to IT.
Deletion
Delete meeting…, Delete audio…, Delete all my data and Remove everything and quit all work on the Mac, and there is no server copy to delete. Exports saved to a folder the person chose stay there until they delete them.
Subprocessors
No company receives meeting content by default, Recordist included. The app downloads its speech model, notes engine and notes model from Recordist's media host, Hugging Face, GitHub and the Ollama registry, and those downloads carry no meeting content. The privacy policy lists the processors for the website, beta requests and purchases.
Security and incidents
Recordist keeps no meeting content on a server. Fixes are listed in the changelog, and the security page names known issues and what to update, such as the optional gateway, which didn't check the token on its HTTP and A2A ports before version 0.1.5. Recordist has no SOC 2 report and hasn't had an independent security audit. Reports to [email protected] are acknowledged within 3 business days.
Install and platforms
Early builds aren't notarised by Apple yet, so macOS asks once to allow the first launch, and on managed Mac computers IT may need to allow it. Recordist needs a Mac with Apple silicon and macOS 14.6 or later. Windows and Linux next.
Accuracy
Notes can be wrong, and they carry a reminder to check them against the recording. The other side of a call shares one label, and in a room every voice is labelled You.

This page is general information to help with a review, and it isn't legal advice. The one outside source is the Case Western Reserve University notice linked above, read on 8 October 2026. If something here is wrong or out of date, write to [email protected] and we will correct it.