Privacy Policy

Capturia has no accounts, no sign-up, no user database, no telemetry, and no analytics. The app phones home to no one: its only outbound calls are your model calls, made on your own key, and a version check against the public GitHub API. The one exception, on shared demo servers only, is a short-lived rate-limit counter described below. The product is open source under MIT, so every claim on this page is verifiable in the source.

In the desktop app, speech recognition runs on your Mac: Apple’s speech engine on macOS 26, a local Whisper model on earlier versions. No bot joins your meeting, nothing is recorded, and no call audio or video is sent anywhere. Only the transcribed command, and any deck you choose to load, go from your machine to the AI provider you configured, on your own key. What that provider does with your requests is governed by its own terms and privacy policy.

The browser demo is the exception: dictation there is handled by your browser’s built-in speech service, not on your machine. In Chrome that service sends your microphone audio to Google for recognition, governed by Google’s privacy policy; Capturia receives only the resulting transcript.

You supply your own AI key. In the desktop app it is encrypted on your Mac with a key held in the macOS Keychain; self-hosters can instead put a key in their own server environment. Either way it travels only to your model provider. There is no Capturia server, so it cannot be sent to or stored on one.

The app sends no usage pings of any kind; the anonymous launch beacon that earlier builds carried has been removed entirely. The website serves static pages with no analytics script. If the app crashes, the crash log is a local file on your Mac that is never uploaded; you choose whether to attach it to a bug report.

One narrow exception on shared demo deployments: to keep the free browser demo from being drained, the server may keep short-lived request counters keyed by a salted hash of your IP address. They expire within minutes, are never linked to what you say or do in the studio, and do not exist at all when you run Capturia yourself.

On launch the desktop app asks the public GitHub API whether a newer release exists. That request carries no identifiers beyond what any HTTP request carries, and it goes to GitHub, governed by GitHub’s privacy policy. Updates are never downloaded or installed automatically; the app only points you at the releases page.

Vote rooms live in whatever server the deployer runs: in-memory in the server’s own process by default, or a Redis instance the deployer supplies. Voting asks your viewers for nothing but an anonymous tap: no sign-in, no name, no phone number. Whoever hosts a vote page is the party handling those requests.

If a data flow changes, this page and its date change with it. Questions, or anything this page leaves unclear: the GitHub issues page.