Data retention and auto-cleanup

What it is

Omniscio holds a lot on your behalf — your sessions and their conversations, the notes and scratchpads you jot, the communications content it has learned from, and the encrypted snapshots it keeps as backups. By default, most of that is kept indefinitely.

"Data retention and auto-cleanup" is the area that decides what is kept and what is removed without you asking. Some of it is opt-in: you switch a window on, choose how many days it should hold, and Omniscio deletes anything older. Some of it is always on, such as the short recovery window that lets you undo a delete before a trashed item is purged for good. And the settings that permanently erase content are guarded by a confirmation, a one-time notice, or a grace period, so nothing irreplaceable disappears the moment you flip a switch.

One rule runs through the whole area: automatic cleanup never touches the data you are actively using. A session you are still working in, a live share, a shared recording, or a note that has not been deleted is left alone — the sweeps only ever reach dead, deleted or superseded records.

Where to find it

• Settings — the Data Retention (days) window (30 days by default) and the Auto-Delete Old Scratchpad Notes setting.
• Settings → General → "Auto-Delete Old Message Content" — the opt-in communications-retention setting.
• Settings → Backup & Restore → Backup Mirror — the retention count for stored backup snapshots.
• A project's menu — the permanent erase action that purges one project's stored data.
• Settings → Accounts → Delete my account — the account-and-data deletion flow.

How it behaves

Each part of the area is owned by its own page:

• Communications content erasure — the opt-in setting that permanently deletes old messages, email samples, voiceprint data, meeting recordings and transcripts, and the digests built from them, after a window you choose: Auto-delete old message content (opt-in communications retention).
• Scratchpad auto-delete — the opt-in toggle that moves old, unedited scratchpad notes to the Trash rather than deleting them outright: Scratchpads (persistent notes and the quick-capture overlay).
• The trash purge — the always-on window after which trashed scratchpads are hard-deleted, with a short recovery window before that: Scratchpads — part 2 (images, formatting, deletion, the CLI and the contracts).
• Vault-note retention — how a deleted KMS note waits in the vault trash until the periodic retention tick reaps it: KMS (the Vault) — notes, editor, search and sharing (part 6).
• Account deletion — what is removed in the cloud straight away versus cleared on this computer at the next launch: Deleting your account / starting from scratch.
• Erasing one project — the permanent, irreversible purge of a single project's stored records: Delete a project.
• Backup retention — how old backup-mirror snapshots are pruned, and the erasure concern behind the age bound: Backup Mirror (encrypted off-machine snapshot) (part 2).
• Reclaiming disk space — the database file only ever grows; shrinking it is a separate, deliberate action: Reclaim disk space (shrink a large Omniscio database).

Related

• Auto-delete old message content (opt-in communications retention) — permanently erasing old communications content after a window you choose.
• Scratchpads (persistent notes and the quick-capture overlay) — the opt-in auto-delete of old scratchpad notes.
• Scratchpads — part 2 (images, formatting, deletion, the CLI and the contracts) — the soft-delete trash and its always-on purge window.
• KMS (the Vault) — notes, editor, search and sharing (part 6) — how the vault trash is swept by the retention tick.
• Deleting your account / starting from scratch — removing your account and clearing this computer's copy of your data.
• Delete a project — the permanent erase of one project's stored data.
• Backup Mirror (encrypted off-machine snapshot) (part 2) — retaining and pruning stored backup snapshots.
• Reclaim disk space (shrink a large Omniscio database) — the deliberate action that shrinks the local database.