Privacy Policy
What the app reads
Your calendar
Meeting Alarms requests full calendar access so it can display your upcoming meetings and schedule alarms for them.
- The app reads event titles, start and end times, calendar names, and optionally event notes and location fields (to detect a video-conference join link such as Zoom, Teams, or Google Meet).
- This data is processed on your device only. It is never uploaded, transmitted, cached on a server, or shared with any third party.
- Meeting Alarms does not modify, create, or delete any calendar events.
Nothing else
The app does not access your contacts, location, photos, microphone, camera, health data, or any other system resource beyond the calendar and notification permissions listed here.
What the app stores on your device
Alarm state
When you enable an alarm for a meeting, the app saves a small record — a hashed event identifier and which alarm types you enabled — in a local database on your device (Apple's SwiftData framework, backed by SQLite).
- This database contains no calendar content (no titles, no dates, no notes). It only stores opaque identifiers and boolean alarm flags.
- The database is included in your standard iCloud and iTunes device backup under Apple's default backup policies. You can disable app data backup in iOS Settings → [Your Name] → iCloud → iCloud Backup.
App preferences
Settings you configure (pre-meeting lead time, snooze duration,
enabled/disabled calendars) are stored in UserDefaults on
your device. These are also included in standard device backups.
Notifications and alarms
Meeting Alarms schedules local notifications and alarms only. There is no server involved: alarms are computed on your device and delivered by iOS directly, with no data leaving your device at any point.
The app holds the Time-Sensitive Notifications entitlement so that pre-meeting alerts can break through Focus and Silent mode. This is a local iOS permission — it does not involve any remote service.
What the app does not do
| Practice | Status |
|---|---|
| Collect analytics or usage metrics | ✗ Never |
| Use advertising or tracking SDKs | ✗ Never |
| Use crash-reporting SDKs | ✗ Never |
| Transmit calendar data to a server | ✗ Never |
| Sell or share data with third parties | ✗ Never |
| Require an account or sign-in | ✗ Not required |
| Show ads | ✗ Never |
| Use push notifications (remote) | ✗ Never |
Meeting Alarms is built exclusively on Apple system frameworks (EventKit, AlarmKit, UserNotifications, SwiftData). No third-party code or SDK is included.
Network access
Meeting Alarms makes no outbound network requests of its own.
The only network-adjacent action the app performs is opening a
video-conference join URL in your installed conference app (e.g. Zoom,
Teams) or Safari when you tap a "Join" button — this is a standard iOS
openURL call that hands off to the destination app and is
not controlled or monitored by Meeting Alarms.
Children's privacy
Meeting Alarms does not knowingly collect data from anyone, including children under 13. Because no data is collected at all, no special provisions apply.
Changes to this policy
If the app's data practices ever change, this document will be updated and the "Last updated" date at the top will reflect the revision. Significant changes will also be noted in the App Store release notes.
Contact
Questions or concerns about this privacy policy?
Meeting Alarms is an independent app. It is not affiliated with Apple Inc., Zoom Video Communications, Microsoft, Google, Cisco, or any other company whose products may appear as calendar integrations.