Privacy

Inside the bridge

Meeting audio and the optional physical microphone pass through realtime macOS Core Audio routes and bounded memory buffers. Meeting Bridge does not write audio to files, databases, MCP messages, or diagnostic logs.

Network

Meeting Bridge has no HTTP listener, cloud API, analytics, or advertising SDK. Local MCP launches the same signed app over stdio and exchanges control state only.

For update checks, the app connects over HTTPS to the signed appcast at releases.viyv.io. It fetches an update bundle only after the user chooses to update. Apart from ordinary web request data, this traffic contains no audio samples, meeting state, or MCP messages.

Your selected AI

ChatGPT Voice, Codex, or another selected AI client may send audio to its provider. Retention, training, region, and account controls follow that provider's terms and settings.

Consent

Follow participant, organization, and regional rules and obtain the consent required to share meeting audio with AI. Neither the GUI nor local MCP starts meeting capture without this confirmation. The bridge does not identify speakers or infer consent.

This website

This site has no account, form, cookie-based client analytics, or tracking pixel. Email you send for support is processed by the relevant mail provider.