Skip to content

What stays on the computer, and what leaves it.

Local and cloud assistants differ in where captured work is stored, where the AI runs and what you explain to your security team. With Overshow, each consultant's private history sits in one SQLCipher-encrypted database on their computer. A cloud assistant processes whatever you give it, from a single prompt to a meeting recording, on its provider's servers.

Private history and what leaves it
Private history (default)
Captured screen text not selected for publication
Daily drafts you have not shared
Full-text search
Ask on the Mac
Crosses the network
Sign-in, billing, device registration, update and continuity checks
What you choose to share, with its source excerpts
Copilot and cloud AI app requests a consultant allows

What runs where in Overshow.

Capture and full-text search run on the laptop on Windows and macOS. The Mac also runs Ask and optional meeting transcription locally. These built-in processing steps do not send captured content to a hosted model.

CapabilityWhere it runs
Screen captureFocused-window text through the accessibility layer first; sparse OCR fallback, images discarded
SearchFull-text search on Windows and macOS
AskLocal language model on the Mac
Meeting audioOptional on-device transcription on the Mac during active or manually started meetings

What leaves the computer, and when.

Account operations and release checks use the network, but those routine requests carry no captured work. Captured work leaves only by a route someone chose. Each route below says what it sends, where it goes and who decides.

Sharing with the engagement

What leaves
Content the consultant publishes, with its saved source excerpts and audit metadata. Never the full private history.
Where it goes
The organisation repository, for colleagues with access to the engagement. It passes through Overshow's web service on Vercel and is stored in Neon, UK (London).
Who decides
The consultant approves it, then publishes it with a separate action. Nothing is shared automatically.

Microsoft 365 Copilot on shared content

What leaves
Shared content and its source excerpts, for the engagements the person asking can access.
Where it goes
Your consultancy's Microsoft 365, where questions, returned excerpts, answers and citations are kept under its policies.
Who decides
Your consultancy enables the connection and grants access per engagement. Copilot needs the relevant Microsoft licence and administrator consent.

A consultant's own Copilot connection

What leaves
Copilot's questions and the bounded excerpts returned from the consultant's permitted history.
Where it goes
Microsoft 365, through Overshow's gateway on Cloudflare, which can read them in transit and does not store them. Your consultancy's Microsoft 365 keeps the questions, excerpts and answers under its policies.
Who decides
Your consultancy decides whether this connection is permitted. Within that, it stays off until the consultant turns it on under Settings, Connections, and it answers only while their computer is online.

AI apps (Mac only)

What leaves
Questions and returned source excerpts, sent to the provider of each cloud AI app the consultant connects. Local AI keeps the exchange on the computer.
Where it goes
The AI app's provider, under its own terms.
Who decides
Your consultancy decides which AI connections are permitted. Within that, the consultant connects each app under Settings, AI clients.

Other local clients

What leaves
The parts of the private history the consultant grants a local client, with secrets removed. It can read as far back as the plan's history allows, unless the consultant sets a shorter window.
Where it goes
That client on the computer, which may send what it reads on to its own provider.
Who decides
Your consultancy decides which AI connections are permitted. Within that, the consultant allows each client under Settings, Connections. Every read is logged, and access can be revoked at any time.

Exports and mirrors

What leaves
Files the consultant chooses to export or mirror.
Where it goes
A folder they choose, which may be cloud-synced.
Who decides
Only when the consultant exports or sets up a mirror.

Diagnostics

What leaves
A diagnostic the consultant reviews and attaches to feedback. It can include captured screen or transcript text.
Where it goes
Overshow, to investigate the report. The diagnostic passes through Overshow's web service on Vercel and is stored in Neon, UK (London).
Who decides
Only when the consultant reviews, attaches and submits it.

Web page titles

What leaves
A captured web address, sent to its own site to fetch the page title and link details.
Where it goes
The site the address belongs to.
Who decides
Off by default, and allowed site by site.

Sign-in, billing and updates

What leaves
Account, device and licence details. No captured work.
Where it goes
Overshow's servers, the payment provider and, with single sign-on, your identity provider (Google Workspace or Microsoft Entra ID).
Who decides
Needed to use the app.

Teams transcripts travel the other way. Selected Teams transcripts go into the consultant's private history. A transcript is never shared automatically. We agree the eligible Teams meetings with your consultancy during set-up, with your administrator's consent.

Which fit is yours.

Where cloud-first is a better fit

  • You want the most capable frontier models without buying Apple silicon
  • You do not capture screens or audio, only chat transcripts
  • Your security posture already permits sending work content to the provider

Where local-first is a better fit

  • You capture screen text or choose meeting transcription and want that material processed locally
  • You work across clients, vendors, or regulated environments and need captured work to stay on the computer unless someone chooses a route that sends it
  • You want to search your captured history without an external index service

Questions to ask before deciding.

Whatever you choose, these four make the trade-offs concrete.

  1. Does the assistant capture screen text or meeting audio? If yes, where is it stored?
  2. Can the assistant search captured text without sending it to a cloud service?
  3. What does exporting or deleting everything look like?
  4. What does a security reviewer have to sign off: an API or a database file?

Questions security reviewers ask.

Why does a local-first app need an account at all?

Sign-in, billing, device registration, and release checks cross the network, but those routine requests do not carry captured content. The local capture index is processed and stored on the laptop. Separately, a consultant can explicitly share selected content, with its source excerpts, to the organisation repository.

Does it work offline?

Capture and full-text search run on-device on Windows and macOS. Ask runs on-device on the Mac, so built-in processing does not depend on a connection. You need to be online to sign in, and the app periodically refreshes its signed entitlement. If its offline grace expires, recall falls back to a shorter historical window until a refresh succeeds.

Does it work with Zoom, Google Meet, and Teams?

Yes. Overshow reads the text on your screen during calls in common meeting apps and browser sessions, and links them to calendar context in your daily draft. Meeting audio is optional. When enabled, it is transcribed on-device during active or manually started meetings. No bot joins the call.

What happens to optional meeting audio?

Raw audio stays on your computer and is removed after terminal processing. Bounded encrypted recovery files, including quarantined speech that produced no usable transcript, can remain until successful processing, deletion, or oldest-first eviction within the shared ten-hour cap. Transcript text stays in the encrypted local database. No voice embeddings are stored or compared across meetings.

What hardware does it need?

A Mac with M1 or later, at least 16 GB RAM and macOS 26 (Tahoe) or later. Windows 11 (x86_64) runs on basic PCs with lower RAM requirements.

What happens if the vendor shuts down?

Your private history is already on your computer, and nothing you captured is deleted. Capture and full-text search run on-device on Windows and macOS, with Ask on the Mac. Access remains subject to the account's entitlement and offline grace. Shared content follows the repository retention terms in your agreement.

Compare it against your current assistant.

Book a walkthrough to compare the boundary against your current assistant and discuss access for an eligible machine.

Mac: M1 or later, at least 16 GB RAM and macOS 26 or later. Windows 11 (x86_64) runs on basic PCs. Access is set up with us on a walkthrough. Pricing is agreed per engagement on the walkthrough. Every deployment includes capture, search and a shared history for each engagement on Windows and macOS. Standard Teams and Microsoft 365 Copilot set-up is included in the paid 90 days, subject to the agreed permissions and Microsoft licences.