Skip to content
Back to home

Privacy Policy

In a nutshell

  • Audio is processed in real time and never stored
  • No API keys are required. Your license key is stored in the desktop app and is sent only to activate and check your plan — to Lemon Squeezy and to MeetVoice's servers, which keep just a one-way hash of it
  • Processing starts on your computer; audio and translation text are only in transit — plus optional non-content product telemetry to our analytics service
  • We do not sell your data; audio and text are processed in transit and not stored on our servers; transcripts are kept only on your device; the text sent when a studio voice or its preview plays is retained by the voice provider (see below)

What data we process

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 Soniox, our primary speech-recognition provider, and is never stored. Soniox processes the audio in its EU, US, Japan or India region, depending on your region. Under Soniox's terms, real-time audio and transcripts are not stored unless storage is explicitly enabled (MeetVoice does not enable it) and are not used for training. Soniox does keep service metadata (usage, billing and account data; no audio or transcript text), and the regional commitment does not cover that metadata, which may be processed outside the region. Deepgram is our fallback speech-recognition provider: the server sends the audio there instead — also in transit only and never stored — when Soniox is unavailable or not enabled for your session, and for app versions that predate Soniox support. Your glossary terms, including participant names that are added to it automatically, are sent with the audio to whichever speech-recognition provider processes it, as recognition hints. 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.

Studio voiceover — when a studio voice or its preview plays, the text to be spoken (the translated text, or a sample phrase for a preview) is sent instead to Cartesia or Inworld (United States), depending on the voice you choose, and the audio comes back. The provider retains these requests under its own policy; training on this data is turned off.

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

AI meeting summaries and term explanations — only when you use these features: when you generate or regenerate a summary, export a meeting as PDF or Markdown or copy it for Notion or Slack (these exports create a summary if the meeting does not have one yet), or ask for a term explanation. For a summary, the extension sends the meeting transcript (translated text with timestamps and speaker display names) and the meeting languages through the desktop app and MeetVoice's translation proxy to the language-model provider (Gemini by Google); the list of participant names is also sent to the proxy but is not passed to the model. For a term explanation, it sends the selected term and the original and translated text of the transcript line it appears in, to Gemini, with OpenAI as an automatic fallback in most regions. The text is processed in transit and not stored on MeetVoice's servers; the finished summary is saved only in the extension's history on your device. To enforce request limits, the translation proxy keeps request counters keyed by a hash of your license key (summaries and term explanations) or by a random per-session hash (translation), and separately by a keyed hash of your IP address; stored counters expire 24 hours after the last request.

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, your license's purchase date (to renew the quota each month on your purchase day), 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 in the desktop application on your device; the extension does not store it. To activate and check your plan, the desktop app sends the key over an encrypted connection to Lemon Squeezy (license activation and validation; activation also sends a one-way device identifier computed from your computer's network hardware addresses) and to MeetVoice's speech-recognition server and translation proxy (for summaries and term explanations), which validate it with Lemon Squeezy and keep only a one-way hash of it. The extension connects to the desktop app with short-lived connection tickets that are kept only in memory.

Subscription and payment records — when you buy or change a subscription, Lemon Squeezy notifies MeetVoice. From these notifications, which may include buyer details, MeetVoice keeps only selected fields: Lemon Squeezy customer, subscription, order and invoice identifiers, plan, subscription status and its changes, amounts and currency, and dates — no name, email address, billing address or card details. To link a subscription to its usage, MeetVoice also looks up the license key through the Lemon Squeezy API and keeps only a one-way hash of it, with the license status and expiry date. If you allowed Google Ads cookies on meetvoice.app (or they are on by default in your country) and came to the site from a Google ad, the ad click identifier (gclid) is added to the checkout link and stored with the payment record, so that purchases can be attributed to ad clicks. A checkout link that already carries the identifier keeps it until the page is reloaded, even if you turn Google Ads off.

