Remote provider data flow

Outcome

External API is an opt-in generation boundary. Selecting a provider is not enough to transmit meeting content: before a remote summary or chat request, you must explicitly authorize the normalized endpoint in Privacy & Data. Strict Local Mode blocks every external generation request.

Audio conversion, recording, Whisper transcription, transcript embeddings, and global-search query embeddings remain local in this flow.

Remote-provider diagram

Audio or recording
  -> local FFmpeg conversion and local whisper.cpp transcription
  -> local Ollama embeddings and retrieval
  -> selected summary/chat context may be sent to an explicitly authorized provider
  -> provider response returns to the application
  -> resulting session data remains in the encrypted local database

Requests that can leave the device

Synthezia constructs OpenAI-compatible generation requests from the endpoint, model, and API key you configure. The API key is retrieved from macOS Keychain only to create the request.

Feature	Data that can be sent to the authorized provider
Final summary generation	Transcript text, summary instructions, and optional title, participants, meeting date, and description.
Per-session chat	Transcript, optional summary, prior conversation, and the current question. Longer sessions can require multiple context requests.
Global cross-session chat	The current question, prior user turns, selected locally retrieved transcript excerpts, and meeting metadata used to present those excerpts.
Early summary preview	Transcript preview text only when the separate allow remote early summaries setting is enabled. It is off by default.

The endpoint must use HTTPS, except for an explicit localhost development endpoint. Credentials in the URL, query strings, and fragments are rejected, and provider requests do not follow redirects. If the endpoint changes, it must be authorized again.

Retention and credential limits

The provider’s policies and configuration govern copies it receives. Deleting a local session or resetting application data does not request deletion from that provider.

The API key is stored in macOS Keychain, not webview local storage. This is a local secret-storage boundary; it is not a provider-neutral retention, access-control, or compliance guarantee.

Related pages

• Network connections
• Data retention and deletion
• Threat model and limitations