No one can read your meetings. Including us.
ParseMeet's privacy isn't a policy you have to trust — it's an architecture you can check. We run no servers. The AI runs on your device, or on Apple silicon that verifiably can't remember you. Storage is yours. Here's the map.
The data map
Where each thing lives.
Never leaves your device
Meeting audio is recorded and transcribed on your device — always. It's kept in the app's local library so you can re-parse a meeting later, and it is never uploaded anywhere, to anyone, for any reason. Delete a meeting and its audio goes with it.
Your library, your devices
Outcome docs live on your device, protected by your device's encryption like the rest of your files. ParseMeet doesn't keep a transcript archive — re-parsing re-transcribes from the audio.
Apple's private stack, and only there
Transcription always runs on your device, on Apple's speech framework. Structuring runs on Apple Foundation Models — on your device, or on the bigger Apple model on Private Cloud Compute, picked automatically. Either way it's private: PCC never stores your data and can't show it to anyone. No vendor, no third-party AI provider, ever.
Your private iCloud database
Meetings sync between your Mac and iPhone through your own iCloud — encrypted in transit and at rest, in a private database that's invisible to us by design. Turn on Advanced Data Protection and it's end-to-end encrypted: not even Apple can read it.
The cloud we said yes to
Why Private Cloud Compute is different.
We deleted our own backend before ever shipping, and we never contracted an AI vendor. The one piece of infrastructure your meetings can ever touch is Apple's Private Cloud Compute — and it earns that exception. Per Apple: data sent to PCC "isn't accessible to anyone other than the user — not even to Apple." It's used only to answer your request, never stored, and processed on Apple silicon servers running a hardened OS with no privileged access — Apple's own staff can't reach it, even during an outage.
You don't have to take Apple's word for it, and you certainly don't have to take ours. Apple publishes every production PCC build for independent security research, pays bounties for anything that undermines the privacy claims, and your device cryptographically refuses to talk to a PCC server whose software hasn't been publicly logged for inspection. That's what we mean by architecture instead of policy: the promise is enforced by silicon, not by terms of service.
Full honesty, because it builds better trust than absolutes: Apple sees content-free metadata about a PCC request — its approximate size, which feature made it, how long it took. Never the content, never linked to your identity. And PCC needs an internet connection; offline, everything simply runs on-device.
Sources: Apple's Private Cloud Compute security overview · Apple Intelligence & Privacy · iCloud data security · CloudKit private databases
Commitments
What we don't do.
These aren't settings you have to find. They're properties of how the app is built.
- No account, no sign-in. We can't tie meetings to an identity we never collected.
- No ParseMeet cloud. We run no servers, so your meetings can't be on them. The only infrastructure that ever processes them is Apple's — stateless, attested, unreadable to anyone but you; the only places they're stored are your devices and your private iCloud.
- No telemetry, period. No analytics, no third-party SDKs — the app contains zero third-party code.
- "Data Not Collected." That's the App Store privacy label ParseMeet launches with — there's nothing on our side to collect with.
- No training on your data. We have no models to train, and Apple states it doesn't train its foundation models on users' private data.
- No dark-pattern retention. Delete a meeting and it's gone — from your device, and from your iCloud.
Recording responsibly
Consent still matters.
Private processing protects the people in your meetings from third parties — it doesn't replace their consent. Recording-consent laws vary by region, and we recommend announcing the recording at the start of every call. When in doubt, ask the room.
Questions about any of this? Read the FAQ or see the formal privacy policy.
Private by architecture.
The most sensitive meeting you have is the one that needs ParseMeet most. In beta now — email me for access.
Email me for beta access