Privacy Policy
In a nutshell
- Audio is processed in real time and never stored
- API keys are stored only on your device
- The server runs locally on your computer
- We do not sell or share your data
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.
Analytics data — Google Analytics collects anonymous data about visits to meetvoice.app.
Advertising data — 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
| 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) |
| LemonSqueezy | Email, payment data | Payment processing |
| Google Analytics | Anonymous data | Website analytics |
| Google Ads | Cookie data | Advertising |
| Cloudflare | IP, request metadata | Hosting, CDN, protection |
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 uses Google Analytics cookies for visit analytics and Google Ads for ad personalization.
The MeetVoice Chrome extension does not use cookies.
You can opt out of analytics via your browser settings or the Google Analytics opt-out plugin.
Your rights
All MeetVoice data is stored locally on your device. To delete it, simply uninstall the extension and/or desktop application.
You can opt out of Google Analytics via the opt-out plugin.
You can deactivate your license through the desktop application.
Data export is not applicable — MeetVoice does not store your data on servers.
Contact
Last updated: March 18, 2026