Screen capture is processed on the consultant's computer. Microsoft processes Teams transcripts before import. Sharing with the engagement, connecting a service or exporting content creates a separate transfer.
Captured text and imported transcripts are stored in your encrypted local history.
Importing a transcript does not share it.
Screen text is indexed locally on Windows and macOS. On the Mac, optional meeting audio is transcribed on-device during active or manually started meetings, and Ask produces answers with source references. Search uses full-text matching on both platforms. Review happens on the consultant's computer.
The organisation repository receives only what the consultant chooses to share, with its saved source excerpts. The consultancy grants access per engagement, and those colleagues can use it in Overshow and Microsoft 365 Copilot. The wider capture index, original sources and drafts are not replicated.
Daily drafting works on Mac and Windows. See system requirements for hardware guidance.
Screen images are discarded after text extraction. Raw meeting audio stays local, with bounded encrypted recovery files held until successful processing, deletion or storage cap eviction. Voice embeddings are not stored or compared across meetings.
Sign-in, billing, device registration and aggregate licence state go to Overshow's account services. These requests do not contain the local capture index.
Choosing Publish sends the content the consultant approved, its saved source excerpts and audit metadata to the organisation repository. Colleagues and their permitted AI connections can retrieve it for engagements they have access to. Nothing is published automatically.
Exports and file mirrors write content to a folder you choose, which may be cloud-synced. A submitted feedback diagnostic can send text you review and attach to Overshow.
Your consultancy decides which AI connections are permitted. Within that, a local client you allow under Settings, Connections gets a scoped token for the parts of your history you grant. It can read as far back as your plan's history allows, unless you set a shorter window. Secrets are removed from what it reads, every read is logged, and you can revoke it at any time. What the client does next is up to that client and its provider.
An AI app you connect under Settings, AI clients, gets scoped, read-only access to your private history, subject to the consultancy's AI policy. A cloud app sends queries and returned excerpts to its provider; a local app keeps the exchange on the computer. You can revoke access at any time. This is separate from access to what the team has shared.
A personal Copilot connection retrieves permitted excerpts from the consultant's local history. Engagement access retrieves shared content and saved excerpts instead. Returned content, prompts, answers and citations enter the organisation's Microsoft 365 environment, where its retention policies and authorised compliance access apply. Revoking Overshow access does not remove existing Copilot conversation history.
Transcripts from eligible Teams meetings are processed in Microsoft 365 before being imported into the consultant's private history. Import does not share them with the organisation repository. During set-up we agree the meetings covered and the Microsoft permissions the administrator grants.
When enabled for an allowed site, URL enrichment sends a captured web address to that site to fetch its page title and link details. The site handles those requests under its own privacy terms.
An authorised Google or Microsoft connection lets the desktop fetch permitted calendar or mail data directly from the provider. Overshow's account service holds encrypted provider tokens and connection metadata, rather than a routine copy of calendar events or messages.
The consultant chooses capture sources and can pause from the app, the menu bar on macOS or the tray on Windows. Sharing with the engagement stays separate from capture.
On macOS, Screen Recording and Accessibility are required for capture. Microphone access is needed for optional meeting audio transcription. On Windows, read-only screen capture needs no equivalent system grants. Capture starts after onboarding is completed.
The privacy notice describes the data processed and the controller and processor roles. Your consultancy is responsible for the permissions and policies required for its use of capture and the organisation repository.
San Digital Limited is registered with the Information Commissioner's Office. Registration is separate from product certification or an assessment of your deployment.
A DPIA template is available for your data protection review. The Trust Centre lists certifications, platform verification and sub-processors for your security team to inspect.
Walk through the data transfers, capture controls and set-up with us.
