Set a sensible retention rule for AI meeting audio, transcripts and notes. Use purpose, access and deletion checks to protect customer and team conversations.

There is no single UK retention period for AI meeting transcripts. Keep each record for a defined purpose, for no longer than that purpose needs, and make sure you can delete every copy when the period ends. Audio, the verbatim transcript and approved meeting notes need not share one deadline. Decide the rule before you turn on automatic capture.

That sounds less convenient than selecting “keep forever”, which is often the default in practice. But a searchable transcript can contain far more than a useful meeting note: health details, a customer’s negotiation position, a colleague’s uncertainty and remarks nobody expected to become a permanent record. The first question is what you actually need to keep.

The ICO’s small-organisation guidance calls this storage limitation: personal data should be kept only as long as needed, then securely destroyed or deleted. It does not give every meeting the same number of days. A finance record, an employment matter and an ordinary project check-in may have different purposes and obligations. You need a decision you can explain, and a way to put it into effect.

Which record do you need after the meeting?

An AI notetaker can leave several records behind. List them separately before setting a deletion period:

RecordWhat it may be needed forQuestion before keeping it
Audio or videoChecking an important disputed pointCould an approved note meet the need instead?
Verbatim transcriptCorrecting names, actions and decisionsWho needs access to every aside and false start?
AI summaryStarting a draft recordHas a person checked it against the meeting?
Approved notes and actionsRunning the agreed workWhat business or legal reason sets their period?
Prompts, logs and copiesOperating or auditing the toolDoes the supplier retain another copy after yours is deleted?

I would normally start by treating the AI summary as a draft. Someone who attended checks decisions, dates and owners before it becomes an approved note. That is an operating rule, not a promise that the model will catch every nuance. The ICO’s answer about AI meeting recordings and draft documents says organisations should check outputs for accuracy and correct inaccurate personal information.

If the approved note records the decision well enough, keeping the raw audio indefinitely needs a separate reason. “We might want it one day” is too vague to set a useful rule. On the other hand, do not delete material that your business is required to retain, or that is subject to a live dispute or preservation obligation, simply because an automatic timer has fired. Put those exceptions in the process and have the appropriate owner decide them.

How should you choose the period?

Start with the purpose and work backwards. Ask what happens to the record, who relies on it and when that need ends. Write down the reason for each period, rather than copying a vendor default or another company’s policy.

For a routine internal project meeting, you might need the recording briefly while the chair checks the draft. The approved action list may remain with the project record for longer. For a customer call, the agreed commitments may belong in the customer record, while the full conversation may add little once accuracy has been checked. For a sensitive HR or health discussion, the meeting type and the information involved need a separate assessment. A blanket rule for every calendar event is unlikely to fit all three.

The ICO’s advice on recording online meetings says to consider whether a less intrusive method, such as taking minutes, could meet the purpose. It also says to tell people why the meeting is being recorded, how it will be used and how long it will be kept. That is a reason to settle the retention rule before the invitation goes out, not after somebody asks for the transcript.

There may already be a lawful basis for a purpose your business has established. Adding an AI tool does not automatically create a new one. Equally, reusing a recording for a new purpose calls for a fresh look. The ICO’s AI meeting-recording Q&A makes that distinction and asks organisations to explain the use in privacy information. Do not treat “everybody agreed to the call” as an answer to every subsequent use of the recording. The ICO’s current consent explainer makes clear that consent is one possible lawful basis, rather than a universal requirement.

Where are the copies hiding?

The calendar invitation and meeting platform are only the start. Your chosen tool might hold audio, a transcript, a summary, prompts and a copy in its own recycle bin. A participant may download a PDF. An integration may place actions in a CRM or project board. Someone may paste the summary into an email or another assistant. Each destination has its own access and deletion route.

Draw a plain data-flow list for the meeting type:

  1. Who can start recording or invite a notetaker?
  2. Which supplier receives the audio or text, and on which account and plan?
  3. Where do the recording, transcript, draft and approved note land?
  4. Which integrations create further copies or tasks?
  5. Who can see, export, correct or delete each item?
  6. What does the supplier say it keeps after your visible copy is removed?

Check the terms and settings for the actual product tier you use. “We can delete the meeting in the app” is only a partial answer if an export, integration or supplier retention process leaves another copy. Do not assume a transcript is gone from every system because its link disappeared from one screen.

This is particularly relevant when a notetaker can write into other systems. I covered the access and approval side in Should AI Have Access to Your CRM?. A retained call summary in the CRM may be useful, but it should be an approved record with an owner, not an unchecked transcript poured into a free-text field.

What should the team be told before recording?

Give people a short, accurate notice. Say that the meeting will be recorded or transcribed, which tool is involved, the purpose, who will receive the output, how long the records are kept and whom to contact with a concern. If an external participant objects, know who can switch the tool off and how the meeting will continue without it. The notice must match the settings, including any automatic joining rule.

Avoid claiming “we need consent” as a universal formula, or “our tool is GDPR compliant” as though that settles your own purpose and settings. The correct lawful basis and any additional conditions depend on the processing. If the meeting covers sensitive material or decisions about people, get an appropriate data-protection review before rolling out a default recorder. The ICO’s meeting advice is a useful starting point; it is not a substitute for assessing your particular use.

Keep the human review visible too. The chair or a named owner should correct the draft, mark the approved version and decide which actions enter other systems. A meeting note should not quietly send a customer message or amend a record just because an AI model labelled a sentence an “action”. The approval boundary is the same one I recommend for AI-generated customer emails: a person checks the facts and decides what leaves the business.

Can you prove the deletion rule works?

Test it on a non-sensitive meeting. Create a recording under the intended business account, approve the notes, and follow the record through the period and deletion route. Check the meeting platform, notetaker workspace, connected document store, exports and any linked tasks. Keep a short log of the test: what was deleted, where, when, by whom and what could not be verified.

If a supplier says a backup or processing log remains for a further period, record that separately. Ask how access is restricted and when it is removed. If you cannot find a deletion setting, an account owner or a documented supplier answer, that is a procurement and operating gap to resolve before routine use. A policy that nobody can execute is just a paragraph.

Review the rule when the tool, plan, integration or meeting purpose changes. For example, switching on automatic CRM export creates a second retention location. A new AI feature in your existing video platform can alter what is captured. A useful AI governance routine includes that change check, along with a named owner and a route to stop use.

A simple rule to write down this week

Take one recurring meeting type and fill in seven fields: purpose, recording owner, records created, where each record goes, who may access it, the justified period for each copy, and the deletion or exception owner. Add a line for who checks the AI summary before it is shared. Then run the deletion test once.

You may decide that ordinary minutes are enough for some meetings. For others, a short-lived recording may make an accurate note easier. Either choice is defensible when it follows the purpose, the people involved and the controls you can actually operate. The useful outcome is an agreed record that can be found when needed and removed when it no longer is.

If you want help mapping one AI meeting workflow, checking the supplier settings and turning the rule into a working process, contact Ajairu.

Meeting Data

Recommended Reads