Privacy, in plain language
Where your conversation data goes
Recording and transcription happen on your device. Cloud features are optional and have different data paths, which we explain below without collapsing everything into “the cloud.”
Last updated: October 20, 2026
Android and Windows updates
When you join the platform list, we store your email and signup date in Supabase and send a welcome email through Resend. No email verification is required. We use your email for the welcome and platform launch announcements; you can unsubscribe using the link in any email. We use limited, hashed request information to prevent abuse.
Unsubscribing stops pending and future platform emails. It does not change your free-month offer or App Store subscription. Contact founder@edgefirst.app to request deletion.
Small-team conversations
When you choose a time for a team call, we share your name, email, company, company size and optional preparation note with Calendly to arrange the meeting. Google Meet provides the call link. The calendar loads only after you continue from the form. These details are used to prepare for and manage your call, not to enroll you in marketing emails.
Meetly for lawyers early access
If you save a place on the lawyers page, we store your email, the page you signed up on, and whether our confirmation email was delivered. We use it to send that confirmation and to tell you when Meetly for lawyers launches. Every email has an unsubscribe link. We do not collect recordings or transcripts through the form.
Meetly Capsule updates
If you ask to be notified about Capsule, we store your email, the page you signed up on and the status of our confirmation email in Supabase, and send that email through Resend. You only receive Capsule launch news and early-bird pricing after you confirm your email with the link we send. Every email has an unsubscribe link. We use limited, hashed request information to prevent abuse. Contact saubhagya@edgefirst.app to request deletion.
Free month of Meetly Pro
If you sign up, we store your email, the role you pick, feedback and scheduling preference, confirmation and offer-delivery status, and program email preferences to provide your offer and ask for feedback. Signing up agrees to setup and feedback emails, including an invitation to a short conversation. You can unsubscribe through any of these emails or contact us. This does not change your App Store subscription.
Feedback calls are optional. If you book one, Calendly manages scheduling, rescheduling and cancellation; Google Meet provides the call link. Booking a call does not confirm your email or affect your free offer.
We do not collect recordings or transcripts through the form. If you have explicitly opted into website analytics, your anonymous analytics identifier may connect the signup to website activity. Confirmation and unsubscribe links are excluded from analytics and replay. Offer details.
The short version
- • Meetly records and transcribes locally. Cloud AI receives transcript text, not recording audio.
- • Cloud AI is off by default. Nothing is sent until you tap Allow on a permission screen that lists what is sent and who receives it, and you can turn it off at any time.
- • Cloud AI routes only through OpenRouter, to Anthropic Claude Haiku (on Amazon Bedrock or Google Vertex) and OpenAI GPT models (on Microsoft Azure). The global route requires formal Zero Data Retention and is never used for training; providers for mainland China, Hong Kong and Macau may keep requests for a limited time, also never for training.
- • Optional iCloud Library Sync can sync recordings and meeting data to your private CloudKit database. Optional Connect AI stores encrypted meeting text and metadata, never audio.
- • If no privacy-compliant AI endpoint is available, Meetly fails closed instead of silently sending the meeting somewhere else.
Your data map
The exact path depends on the features you enable. Swipe the table horizontally on a small screen.
| Data | On your device | Optional iCloud sync | Cloud AI summary | Meetly storage |
|---|---|---|---|---|
| Recording audio | Recorded and stored locally. | Synced to your private Apple CloudKit database when Library Sync and its separate audio backup option are enabled. Transfers are encrypted in transit. | Not sent. | Meetly does not operate a recording-storage server. |
| Transcript and meeting details | Stored locally with the meeting. | Transcript, summary, metadata, and supported preferences can sync through CloudKit. | When Cloud AI summaries are enabled, relevant transcript text, your notes and attached note photos are sent for summary and title generation, including automatic processing. Recording audio is not included. | No Meetly summary backend stores a plaintext copy. Connect AI is a separate, optional encrypted service described below. |
| Generated summary | Returned to and stored on your device. | Can sync with its meeting when Library Sync is enabled. | Processed transiently by OpenRouter and the selected model provider under the controls below. | Not retained by a Meetly summary server. |
| Operational and product telemetry | App settings and local diagnostic state. | Apple processes CloudKit operational metadata under its terms. | Request time, model/provider, token use, latency, cost, request IDs, IP/network and abuse-prevention data may be processed. | Analytics is enabled by default and can be turned off in app Settings. Meetly sends a minimal allowlisted set of content-free product events. No transcript, summary, audio, title, filename, email, or Apple ID is included. |
Cloud AI summaries and OpenRouter
Cloud AI is optional and off by default. The first time you turn on cloud summaries (or the newspaper), Meetly asks for your permission on a screen that lists what is sent and who receives it; nothing leaves your device unless you tap Allow, and you can turn it off at any time in Settings › AI connections. When the recipients or what is sent change, Meetly asks again once before the next cloud request; until you allow it, summaries run on your device where possible or wait for you, and nothing is sent.
What is sent, and to whom
- • Sent: the conversation's transcript text, speaker and participant names, your typed notes and attached note photos (with the text read from them on your device), its title, date and length, names and terms found on your device, any summary instructions or corrections you wrote, and an anonymous install code (see below). Never the audio.
- • Recipient: OpenRouter, Inc., which passes the request to the AI models for your region. Globally: Anthropic Claude Haiku 5.5 hosted on Amazon Bedrock or Google Vertex AI, and OpenAI GPT models (GPT-6 Luna, GPT-5.6 Luna, with GPT-5 Mini as a fallback) hosted on Microsoft Azure. In mainland China, Hong Kong and Macau: Moonshot AI Kimi K2.6 from the providers listed below.
- • Relay: where OpenRouter blocks a network, the app re-sends the identical encrypted request through Meetly's stateless relay (a Supabase Edge Function) to OpenRouter. The relay does not store or read the conversation.
- • Used for: summaries, titles, AI notes and insights, and your newspaper (daily and weekly editions) if you use it.
- • Identifier: global requests that use Claude Haiku or GPT-6 Luna carry an anonymous install code: a one-way hash of a random ID created on your device. It contains no name, email, Apple ID or meeting ID. Amazon Bedrock and Google Vertex require an end-user code so they can detect abuse; Meetly sends no session or meeting ID with these requests.
Meetly calls OpenRouter from the app (or through the relay above). Meetly does not call Anthropic, OpenAI or any other AI provider directly.
Content controls
- • Formal Zero Data Retention is required on every global request: each one asks OpenRouter for ZDR endpoints only and denies provider data collection. Anthropic's and OpenAI's own first-party endpoints are not ZDR, so Meetly does not use them.
- • If a model has no ZDR endpoint available, the request is refused rather than sent elsewhere, and Meetly writes the summary with its ZDR GPT-5.6 Luna route on Azure instead.
- • Providers serving mainland China, Hong Kong and Macau are tried ZDR-first; some may keep requests for a limited time (see below). No route uses your content for training.
- • OpenRouter prompt/response logging is disabled.
- • Provider and model allowlists prevent an unapproved fallback.
What “ZDR” does not mean
ZDR means the approved inference endpoint does not retain prompt or response content after processing. It does not mean no metadata is processed. OpenRouter retains operational metadata and says a small sample of prompts may be categorized anonymously using a ZDR model, without association to an account or user.
Current regional routes
| Device region | Model | Approved provider route | Required privacy policy |
|---|---|---|---|
| Global, including Taiwan and South Korea: reading and sorting the conversation | Anthropic Claude Haiku 5.5 | OpenRouter → Amazon Bedrock, then Google Vertex AI | Formal ZDR required; data collection denied; no other host. |
| Global: writing the summary and the newspaper | OpenAI GPT-6 Luna | OpenRouter → Microsoft Azure | Formal ZDR required; data collection denied; no other host. |
| Global: standard summary, titles, and the fallback when the above cannot run | OpenAI GPT-5.6 Luna (GPT-5 Mini as model fallback) | OpenRouter → Microsoft Azure | Formal ZDR; data collection denied; no provider fallback. |
| Mainland China, Hong Kong, and Macau | Moonshot AI Kimi K2.6 | OpenRouter → first, ZDR providers only: Inceptron, Decart, CoreWeave, Crusoe, DeepInfra, Venice, Parasail, SiliconFlow, Novita, DigitalOcean, Moonshot AI, Phala, Fireworks, Baseten. Only if none of those is available (this second tier is on by default; Meetly can switch it off remotely): Baidu, Chutes, StreamLake, GMICloud, Cloudflare, Atlas Cloud. | First tier: formal ZDR, data collection denied. Second tier: these providers may keep requests for a limited time under their own terms; OpenRouter lists each as not training on prompts. Nothing outside these two lists; otherwise Meetly fails closed. |
Eligibility was checked against OpenRouter's published endpoint and provider-policy data on October 20, 2026. These routes are remotely managed so Meetly can rotate a restricted runtime key, adjust the China provider lists, or change an approved model/provider without waiting for an app release; any change that alters who receives your data is reflected here first. The app also contains a restricted runtime key so summaries can continue if Firebase Remote Config is unavailable. The OpenRouter management credential is never included in the app.
China, Hong Kong, Macau, and VPNs
- • Meetly selects the Greater China route only when the device Region is CN, HK, or MO. It does not infer this from language, IP address, SIM, or Chinese text. Taiwan and South Korea stay on the global route.
- • A VPN may change network reachability or the location OpenRouter/providers infer, but it normally does not change Meetly's selected route unless the device Region changes.
- • The regional route is designed to improve availability. We do not guarantee VPN-free operation because reachability can vary by country, carrier, Wi-Fi provider, and upstream policy.
- • If OpenRouter or every approved endpoint is unavailable, Meetly shows an error and keeps your transcript local. It does not silently switch to direct Kimi or another unapproved provider.
What OpenRouter and providers may still process
To route, bill, secure, and troubleshoot the request, OpenRouter and the selected provider may process timestamps, requested and served model, provider, token counts, cache usage, latency, cost, completion status, data/edge region, request or generation IDs, app attribution, user agent, IP address, and related network or abuse-prevention signals. Meetly does not add participant names, meeting titles, meeting IDs, or account identifiers to optional OpenRouter metadata fields. The only identifier it adds is the anonymous install code described above, and only on global Claude Haiku and GPT-6 Luna requests.
See OpenRouter's current data collection, Zero Data Retention, and privacy documentation. Provider eligibility can change; Meetly's request and preset restrictions are designed to fail closed if an endpoint no longer qualifies.
iCloud Library Sync (optional beta)
If you enable Library Sync, Meetly uploads transcripts, summaries, meeting metadata, and supported preferences to your private CloudKit database so your Meetly library can be restored and synchronized. Recording chunks sync only when the separate audio backup option is enabled. Apple processes and stores that data under your Apple account and Apple's terms. Meetly does not describe ordinary CloudKit storage as end-to-end encrypted.
Turning sync off stops future syncing but may not delete records already stored in iCloud. You can manage iCloud data through Apple's controls. Because this feature is beta, export important meetings and confirm recordings before uninstalling the app.
Connect AI (optional)
Current hosted connection mode
When enabled, Meetly uploads AES-256-GCM encrypted transcript text, summaries, participants, highlights, action items, and meeting metadata to mcp.getmeetly.ai. Recording audio is not included. Once enabled, authorized conversation context can continue syncing automatically. Private iCloud sync alone does not authorize access by an AI assistant.
How access works
The encryption key is generated on your device and kept in the iOS Keychain. Authorized requests decrypt the minimum needed data in request memory. The MCP service does not persist or log meeting plaintext, connection keys, bearer tokens, tool arguments, transcripts, or generated artifacts. Tool results are then handled under your connected agent provider's terms.
Private iCloud connections — staged rollout
A new connection mode is being prepared. It is not enabled by this page, and existing hosted connections are not automatically migrated. Once enabled and verified for your library, transcripts, searchable meeting titles/tags and independent AI notes will be stored in your private iCloud library. The MCP service will retrieve authorized content on demand without keeping another transcript copy in the new path.
Searchable titles and tags use private iCloud metadata; they are not advertised as end-to-end encrypted. The MCP service processes selected plaintext during retrieval, and content returned to an AI assistant is handled under that provider's terms. Content therefore leaves Apple's ecosystem when you authorize an assistant to receive it. Unsupported account-security configurations must fail safely without weakening your protections.
Meetly sign-in, CloudKit authorization and each assistant connection's permissions are separate. An enabled connection covers all current and future supported meetings synced to that library. Saving titles, tags and AI notes requires additional permission and preserves the transcript and native summary. Private library sync does not itself authorize an assistant.
In this mode, Supabase will retain authorization and connection state, encrypted CloudKit credentials, separately authorized encrypted preferences, public guidance and content-free telemetry. Preference encryption will be separated from the legacy transcript key. Meeting titles, tags, transcripts and AI notes will not form a new hosted index or content cache.
Access changes take effect for future retrieval after server acknowledgement; an offline change may still be pending. Revocation cannot erase content an assistant already received. Existing hosted copies require verified migration and a separate retention/deletion process, including backup expiry; this page does not claim those copies have been removed.
Optional account preferences
The Connect Meetly pairing page explains that connecting authorizes meeting access and an encrypted account preference profile, such as how you want briefings written, in one action. Reading preferences requires the preferences:read OAuth permission; updating or clearing requires preferences:write. The agent should save only preferences you ask it to remember. Existing meeting-only connections need one reconnect through the current pairing page; their permissions are not silently expanded. Direct connection keys used outside that OAuth flow do not automatically grant profile access.
The profile belongs to your paired Meetly account identity, recovered through iCloud Keychain, rather than a separate website account. It is encrypted at rest using that identity's existing encryption key. The server decrypts it during an authorized call so the connected agent can use it; this is not zero-knowledge storage.
Your raw ChatGPT memory is not automatically imported. Ask your connected agent to clear the saved profile by calling update_user_preferences with an empty profile object ({}). A cleared profile is separate from your meeting records.
Saving an account preference does not create or verify a scheduled briefing. Scheduling is managed by ChatGPT or the other host you use, subject to its capabilities. Clearing the profile does not cancel tasks in that host.
Processors and retention
Supabase processes encrypted meeting blobs, encrypted account profiles, device records, and OAuth metadata; Vercel forwards requests on the branded MCP domain. Encrypted meeting blobs and device records remain until deletion; account profiles remain until cleared or deleted. You can revoke access in Meetly; deletion requests to founder@edgefirst.app are completed within 30 days, subject to legal and security requirements.
Privacy-safe product analytics
Meetly enables Firebase Analytics and PostHog by default for a small, allowlisted set of product events such as onboarding progress, recording completion, summary success or failure category, feature use, and subscription state. You can turn product analytics off at any time in Settings. Events can include coarse app, device, locale, route, duration bucket, and acquisition-attribution information. They do not include recording audio, transcript or summary text, meeting titles, filenames, participant names, email addresses, Apple IDs, or advertising identifiers.
With product analytics enabled, Firebase Analytics and PostHog also receive language codes identified by on-device transcription models, detection confidence or availability status, and the transcription engine used. This helps us measure language support and reliability. These events contain no recording audio or transcript text.
A three-step survey asks what you like and what you want improved. The first two steps require an answer, with “Still exploring” and “No issues so far” available as neutral choices. On the final step, country, up to three non-English languages, and written feedback of up to 1,000 characters are optional; choose Finish to complete the survey. With product analytics enabled, your selected choice, country, and language codes go to Firebase Analytics and PostHog to prioritize improvements; written feedback goes only to PostHog. With product analytics disabled, completing the survey sends no responses. The country is your answer, not an inferred location. The survey does not automatically include recording audio or transcript text.
Meetly does not collect session replays or screen recordings for app analytics. PostHog receives sanitized crash and processing diagnostics, including processing stages, elapsed time, error codes, app and OS versions, and opaque recording, job, and attempt identifiers. RevenueCat processes purchase and entitlement information; a pseudonymous analytics identifier links subscription events with product analytics. Product analytics can be turned off in Settings.
Your controls
- • Use local recording and transcription without Cloud AI.
- • Turn iCloud Library Sync, Connect AI, or product analytics off.
- • Delete local recordings and transcripts in Meetly.
- • Revoke connected-agent access from Settings.
Recording responsibility
You are responsible for obtaining any consent required to record or process a conversation and for confirming that your use meets applicable laws, workplace rules, and confidentiality obligations.
Questions or data requests?
Contact us about this policy or optional Meetly service data:
founder@edgefirst.app