Security · Network disclosure

Every network connection the app can make.

Below is every outbound connection, what it sends, and how to switch it off. You can confirm the local-first claim yourself with the in-app network log or a packet capture.

Last verified against v0.6.65 · 2026-09-16

The core promise

By default, meeting audio, transcripts, summaries and voiceprints are processed locally. Optional cloud providers, integrations and companion features have separate data flows. The disclosure below explains network behavior and exceptions.

Applies to v0.6.65 and later. Hard Offline Mode is enforced in the application core, including the update check; every redirect is re-checked and local traffic is never sent through a proxy. An administrative policy file can lock it for a whole organisation.

Connections

#PurposeDestinationWhenWhat is sentOff switch
1Auto-update check + downloadGitHub Releases (public release repo)App start / manual “Check for updates”HTTP GET only; no user data. Standard HTTP metadata (IP, user agent) reaches GitHub. Updates are ed25519-signature-verified before install.Hard Offline Mode refuses it in the application core and logs the attempt; the administrative policy can disable updates
2AI model downloadHugging Face (primary model host), then GitHub public release repos (fallback mirror and the llama.cpp runtime). Every download is checksum-verifiedFirst-run wizard, model change, repair; always user-initiatedHTTP GET of model files; no user dataDon’t run downloads; offline mode blocks; an internal mirror can be allow-listed by policy
5In-app feedback (user-triggered)LocalTranscript feedback endpointOnly when the user opens the feedback form and clicks SendMessage, optional reply email, app version, explicitly attached screenshots and optional diagnostic-log tailDo not send feedback; Hard Offline Mode blocks it
6Cloud transcription / cloud AI (optional providers)OpenAI, Anthropic, or Infomaniak (Switzerland), as the user choosesOnly when the user explicitly configures a cloud provider with their own API key. Local is the defaultMeeting audio (cloud transcription) or transcript text (cloud AI actions), sent to the provider the user chose under the user's own accountNever configure a provider; “local” is the default; Hard Offline Mode blocks
7Calendar fetch (iCal)The user's own calendar URLOnly when the user configures a calendar URLHTTP GET of the iCal feedDon't configure; offline mode blocks (LAN URLs still allowed)

Documents for IT and data protection

Written for IT departments and data protection officers, for the current version. English only for now; German versions on request.

What never has a network path

Your meetings database, audio clips, and voiceprints stay in the app’s local data folder. Protected by your operating-system account; we recommend BitLocker on Windows or FileVault on Mac.

For IT & data protection officers

In the default configuration, meeting content is processed on-device only, so there is no cloud processor to assess for FADP/GDPR purposes. Speaker recognition is local-only biometrics. Hard Offline Mode and the exportable audit log serve as the procurement demo.

Managed installs (MSI for Intune / Group Policy) and an administrative policy file that locks offline mode, blocks cloud providers and disables features for a whole organisation are available. A custom edition with its own name and defaults is available on request. Questions, DPIA support, or a pilot: hello@localtranscript.com.

All local features free · no card · no account