Privacy Policy

MeetVoice processes the following types of data:

Speech audio — processed in transit only. Audio streams from your computer through the MeetVoice speech-recognition server (hosted on Cloudflare) to Deepgram and is never stored. Older app versions that still offer the optional own-Deepgram-key setting, and self-hosted MeetVoice servers configured with their own Deepgram key, send audio directly to Deepgram instead, bypassing the speech-recognition server. Voiceover sends the translated text to a speech-synthesis service — Google Cloud Text-to-Speech by default, Microsoft Edge TTS as a fallback — and receives the audio back, also in transit only.

Translation text — transmitted in transit through MeetVoice's stateless translation proxy to the translation API (Gemini by Google, or OpenAI). Text is not stored.

Own Deepgram key (older versions) — older versions of the extension could store an optional Deepgram key in the extension's own isolated storage (IndexedDB), which web pages, including meet.google.com, cannot access; the current version deletes a stored key when it updates. While such a key is in use, the desktop app sends MeetVoice's translation proxy a one-way hash (SHA-256) of the key instead of the key itself, to rate-limit requests; MeetVoice's servers never receive the key. If you connect the extension to a remote server, the server address you confirmed is kept in the same isolated storage and is never sent to MeetVoice's servers.

Speech-recognition usage metering — to enforce plan quotas and prevent abuse, the speech-recognition server stores a hash of your license key, a device identifier, and usage counters (seconds of recognition). Raw IP addresses are never stored — trial limits use a daily hash (SHA-256 of IP + date). Usage records contain no audio and no text.

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.

Audio and text are used exclusively to provide the real-time translation service. Data is processed in transit and not stored. Usage counters are used solely to enforce plan quotas and prevent abuse.

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

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

The remote server address you confirmed is kept in the extension's own IndexedDB — isolated storage on your device that web pages, including meet.google.com, cannot access. It is not synced to your other devices and is deleted when you reset the connection to automatic or uninstall the extension. A Deepgram key saved by an older version of the extension is deleted from the same storage when the extension updates.

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 through the MeetVoice speech-recognition server to Deepgram; older versions with your own key, and self-hosted servers with their own key, send it 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.

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.

Most MeetVoice data stays on your device (extension settings, the confirmed remote server address, 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 or speech-recognition usage records linked to your device or license, 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.

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.

Desktop app. Sends non-content telemetry to analytics.meetvoice.app: a random device_id, session timing, UI/peer languages, voice/translation providers, trial vs paid flag, app version, OS family, OS version, country (ISO-2, derived from network edge, not stored as IP), and translation quality signals (a category code such as "empty" or "unchanged", plus a rounded ratio between source and translation length). 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.

Chrome extension. Sends daily counts of which extension features and settings you use — for example opening the transcript panel, exporting a transcript or generating a summary, or changing a setting away from its default — to analytics.meetvoice.app through the desktop app. We do not receive meeting audio, speech, transcript or translation text, participant names, glossary terms, or API keys. These counts are tied to the same random device_id as the desktop telemetry above, plus the extension version, and are deleted after 90 days. You can turn this off in the extension’s Settings → Advanced (“Send usage statistics”).

Retention: session, event, and pageview records are deleted after 90 days; speech-recognition server usage records (license-key hash, device identifier, usage counters) are deleted after at most 12 months of inactivity. Payment records retained by Lemon Squeezy follow their policies.

Contract / legitimate interest: product telemetry to operate and improve MeetVoice; aggregate, identifier-free welcome-page visit counting (no cookies or device storage); Chrome extension feature and settings usage counts (see Section 9), processed under the same legitimate interest, with an opt-out in Settings → Advanced.

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.

Contract: speech-recognition usage metering (license-key hash, device identifier, usage counters) is processed as necessary to provide the subscription service you signed up for.

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.