Privacy & Security

Understand the local processing boundary for meeting audio, transcripts, summaries, screenshots, search, embeddings, and Q&A.

Step-by-Step Guide

  1. Meeting audio and derived meeting content are processed locally by the desktop application.
  2. Speech recognition, summary generation, semantic embeddings, and meeting Q&A do not require a third-party inference API.
  3. The meeting knowledge index is stored locally with the meeting library.
  4. Network access may still be used for explicit model downloads and application updates.
  5. Always follow the recording-consent, workplace, contractual, and legal requirements that apply to your meetings.

Learn the practice

Privacy Architecture: Meeting-content inference is designed to run locally. Model downloads and application updates are separate from sending meeting audio, transcripts, summaries, screenshots, or retrieval context to a hosted inference API.