1. In brief
Meeting Alarm does not create accounts, operate its own servers, show ads, or send your calendar data to the developer. Calendar data is processed on your device to show your schedule and trigger alarms.
2. Data the app accesses and why
After you grant permission to read your calendar, the app accesses your meeting title and time, calendar ID and name, attendance status, and technical event details. It uses this information to show meetings, apply your selected filters, and trigger alarms at the chosen time.
For a specific meeting, the app may read its location and description only to find a Google Meet, Zoom, or Teams link and show a Join button.
3. Local storage and deletion
The app stores your settings on your device: selected calendars and meeting types, alarm timings, sound, appearance, and whether Meeting Alarm is turned on.
To repeat an active alarm and avoid ringing twice for the same meeting, it temporarily stores that meeting’s ID, time, and title on the device. These technical records are removed after the relevant event has ended or you dismiss the alarm.
To help diagnose technical issues, the release version keeps a technical app log on your device for approximately 24 hours. It records technical events and configuration status, but not calendar titles, descriptions, locations, calendar names, or account names. Log entries are removed automatically after that period.
At your explicit request, you can export a diagnostic report from the app using Android’s share sheet. The report is not sent automatically. Before export, you can choose to include calendar details. If you do, the temporary report may include calendar and account names, event titles, times and identifiers, attendance status, locations and descriptions, including video-call links. It is shared only with the recipient or service you select. The temporary report is kept in the app cache and is eligible for removal on a later app start after it is more than one hour old.
The app disables Android backup for its data. Uninstalling the app removes its local data from the device.
4. Data sharing and third parties
The current version does not operate its own servers and uses no analytics, advertising, or tracking SDKs. It does not send calendar data to the developer. Calendar synchronisation is performed by the calendar service you use on your device, not by Meeting Alarm. Calendar data can leave the device only when you choose to include calendar details in a diagnostic export and select a recipient or service in Android’s share sheet.
The app includes Google Play Billing for the optional one-time Meeting Alarm Pro purchase. Google Play Billing may use network access to communicate with Google Play to show prices, process purchases, and verify your Pro entitlement. The developer does not receive card details or calendar data through this process. The app receives from Google Play only information needed to check whether Pro is available to you.
5. Permissions
- Calendar — to read meetings and trigger alarms.
- Notifications and full-screen alarms — to show the alarm.
- Exact alarms, background operation, and battery-optimisation exemption — to trigger an alarm at the chosen time.
- Display over other apps — so the alarm screen is visible during an active alarm.
- Vibration — for alarm vibration.
- Internet — used by Google Play Billing to show prices, process a Pro purchase, and verify Pro access.
6. Children
The app is not specifically directed to children and does not create user profiles.
7. Changes
If this policy changes, we will update its text and effective date.
This policy will also be available through a public link in the Google Play listing.