Legal

Privacy Policy

Last updated: 2 October 2026

Alarmingly is a calendar alarm app. This page explains, in full, what data it accesses, what it does with that data, and — just as importantly — everything it does not do. If you only read one paragraph, read this one:

Alarmingly reads your Microsoft 365 or Google Calendar events to schedule and display alarms. Calendar access is read-only: the app does not create or change calendar events. Calendar content, settings, and alarm data stay in the app's local storage and are not uploaded to an Alarmingly-operated server. The app has no analytics, advertising, or crash-reporting SDKs. Calendar requests go directly from your device to Microsoft or Google, and Google Play processes subscription purchases. Those providers process information under their own terms.

What Alarmingly reads from your calendar

Once you sign in to a Microsoft 365 or Google account, Alarmingly reads your calendar events (subject, time, location, attendees, your response status, and the meeting body/join link) for the purpose of deciding which meetings should get an alarm, and what to show on the alarm screen when one fires. This happens directly between the app on your device and Microsoft's or Google's own calendar service. The app does not relay calendar content through an Alarmingly-operated server or send it to us. The provider receives the authenticated calendar requests needed to return the events you asked the app to read.

Read-only calendar access

Alarmingly requests read-only calendar permissions. It does not write dismissal markers, settings, or any other changes to Microsoft or Google calendar events. Dismissing an alarm affects that device only; dismissal state is not synchronized to another device. Settings are stored locally and are not synchronized through your calendar or a cloud application database.

Where your data is stored

Cached calendar event data, alarms, and settings are stored in the app's private storage on your device. The app does not upload them to Alarmingly or a cloud database. Signing out disconnects the provider account and removes its local alarms; cached calendar records may remain in the local sync cache until they are cleared with app storage or the app is uninstalled. Your settings are separate and remain on the device. On Android, Alarmingly excludes its calendar and alarm databases, saved Google account identities, and native alarm state from new phone backups and device-to-device transfers. Your phone's automatic backup may still copy settings, subscription entitlement information, and imported alarm sounds to your Google account if device backup is enabled. This is controlled by your Android backup settings and is separate from live app synchronization. Backups made before these exclusions may still contain older app data until they are replaced or removed.

Signing in

Alarmingly signs you in using Microsoft's own sign-in (MSAL) or Google's own sign-in, depending on which you connect. Your username and password are entered directly into Microsoft's or Google's own sign-in screen — Alarmingly never sees, handles, or stores your password. What Alarmingly holds afterwards is an access token, issued by Microsoft or Google. The provider's platform sign-in SDK manages its token cache on your device; Alarmingly uses access tokens to make the calendar requests described above. Tokens are not sent to Alarmingly or stored in the app's settings or event database.

How Alarmingly protects your data

Calendar requests go directly from your device to Google Calendar or Microsoft Graph over HTTPS, which protects event data and access tokens while they travel between your device and the provider. Alarmingly does not pass those requests through its own server. The app asks for read-only calendar access and uses the returned event data only to display meetings and schedule local alarms.

On Android, the calendar cache, alarm database, settings, and saved account details are kept in the app's private internal storage. Android prevents other ordinary apps from accessing that storage. On macOS, Alarmingly uses its sandboxed application storage. Google Sign-In and Microsoft MSAL manage their sign-in token caches on the device; Alarmingly does not copy OAuth tokens into its calendar or alarm databases or settings file.

Alarmingly does not add separate encryption to its local SQLite calendar and alarm databases. Their protection depends on your device's operating system and security settings. Someone with privileged access to your device or a copy of its backup may be able to read cached calendar details. Existing Android backups made before the exclusions above may still contain the databases.

Other service providers

Microsoft and Google receive the authentication and calendar API requests required for the account you connect. If you buy Alarmingly Pro, Google Play processes the purchase and subscription. Alarmingly does not receive or store your payment card details. The app stores subscription entitlement information locally on your device.

What Alarmingly does not do

• No analytics, advertising, or crash-reporting SDKs. Alarmingly does not send app usage or crash reports to its own servers.
• No Alarmingly-operated backend for calendar data, preferences, or dismissal state.
• No selling or renting of calendar data or app preferences.
• No access to your calendar data beyond what's described above — meeting content is never read for any purpose other than deciding on and displaying an alarm.

This website

This static website has no analytics, advertising, tracking scripts, or tracking cookies. Its pages and fonts are served from this website rather than a third-party font service. As with any website, your browser sends ordinary connection details (such as an IP address and requested page) to the website host to load the page; those details are handled under the host's own operating practices. Visiting this site does not send us calendar or app data.

Permissions Alarmingly asks for, and why

These are the only reasons Alarmingly requests each permission:

• Calendar access — read-only access to retrieve events and schedule alarms.
• Notifications — to show the alarm, and a heads-up banner in banner mode.
• Exact alarms / "alarms & reminders" — so an alarm fires at the precise time you configured, even if the app isn't running.
• Display over other apps / full-screen intent — to show the full-screen ringing alarm over your lock screen, the way a real alarm clock does.
• Vibration — to vibrate alongside (or instead of) the alarm sound, if you've enabled it.

Alarmingly does not request access to contacts, photos, location, messages, or any other data unrelated to the above.

Your choices and how to remove your data

• Remove an account in Settings → Accounts to disconnect its provider credentials and clear that account's local alarms. To remove any retained calendar cache and settings, clear the app's storage or uninstall the app.
• Uninstall the app to remove its local settings, alarm data, and calendar cache from the device. An Android backup may later restore eligible settings and imported sounds; an older backup may also retain previous app data.
• Revoking Alarmingly's access from your Microsoft or Google account settings (outside the app) stops it from reading your calendar at all.

Children's privacy

Alarmingly is not directed at children and is not intended for use by anyone under the age required by their calendar provider's own terms. Alarmingly does not operate an account system or collect data on its own servers.

Changes to this policy

If this policy changes, the "Last updated" date at the top of this page will change with it. Please check back here if you want to know about updates.

Contact

Questions about this policy or how Alarmingly handles data can be sent to privacy@alarmingly.app.