Local by default

Core meeting capture is processed and stored locally:

  • audio capture;
  • transcription;
  • speaker diarization;
  • meeting Markdown and available media in your vault.

Raw audio is not sent to an external transcription provider. Your finalized content remains in your local vault unless you choose a feature that processes or shares it externally.

Features that can send content

External AI or sharing features require relevant context to leave your Mac. Depending on the feature and its settings, that context can include:

  • transcripts and meeting outlines;
  • screenshots or other screen context;
  • your notes and selected text;
  • prompts, Skill options, and generated results;
  • profile or calendar context needed for the request.

Examples include Action Skills, Meeting Skills, Ask, automatic AI meeting titles, Share to Web, and webhooks.

Current AI providers include OpenAI, Google, and Anthropic. Production content is handled through business or paid offerings configured not to train general-purpose models, although providers may retain limited data for service operation, security, abuse prevention, or legal compliance under their terms.

Keep content on your Mac

To minimize external processing:

  1. Disable Automatic meeting title.
  2. Do not run Action Skills, Meeting Skills, or Ask on sensitive content.
  3. Disable automated Meeting Skills.
  4. Do not use Share to Web or external webhooks.
  5. Review screen, selected-text, and file inputs before running an Action Skill.

Capturing a local screenshot does not by itself send it. Selecting that screenshot as AI context does.

Failure diagnostics

Error reports for an unexpected background-process failure can include your Mac model, total RAM, recent memory usage, and system memory pressure. The age of each measurement is included so an older reading is not mistaken for the state at the exact moment of failure. These reports do not include your computer name, serial number, or meeting content.

Recording-start and vault-review failures can also include the processing stage, fixed filesystem error codes, and whether recording, cleanup, or helper shutdown was active. These diagnostic fields exclude file paths, filenames, and meeting content.

Network failure reports can include a fixed API operation label, request method, configured time limit, attempt count, response status, and whether the failure happened before a response arrived or while it was being read. Timing, response byte counts, and proxy or certificate diagnostic availability help distinguish different failures. These fields exclude request and response content, URLs, and query parameters.

Audio and screenshot retention

Open Settings → Meeting → Save audio to control whether finalized meeting audio is kept, and use Keep audio to choose its retention period. Deleting or not retaining audio does not remove the need to obtain recording consent.

Use Keep screenshots in Settings → Meeting → Smart screenshot to choose a separate retention period for saved meeting screenshots. Keep audio remains in the Audio card. Each retention row reports its current storage usage, and both settings default to Forever. Choosing a shorter period deletes only media older than that period; it does not delete the meeting, transcript, notes, or Skill results.

For the complete policy, read the current Privacy Policy.