AI Notetaker Policy for Companies: A Template You Can Adopt This Week

Notepik team8 min read

Somebody on your team is probably already using an AI notetaker. It may be on an approved account, or a guest may have brought one to your call, or an employee may have connected one to their calendar months ago and forgotten. Security teams call software that handles company information without anyone having reviewed it "shadow AI", and meeting notetakers are one of the easiest ways for it to spread: a bot joins a call from a calendar link, and each new person it meets is invited to give it access to their own calendar too.

A ban rarely works, and it takes away something people value. A short written policy works better. It names the tools that are allowed, says what attendees are told, limits who sees the notes and sets when they are deleted. This article explains the decisions a policy has to make, suggests defaults for common meeting types, and gives you a template to copy. It is a starting point, not legal advice, so have a lawyer look at it if your work involves regulated information.

Why write one now

Lawsuits have made notice and consent a business question. Class actions in California accuse well-known notetakers of recording people who never agreed to it. We summarise what is alleged, and what is not decided, in our guide to the Otter.ai and Granola cases.

Tools spread from person to person. One person connects a notetaker to their calendar, it joins a call, and the other attendees are offered the same. Without a policy, nobody decides which of them is allowed.

Notes are records. A transcript holds names, figures and things said off the cuff. Where it is stored, who can read it and how long it stays are decisions, and they are easier to make once than to untangle later.

The seven decisions a policy has to make

  1. Which tools are approved. One list, kept by one person.
  2. When recording is allowed, and when it is not. Defaults by meeting type, with a way to ask for an exception.
  3. What attendees are told. Before recording starts, in words, not only through a bot in the participant list.
  4. Who can see the notes and share them. Attendees and people who need them, not the whole company by default.
  5. How long notes are kept. A period for each type of meeting, and a person who deletes them.
  6. What the vendor may do with the content. In particular, whether it may train models on it.
  7. What to do when something goes wrong. Who to tell about an unapproved tool or a recording nobody announced.

Which meetings to record

These are suggested defaults, to be adjusted to your industry and the laws that apply to you.

MeetingSuggested defaultWhy
Internal planning, standups, retrospectivesRecord, with a notice in the inviteLow sensitivity, and the notes become shared memory
Customer or client callsRecord after telling them at the start, and agree it in advance for regulated clientsOutside parties have their own rules and expectations
Sales discovery and demosRecord after telling them at the startThe write-up feeds follow-up, and the notice sets the tone
Job interviewsAsk the candidate first, and follow your recruiting rulesIt involves a person's data and a hiring decision
Performance reviews and HR conversationsDo not record unless HR approvesSensitive, and often covered by extra rules
Legal advice or privileged discussionsDo not record unless counsel agreesRecords can affect privilege
Health, therapy or other regulated settingsOnly with a tool and setup approved for that regimeExtra obligations apply
Board meetingsAgree it in the board's own rules, and check records retentionMinutes are corporate records

A template you can copy

Adapt the wording to your company. Where it says the policy owner, name one person.

1. Purpose. This policy sets out when and how AI notetakers may be used in company meetings. It protects the people we meet with, our customers and our own information.

2. Approved tools. Only tools on the approved list may record or transcribe company meetings. The policy owner keeps the list. A tool is approved after a review of where it stores data, whether it trains models on content, who can access recordings and how content is deleted. Personal notetaker accounts, and bots connected to a calendar without approval, may not be used for company meetings.

3. Notice and consent. Everyone on a call is told before recording starts. Where a bot joins, its presence in the participant list is not enough on its own: the host also says that the call is being recorded and written up. Where recording happens without a bot, the host says so aloud or writes it in the invite. If anyone objects, recording stops or does not start. Calls with people in other countries or states follow the stricter rule.

4. Meetings that are not recorded. HR matters, performance conversations and legal advice are not recorded unless the policy owner or counsel approves in writing. Meetings in regulated settings are recorded only with a tool and setup approved for them.

5. Access. Notes are visible to people who attended and to colleagues who need them for their work. A public share link needs a manager's approval, is given an expiry date and is revoked when no longer needed. Transcripts are not sent outside the company without checking that the people in them would expect it.

Still writing meeting notes by hand?

Notepik joins the call, writes the summary, and hands you the action items before you have closed the tab.

Read our security overview

6. Retention and deletion. The policy owner sets a retention period for each type of meeting and writes it down. Notes that are no longer needed are deleted. When someone leaves, the ownership of their recordings is reassigned.

7. Vendor use of content. Approved tools may not use our meeting content to train models for anyone, and must delete content when asked.

8. Mistakes and complaints. Anyone can ask for a recording of them to be deleted. Anyone can report an unapproved tool or a recording nobody announced to the policy owner. Mistakes are corrected, not punished, so that people report them.

9. Review. The policy owner reviews this policy every year, and whenever the tools or the law change.

Making it stick

A policy only works if people can follow it without friction.

  • Offer an approved tool. A rule with no alternative sends people back to whatever they used before.
  • Put the notice in your invite template. One line, added once, covers every meeting.
  • Review calendar access. Your Google Workspace or Microsoft 365 admin console lists the third-party apps that people have connected to their calendars. Check it every quarter.
  • Explain the reason in fifteen minutes. People follow rules they understand, and the lawsuits make the reason easy to explain.
  • Name an owner. A policy with no person behind it is a document, not a practice.

How Notepik fits a policy like this

We built Notepik to be easy to govern, and we will be plain about where it needs your help.

  • The bot is always visible. It joins as a named participant, Notepik Notetaker, so the notice in clause 3 starts from something people can see.
  • The Chrome extension asks first. It records a browser tab with no bot, so it does not announce itself. It will not start until the person recording confirms that they will tell everyone, and your policy should say how the host does that.
  • Roles limit access. Owner, admin, member and viewer roles control who can read, edit and share.
  • Sharing is a choice. Share links are off until an owner or admin turns one on, can carry an expiry date and can be revoked at any moment.
  • Content is not used for training. Meeting content is never used to train models, and our processing providers are contractually barred from doing so.
  • Deletion exists. Owners and admins can delete a meeting, and closing a workspace deletes everything after 30 days.

We do not have SOC 2 or ISO 27001 certification today. If your vendor review requires one, say so early. Our security page and consent page set out what we do and do not claim.

Frequently asked questions

How long should an AI notetaker policy be?

One page is enough for most companies. Long policies are not read, and the decisions that matter are few: which tools, when to record, what people are told, who sees the notes and how long they stay.

Who should own the policy?

Whoever owns security, legal or operations, as long as it is one named person. Shared ownership usually means nobody reviews it.

Do we need consent from external guests?

It depends on where everyone is located, and the rules differ widely. The safe default is to tell them at the start and let them decline. For regulated clients, agree it in advance.

Can a policy replace legal advice?

No. It sets your own rules and makes them visible. Whether those rules satisfy the law that applies to you is a question for a lawyer.

Where can I try a notetaker that fits this policy?

Notepik has a free plan for one person, with no card required, so you can test the bot or the extension on a real meeting and see whether the write-up is useful. See pricing.

Try Notepik on your next meeting

Free to start, no card required. Connect a calendar or paste a link, and the summary is waiting when the call ends.

Related reading

Back to the blog