MeetingMemo Server Privacy Policy
Effective: July 2026 · Last updated: July 2026
The short version: MeetingMemo Server is an optional, opt-in feature. When you turn it on, only your meeting's transcript text is sent to our server, which forwards it to an AI provider to generate a summary, action items, and answers to your questions about the meeting. Your audio never leaves your Mac. The text is processed and discarded - it is never stored on our servers or in our logs - and it is not used to train any model. This is a separate policy that covers only this feature; everything else about the app is described in the main Privacy Policy.
1. Scope
This policy covers only the optional MeetingMemo Server feature - a hosted-AI path for generating meeting summaries, action items, and chat answers. It is off by default and requires your explicit, in-app opt-in before any data is sent. If you never turn it on, nothing described here happens. For how the rest of MeetingMemo handles your data - on-device recording and transcription, iCloud sync, on-device AI, and bring-your-own-key cloud AI - see the main Privacy Policy.
2. What Is Sent
When you use MeetingMemo Server, only your meeting's transcript text is sent for processing. Your audio never leaves your device. Recording and transcription still happen entirely on your Mac; only the resulting text is transmitted. No MeetingMemo account or personal profile is created for this feature.
3. Where It Goes
The transcript text is sent to MeetingMemo's own server - a Cloudflare Worker - which forwards it to Groq, running the open-source gpt-oss-120B model (an OpenAI open model), hosted in the USA. The generated summary, action items, and chat answers are returned and shown to you in the app.
4. Retention
MeetingMemo's server is a pass-through, not a store. Your transcript, the generated summary, and any other AI-generated text are never stored on our servers or in our logs. Each request is processed and then discarded. Processing runs under Zero Data Retention terms we have contracted with the provider, and your content is not used to train any model.
5. What We Do Store
The only data we store is non-content, operational information tied to your subscription - never your meeting content. Specifically:
- The RevenueCat subscriber identifier.
- Your remaining points balance.
- A cached subscription status.
- Aggregate request and token counts (counts only, never content).
6. Access Control
MeetingMemo Server requires an active MeetingMemo subscription. Requests are authorized by your RevenueCat subscriber identifier so that the feature is available only to entitled subscribers.
7. Your Control
You are always in control of this feature:
- It is off by default, and you opt in explicitly in the app before anything is sent.
- You can turn it off at any time in Settings.
- You can instead use the fully on-device AI path (via a local Ollama instance) or the bring-your-own-key path - with either of those, no data leaves your device to us.
8. Third-Party Processing
We only make representations about our own handling of your data. The transcript text is forwarded to Groq for processing under the Zero Data Retention terms described above; beyond those contracted terms, we do not make representations about the provider's internal data practices. Groq's own processing is governed by its privacy policy, and infrastructure is provided by Cloudflare.
9. Contact
If you have any questions about this policy or how MeetingMemo Server handles your information, please contact us at:
Changes to This Policy
We may update this policy from time to time. Any changes will be posted on this page with an updated revision date, so you can review what changed.