Product analytics — the desktop app sends non-content telemetry to analytics.meetvoice.app; welcome pages record pageviews with a random ID via a browser beacon only when MeetVoice site analytics is enabled — by you in the cookie banner or, for visitors in Ukraine and other countries where prior consent is not required, by default until you switch it off (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. The page that opens after you remove the extension is also counted in totals: its visits per day and country, and the reason you choose there per day (without country). So that repeat visits and answers are not counted twice on the same day, the server also keeps a keyed hash of your IP address until the end of that day (UTC) — one for opening the page and one for choosing a reason; the address itself is not stored, and the hash does not record which reason you chose and is not linked to your license, email or device identifier.

Website analytics — with your consent (for visitors in Ukraine and other countries where prior consent is not required, by default until they switch it off), Google Analytics collects data about visits to meetvoice.app.

Advertising data — with your consent (for visitors in Ukraine and other countries where prior consent is not required, by default until they switch it off), Google Ads and the Meta Pixel may use cookies on meetvoice.app. The Lemon Squeezy checkout pages, which are run by Lemon Squeezy, load the Meta Pixel and Google Analytics independently of the meetvoice.app cookie banner and report checkout and purchase events (such as order value and currency).

How we use data

Audio and text are used exclusively to provide the features you use: real-time translation and voiceover and, when you request them, meeting summaries and term explanations. Audio and text are processed in transit and are not stored on MeetVoice's servers; transcripts are saved only on your device. The only exception is the text sent when a studio voice or its preview plays, which the voice provider retains (see above). Usage records (usage counters and the license purchase date) are used solely to enforce plan quotas, prevent abuse, and monitor plan usage and service capacity.

The license key and its hash are used only to check your plan and enforce its limits. Subscription and payment records are used to provide and support your subscription, for accounting, refunds and disputes, and to attribute purchases to advertising.

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

Chrome Web Store Limited Use. MeetVoice's use and transfer of information received from the Chrome extension comply with the Chrome Web Store User Data Policy, including the Limited Use requirements. We transfer this information to third parties only as necessary to provide or improve these features (for example, to the speech-recognition, translation and voice providers listed in this policy), to comply with the law, to protect against abuse, or as part of a merger or sale with your prior explicit consent. These limits also apply to aggregated or de-identified data derived from it. This information is used only to provide and improve the extension's features described in this policy; it is not sold or transferred to advertising platforms, data brokers or other information resellers, not used for advertising or to determine creditworthiness, and people do not read it unless you explicitly agree to that for specific data, it is necessary for security or to comply with the law, or the data is aggregated and de-identified and used only for internal operations. The website and checkout advertising data described in Section 1 is not information received from the extension.

Third parties

MeetVoice uses the following third-party services:
ServiceDataPurpose
SonioxAudio (in transit)Speech recognition (primary); EU, US, Japan or India region
DeepgramAudio (in transit)Speech recognition (fallback)
Cloudflare (MeetVoice speech recognition)Audio (in transit), usage counters, license purchase dateBuilt-in speech recognition and plan-quota metering
Gemini (Google)Text (in transit)Translation, AI meeting summaries and term explanations (primary)
OpenAIText (in transit)Fallback for translation and term explanations; voiceover on self-hosted servers
Google Cloud Text-to-SpeechText (in transit)Voiceover (primary)
Microsoft (Edge TTS)Text (in transit)Voiceover (fallback)
CartesiaText; retained by the provider under its own policy, not used for trainingStudio voiceover and voice previews; United States; no training on this data
InworldText; retained by the provider under its own policy, not used for trainingStudio voiceover and voice previews; United States; no training on this data
Lemon SqueezyEmail, payment data, license key and a one-way device identifier (activation and validation), ad click ID (gclid) added to checkoutPayment processing and license validation (merchant of record)
Google AnalyticsVisit statistics, random cookie IDWebsite analytics
Google AdsCookie dataAdvertising
MetaIP address, page URL, browser and cookie IDs, visits and checkout events; LS purchases: transaction ID, amount, tax and currency. Installer requests and extension store visits.Advertising
CloudflareIP, request metadataHosting, CDN, protection
MeetVoice Analyticsdevice_id, session metrics, country (ISO-2), per-license usage summary, app health and migration events, keyed IP-address hash (page shown after the extension is removed, until the end of the UTC day)Product analytics (desktop); welcome pageviews; page shown after the extension is removed

Older app versions with your own Deepgram API key, and self-hosted servers with their own Deepgram key, send audio 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 is processed in real time and never stored. Text is not stored on MeetVoice's servers; meeting transcripts are saved only locally, in the extension's history on your device. The only exception is the text sent when a studio voice or its preview plays, which the voice provider retains (see above).

AI meeting summaries, and the speaker names shown in transcripts, are kept in the same local history.

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 in the desktop application on your device. It leaves the device only over encrypted connections to check your plan (see Section 1); MeetVoice's servers keep only a one-way hash of it.

The MeetVoice desktop server runs on localhost. Audio for speech recognition is sent from your computer through the MeetVoice speech-recognition server to Soniox (or to Deepgram as the fallback); 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.

Cookies and tracking

The meetvoice.app website may set Google Analytics, Google Ads and Meta Pixel cookies for visit analytics, ad personalization and conversion measurement. Outside Ukraine and other countries where prior consent is not required, cookies are loaded only after you accept them in the cookie consent banner shown on your first visit, and analytics and marketing tracking are disabled by default. For visitors in Ukraine and other countries where prior consent is not required, analytics and marketing cookies are enabled from the first visit and no banner is shown; you can switch them off at any time on the Cookies page. If we cannot determine your location, or your browser sends a Global Privacy Control signal, we show the banner.

First-party welcome-page measurement (MeetVoice site analytics) runs only if you enable it in the cookie banner (in those countries it is enabled by default until you switch it off). It stores a random identifier in localStorage and sends it with a pageview to analytics.meetvoice.app each time you open a welcome page. Withdrawing consent in the cookie banner, or switching site analytics off on the Cookies page, deletes the identifier from your browser.

The Lemon Squeezy checkout pages are run by Lemon Squeezy: they load the Meta Pixel and Google Analytics regardless of your choices on meetvoice.app, under Lemon Squeezy's own cookie and privacy terms.

The MeetVoice Chrome extension does not use cookies.

Controlling your data

Most MeetVoice data stays on your device (extension settings, the confirmed remote server address, the license key — see Section 1). 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. Full payment records are held by Lemon Squeezy as merchant of record; requests about the limited subscription and payment records MeetVoice keeps (see Section 1) go to the same email.

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, 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). It also sends app health events: each app start (time, app version, which desktop app — the current one or the new one — and which operating system family is running, processor architecture, normal or safe mode and its reason, a start that failed and why, a count of recent unstable starts, and whether the app had to restore its settings), a failed start of the app's local translation service, a failed update install, and the steps of the automatic move to the new desktop app (a random move identifier, the attempt number, step and error codes, the version moved from). These events carry the same random device identifier and a rollout group number (0–9), except a failed or safe-mode start sent before the app knows its device identifier, which carries neither. This telemetry contains no meeting audio, transcript text, or API keys.

