Can You Use an AI Notetaker in a Meeting Covered by an NDA?
Review an AI notetaker against your NDA: permitted recipients, purposes, service providers, copies, and deletion, with a worked confidential-meeting example.
A client sends a signed NDA before a product workshop. Everyone on the invitation is covered, the meeting room is private, and the consultant has a good reason to want accurate notes. Then someone enables an AI notetaker that sends the conversation to another company.
Whether that is permitted depends on the agreement and the actual workflow. An NDA can allow appropriate service providers, restrict them, or leave a question that needs resolving before disclosure. Permission to attend the meeting does not, by itself, answer whether an external provider may receive its contents.
The useful review is quite specific: what information will the tool capture, who can receive or use it, and does that handling fit the promises already made? This guide examines those questions through a fictional client engagement, drawing on US trade-secret law and UK confidentiality guidance reviewed on November 1, 2026. It is general information, not advice on the meaning or enforceability of a particular contract.
Read the agreement before reviewing the app
Start with the signed documents, including any services agreement, security schedule or client instructions that supplement the NDA. A software vendor’s security page cannot expand permission granted by the client.
The UK Intellectual Property Office’s NDA guidance explains that agreements should identify a permitted purpose and account for necessary onward disclosures. It also notes that an agreement can cover information shared orally in meetings, rather than only marked documents. For an AI workflow, those points suggest several questions to take to the person responsible for interpreting the contract:
| Contract question | Meeting-tool question |
|---|---|
| Which information is protected, and are there marking or follow-up requirements? | Does capture include oral disclosures, shared slides, incidental discussion or material outside the intended project? |
| Who may receive it? | Are hosted AI providers, their subprocessors and support personnel within the permitted recipient arrangements? |
| What use is permitted? | Is processing limited to this engagement, or can material support unrelated analytics, product improvement or training? |
| What copying and security conditions apply? | Are audio, transcripts, summaries and exports handled under the required controls? |
| What happens when the work ends? | Can the organisation satisfy return, deletion and permitted-retention provisions across its copies and providers? |
These are review questions, not standard clauses that every NDA contains. An agreement allowing disclosure to employees and professional advisers may need a separate analysis for an AI service provider. A clause allowing contractors may impose conditions such as confidentiality obligations, necessity, notice or prior written approval. The actual wording controls.
Separate contractual permission from recording permission
The client representative who signed the NDA may have authority over company information without being able to settle every participant’s recording rights. Conversely, a participant saying “yes, record this” may not have authority to amend the company’s contract.
Treat those as separate checks. The meeting host needs the applicable recording and privacy analysis, while the engagement owner needs a documented answer about the agreement. Cross-border calls can add legal systems beyond the contract’s governing law; Summit’s US recording-consent guide and European recording guide explain why a single platform notification may not resolve the whole question.
For our fictional workshop, the consultant asks the client’s authorised contact to approve a defined method before the meeting. The request describes the capture, processing location, recipients and working-record disposal, rather than asking generally whether “AI” is acceptable. The host then follows the separately approved participant notice and recording procedure. If either review remains unresolved, the workshop uses agreed manual notes.
Follow the information beyond the transcript
Imagine that the workshop concerns an unreleased component design. Its commercial sensitivity is in the discussion of tolerances, delivery constraints and a prospective customer’s requirements, not just in the file marked confidential.
The consultant’s proposed workflow creates several places to check. Audio may go to a speech-recognition service; transcript passages may go to a different model provider; the finished summary may be emailed to attendees and copied into a project system. A connector can later make the same material available to another assistant. A colleague who missed the workshop may obtain access through a shared folder.
For this example, the engagement owner makes a short recipient inventory containing the legal entity or internal group, the material received, its purpose, its access conditions and its retention arrangements. That is a proposed way to test the agreement against reality, not a claim that every NDA mandates this format.
A “no training” promise answers one of those questions. It does not establish that the provider receives nothing, that no support access exists, or that every copy disappears when a user deletes a conversation. Likewise, an encrypted connection protects a transfer without deciding whether the transfer was authorised. Ask for the evidence needed to fill the inventory instead of treating one attractive privacy statement as the whole answer.
Consider trade-secret protection without assuming automatic loss
Confidential business information and legally protected trade secrets overlap, but they are not identical categories. Under 18 USC §1839, the US federal definition of a trade secret includes both independent economic value from secrecy and reasonable measures to preserve that secrecy. Its misappropriation definition also addresses certain disclosures or uses made without consent in breach of duties of secrecy or limited use.
That makes the controls around an AI service relevant. It does not establish a rule that using cloud software automatically destroys protection, or that installing a local app automatically preserves it. The information, restrictions, contractual arrangements and actual handling all matter.
Federal law also does not generally displace other trade-secret remedies: §1838 preserves the role of other applicable laws, subject to its stated exception. State law and contractual remedies therefore require their own review. A blog checklist cannot determine the outcome of a dispute merely from the name of the software used.
In the workshop example, limiting capture to the relevant discussion, controlling access and keeping a clear account of approved disclosures would give the organisation something concrete to explain about its precautions. Those are proposed operational measures, not a legal finding that the client’s design qualifies as a trade secret.
Work through an approval decision for the client workshop
Suppose the hypothetical agreement permits the consultant to use the client’s information only to evaluate the component design, and requires written approval before sharing it with additional service providers. The consultant initially proposes a hosted notetaker but has not identified its downstream model provider.
The missing provider is a reason to pause that configuration. It would be premature to tell the client that the proposed processing fits the contract when the recipient list is incomplete. The consultant can obtain the missing information and seek the required approval, or propose a narrower method.
For a local option, the engagement owner records these illustrative conditions:
- Capture only the workshop segments covered by the agreed scope, with the host responsible for stopping when excluded material arises.
- Use an assigned, protected company Mac with local processing selected, and review sync, connectors, backups and exports separately.
- Restrict source material to the designated reviewer; send only a checked decision record to the approved project recipients.
- Apply the agreed working-record schedule and any contractual return or deletion requirements, with legal review of preservation obligations and retained-copy exceptions.
- Review changes to processing or recipients before they are used for this engagement.
These conditions still need to fit the real agreement and applicable law. A requirement to delete information must be reconciled with a litigation hold or other preservation duty rather than followed blindly. The consultant should also check whether a later request to certify deletion covers copies outside the app, including backups and exported documents.
The resulting approval should be understandable to the person hosting the next workshop. A decision that names the configuration, permitted uses and recipients is more actionable than an email saying that the software is “secure.”
What local processing changes for Summit
With the required models downloaded and Local Models selected, Summit can process meeting content on the Mac. Its security documentation describes optional hosted AI, iCloud sync and other data flows; MCP access and exports also need to be included in the organisation’s review. Local processing can remove a hosted AI recipient from the proposed workflow, which may simplify a particular contractual question.
The remaining record still needs protection. Summit does not separately encrypt its local database or recordings, so endpoint controls such as FileVault and restricted account access matter. A transcript exported to a synced project folder follows that folder’s access and storage arrangements. Keeping the original local does not make the exported copy local too.
Most importantly, local capture cannot override a no-recording term or an instruction to keep no verbatim record. If the agreed method is a selective set of human notes, follow that method until an authorised change has been made. The next useful step is to take the proposed data flow and recipient list to the person who owns the agreement, before the confidential conversation begins.