Local data storage

Application data location on macOS

Synthezia resolves its application-data directory from its Tauri application identifier, com.synthezia.synthezia. In a standard macOS user account, that directory is:

$HOME/Library/Application Support/com.synthezia.synthezia/

$HOME represents the signed-in user’s home directory. Do not share database files, settings storage, model files, or exported summaries unless you intend to share their contents.

What is stored there

Location or mechanism	Contents	Important deletion detail
`synthezia.db`	Session metadata, source audio paths, transcripts, summaries, processing status, errors, transcript chunks, embeddings, and search/index data. SQLite write-ahead logging is enabled.	Session deletion removes the session database row and derived indexes. Reset app data clears all session and index rows.
`audio/`	Normalized WAV copies created during import or recording processing.	Ordinary session deletion and Reset app data do not remove these files. The development-only full installation reset clears this directory.
`models/`	Downloaded Whisper model files.	Model Manager can delete models; the full installation reset clears the directory.
`ollama/models/`	Models owned by the bundled local Ollama runtime.	Model Manager asks Ollama to delete a model; the full installation reset clears the Ollama directory.
Webview local storage	Synthezia settings, provider base URL and API key, model choices, UI flags, and custom summary templates.	Reset app data removes keys that begin with `synthezia-`. The API key is not stored in macOS Keychain.
User-selected export destination	Markdown, PDF, or DOCX summary exports.	Outside the application data directory and outside Synthezia’s deletion actions.

Synthezia also maintains local runtime state such as the selected loopback Ollama host and an Ollama runtime log in the application-data directory. This page does not treat those files as a separate encrypted store or a remote backup.

Source media and exports

For imported sessions, Synthezia reads the source file selected in the native picker. That user-owned original remains where it was selected. Exported summaries are new files written only after you choose a destination in the save dialog.

Important limitation for audio copies

The current session-deletion flow removes database data and search indexes, but it does not remove normalized WAV copies. A normal app-data reset also leaves those files in place. Review data retention and deletion before relying on either action to remove all local audio.