MeetMi Privacy Policy

Version: managed-ai-apple-pages-v8
Effective: 2026-11-14 (v7: 2026-11-06, v6: 2026-11-01, v5: 2026-10-04, v4: 2026-09-27, v3: 2026-09-26, v2: 2026-09-19, v1: 2026-08-29)
Applies to: MeetMi Managed AI distributed through the Apple App Store on macOS and iPhone. Both apps are one App Store record with one shared subscription and use this same policy.

MeetMi is developed by Jin Lu, the developer and seller shown on the App Store listing. Privacy questions and requests: support@meetmi.ai.

中文 · Support

1. Scope

This policy applies to MeetMi Managed AI sold through the Apple App Store.

MeetMi Local is a separate BYOK product with a different app identity, storage, preferences, logs, and Keychain service. It uses the user’s API key to connect directly to a user-selected endpoint: OpenRouter, another HTTPS Responses endpoint, or the Claude API. Local does not use the MeetMi relay, subscription entitlement, or Credit system.

2. On-device processing

• The microphone and, on macOS, system audio are used only after the user starts a meeting.
• MeetMi does not save or upload raw audio.
• Speech recognition and subtitle translation use Apple on-device capabilities.
• Transcripts, advice, analysis, notes, workspace indexes, and extraction caches are stored on the device or in a user-selected workspace by default.
• With iCloud sync on (the default; it can be turned off in Settings), meeting history — each meeting’s transcript, advice, analysis, notes, marks and title — is also kept in the user’s own private iCloud database and synced to the user’s other devices running MeetMi with the same Apple Account. This uses Apple’s CloudKit under Apple’s iCloud terms; the developer cannot read that database, and nothing synced passes through the MeetMi relay. Workspaces sync too: each one’s name and a copy of its AGENTS.md (each meeting also keeps the AGENTS.md it ran with) and, unless the user turns background material off separately in the same place, the names of its documents and the text MeetMi extracted from them. The documents themselves, where folders are on each device and access to them, document indexes, caches and semantic vectors, settings and keys are not synced. When a workspace’s folder is in iCloud Drive, its place within the user’s iCloud Drive (for example Clients/ACME) syncs too, so the user’s other devices can open the same folder without choosing it again. Turning sync off stops syncing on that device; it does not delete what is already in iCloud.
• On iPhone the microphone is the default and the only audio source on iOS 26. From version 1.0.1 on iOS 27, the user may also turn on system audio: at the start of each meeting iOS shows its own sharing sheet, and once the user agrees MeetMi receives the sound the phone is playing (a video, a lecture, a podcast). Only the sound is used; screen frames are discarded as they arrive and are never stored or uploaded. iOS does not pass call audio (phone, FaceTime, WeChat, Zoom and similar) to any app, so calls cannot be heard this way. A meeting the user has started keeps transcribing while the phone is locked or another app is in front; it stops when the user ends or pauses it. From version 2.0, while a meeting runs the Lock Screen and Dynamic Island show that MeetMi is listening and up to three keywords from the latest advice, never the advice text or the transcript; the user can turn the keywords off in Settings. They are shown on the device only.

3. Managed cloud AI

After explicit consent, MeetMi may send the on-device transcript, user questions and stated concerns, existing analysis, task context, relevant workspace snippets requested by AI, and protocol data needed for strict tools and structured output.

Recipients from version 1.3:

MeetMi (App Store, macOS or iPhone) → MeetMi relay → Anthropic (Claude Haiku 5.5)
Only if Claude cannot answer:          MeetMi relay → OpenRouter → DigitalOcean, Morph, CoreWeave or Together (DeepSeek V4 Flash)

Versions 1.2 and earlier use only the OpenRouter route.

The relay sends each request to Anthropic’s Claude API first. If Claude cannot answer it (an outage, a timeout, or a request Claude declines), the relay sends the same request through OpenRouter to one of the providers named in the in-app data notice, which answers instead.

