Skip to content
Back to home

Privacy Policy

In a nutshell

  • Audio is processed in real time and never stored
  • API keys are stored only on your device
  • Translation runs on your computer; optional non-content product telemetry goes to our analytics service
  • We do not sell your data; speech APIs process audio and text only in transit (with your own keys where applicable)

What data we process

MeetVoice processes the following types of data:

Speech audio — transmitted in transit through the speech recognition API (Deepgram) and text-to-speech (built-in voice, or OpenAI if API key provided). Audio is not stored on our servers or anywhere else.

Translation text — transmitted in transit through the translation API (Groq or OpenAI). Text is not stored.

API keys (BYOK) — your Deepgram and Groq keys (OpenAI optional) are stored exclusively in the browser's local storage (chrome.storage.local) on your device.

Extension settings — UI language, translation languages, operating mode — stored locally in the browser.

License key — stored locally in the desktop application.

Product analytics — the desktop app sends non-content telemetry to analytics.meetvoice.app; welcome pages record anonymous pageviews via a browser beacon only after you enable MeetVoice site analytics in the cookie banner (see Product analytics below). Independently of the banner, welcome pages also count aggregate visit totals (date, page, country only) — this counting stores no identifiers and accesses nothing on your device, so it does not require consent.

Website analytics — with your consent, Google Analytics collects anonymous data about visits to meetvoice.app.

Advertising data — with your consent, Google Ads may use cookies on meetvoice.app.

How we use data

Audio and text are used exclusively to provide the real-time translation service. Data is processed in transit and not stored.

Analytics are used to improve the website and product. Advertising data is used to attract new users.

Third parties

MeetVoice uses the following third-party services:
Service Data Purpose
Deepgram Audio (in transit) Speech recognition (STT)
Groq Text (in transit) Translation (primary)
OpenAI Text (in transit) Translation and TTS (optional)
Microsoft (Edge TTS) Audio (in transit) Text-to-speech (free)
Lemon Squeezy Email, payment data Payment processing
Google Analytics Anonymous data Website analytics
Google Ads Cookie data Advertising
Cloudflare IP, request metadata Hosting, CDN, protection
MeetVoice Analytics device_id, session metrics, country (ISO-2) Product analytics (desktop); welcome pageviews

When using your own API keys (BYOK), data is sent directly to the providers. MeetVoice does not see or store this data.

Storage and security

Audio and text are not stored — they are processed exclusively in real time.

API keys are stored in chrome.storage.local — the local storage of the Chrome profile.

The license key is stored locally in the desktop application.

The MeetVoice desktop server runs on localhost. Audio (for speech recognition) is sent from your computer directly to Deepgram. Translation text passes in transit through MeetVoice's stateless cloud proxy — it is not stored. The extension communicates with the local server via a local WebSocket connection.

Cookies and tracking

The meetvoice.app website may set Google Analytics and Google Ads cookies for visit analytics and ad personalization. Cookies are loaded only after you accept them in the cookie consent banner shown on your first visit. By default, analytics and marketing tracking are disabled.

First-party welcome-page measurement (MeetVoice site analytics) runs only if you enable it in the cookie banner. It stores a random identifier in localStorage and sends an anonymous pageview to analytics.meetvoice.app.

The MeetVoice Chrome extension does not use cookies.

Your rights

Most MeetVoice data stays on your device (extension settings, API keys, license). Uninstall the extension and/or desktop app to remove it locally.

The desktop app sends non-content product telemetry to our analytics service (see Product analytics above) — not meeting audio, transcript text, or API keys. To request deletion of telemetry linked to your device, email support@meetvoice.app.

Opt out of Google Analytics on the website via the browser add-on.

Deactivate your license in the desktop app. Payment records are held by Lemon Squeezy as merchant of record.

Contact

For privacy-related questions, contact us:

Data controller

Controller: Oleksii Herasymchuk, Zhytomyr, Ukraine. Email: support@meetvoice.app.

For purchases, Lemon Squeezy (merchant of record) also processes buyer email and payment data under their own privacy policy.

Product analytics

Desktop app. Sends non-content telemetry to analytics.meetvoice.app: a random device_id, session timing, UI/peer languages, TTS/translation providers, trial vs paid flag, app version, OS family, OS version, and country (ISO-2, derived from network edge, not stored as IP). We do not receive meeting audio, transcript text, or API keys.

Welcome pages. The browser sends a beacon only if you enable MeetVoice site analytics in the cookie banner. The beacon carries a random anonymous_id (stored in localStorage after opt-in), page path, country (ISO-2), referrer (query string stripped), and UI language — not your name, email, or meeting content.

Retention: session, event, and pageview records are deleted after 90 days. Payment records retained by Lemon Squeezy follow their policies.

Legal bases (GDPR)

Contract / legitimate interest: product telemetry to operate and improve MeetVoice; aggregate, identifier-free welcome-page visit counting (no cookies or device storage).

Consent: Google Analytics, Google Ads, and MeetVoice site analytics (welcome page) on meetvoice.app — all via the cookie banner.

Payment: processed by Lemon Squeezy as separate controller for checkout.

Your rights

You may request access, correction, deletion, or restriction of personal data we control by emailing support@meetvoice.app. Local app data can be removed by uninstalling the extension and desktop app.

EU/EEA residents may lodge a complaint with their local supervisory authority. Ukraine: Office of the Ukrainian Parliament Commissioner for Human Rights (data protection).

Google Analytics opt-out: browser add-on.

Last updated: May 20, 2026