How Long to Keep Meeting Recordings: A Retention Guide

Most teams only ask how long to keep meeting recordings after it is already a problem: a hard drive is full, a client asks you to delete an old call, or someone wants to know why a recording from eight months ago still exists. The honest answer is that there is no single number that fits every meeting. A sales call, a board meeting and a quick internal standup all carry different risk and different reasons to keep the file around, and in India the DPDP Act adds a layer most teams have not looked at yet. This guide gives you a working retention policy by meeting type, what the law actually says, and what to do when someone asks you to delete a recording early.

Why "just keep everything" is the wrong default

Keeping every recording forever feels safe, but it quietly creates three problems. Storage grows without anyone noticing, since an hour of recording can run into several hundred megabytes, and a team that records daily builds up a large archive within a year. Old recordings become a liability rather than an asset, because a recording nobody remembers making is also a recording nobody is watching for things that need to be redacted or protected. And if a dispute or a legal request ever reaches your company, a messy archive makes it harder, not easier, to find the one recording that actually matters.

The opposite mistake, deleting everything quickly, is just as costly. Microsoft's own usage data shows that most meeting recordings are never watched again after a couple of months, but the small number that are rewatched tend to matter a great deal: a decision that gets disputed later, an action item nobody remembers committing to, or a client meeting where "what did we actually agree to" comes up weeks after the call. The goal is not to pick one retention period. It is to pick a different one for each kind of meeting, based on how likely you are to need it again.

What Indian law actually requires

India's Digital Personal Data Protection (DPDP) Act sets the baseline, though its retention and erasure provisions are not yet fully in force. Once they apply, the general rule is simple: personal data, which includes a recording of someone's voice and a transcript naming them, should be erased once the purpose it was collected for is served, or once the person withdraws consent, whichever happens first. There is no single fixed number of days written into the Act for ordinary business recordings. Instead, the responsibility sits with your organisation to decide, and be able to explain, how long each category of recording is genuinely needed.

A few things are worth knowing if you operate in India:

• If another law requires you to keep certain records longer, for example company, tax, employment or anti-money-laundering rules, that longer period wins. A board meeting recording tied to a statutory minute, for instance, may need to be kept well beyond what an internal policy would otherwise set.
• Deletion has to reach everywhere a copy exists, not just your main recording folder. That includes backups, shared drives, laptops that downloaded a copy, and any tool that stores a transcript alongside the audio.
• Rules around large platforms with tens of millions of users and required notice periods before deletion do not usually apply to a regular company recording its own meetings, but they signal the direction regulators are heading: predictable retention periods and advance notice before data disappears.

If your company is subject to a specific regulator, such as the Reserve Bank of India for financial services or a sector regulator with its own recordkeeping rules, check that rule first. It will usually set a firm minimum that your internal policy should simply inherit.

A retention policy by meeting type

Instead of one rule for every recording, set a retention period per category. The table below is a starting point that works for most Indian teams. Adjust the numbers to fit your own risk and storage budget, but keep the shape: recordings tied to a decision or a client relationship last longer than recordings that exist mainly as a backup to notes someone already wrote.

Once you have a table like this, the hard part is actually enforcing it. A policy that lives in a document nobody reads is not a policy. The tool you record with should be able to delete audio automatically once the period you chose is up, rather than relying on someone remembering to clean up a folder every quarter.

Handling an early deletion request

Even with a retention schedule in place, someone will occasionally ask you to delete a specific recording before its time is up: a guest who attended one call and does not want it kept, a client who wants an old recording removed once a project ends, or an employee asking about a meeting they were named in. Two things make this easy to handle instead of stressful.

First, know in advance who can approve an early deletion and how quickly it should happen. A reasonable default is a few business days, communicated back to the person who asked. Second, make sure deleting a recording actually deletes it everywhere, including any transcript, summary or shared minutes that quote the recording directly. A transcript that still contains a sentence from a recording you claim to have deleted defeats the purpose of deleting it.

If the person asking was not a guest invited by you, for example someone outside your organisation who is not a paying user of your recording tool, make sure the tool itself gives them a way to ask without having to track down an administrator first. That is worth checking before you choose a notetaker, not after someone asks and you realise there is no process for it.

Keeping recordings without keeping all the risk

A lot of this gets easier if the tool you record with treats retention as a setting, not an afterthought. Zrec lets a team set automatic audio deletion anywhere from 7 to 365 days, so the policy you write down is also the policy the software actually follows, instead of depending on someone remembering to clean up a folder every few months. Guests who were not invited by you can also request their own deletion directly, which covers the awkward case above without an email back and forth. Since Zrec writes the minutes of meeting, the decisions and action items stay searchable and linked to the moment they were said, even on a shorter audio retention window, so a shorter retention period does not mean losing the record of what was decided, only the raw recording behind it.

For the legal side of recording meetings in the first place, including consent, see our guide on whether it is legal to record meetings in India. And if client or project meetings are the category you are most worried about keeping track of, our guide to minutes of meeting for client meetings covers what to capture so the written record carries most of the weight, even after the recording itself is gone.

Reviewing the policy once it exists

Treat your retention policy as something to revisit once a year, not something you set once and forget. Three things change often enough to matter: the law, since the DPDP Act's rules are still being finalised and will likely be clarified further; your own storage costs, which grow as your team records more meetings; and your business itself, since a client relationship that used to be short-term project work might turn into a multi-year contract that deserves longer retention than you originally planned for. A short, scheduled review each year is enough to catch all three before they become a problem.

If you only do one thing after reading this: write down a retention period for each meeting type you actually hold, even a rough one, and set your recording tool to enforce it automatically. A policy that depends on someone remembering to delete old files manually will not survive the first busy quarter. For more on building a workflow from your meetings that doesn't depend on remembering anything, see the Zrec home page.