Privacy Policy

Last updated: July 13, 2026

This policy explains what Koe processes when you use the macOS application (the "App") and koe.fm (the "Site"). The important distinction is the processing mode you choose. Local, bring-your-own-key (BYOK), and Pro do not have the same data flow.

The short version

  • Koe ships without remote product analytics, remote application logs, or remote crash reporting.
  • Local transcription can run without sending audio or transcript text off your Mac.
  • BYOK requests go directly from the App to the provider you configure. Koe is not in that request path.
  • Pro transcription and transformations pass through Koe services to the selected provider. Koe does not write audio or transcript content from these requests to its database.
  • Transcription history is saved locally by default. You can disable future history, delete individual entries, or clear it all.
  • An email-authenticated account stores account, subscription, and a small set of preference data. It does not sync transcripts, audio, dictionary terms, prompts, or provider keys.

Processing by mode

Local transcription

Audio is captured and transcribed on your Mac with a downloaded local model. Koe does not send that audio or the resulting transcript to Koe or a transcription provider.

Local transcription does not automatically make every later step local. If you enable a cloud transformation, the transcript and the instructions needed for that transformation follow the BYOK or Pro transformation path described below.

BYOK transcription and transformations

For BYOK transcription, the App sends audio directly to the provider you select, such as Mistral, OpenAI, or Groq. For BYOK transformations, the App sends the selected transcript and transformation instructions directly to the configured compatible provider.

Koe servers are not in the BYOK request path. Provider keys are kept in a separate local App data file and are not included in Koe settings sync. They are currently protected by your macOS user account and filesystem permissions; they are not stored in the macOS Keychain. Each provider's own terms, logging, and retention rules apply to data sent to it.

Pro transcription

Pro uses your Koe account and subscription state to authorize a request. Audio passes through a Koe endpoint and is forwarded to the transcription provider selected by the App. The request and response exist in server memory while the request is handled. Koe does not write the audio or transcript content to its database.

The selected provider receives the audio and returns the transcript. Its own data-use and retention terms apply.

Pro transformations

When you enable cleanup, formatting, summarization, translation, or a custom transformation, the App sends the transcript plus the required instructions and any relevant dictionary terms through Koe to OpenRouter and the configured model. Audio is not part of this request. Koe does not write the input text or transformed result to its database.

Do not place secrets in custom prompts or dictionary entries that you do not want sent to the selected transformation provider.

Data stored on your Mac

The App may store the following locally:

  • App preferences and configuration
  • Downloaded transcription models
  • Provider keys in a separate local App data file
  • A bounded diagnostic log of up to 200 recent entries; it stays local unless you explicitly export it
  • Transcription history in a local SQLite database when Save transcription history is enabled

History saving is enabled by default. A history record can include the resulting text, raw text, language, model, mode, duration, actions, destination app identifier, and timestamp. Local history remains until you delete entries, clear all history, or remove the App's local data. Turning history off stops new entries; it does not delete existing ones.

Account, subscription, and synced preferences

You do not need an email account for local or BYOK use. If you sign in or use Pro, Koe uses Supabase for authentication and account storage. Koe may store:

  • Email address and account identifier
  • Stripe customer, subscription, price, status, billing-period, and cancellation fields
  • Account creation and update timestamps
  • A limited preference set: shortcut, selected model identifier, cloud billing mode, auto-paste, auto-submit, and sound setting

Transcripts, audio, dictionary terms, custom prompts, hooks, provider keys, and local diagnostic logs are not part of this settings sync.

Stripe processes payment details. Koe stores Stripe identifiers and subscription state, but does not receive or store your full card number.

Website and demo

The Site does not use advertising trackers or product analytics and does not set analytics cookies. Hosting and network providers may process ordinary request metadata such as IP address, user agent, requested URL, timestamp, status, and abuse/security signals as part of operating the Site.

If you deliberately start the microphone demo, browser audio is sent to Koe's demo service and a managed transcription provider. Audio and returned text are handled for that live request and are not written to Koe's product database. The demo service uses network information to enforce a usage budget and prevent abuse.

Automated downloads, update checks, and release-manifest requests also produce ordinary server request metadata. They do not include transcript content.

Remote telemetry and diagnostics

The App does not send product-usage events, settings snapshots, diagnostic logs, or crash reports to Koe. Local diagnostic logs can be exported by you for support. Review an export before sharing it.

Retention and deletion

  • Local App data remains on your Mac until you delete it.
  • Audio and transcript content handled by Koe's Pro and demo endpoints is not intentionally persisted to Koe's product database.
  • Account, synced preference, and subscription records remain while the account is in use. To request account deletion, email hi+koe@gwendall.com. Some billing, fraud-prevention, dispute, security, or legal records may need to be retained after deletion.
  • Stripe, Supabase, hosting providers, and AI providers retain data under their own policies and configured service terms. Koe cannot delete data held independently under a BYOK relationship; contact that provider directly.

Koe does not currently offer self-service account deletion in the App. Adding a verified deletion flow and publishing exact processor retention periods are tracked product work; until then, deletion requests are handled by email.

Service providers

Depending on the feature you choose, data may be processed by:

  • Supabase for authentication, account records, and synced preferences
  • Stripe for billing
  • Mistral, OpenAI, or Groq for selected transcription requests
  • OpenRouter and the selected model provider for Pro transformations
  • Vercel and Koe's network infrastructure for Site and API delivery

The exact recipient depends on the mode and model you select in the App.

Security

See Security for the data-flow diagrams, local storage boundaries, update signing, and disclosure contact.

Children's privacy

Koe is not directed to children under 13, and we do not knowingly collect personal information from them.

Your rights and contact

Depending on where you live, you may have rights to access, correct, export, object to, or delete personal data. To make a request or ask a privacy question, email hi+koe@gwendall.com. We may need to verify that the account belongs to you before acting on a request.

Changes

We may update this policy as Koe changes. We will update the date above and provide additional notice when a change materially affects how account or content data is handled.