How long to keep meeting recordings, and when to delete them

The short answer

• Default to 30 to 90 days for audio. That covers the realistic window in which someone needs to hear the exact words again. After that the transcript answers the question faster anyway.
• Keep the transcript longer than the audio, and the summary longer than the transcript. Three different assets, three different risks, three different periods. This is the single most useful idea on this page.
• There is no general law that says how long to keep a meeting recording. In the UK and EU, GDPR tells you to keep personal data no longer than you need it and leaves the number to you. Sector rules and a few company-law rules set real minimums, and those are listed further down.
• Match the period to the risk, not to the storage cost. Storage is cheap. A five-year-old recording of a heated HR conversation, sitting in a shared account, is not.
• Stop deleting the moment a dispute looks likely. A legal hold overrides your schedule. Nothing on this page beats that rule.
• Write it down on one page and actually apply it. An undocumented policy is the same as no policy when a regulator or a lawyer asks what you do.

Read this first: this is general information, not legal advice

This page explains how retention decisions are usually made and points at real, named rules so you can check them yourself. It is not legal advice, and it is not a compliance sign-off for your organisation.

Retention rules differ by country, by US state, by sector, and by the contracts you have signed. A rule that binds a broker-dealer in New York has nothing to do with a design studio in Berlin. A hospital, a school, a law firm, and a two-person agency all land in different places. Laws and regulator guidance also change, and this page carries a date at the top for that reason.

If a recording could end up in a dispute, a regulatory inspection, or a subject access request, get the schedule checked by a lawyer or your data protection adviser before you rely on it. That review is cheap compared with the alternative.

One more thing worth settling before retention: whether you were allowed to record at all. Consent rules vary sharply by country and by US state, and they are covered separately in do you have to tell people you're recording a meeting.

The recording, the transcript and the summary are three different things

Most retention arguments get stuck because people treat one meeting as one object. It is not. A recorded meeting produces at least three assets, and they do not deserve the same treatment.

The audio is the most sensitive and the least used. It carries tone, hesitation, side comments, the person who joined late and complained about a colleague, and the voice of everyone in the room. Voice is personal data on its own. Audio is also the largest file and the hardest to search.

The transcript is the working record. It is text, so you can search it, quote it, and redact a line from it. It still contains everything that was said, so it is not harmless, but the risk profile is lower and the usefulness is much higher.

The summary, the decisions, and the action items are the part with lasting value. Six months later, nobody wants 9,000 words. They want what was agreed, who owns it, and by when. That fits on half a page.

So the pattern that works for most teams is simple. Delete the audio early. Keep the transcript for a medium period. Keep the summary and the decisions for as long as the work they describe matters. You lose almost nothing operationally and you shrink the sensitive pile fast.

There is one caveat, and it matters. If the exact wording could ever be contested, the audio is your evidence and a transcript is a derived document with mistakes in it. That applies to disciplinary meetings, contract negotiations, and formal interviews. For those, keep the audio for the full period, or keep none of it at all and take contemporaneous written notes instead.

Why keeping everything forever is a liability, not an asset

The instinct to keep everything comes from a good place. You never know what you will need. But a growing archive of meeting audio works against you in ways that are easy to list and hard to argue with.

• Everything you hold is discoverable. In litigation, records you still have can be requested. Records you deleted on a documented schedule, before any dispute was on the horizon, generally cannot be held against you the same way. Routine deletion under a written policy is a normal, defensible practice.
• Every recording is a breach waiting for a bad day. The size of a data breach is decided by what was in the account when it happened. A team that keeps 90 days of audio has a smaller problem than one holding four years of it.
• Subject access requests get expensive. Under GDPR, a person can ask what personal data you hold about them. If that means combing through 600 recordings, someone spends a week on it. If it means 40 transcripts and a folder of summaries, it is an afternoon.
• Old audio decays into a misleading record. A recording from three years ago, with no context and half the participants gone, invites the wrong conclusion more often than it settles anything.
• Consent does not stretch forever. People agreed to a meeting being recorded. Very few of them assumed that recording would sit in a shared account indefinitely. Keeping it far past the stated purpose is exactly what the storage limitation principle is aimed at.
• Nobody can find anything anyway. Archives without a retention rule are almost always archives without a naming rule either. Volume by itself does not produce recall.

A sample retention schedule by meeting type

Copy this, then adjust it. The point is not that these exact numbers are right for you. The point is that a meeting type should decide the period, and that the audio should almost always go before the notes do.

Where the law names a number, and where it does not

Almost every retention question ends in "it depends", which is unhelpful, so here are named rules with real numbers. Check each one against your own situation before using it. None of these were written with AI meeting recordings in mind, and most govern the record rather than the audio.

Legal hold beats your schedule, every time

A retention schedule is a peacetime rule. The moment a dispute becomes reasonably likely, it stops applying to anything connected to that dispute.

The trigger is earlier than most people expect. It is not the day you are served with papers. In US practice the duty to preserve attaches when litigation is reasonably anticipated, which can be a threatening letter, a formal grievance, a serious complaint from a client, or a regulator's first question. Deleting relevant records after that point, even on a schedule you wrote in good faith, is where organisations get into real trouble.

