Remote provider data flow

Outcome

You can assess the external boundary created by choosing External API in Synthezia settings. This setting does not send the original audio file to the configured provider in the current processing flow; conversion and Whisper transcription remain local.

Remote-provider diagram

Audio or recording
  -> local FFmpeg conversion
  -> local whisper.cpp transcription
  -> transcript, question, prompt, and retrieved context may be sent to the configured provider
  -> provider response returns to the application
  -> resulting session data remains stored locally

Requests that can leave the device

Synthezia constructs OpenAI-compatible requests from the base URL, model, and API key you enter. The key is sent as an HTTP authorization credential when one is configured.

Feature	Data that can be sent to the configured provider
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 be processed as multiple context requests.
Session embeddings	Transcript chunks and summaries. The current embedding model identifier is fixed in the application and may not be available from every compatible endpoint.
Global cross-session chat	The current question, prior user turns, selected transcript excerpts, session metadata used for retrieval, and provider-side query embeddings when External API is selected.

Synthezia posts generation requests to the configured /chat/completions path and embedding input to /embeddings. The current setting accepts a non-empty base URL but does not enforce an HTTPS scheme. Choose and review a provider URL and transport configuration appropriate for your data.

Local operations that remain separate

Audio conversion and Whisper transcription stay in the local path.
Returned summaries and locally derived session data are written to SQLite on the device.
The background embedding phase for the newer global transcript index uses local Ollama, even when External API is selected for the answer path.

Retention and credential limits

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

The API key is persisted in Synthezia’s webview local storage. This is not equivalent to using macOS Keychain storage. Do not treat it as a managed secret store.