Encrypted at rest on your laptop
The local database is encrypted with key material derived from your platform keychain. It is not automatically replicated; an approved record enters the organisation repository only when you publish it.
Private by architecture, not by promise.
A privacy policy is a promise. An architecture is a fact. Overshow keeps the local capture index on your device. Content crosses the boundary only through an explicit action, including publishing an approved record to the organisation repository.
Where your data lives, and does not
Processed on-device
Speech-to-text, OCR, and semantic search all run locally. Captured frames, audio, documents, and queries do not need an external model.
Transit only when you opt in
Routine traffic covers account, billing, and device registration. Explicit publication, exports and integrations stay under your control.
What Overshow never does.
No automatic cloud copy of your local memory
There is no server-side replica of the local capture index. The organisation repository contains only approved records and source excerpts a consultant explicitly publishes.
No retained screen recordings
Screen frames are read for text and context, then discarded. Overshow keeps the understanding, not the pixels.
No training on your data
Your memory is not a training corpus. Models are trained elsewhere and shipped to your device.
No silent sharing, ever
There is no content telemetry on what you capture, search, or ask. Sharing happens only through an action you take.
Control is a panel, not a paragraph.
Pause capture from the menu bar or the app. Ignore lists and exclusion categories keep sensitive surfaces out entirely, and no admin or cloud process can override them on your behalf.
Capture
Pause all captureOne action
Password managersAlways excluded
Private browsing and remote desktopsBuilt-in rules
Banking, health, and custom patternsOptional blocks
What Overshow's servers see
Sign-in and billingRoutine
Device registration metadataRoutine
Aggregate licence stateRoutine
Your local capture index, searches, and questionsNot replicated
Approved record and approved source excerptsOnly when you publish
Your data, on your terms, including deletion.
Retention is configurable. Exports happen only when you run them. Deleting the local database removes the private work memory from that Mac; approved records already published to the organisation repository follow its separate retention and deletion controls.
- Retention configurable from Settings
- Exports are manual and user initiated
- Delete the local database with one explicit action
- Published organisation records have a separate deletion boundary
Settings, data
RetentionYour choice
DatabaseEncrypted locally
ExportManual only
Delete everythingOne action
Questions people ask before installing
The safest place for your work memory is your own machine.
Review the Trust Centre or book a walkthrough and inspect the local model with us.