Privacy Policy
In a nutshell
- Audio is processed in real time and never stored
- API keys live only on your device — and only if you add one (they are optional)
- Processing starts on your computer; audio and translation text travel only in transit — plus optional non-content product telemetry to our analytics service
- We do not sell your data; audio and text are processed only in transit — never stored
What data we process
MeetVoice processes the following types of data:
Speech audio — processed in transit only. With the built-in speech recognition (trial and all paid plans), audio streams from your computer through the MeetVoice speech-recognition server (hosted on Cloudflare) to Deepgram and is never stored. If you connect your own Deepgram key, audio goes directly from your computer to Deepgram, bypassing the speech-recognition server. Voiceover uses the built-in voice (Microsoft Edge TTS), 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.
Optional API key (BYOK) — if you add your own Deepgram key, it is stored exclusively in the browser's local storage (chrome.storage.local) on your device.
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.
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. 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.
Third parties
| Service | Data | Purpose |
|---|---|---|
| Deepgram | Audio (in transit) | Speech recognition |
| Cloudflare (MeetVoice speech recognition) | Audio (in transit), usage counters | Built-in speech recognition and plan-quota metering |
| Gemini (Google) | Text (in transit) | Translation (primary) |
| OpenAI | Text (in transit) | Translation (fallback), optional voiceover |
| Microsoft (Edge TTS) | Audio (in transit) | Voiceover (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 |
If you use your own Deepgram API key, audio is sent directly to Deepgram, bypassing the MeetVoice speech-recognition server — MeetVoice does not see or store it. Translation never needs an API key.
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 through the MeetVoice speech-recognition server to Deepgram — or directly to Deepgram if you use your own key. 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 or speech-recognition usage records linked to your device or license, email [email protected].
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
Data controller
Controller: Oleksii Herasymchuk, Zhytomyr, Ukraine. Email: [email protected].
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, voice/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; 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.
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.
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.
Your rights
You may request access, correction, deletion, or restriction of personal data we control by emailing [email protected]. 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: July 23, 2026