Data management

Where Your Local Data Lives

The desktop app's private capture index is stored locally on your computer. On a Mac the database file is at:

~/Library/Application Support/Overshow/db_<user_id>.sqlite

and logs are written to:

~/Library/Application Support/Overshow/data/logs/

On Windows the database file is at:

%LOCALAPPDATA%\Overshow\db_<user_id>.sqlite

and logs are written to:

%LOCALAPPDATA%\Overshow\data\logs\

Paths respect your operating system user account; another user on the same machine does not share those files.

The organisation repository is a separate, explicit boundary. If you choose Publish, the approved record, its approved source excerpts, and publication audit metadata are stored for authorised organisation members. Drafts, original sources, and the wider local capture index are not copied there.

Opening the folder

Quit Overshow first. On a Mac, choose Go → Go to Folder in Finder and enter ~/Library/Application Support/Overshow/. On Windows, press Windows+R and enter %LOCALAPPDATA%\Overshow. Do not edit the encrypted database or its sidecar files directly. Logs needed for support can be attached through the in-app feedback flow.

Reset local data

Use Settings → Data → Reset local data and type delete to remove the per-user SQLCipher database and replayable recovery queues. After reset, previously indexed local content cannot be recovered on that computer; treat the confirmation seriously.

The reset includes captured screen text, transcripts, meetings, search data, locally synced calendar data, mail metadata and bounded excerpts, and derived records. It does not remove markdown mirror files or other plaintext exports outside the database, change operating system permissions, sign you out, delete the web account, or delete approved records already published to the organisation repository.

No Cloud Backup or Sync of the Local Index

The product does not upload your capture database to Overshow-managed cloud storage for backup or cross-device sync. If you use Time Machine, iCloud Drive, Windows File History, OneDrive folder backup, or third-party backup tools, those copies are between you and those services. Overshow does not pull your index back from the internet.

Published approved records are not a backup of that index. They are deliberately selected organisation records with their own membership, retention, and deletion controls.

Remote access

There is no mechanism for Overshow support to browse or retrieve your local capture content remotely. Support cannot "open" your index from our side. Optional connected providers and explicitly approved local or AI clients are separate network boundaries: the desktop app fetches authorised calendar or mail data from the provider, and an approved cloud client receives only the queries and snippets returned to it. Authorised organisation members can retrieve an approved record and source excerpts only after the consultant separately publishes them.

Retention

Captured history, locally synced calendar data, and mail metadata and excerpts are retained in the encrypted database by default. Your account's entitlement sets the searchable-history window, which limits recall; it does not delete older local data.

Use pause and exclusions to stop or narrow new capture. Use the Settings retention control for an explicit capture age cap, where available, or Reset local data when you want a clean slate. An operator may configure a separate hard-retention cap for mail. Without that policy, mail remains until the local database is reset or removed.

Revoking Overshow in Google or Microsoft stops future provider access but does not delete data already stored locally. Deleting the web account removes provider tokens held by app.over.show, but it does not remotely erase your computer. See Deleting your account for the recommended order.