What a small team should actually do is short. Name one person who can call a hold. When they call it, they send a plain email naming the matter, the people involved, and the date range, and asking recipients not to delete anything in that range. Then someone checks that automatic deletion, in every tool including the meeting app, is paused for those items. Keep the email. It is the evidence that you acted properly.

Release the hold in writing too, once the matter closes. Holds that are never lifted quietly turn into keeping everything forever, which is the problem you were trying to avoid.

Write a one-page policy your team will actually follow

Long policies fail because nobody reads them. Aim for one page that a new joiner can absorb in two minutes. These are the fields worth having.

1. 1List your meeting types. Four to eight is plenty. Standups, project meetings, client calls, interviews, HR, board. If a type never appears on your calendar, leave it out.
2. 2Set three periods for each type, one for audio, one for the transcript, one for the summary and decisions. Copy the table above as a starting point and change what does not fit.
3. 3Write one line of justification per row. This is the part regulators care about, and it forces you to notice the rows you cannot defend.
4. 4Name the owner. One person per meeting type is responsible for deletion actually happening. Shared responsibility means nobody does it.
5. 5Set a review rhythm. A calendar reminder on the first Monday of each quarter, with 20 minutes to clear anything past its date, beats an unread automation nobody trusts.
6. 6Write the legal hold paragraph. Who can call one, how it is communicated, what pauses, and who lifts it.
7. 7Say where the surviving notes live. If summaries are the long-term record, they need a permanent home outside the recording app, in a document store you already back up.
8. 8Add a consent line. How people are told a meeting is being recorded, and how long you tell them it is kept. If you promise 90 days, the promise is now your rule.
9. 9Date it and set a yearly review. Sector rules and privacy law both move. An undated policy looks abandoned even when it is not.

Making deletion real in a cloud app

A schedule only counts if the data is genuinely gone at the end of it. In a cloud meeting tool that takes a few checks, and they are the same checks in every app. There is more detail in where are my meeting recordings stored and in the step-by-step in how to delete a meeting recording permanently.

• Confirm deletion reaches the server, not just the screen. Delete a test note, then look for it on a second device. If it is still there, you hid it rather than removed it.
• Check whether audio and transcript delete together or separately. Some products drop the audio once transcription finishes. Others keep both until you say otherwise. This decides whether the audio-light pattern is one action or two.
• Read the backup sentence in the privacy policy. Deleted items usually persist in backups for a defined window. That is normal engineering, but you should know the number so you do not tell a client something untrue.
• Check whether deleting the account deletes the data. Closing an account and erasing its contents are not always the same operation.
• Remember exports. A PDF you emailed to a client is outside every retention control you own. Track where the notes went, not just where they started.
• Understand who else holds a copy. Speech and language model providers behind any AI note taker are subprocessors, and their handling applies to your meeting too. This is part of what GDPR compliance for AI meeting transcription asks you to check.
• Do not accept a certification claim without seeing it. If a vendor's page says SOC 2 or ISO 27001, ask for the report or the certificate. A logo is not evidence.

If you would rather keep the notes and drop the audio

This is where a tool either helps or gets in your way. The pattern that most teams settle on, short audio life and long note life, only works if the notes are good enough to stand alone once the recording is gone.

Noter AI is built around that. A recording produces a transcript with speaker labels and timestamps, an executive summary, and a list of action items with owners. You can reshape the same recording into minutes of meeting, key bullet points, an email, a to-do list, or a formal report, so the version you archive is the version you would actually read a year later. If a name or a term came out wrong, you can edit the transcript and re-run the summary so the archived note is correct before the audio goes.

For teams that work in more than one language, the same applies to the record you keep. Transcription covers 60+ languages with automatic detection, and the language is tagged word by word, so a meeting that switches between Arabic and English, or Spanish and English, comes back with both rendered properly instead of the second language arriving as phonetic nonsense. Finished notes translate into 18 languages, which matters when the archived summary has to be readable by a head office that did not attend.

Export is what makes deletion safe. PDF, Word, plain text, and rich-text copy all work, so the summary can live in your own document store while the recording lives on a short clock inside the app. Folders and search across every note's title and AI notes keep the surviving record findable.

On price, it is $9.99 a month or $49.99 a year, per person rather than per seat. That matters for retention more than it sounds. Per-seat tools push teams toward one shared account holding everyone's recordings, which is the worst possible shape for a retention policy. Here each person holds their own subscription, records from their own phone and owns their own deletions. That is five subscriptions for five people, not one shared login, which is the point.

The honest limits, stated plainly. Transcription happens in the cloud, so audio is uploaded and there is no offline mode. Data is encrypted in transit and at rest, and you can delete notes and your whole account from inside the app at any time. There is no automatic retention timer, so the schedule above is something you run, not something the app runs for you. And no certification such as SOC 2, ISO 27001, or a HIPAA business associate agreement is documented, so if your work requires one, this is not the tool for that work. You can test all of this on a real meeting during the free trial, on iOS or Android, before you commit anything sensitive to it.