Meeting recording consent and privacy checklist

Meeting capture went from exotic to default in about three years, and norms have not caught up. The result is a widening gap between what tools can do — join silently, record everything, keep it forever — and what participants would agree to if asked. This checklist is for closing that gap. It is a practical baseline, not legal advice: recording law varies by country and by state, and some jurisdictions require every participant's consent. When in doubt, ask counsel — and when still in doubt, ask permission anyway, because the reputational rule is stricter than most legal ones.

Before the meeting

• Tell people, before capture starts. Consent given after recording began is not consent for the first five minutes. Put it in the invitation when you can; say it at the top of the call regardless.
• State the purpose. "Recording for notes and action items, transcript shared with attendees" is a purpose. "We record everything" is a policy nobody agreed to.
• Check the content class. Regulated material — health data, legal strategy, HR matters, unannounced financials — may be inappropriate for your transcription tool at all, regardless of consent. Decide before the meeting, not during.
• Know your jurisdictions. With participants in multiple countries or US states, the strictest consent rule in the room is the one that applies. All-party-consent regimes are common; assume one applies unless you know otherwise.

During the meeting

• Capture must be visible. A recorder that joins as a named, visible participant can be seen and challenged; software that captures silently cannot. If your tool offers a stealth mode, that is a reason to distrust the tool, not a feature to use.
• The host can remove it. Consent includes the right to withdraw. Anyone in the call should be able to say "let's go off the record", and the removal should take effect immediately.
• Renew consent when the room changes. A late joiner did not hear your opening disclosure. One sentence — "heads up, we're recording for notes" — costs nothing.
• Pause for the sensitive part. The compensation discussion in an otherwise routine meeting does not need to be in the transcript. Pausing capture for ten minutes is a feature of a mature recording culture.

After the meeting

• Restrict by default. A recording of a conversation is not a publication of it. Default access should be the participants — wider sharing is a deliberate act by someone accountable, not a side effect of storage.
• Keep the transcript, question the audio. For most purposes the transcript is the useful artifact. Audio of people's voices is higher-risk data with lower ongoing value; deleting the recording once the transcript exists is a defensible default.
• Review AI summaries before relying on them. Summaries compress, and compression makes choices. Before a summary drives a decision — or is forwarded as the record — check it against the transcript it came from.
• Delete when the purpose ends. Retention "forever, just in case" is how archives become liabilities. Tie retention to the purpose you stated at the start, and honor deletion requests without friction.
• Document the rights process. Participants should be able to find out what was kept, ask for it, and ask for its deletion — and someone should own answering.

Where DayMarshal fits — honestly

DayMarshal's capture is built on the visible-by-design side of every line above: the notetaker joins under an honest, fixed name every participant can see and remove; nothing is ever joined automatically; the audio recording is deleted at the provider once the transcript is retrieved; recorded meetings arrive private to their owner, and sharing them is an explicit act. In-person recording asks for an explicit consent confirmation before the microphone opens and stores when it was given. What no tool can supply is the sentence at the top of the call — that one is yours.