Privacy

Where your data goes, and where it does not.

This is not a privacy policy written to hide the ball. It is a plain description of what actually happens when you use Verenu.

What happens when you speak

1

You hold the hotkey

Audio is recorded locally by the app and held in memory. It does not touch a server until you release the key.

2

Audio goes to your provider

The recording is sent directly to the transcription provider you configured, using your own API key.

3

Text goes to cleanup

The raw transcript, plus the active context group's vocabulary, snippets, and style instructions, is sent to your selected cleanup provider.

4

History stays local

The final text, settings, context groups, vocabulary, snippets, and credentials stay on your device unless you export them.

What stays and what leaves

Stays on your device

  • API keys in Credential Manager or Keychain
  • Settings in local app storage
  • Transcription history in local SQLite
  • Context groups, vocabulary, snippets, and auto-learn data
  • Logs unless you choose to export them

Leaves only by your choice

  • Recorded audio to your transcription provider
  • Raw transcript to your cleanup provider
  • Active context group's vocabulary, snippets, and style instructions with cleanup requests
  • Update checks to the Verenu release metadata cache
  • Coarse product analytics on supported builds, when enabled

Optional product analytics

Supported builds use PostHog to help us understand coarse product usage and reliability. It is enabled by default, but you can turn it off during onboarding or at any time in Settings → Privacy. This is pseudonymous usage analytics, not an account system or a claim of mathematical anonymity.

What it measures

  • Coarse feature usage and reliability categories
  • Settings adoption and safe pipeline timing buckets
  • Basic app and operating-system metadata
  • A temporary randomized pseudonymous identifier, unrelated to accounts or devices

What it never receives

  • Dictated audio, transcripts, or cleaned text
  • Prompts, clipboard contents, window or app contents, URLs, or accessibility text
  • Credentials, microphone names, or raw error messages

Cookies and this website

This site (verenu.com) does not use analytics, advertising, or tracking cookies, and does not run any third-party tracking scripts. It uses your browser's local storage only to cache release and docs data you've already requested, so pages load faster on repeat visits. That cache never leaves your browser and is not used to identify or track you across sites.

Provider policies still matter

When you send audio or text to Groq, OpenAI, Google, or AssemblyAI, that provider's privacy policy applies to that data. AssemblyAI is a transcription-only provider. Verenu cannot control what those providers do with your data.

If you need to minimize what leaves your machine, choose a provider with strong data policies. Local support is in early development.

Read your provider's current API data handling terms before you use a key. That is the one place where the privacy story can change outside this site.

Who runs this

Verenu is an open-source project published under the Verenu GitHub organization, not a registered company. Privacy questions, data requests, or complaints: hello@verenu.com. Verenu is developed from Canada and this policy is written with Canadian privacy law (PIPEDA) as its baseline.