Jaegerlarm Privacy Policy

Effective date: August 1, 2026

Jaegerlarm keeps app-owned data on your device. The app does not send your Calendar or alarm data to a backend service.

Data Stored On Device

Jaegerlarm stores the local information needed to create and manage alarms you choose, including:

• AlarmKit UUIDs for alarms created by Jaegerlarm.
• Calendar identifiers and external identifiers needed to relink selected event occurrences.
• Event title, location, start and end dates, all-day state, time zone, and source calendar snapshot needed to show useful rows when Calendar access is unavailable.
• Trigger, snooze, sound, status, and synchronization metadata.
• Preferences such as default lead time, default snooze, default sound, and selected calendars.
• Custom alarm sounds that you import or record inside the app.

Data Not Collected

Jaegerlarm does not store event notes, attendees, attachments, analytics identifiers, advertising identifiers, login data, or network data.

Network, Analytics, And Tracking

Jaegerlarm does not send app data to a backend, does not use CloudKit, and does not use analytics, advertising, tracking, or third-party SDKs.

Calendar Events

Jaegerlarm reads Calendar events only so you can choose which events should have separate AlarmKit alarms. It does not modify Calendar events and does not add EKAlarm objects to Calendar events.

Apple Privacy Manifest

The app privacy manifest declares no tracking and no collected data. It declares UserDefaults access for app functionality preferences.

Support

For help with Jaegerlarm, visit the support page.