Effective date: 21 July 2026
Developer: Senko Apps Project
Privacy contact: senko.apps@gmail.com

1. In brief

Meeting Alarm does not create accounts, use 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 calendar-read permission, 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, timings, sound, appearance, and whether protection is enabled.

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 when the meeting starts or you dismiss the alarm.

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 has no own servers and uses no analytics, advertising, or tracking SDKs. It does not request internet permission and 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.

If a version of the app offers a one-time Meeting Alarm Pro purchase, Google Play processes the payment. The developer does not receive card details. The app receives from Google Play only information needed to check whether Pro is available to you.

5. Permissions

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.