Privacy policy

Earkeep transcribes your meetings locally, on your device. Your audio is processed only in memory and is never written to disk and never uploaded anywhere. Your transcripts are saved as plain files on your own computer, under your control. There's no account, no cloud storage of your meeting data, and no telemetry that sends your meetings, transcripts, or usage patterns to us.

The only outside parties involved at all are Creem (our merchant of record, who handles your purchase and license key) and our own self-hosted, cookieless website analytics. Both are described in detail below, with nothing left vague.

Audio. While Earkeep is running, it processes microphone and system audio only in memory, to run local transcription. That audio is never written to disk in any form, and it is never sent to Earkeep, to us, or to any third party. There is no server that receives your audio, no API call that carries it, and no upload step of any kind.

Transcription. Transcription runs entirely on your device, using Whisper or Parakeet models running locally with Apple Silicon hardware acceleration. Earkeep does not call out to any transcription APIs to do this work.

Storage. Transcripts are saved as plain files on your device, in a location you control. You can open them, search them, back them up, or feed them to any tool you choose. We don't have a copy. There is no Earkeep server that stores, syncs, or backs up your meeting transcripts.

No account required. Using Earkeep, including the full 14-day trial, requires no email address, no sign-up, and no cloud account of any kind.

Calendar connections. If you connect Google Calendar, Apple Calendar, Microsoft Outlook, or an ICS calendar URL so Earkeep can start and end meeting spans automatically, that connection is used only to read event names, times or other metadata from your calendar, on your device, so Earkeep knows when a meeting starts and ends.

In-app agents and MCP. Earkeep lets you run other local agent apps (Claude Code, Codex, Cursor Agent, Gemini CLI, and others) directly against your meeting history, and exposes an MCP server so external tools can read your meetings too. These are integrations you choose to use and configure yourself; whatever data leaves your machine through them is governed by the privacy policy of whichever agent or tool you've connected, not by Earkeep. Earkeep itself doesn't relay your meeting data anywhere on its own.

Earkeep is sold through creem.io, which acts as the merchant of record for every purchase. That means Creem, not Earkeep, is the party that actually processes your payment and is responsible for the data involved in doing so.

When you buy Earkeep, Creem's hosted checkout collects and processes:

• Your email address (to send your license key and receipt)
• Your payment details (processed by Creem and its payment processors; Earkeep never sees or stores your card details)
• Billing information needed for tax/VAT compliance, where applicable

Creem then issues a license key by email. That key, and the fact that it's associated with a license instance on your device, is what Earkeep itself stores and checks.

License activation and validation. When you activate your license, Earkeep calls Creem's license API to register your device as that license's active instance, and checks in periodically afterward to validate the license is still active. These checks use an offline grace period: Earkeep does not phone home every time you launch the app, and normal offline stretches between checks don't interrupt your use of the app. This is deliberate: license enforcement shouldn't mean constant network chatter, and it doesn't touch your meeting data at all, only the license key and device instance.

Even our website respects your privacy. earkeep.com uses self-hosted, cookieless analytics. Concretely, that means:

• No cookies are set for tracking, so there's no cookie banner to click through, because there's nothing that requires consent under cookie law in the first place.
• No cross-site tracking. Your visit to earkeep.com isn't linked to your activity on other sites, and there's no advertising pixel following you around afterward.
• Only aggregate data is collected: page views, referrers, rough visit counts, and which pages get clicked. None of this is tied to an individual identity, and none of it touches the app or your meetings, which run entirely separately on your device.

If you email [email protected] (support, license issues, feature requests, or anything else), that message and your email address are used only to have the conversation and resolve whatever you wrote in about. We don't add you to a marketing list from a support email, and we don't share your email with anyone outside of what's needed to help you.

Because transcription and storage happen locally on your device, Earkeep the company never holds a copy of your meeting audio or transcripts. There's nothing on our servers to request, correct, or delete on that front, because it was never sent to us: your device is the only place that data ever exists.

The data that does involve us is narrower and handled by named parties:

• Purchase data (email, payment, license key) is processed by Creem as merchant of record. Rights around that data (access, correction, deletion) are best exercised through Creem directly, or by emailing us and we'll help route the request.
• Support email correspondence is held only as long as needed to resolve your request. Email [email protected] if you'd like a copy of, or the deletion of, correspondence you've sent us.
• Website analytics are aggregate and not tied to an individual, so there's no per-person record to request or delete.

For any privacy question or request not covered above, email [email protected] and we'll sort it out directly. There's no ticketing system standing between you and an answer.

If this policy changes, we'll update the effective date and describe what changed. Because Earkeep is local-first by design, we don't expect the core promise (your audio and transcripts never leave your device) to change; if it ever did, that would be the most prominent thing on this page, not a quiet edit.

Questions about any of this go to [email protected].