What should meeting memory include?

A useful meeting memory includes the date, participants, topics, decisions, commitments, open questions, and a transcript that can verify the summary.

Does Nod keep the meeting recording?

No. Audio is held only long enough to transcribe and is discarded; Nod stores the transcript and summary instead.

Does bot-free capture remove the need for consent?

No. Recording and transcription duties depend on law, policy, and participant location, not on whether a bot appears in the attendee list.

Meeting Memory: Decisions, Promises, and Context

Keep the decision, the promise, and the reason

Meeting memory is the durable context that survives beyond a single recap: what was decided, why it was decided, who promised what, and which question stayed open. Nod captures that context without joining the participant list, stores no audio, and lets you search across past meetings instead of reopening recordings or relying on someone’s recollection.

Download for Mac

14-day free trial · no card

By Vlad Kampov, Nod co-founder · Published September 1, 2026

Product evidence: Each completed capture includes a transcript and structured meeting intelligence, and cross-meeting Ask can retrieve related context from more than one session.
Limits: A generated answer can be incomplete or wrong. The original transcript remains the evidence to check, and recording consent is still the user's responsibility.
Method: This page is based on reproducible workflows in the current Nod macOS product and the public security, pricing, and product documentation linked below. It makes no aggregate usage or outcome claim.

Sources and related reading

From one call to a verifiable record

Start Nod before the meeting and stay in the conversation. When the call ends, review the summary's decisions, action items, and open questions. Correct anything that matters, then keep the transcript as the source evidence. Before the next meeting, ask what changed and open the cited session rather than trusting a remembered paraphrase.

No recorder participant in Zoom, Meet, Teams, or other Mac audio
No stored audio file
Structured summary and full searchable transcript
Answers across earlier meetings with source sessions

A memory is more useful than a recording library

A recording preserves everything but makes retrieval expensive. Meeting memory keeps the text needed to search and verify without retaining the voice recording. If the original audio is a legal, compliance, coaching, or review requirement, Nod is the wrong tool because it deliberately does not keep one.

Consent still applies

Bot-free capture changes the meeting experience, not the user's duty to notify participants or obtain consent. Requirements vary by jurisdiction and context. Review the recording and consent guidance and follow your organization's policy before capture.

See the broader AI working memory category, conversation memory across several calls, and the practical guide to decision memory.

Frequently asked questions

What should meeting memory include?
A useful meeting memory includes the date, participants, topics, decisions, commitments, open questions, and a transcript that can verify the summary.
Does Nod keep the meeting recording?
No. Audio is held only long enough to transcribe and is discarded; Nod stores the transcript and summary instead.
Does bot-free capture remove the need for consent?
No. Recording and transcription duties depend on law, policy, and participant location, not on whether a bot appears in the attendee list.