The relay does not intentionally persist or log transcripts, questions, document snippets, request bodies, upstream error bodies, or streamed response content; it holds an answer in memory only until the answer is complete. The AI services process what they receive under their own terms:

• Anthropic deletes Claude API inputs and outputs within 30 days and does not use them to train its models. Content that Anthropic’s automated safety systems flag may be kept for up to 2 years, and longer where the law requires.
• On the OpenRouter route, OpenRouter and the provider process the request under their own terms.

Upstream services see the relay’s network address rather than a direct connection from the user’s device. So that a safety action Anthropic takes applies to one user rather than to all of MeetMi, the relay registers each user with Anthropic under an opaque label derived from the purchase or download record (no name, email or Apple ID) and attaches it to that user’s requests. Every request the relay sends to OpenRouter, from any version of the app, carries the same label, and OpenRouter passes only a hash of it on to the provider.

Before sending, the app displays the relay domain, the routes and models, the data scope, and the policy version. A material change to recipients, model, providers, scope, or policy invalidates prior consent and requires renewed consent.

4. Web search

Web search is off by default, is stored as its own consent record separate from the recording notice and Managed AI consent, and can be withdrawn on its own. It is used only by Deep Research and MeetMi discussions; realtime advice and meeting notes never go online, and that is enforced on the server, not merely by a setting in the app.

Provider and domain. The search provider is Exa (api.exa.ai). Requests are forwarded by the MeetMi relay, so Exa sees the relay’s network address rather than a direct connection from the user’s device. This path is separate from the AI inference chain and does not pass through OpenRouter.

What is sent. Only the search terms the model distils from meeting content. When the original text is needed, the result URL is also sent and Exa fetches the page. The full transcript, workspace documents, and the user’s own questions are not sent to Exa.

Retention and training. Exa’s published terms state that search terms sent to it may be retained and used to improve and train its own models. Search terms are distilled from meeting content and may contain company names, personal names, and other proper nouns mentioned in the meeting. The user must explicitly acknowledge this when first enabling web search before the feature becomes active. Exa’s terms: https://exa.ai/privacy-policy.

International processing. Exa is a US provider and requests are processed on its servers.

Renewed consent. A change to the search provider, its domain, or the web-search policy version invalidates existing web-search consent and requires a fresh acknowledgement. Such a change does not affect the recording notice or Managed AI consent.

Availability. Web search comes with the subscription. The free weekly allowance does not include it, and the relay refuses search requests made with a free-allowance token. It is off by default and stays off until the user turns it on and acknowledges the retention notice above.

5. Apple purchases, entitlement, and Credit

• Purchases and subscriptions are processed through Apple StoreKit and the App Store. MeetMi does not process full card details in the app.
• Necessary StoreKit transaction JWS data and an opaque association value may be sent to the MeetMi relay to validate subscription, refund, revocation, and restoration and to issue a short-lived access token.
• The free weekly allowance needs no purchase. To grant it, the app sends the App Store’s signed record of the download (StoreKit AppTransaction) to the MeetMi relay. The relay checks Apple’s signature and keeps an opaque subject derived from the download identifier, that week’s allowance, the content-free request records described in section 6, and, from version 1.3, the identifier of the opaque Anthropic registration described in section 3. It never receives an Apple ID or email.
• JWTs contain no Apple ID, email, full transaction JWS, or OpenRouter key.
• The service stores entitlement, Credit, and content-free usage against an opaque subject.
• MeetMi is free to start: each Apple Account gets 250 Managed AI credits a week at no charge, reset every Monday 00:00 UTC and shared by the Mac and iPhone apps. Unused credits do not carry over. A monthly subscription (three plans from version 2.0, differing only in the size of the allowance) adds a larger allowance that resets with the subscription period, plus web search. The subscription is a universal purchase: one subscription covers the Mac and iPhone apps, and its allowance is one pool shared by both.
• MeetMi does not sell Credit top-ups. If consumable IAP Credit is introduced later, it will be accounted for separately from monthly allowance and will not expire merely because a monthly period resets.
• If entitlement or Credit is unavailable, new AI requests stop while on-device transcription, translation, history, and export continue.

