What it captures
Screens, audio, documents, and windows. How much, and how to limit it.
overshow is in public beta — meetings, ask, and actions are live. more coming soon.
see the roadmap →FAQ
Frequently asked questions about Overshow: on-device processing, storage, pause controls, platforms, AI assistants, speakers, and pricing.
Question themes
Screens, audio, documents, and windows. How much, and how to limit it.
On-device storage, encryption, and what (if anything) leaves the laptop.
Search, Ask, daily summaries, and meetings.
If the answer is not here, the fastest route is to try it on a real laptop for a week.
Frequently asked questions
Filter 17 answers by topic or search every question and answer.
Your active window — and only while it is on a display you allow — plus meeting audio when a meeting is active or manually started, and local documents in folders you point it at. OCR reads text off each captured frame. Transcription runs over short rolling windows with a small overlap so words are not cut off. You must obtain consent from everyone before you record them — see Recording consent & your legal obligations.
In a local SQLCipher-encrypted SQLite database on your laptop, with full-text search and on-device semantic embeddings for semantic search. No screen images or video files are persisted: only OCR text, audio transcripts, and metadata derived at capture time. Nothing captured is sent to a shared cloud database. The security page has the full control list.
By default, no captured content leaves. What does sit in the cloud: sign-in and billing data, device registration metadata, and aggregate licence-usage counts. No telemetry and no captured content. Manual exports only move data when you explicitly run them. See local vs cloud for the side-by-side.
Yes. Pause from the tray menu, the app, or a keyboard shortcut. Resume when you are ready. You can also exclude specific windows, apps, displays, or categories (HR tools, password managers, private browsing) so they are never captured in the first place. The security page lists the default exclusions.
On Free, 7 days. On Pro, unlimited history. Storage grows roughly 500 MB per month for the database (OCR text, transcriptions, embeddings), bounded by your retention settings. See pricing and system requirements for plan and disk detail.
v1.0 is macOS 26 (Tahoe) on Apple Silicon only. See system requirements for details.
Overshow captures only your active window, and only while it is on a display you allow. It records which display hosted each capture, so you can filter results by it. Choose which displays are allowed in Settings → Capture; a single-display Mac has nothing to pick. Changing the allowed displays needs an app relaunch.
A developer-only integration can expose a small approved tool surface to AI clients you approve, so they can draw on your local history. It is a local capability for developer builds and is not part of shipping releases. When used, the desktop app has to be running and each connection requires explicit consent. For day-to-day use, the in-app Ask feature gives you grounded answers from your own captures without connecting another tool. See local vs cloud for the safety posture.
Yes, within a meeting. On-device speaker labelling runs locally and separates speakers per meeting. You can rename or merge those speakers within the meeting. The only voice embedding Overshow stores is your own, kept on your device, so it can tell your voice apart on calls. Overshow does not store or match other people's voices, does not recognise other people's voices across meetings, and this is not a planned feature. You can filter search results by speaker. You must obtain consent from everyone before you record them — see Recording consent & your legal obligations.
Only if you want meeting audio transcription. Screen recording is always required for capture. Microphone and accessibility permissions are optional. The installation steps walk through each permission prompt. You must obtain consent from everyone before you record them — see Recording consent & your legal obligations.
Plan for about 500 MB per month for the SQLite database, bounded by your retention settings. 20 GB free is a comfortable baseline. Retention is configurable from the settings. See system requirements for more detail.
Quit the app and drag it from Applications. The local data directory (SQLite database at `~/Library/Application Support/Overshow/db_<user_id>.sqlite` and logs) sits under your macOS user profile and can be deleted manually. If you remove that support directory before reinstalling, Overshow treats the next launch as a fresh install, clears stale account Keychain entries, and asks you to sign in again.
One active device per user. Signing in on a second laptop revokes the first one automatically. This keeps capture and billing linked to a single machine. See the security page for the identity model.
Unlimited searchable history. Everything else (capture, OCR, transcription, search, chat, meetings) is already included on Free with a 7-day window. See pricing for the full breakdown.
Free already gives every feature for 7 days. When you want unlimited history, move to Pro; there is no separate trial to start or end. You can join the beta to get in early, or go straight to pricing.
SSO (Google, Microsoft Entra ID), a dedicated account manager, SLA-backed support, and a 3-month paid pilot scoped to up to 25 users. Enterprise pricing is custom and sized to the organisation. Submit an enterprise enquiry to talk.
The Trust Centre lists the artefacts: data flow, encryption, sub-processors (Neon, Stripe, Vercel), identity model, capture controls, and operational health. The security page covers the specifics. We walk security teams through each of them for enterprise pilots.