Privacy Policy

Effective: July 24, 2026

The short version: We run no servers and collect no data — from the app or from this website. Your meetings are processed on your device or by Apple's Private Cloud Compute (which, per Apple, never stores them and cannot show them to anyone — including Apple and us), and stored on your device and in your private iCloud database, which we cannot access. This site sets no cookies and runs no analytics.

1. Who is responsible

ParseMeet is developed and operated by Omar Selim, an independent developer (Alwin-Brandt-Stieg 8A, 25474 Hasloh, Germany). For anything privacy-related, write to privacy@parsemeet.com. Under the GDPR, Omar Selim is the controller for this website. The app itself processes your data on your device and, for some AI requests, via Apple's Private Cloud Compute under your own Apple account — never on servers we operate.

2. The app: your meeting data

  • Audio recordings of meetings you choose to record.
  • Outcome docs — the decisions, action items, and summaries the app generates.
  • Calendar-derived metadata (meeting titles, times, attendee names and email addresses), if you grant calendar access. Calendar data is read on-device and never reaches us.
  • Templates and settings.

All of this is stored in the app's private container on your Mac, iPhone, or iPad. Outcome docs, templates, and meeting metadata are synced between your devices through your private iCloud database (see §3); audio recordings stay on the device that recorded them. ParseMeet has no servers; nothing is ever transmitted to us — there is nothing on our side to transmit to. Transcript text is not stored at all — if you re-parse a meeting, the app re-transcribes the audio on-device.

3. The app: Apple system services

A few operating-system features exchange data with Apple under your own Apple account and Apple's privacy policy. This data is user-private — we never see any of it:

  • App Store / StoreKit — processes your purchase and trial state.
  • iCloud / CloudKit — stores your iCloud identity, a small trial-anchor value, and your synced meetings, in your private iCloud database. Private databases are not visible to the developer; the data is encrypted in transit and at rest, and end-to-end encrypted if you enable Advanced Data Protection.
  • Apple speech models — a one-time on-device model download from Apple.
  • Apple Intelligence / Foundation Models — runs on your device; meetings may be processed by Apple's Private Cloud Compute, which per Apple never stores the data, uses it only to fulfill the request, and makes it accessible to no one — not Apple, not us. Apple retains only content-free request metadata (approximate size, feature, duration), unlinked to your identity.

4. App Store privacy label

ParseMeet launches with the App Store privacy label "Data Not Collected." The app contains no analytics, no advertising, and no third-party SDKs of any kind, so there is nothing on our side that could collect your data.

5. This website

parsemeet.com is a static site. It sets no cookies, runs no analytics or tracking, and has no forms. It is served by Cloudflare Pages; Cloudflare processes technical connection data (such as your IP address) in short-lived server logs to deliver and secure the site. The legal basis is our legitimate interest in operating a secure website (Art. 6(1)(f) GDPR). See Cloudflare's privacy policy.

6. Email

If you email support@parsemeet.com or privacy@parsemeet.com, we process your address and message to answer you (Art. 6(1)(b) and (f) GDPR) and delete the correspondence once it is no longer needed.

7. Your rights

Under the GDPR you have the rights of access, rectification, erasure, restriction of processing, data portability, and objection, plus the right to complain to a supervisory authority. In practice: your meeting data lives on your devices and in your private iCloud database, and we hold no copy — deleting a meeting in the app removes it from both, which is the real right to erasure. For anything else, email privacy@parsemeet.com.

8. Changes

If this policy changes, the new version appears on this page with an updated effective date. Since we collect nothing, changes are expected to be rare and editorial.