6. Credit metering

The technical baseline meters input tokens + 2 × output tokens and converts that amount to Credit. Claude counts the same text as about 1.9 times as many tokens, so a Claude answer is metered at its token count divided by 1.9, and at no less than its cost allows (one credit covers at most $0.002 of Claude usage). When Claude cannot answer and OpenRouter answers instead, only the answer that arrives is charged. Content-free usage is recorded by activity: meeting listening, user questions, deep research, advisor discussion, and meeting notes.

The relay also keeps one content-free record of each AI request, for subscribers and free users alike: the first characters of the opaque subject, whether the request was free or under a subscription, which provider answered, the activity, token counts, the Credit charged and what the provider charged MeetMi. It contains no meeting content, question, document, Apple ID or email. These records are kept in Cloudflare Workers Analytics Engine for three months and are used only to run the service: to see usage and cost, and how many people come back.

The app may show Credit, period reset, activity breakdown, and a settings-based meeting-time estimate. The estimate is not a guarantee. MeetMi Local does not use Credit.

7. Local logs and caches

Detailed debug logging is off by default. When enabled it may contain meeting content, prompts, and diagnostics, but authentication headers, Apple transaction credentials, JWTs, licenses, API keys, and cookies are excluded or redacted.

Users can clear logs and rebuildable document caches. Production relay configuration disables request-content observability and does not use Tail, Logpush, Sentry, or another service to log meeting content.

8. Controls and deletion

Users can decline or withdraw Managed AI consent, disable or withdraw web-search consent, use Apple’s subscription management and restore-purchase features, delete meeting history, clear caches and logs, and delete files in their own workspaces.

With iCloud sync on, deleting a meeting deletes it from iCloud and from the user’s other devices too. Removing a workspace removes it from the user’s other devices as well; no device’s folder or files are touched. MeetMi’s data can be removed from iCloud in the iCloud storage settings of the user’s Apple Account; the meetings on each device stay, and they are synced again only when the user chooses to in Settings.

Removing the app may not remove files in a user-selected workspace. Those files are managed by the user in Finder (macOS) or the Files app (iPhone). A request to delete server-side entitlement or usage records is separate from deleting local or workspace files; email support@meetmi.ai.

9. Third parties, international processing, and security

Apple, Anthropic, OpenRouter, the providers named in the active policy, and — once the user separately consents to web search — the search provider Exa may process relevant data outside the user’s country under their own policies.

What syncs through iCloud — meeting history, workspaces and the text extracted from documents — is stored by Apple in the user’s private CloudKit database under Apple’s terms. Syncing sends none of it to Anthropic, OpenRouter, AI providers or Exa.

Controls include a strict request allowlist, a provider allowlist, store=false, price limits, short-lived JWTs, separate Keychain storage, App Sandbox, encrypted transport, and content-logging prohibitions. No internet transmission can be guaranteed absolutely secure.

Anthropic privacy information: https://www.anthropic.com/legal/privacy

OpenRouter privacy information: https://openrouter.ai/privacy

Exa privacy information: https://exa.ai/privacy-policy

10. Recording and user responsibility

Meetings may contain another person’s personal information, confidential information, or regulated data. The user is responsible for notices, permissions, and authority required by applicable law, contract, organisational policy, and meeting rules.

System microphone/screen-recording permission, MeetMi’s recording notice, and Managed AI consent are not consent from other participants.

11. Children, tracking, and sale

MeetMi is not directed to children, does not perform cross-app tracking, does not sell personal information, and does not use meeting content for advertising.

12. Regional availability

MeetMi is not offered in mainland China until a separate assessment of China’s personal-information (PIPL) and app filing rules is complete. It is available in the App Store’s other countries and regions.

13. Changes and contact

Updates will identify a version and effective date. Material changes to cloud-AI recipients, data scope, purchasing, or retention will also trigger renewed in-app consent or an updated notice.

• Privacy contact: support@meetmi.ai
• Support: Support page
• Public Privacy URL: https://meetmi.ai/privacy/