Eavesy

Privacy

Last updated: 2026.

What we promise

  • Local + cloud, both real. On desktop, every meeting lives as a real folder on your disk — Markdown summary, full transcript, audio, JSON metadata — in addition to the cloud copy. You can open these in Obsidian, drag them to Dropbox, or inspect them in VS Code.
  • Encrypted in transit and at rest. TLS protects data in transit. Cloudflare-managed encryption protects R2 objects and D1 data at rest.
  • API keys in your OS keychain on desktop. Encrypted at rest in the cloud for web/mobile.
  • Operational analytics do not receive recording content, audio, transcript text, summaries, or notes. PostHog and Sentry receive product events and diagnostic errors only.
  • Eavesy does not train models on recording content. Cloudflare Workers AI and Anthropic’s commercial API state that customer content is not used for model training without an explicit opt-in. A connected OpenRouter account follows the provider privacy settings you control there.
  • Portable export. Download a meeting bundle or an individual capture from its detail page; Mac sessions also remain as normal local files.
  • Deletion that includes cloud copies. Delete individual captures in the app. Until self-service account deletion ships, contact support for full account removal; local folders remain under your control.

Who sees your data

A clear, public list of every third party that ever touches user data:

  • Anthropic — AI summaries & action-item extraction under its commercial API policy
  • Cloudflare — all infrastructure (Workers, R2, D1, Vectorize, Queues, KV), plus Workers AI for transcription (Whisper) and semantic-search embeddings
  • Clerk — authentication
  • OpenRouter — optional bring-your-own AI connection
  • Stripe — billing when paid plans are enabled
  • Sentry — operational error diagnostics without recording content
  • PostHog — product usage events without recording content

BYO keys

Settings lets you connect OpenRouter or supply your own Anthropic key for summaries and chat. When configured, those calls bill to your account. Calls still flow through Eavesy so the service can assemble the requested context and prompts.