Welcome pages. The browser sends a beacon only when MeetVoice site analytics is enabled — by you in the cookie banner or, for visitors in Ukraine and other countries where prior consent is not required, by default until you switch it off. The beacon carries a random anonymous_id (stored in localStorage once site analytics is enabled and reused on later visits), the page name, country (ISO-2), referrer (query string stripped), and your browser's language setting — 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. These counts contain no 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 (including app health and migration events) are deleted after 90 days; speech-recognition server usage records (license-key hash, license purchase date, device identifier, usage counters) are deleted after at most 12 months of inactivity. Our analytics service also keeps a per-license usage summary from the speech-recognition server (license-key hash, plan, seconds used, number of devices, and the start and end of each quota period, which show the day and time of purchase); each summary is deleted 365 days after its quota period ends. Payment records retained by Lemon Squeezy follow their policies. The subscription and payment records MeetVoice receives from Lemon Squeezy are kept for accounting, refunds and dispute handling and are not deleted automatically; the ad click identifier (gclid) stored with a payment is erased 365 days after the payment. Request-limit counters expire 24 hours after the last request. The IP-address hashes used on the page shown after the extension is removed expire at the end of the UTC day, at most one minute after midnight.

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); aggregate counting on the page shown after the extension is removed, including the reason chosen there, with a keyed hash of the IP address kept until the end of the day (UTC) so that repeat visits and answers are not counted twice (no cookies or device storage); per-license usage summaries from the speech-recognition server (see Section 9) to monitor plan usage and service capacity; 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 (including the ad click identifier added to the checkout link), the Meta Pixel, and MeetVoice site analytics (welcome page) on meetvoice.app — via the cookie banner; for visitors in Ukraine and other countries where prior consent is not required, these are enabled by default until the visitor switches them off.

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

Contract: speech-recognition usage metering (license-key hash, license purchase date, device identifier, usage counters) is processed as necessary to provide the subscription service you signed up for. The same applies to license-key validation, AI meeting summaries and term explanations you request, and the subscription and payment records MeetVoice receives from Lemon Squeezy (also kept for accounting and legal obligations).

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: November 12, 2026