Privacy overview

Local-first by design

Overshow is built so that capture, processing, and storage happen on your Mac. Your indexed content and derived artefacts stay in a database on disk under your user account. That is not a slogan: the desktop app runs transcription, text extraction, embedding, and search without sending those payloads to Overshow’s servers for processing.

You are always in control of what Overshow captures. Pause and resume, exclude applications, and use built-in exclusion categories so the index reflects choices you make in Settings. not a default that assumes everything should be recorded.

What stays on your device

Screen activity you choose to record, audio you choose to record, transcripts, on-screen text, search indexes, summaries, and related metadata are handled locally. Overshow does not operate a default cloud pipeline that reads your capture content for product analytics or model inference. The desktop app does not send behavioural telemetry to Overshow by default.

The three exceptions

Only the following categories routinely involve Overshow’s online services:

• Authentication. Signing in (for example via OAuth or email magic links) uses app.over.show and identity providers you choose.
• Billing. Subscription and payment handling goes through Stripe when you purchase or manage a plan.
• Optional calendar sync. If you enable it, calendar connection data is handled with encryption in transit and according to the integration settings you approve.

Nothing in that list replaces on-device capture or search. They cover account, payment, and an optional integration. not continuous processing of your screen or microphone in the cloud.

Go deeper

• On-device processing. what runs locally and what that means day to day
• Encryption at rest. how sensitive material is protected on disk
• Capture controls. pause, resume, and per-app exclusions
• Trust centre. policies and commitments in one place
• Security. how we approach security for the product and infrastructure