Privacy, plainly.
Effective October 20, 2026 · Minutes for Mac and iPhone, by OmniHarmonic
Minutes records, transcribes and summarizes meetings on your own devices. There is no Minutes server and no Minutes account: the developer never receives your recordings, transcripts, notes, calendar data or credentials. This policy explains what the app stores, what it sends and where, how it protects it, and how to remove it.
Recording others
Recording a conversation can require everyone's consent, depending on where you and they are. Tell participants when you record. Minutes shows this reminder before your first recording.
What stays on your device
Recordings, transcripts, notes, summaries, moments, speaker names, folders and remembered voice profiles are stored in the app's private storage on your Mac or iPhone, protected by the operating system's file protection and your device's disk encryption. Speech recognition runs on device; when a device cannot transcribe on device, Minutes shows an error instead of sending audio to a cloud service. Optional summaries use Apple's on-device Foundation Models. Minutes contains no advertising or analytics SDK. Installing speaker models downloads them from their publisher; no meeting data is sent in that request.
Google user data
What Minutes accesses
Connecting Google Calendar is optional. If you connect it, Minutes asks for two read-only permissions and nothing else (no Gmail, Contacts, Drive or calendar editing):
| Permission | Data read | Used for |
|---|---|---|
calendar.calendarlist.readonly | The names and identifiers of calendars in your list | Letting you choose which calendars Minutes shows |
calendar.events.readonly | For events in the next few weeks on the calendars you chose: title, start and end time, conference link, organizer, and each attendee's name, email address and RSVP status | Showing upcoming meetings, reminding you before a meeting starts, starting a recording for that meeting, naming the recording after the event, linking a recording to its event, and offering invitees as names to pick when you label who spoke |
How Minutes uses it
- Event details are shown only in the app, on your device, and saved with a recording only when you record that meeting or link a recording to the event.
- Invitee names and email addresses are suggestions. Minutes never treats a calendar invitation as proof that someone attended or spoke, and never records or remembers anyone's voice because they were invited. Choosing a speaker and remembering a voice are separate actions you take.
- When you ask for a summary, the meeting's title and the names you assigned to speakers may be given to Apple's on-device model, on your device, to write that summary. They are not sent to Apple's servers or to the developer.
- Google user data is never used for advertising, never sold, never used to build profiles unrelated to your meetings, and never used to develop, improve or train generalized artificial intelligence or machine learning models.
With whom Google user data is shared, transferred or disclosed
The developer has no server and does not receive, store or have access to your Google user data. It is not shared with any third party, with these exceptions, each of which happens only at your request:
- Google receives the requests needed to sign you in and read the calendars you chose.
- Your own iCloud account (Apple), if you turn on Settings → Sync: meetings, including any event title, times and invitee names and email addresses saved with them, are stored in your private iCloud database so they appear on your other devices. Only your Apple Account can read that database; the developer cannot.
- Destinations you choose: if you save a meeting as a Markdown file, share it, or save it to a Parachute vault you sign in to, the copy includes the meeting's title, times and attendee names. That copy is then governed by the place you sent it.
Minutes does not transfer Google user data for any other purpose. It will not disclose it except as required by law, and because the developer holds none, there is nothing the developer could disclose. Minutes's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How Google user data is protected
- Sign-in uses Google's own page in your browser with OAuth 2.0, PKCE and a one-time state check. Minutes never sees your Google password.
- Access and refresh tokens are stored only in the Keychain on your device, encrypted by the operating system, and are never written to logs, files, preferences or exports.
- All requests to Google use HTTPS (TLS). Minutes requests read-only access, so it cannot change or delete anything in your Google account.
- Calendar data saved with meetings is protected by your device's file protection and disk encryption; iCloud sync data is encrypted in transit and at rest by Apple and is readable only by your Apple Account.
- Remembered voice profiles, which are sensitive, never leave the device that created them: they are excluded from iCloud sync and from every export.
Removing Google access and data
Use Disconnect in Settings → Calendar to remove the tokens from your device and revoke them with Google, or remove Minutes in your Google Account connections. Disconnecting stops all access; event details already saved with your meetings remain until you delete those meetings, which also removes them from iCloud when sync is on.
Voice profiles
Remembering a voice is optional and separate from naming a speaker. Only remember someone's voice with their consent. Voice profiles stay on the device that created them, are never synced or exported, and can be forgotten at any time from People or Settings.
iCloud sync
Sync is off until you turn it on. It stores meetings (transcripts, summaries, notes, moments, speaker names), folders and people in your private iCloud database, using your own iCloud storage, so your Mac and iPhone show the same library. Recordings are included only if you turn on "Include recordings". Voice profiles and speaker voice data are never synced. Turning sync off stops syncing and keeps everything on the device.
Exports and your vault
If you sign in to a Parachute vault, Minutes saves the meetings you export (title, times, attendee names, summary, transcript and your notes) to the vault and folder you choose; automatic saving is optional. The sign-in token is kept in the Keychain. Files you save or share and notes in your vault have their own retention and must be deleted where they are.
Retention and deletion
Meetings stay on your device until you delete them. Deleted meetings move to Recently Deleted, where you can restore them or delete them permanently. You can delete a meeting's audio and keep its transcript in Settings → Storage. Removing the app removes its local data; device backups and exports are removed separately. To remove the iCloud copy, delete meetings while sync is on, or use Remove iCloud Copy in Settings → Sync, which deletes all Minutes data from your iCloud and keeps it on the device.
Children
Minutes is not directed to children under 13 and does not knowingly collect their information.
Website and testing
This website has no analytics, advertising cookies or sign-in. Its hosting provider processes ordinary network metadata to deliver pages. If you test through TestFlight, Apple may collect diagnostics and feedback under its own policy. If you email us, we receive only what you send; please do not include recordings, transcripts, tokens or voice data.
Changes
If this policy changes, the new version is posted here with a new effective date before the change applies.
Contact
Privacy questions: [email protected].