When someone asks you to delete a meeting recording

Most guidance on meeting recordings stops at consent. Getting permission is the easy part — it happens once, at the top of a call, when everyone is agreeable. The hard part arrives months later, in a one-line message: can you delete the recording of the meeting on the 14th?

Whether that request is a two-minute job or a bad week depends entirely on choices you made before it arrived.

Who can ask, and what you owe them

Anyone who was in the room can ask. Under GDPR and similar regimes they may have a formal right to erasure; in most of the world they simply have a reasonable request and you have a reputation. Treat both the same way, because refusing a reasonable request on the grounds that it is not legally mandatory is how you become the company that argued about it.

Three answers are legitimate, and only one of them is "no":

• Yes, and here is confirmation. The default. Cheap when your storage is tidy.
• Yes, with a stated exception. You may have an obligation that outranks the request — an active legal hold, a regulatory retention rule. Say which one, in a sentence, rather than gesturing at "compliance reasons".
• Not yet, because I need to check something. Buying a day to find every copy is fine. Going quiet is not.

What is never legitimate is deleting the copy they know about and keeping the one they do not.

Find every copy before you promise anything

This is where deletion requests go wrong. The recording is rarely one file. By the time somebody asks, a single meeting may exist as the audio, a transcript, an AI summary, tasks extracted from that summary, a shared link somebody forwarded, and a paragraph pasted into a chat thread.

Write the list down before you reply. For each copy, decide whether it is the recording or a work product derived from it — because they are different questions. A transcript is usually the recording by another name. A task that says "send the revised quote by Friday" usually is not; it is a commitment that happens to have originated in a conversation, and deleting the audio does not oblige you to abandon the work.

Say which you are doing. "The recording, transcript and summary are gone; the two tasks that came out of it remain, without any quoted content" is an answer somebody can accept or push back on. Silence about the derived copies is what turns one request into three.

Make it a two-minute job in advance

Everything above is easier if you decided these things while nobody was asking:

• Keep less by default. Audio is the highest-risk artifact with the shortest useful life. If the transcript exists, the audio usually does not need to. Deleting it on a schedule means most deletion requests are already half-satisfied when they arrive.
• Know where copies go. A tool that scatters transcripts into documents, chats and email creates deletion work in proportion to how useful it was. One that keeps the record in one place and links to it does not.
• Restrict sharing to a deliberate act. A recording that was private until somebody explicitly shared it has a knowable audience. One that defaulted to the whole company does not.
• Give the request an owner. "Someone should own answering" is a sentence in every privacy checklist and a name in very few companies. Pick one.

What to do when it has already spread

Occasionally the answer is genuinely hard: the transcript went to a client, or a summary is quoted in a board pack. You cannot unsend those, and pretending otherwise is worse than admitting it.

Do three things. Delete what you control, immediately. Tell the person precisely what is outside your control and where it went. And — if the content is sensitive — contact the recipients yourself rather than making the requester chase them. The last one is what separates a company handling a request from a company deflecting one.

Where DayMarshal fits — honestly

DayMarshal is built so most of this is already done before anyone asks. The audio for an online meeting is deleted at the provider once the transcript is retrieved, and in-person recordings delete their temporary audio after the durable transcript is assembled — so the highest-risk copy usually no longer exists. Recorded meetings arrive private to their owner; sharing one is an explicit act, which means the audience is knowable. Deleting a meeting removes its transcript, summary, and extracted outcomes together, so there is no orphaned derivative left behind. Tasks that came out of a meeting are kept, deliberately: they are your work, not a copy of somebody's voice.

What no tool supplies is the decision about who answers the message. That one is yours.

If you have not yet set the norms this article assumes, start with the meeting recording consent and privacy checklist — it covers the before-and-during that makes the after straightforward.