Security & Privacy
Minutes captures, transcribes, and stores conversations on your own machine. If you connect a cloud AI assistant or summarizer, the meeting context you authorize is sent to that provider. Use a local model or skip summarization for an on-device workflow. Local storage does not remove your responsibility for access controls, consent, backups, or retention.
Every step, on your device
Stays on deviceMic (cpal) and system audio (native macOS capture in the desktop app, or a loopback device), recorded on your machine
On-device speech models, selected for your platform and configuration
pyannote ONNX models, local; speaker labels never computed in a cloud
Markdown + YAML frontmatter on your own disk, 0600 owner-only permissions
The recording and transcription pipeline processes audio on your device. Optional AI assistants and summarizers are a separate boundary: a cloud provider receives the context you authorize.
The durable record is plain markdown in ~/meetings on your disk, written with 0600 permissions. Grep it, back it up, delete it; no export button between you and your data.
Minutes does not require an account to capture and store conversations. Your device security, backups, file-sync services, and chosen AI providers still matter.
Every claim on this page is verifiable in the repository; capture, transcription, and storage are readable Rust, not a trust-center PDF.
Setup and updates can download models and software. Connected AI assistants and summarizers may send authorized transcript context to their model provider. A local model keeps that processing on-device. Review each assistant and provider configuration before sharing a meeting.
Files copied into a synced folder follow that service's settings. Your browser also uses website analytics on this site, separately from the desktop recording pipeline. Website download and setup events contain an action category and page path, not meeting content or clipboard text.
Local processing is a deployment choice, not a compliance certification. Review recording consent, device access, encryption, retention, backup destinations, and any cloud AI provider with the people responsible for your organization's requirements.
Do not infer that local files are immune from disclosure obligations or that connecting a cloud assistant creates no third-party access. See the agent integration guide for the data path.
Minutes is MIT-licensed and the entire pipeline is readable Rust. Audio capture lives in crates/core/src/capture.rs, transcription in crates/core/src/transcribe.rs, and output permissions where files are written. Don’t take an SEO page’s word for an architecture claim; read the code, or have your security team do it. That’s the point of shipping it open.
Next step