Where your audio goes.

Audio capture and live transcription happen on your Mac. The microphone stream and the system-audio stream are read by Kennan, fed through voice-activity detection and the on-device speech-to-text model, and rendered as a transcript in the meeting window. The recording, the diarization, and the transcript live in memory or on local disk under your control. They are not uploaded.

On-device transcription is the default. The model runs as part of the app, with no network calls in the speech-to-text path. If you choose a cloud transcription provider in settings, that section becomes the part below.

Two parts of the product can call a third party, and only when you have configured a key for one. The first is the assistant: when you ask Kennan to suggest a move, the prompt and the relevant transcript window are sent to whichever LLM provider you chose, using the API key you supplied. The second is cloud speech-to-text: if you switched the transcriber to a hosted provider, the audio stream goes there directly.

Both calls go from your Mac to the provider you picked. There is no Tesouro-operated server in the request path. We do not relay the request, we do not see the request, we cannot read the response on your behalf.

The exact endpoints depend on the provider. They are listed in the app's settings panel next to each provider, and they are the same endpoints the provider documents publicly. If you want to inspect the traffic, you can.

We do not log your conversations. We do not log your transcripts. We do not log the prompts you send to your LLM provider, or the responses they return. We could not produce them if you asked us to, and we could not produce them if a third party asked us to.

This is an architectural property, not a policy promise. There is no Tesouro-operated server in the request path for any LLM or transcription provider, today or planned. Bring-your-own-keys is the constraint that makes the rest of this page true; it is not a feature toggle that could quietly flip.

When you sign up for the waitlist, we store your email address, the moment you submitted it, and a single-use token used to confirm the email by clicking the link we send you. The record is held in Cloudflare D1. The lawful basis is your consent, given when you submitted the form.

We use the address for one purpose: to email you when Kennan is ready, and to email occasional product updates between now and then. We will not pass it to anyone, and we will not use it for anything else. If you want it removed, send a one-line note to hello@kennan.app and it will be deleted on receipt.

Aggregate page-view counts via Cloudflare Web Analytics. No cookies, no third-party JavaScript, no per-visitor identity, no session replays, no fingerprinting. We do not run Google Analytics, Plausible, PostHog, Segment, or any pixel. We can tell you that the bibliography page got a hundred visits last week. We cannot tell you which of them was you.