Skip to content

Data retention and deletion

Retention is user-controlled, not time-based

Section titled “Retention is user-controlled, not time-based”

The inspected application has no automatic time-based retention schedule for sessions, transcripts, summaries, local indexes, or settings. They remain in their respective local stores until you delete a session, reset app data, delete a model, remove an export, or otherwise remove the data.

Action Removes Does not remove
Delete one session The session’s SQLite row, transcript, summary, and derived session and global search indexes. The original imported source file, normalized WAV copies in the application audio directory, and exports.
Clear a summary The persisted summary and its session-level summary embedding. The transcript, session row, and any external-provider copy.
Reset app data All session and index rows in SQLite plus Synthezia-prefixed webview local-storage settings and templates. Normalized audio copies, downloaded models, user-owned import files, and user-selected exports.
Delete a model in Model Manager The selected local Whisper model or local Ollama model when the operation succeeds. Sessions, summaries, settings, audio, and external-provider data.
Development-only full installation reset Session/index rows, Synthezia-prefixed storage, downloaded models, local audio copies, and Ollama runtime state. Imported source files and files you exported to a chosen destination.

The full installation reset is exposed only in the development UI. It is not a normal end-user deletion method.

Per-session and global chat messages are held in frontend memory in the current flow. Reloading the application or clearing that frontend conversation removes those in-memory messages, while the transcript and summary source data remain in SQLite.

If External API is selected, a provider can retain data it received under its own policies. Local session deletion and app reset do not contact that provider or prove remote deletion.

  • Export or back up only the files you intend to keep; the database reset cannot be undone through Synthezia.
  • Delete exports separately from the destination where you saved them.
  • If normalized audio removal matters, treat the current ordinary deletion and reset-app-data flows as incomplete for that category.