Privacy Policy

This Privacy Policy explains how Meeting Alarm ("Meeting Alarm," "the app," "we," "us," or "our"), a Windows desktop application published by Atomic Design Studios, handles information when you use the app.

The short version: Meeting Alarm reads your calendar so it can alarm you before your meetings. All of your data — your calendar events, your sign-in tokens, and your settings — is stored locally on your own device. We do not operate servers that collect, store, or process your personal data, we do not sell or share your data, and we do not use it for advertising.

Who This Policy Applies To

This policy applies to anyone who installs and uses the Meeting Alarm desktop application on Windows and connects one or more Google or Microsoft (Outlook) calendar accounts.

What Information the App Accesses

Meeting Alarm connects directly from your device to Google and/or Microsoft to read your calendar. The specific information accessed depends on which account(s) you connect.

Google accounts

When you connect a Google account, the app requests these permissions:

• See your calendars and the events on them (calendar.readonly, read-only) — used to read your upcoming events so the app can schedule alarms for them. The app reads event details such as the title, start and end times, recurrence information, and any meeting link attached to the event.
• See your primary Google Account email address (userinfo.email) — used only to identify and label the connected account inside the app.
• See your personal info, such as your name (userinfo.profile) — used only to display the connected account's name inside the app.

Meeting Alarm requests read-only access to your calendar. It cannot create, edit, or delete any of your calendar events.

Microsoft / Outlook accounts

When you connect a Microsoft account, the app requests:

• Read your calendars (Calendars.Read, read-only) — used to read your upcoming events to schedule alarms.
• Sign you in and read your basic profile (User.Read) — used to identify and label the connected account.
• Maintain access to data you have given it access to (offline_access) — used to keep your account connected so the app can refresh your calendar in the background without requiring you to sign in again.

How the App Uses This Information

Your calendar and account information is used solely to provide the app's core function:

• To display your upcoming meetings inside the app.
• To schedule and fire alarms on your device before each meeting begins.
• To show the connected account's name and email so you can tell your accounts apart.
• To open a meeting's join link in your browser when you click "Join" on an alarm.

The app does not use your information for any other purpose. It does not build advertising profiles, and it does not analyze your data for marketing.

Where Your Information Is Stored

All of your data stays on your device. Meeting Alarm does not have its own servers and does not transmit your calendar data, profile data, or sign-in tokens to us or to any third party. Specifically:

• Sign-in tokens (the credentials that let the app read your calendar) are stored in the Windows Credential Manager, the operating system's secure credential store, with an encrypted fallback to the app's local data folder if the Credential Manager is unavailable.
• Calendar events, app settings, and alarm schedules are cached in files inside the app's local application-data folder on your device.

The only network connections the app makes with your information are the direct, encrypted (HTTPS/TLS) requests to Google and Microsoft to sign you in and to fetch your own calendar. That data travels from Google/Microsoft to your device and is not routed through any server we control.

How Your Information Is Shared

We do not sell, rent, trade, or share your personal information with any third party. Because the app has no backend servers, your data is never transmitted to us. The only third parties involved are:

• Google and Microsoft, whose APIs you authorize directly to provide the app with read access to your own calendar. Your use of those services is governed by Google's Privacy Policy and Microsoft's Privacy Statement.
• Microsoft Store, which handles app distribution and subscription billing (see Payments section below).

Google API Services User Data Policy — Limited Use

Meeting Alarm's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide the user-facing features of the app — reading your calendar to display meetings and fire local alarms.
• We do not transfer Google user data to any third party, except as necessary to provide those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with user notice and consent.
• We do not use Google user data for serving advertisements.
• We do not allow humans to read your Google user data, unless: (a) we obtain your affirmative consent for specific data, (b) it is necessary for security purposes such as investigating abuse, (c) it is required to comply with applicable law, or (d) the data is aggregated and anonymized and used for internal operations. In normal operation, your Google data never leaves your device, so it is never accessible to us at all.

Data Retention and Deletion

Because your data lives on your device, you control it directly:

• Disconnect an account: Removing an account in the app's Settings deletes that account's stored sign-in tokens, cached calendar events, alarms, and related settings from your device.
• Uninstall the app: Uninstalling Meeting Alarm removes the app and its locally stored data from your device. Sign-in tokens stored in the Windows Credential Manager can also be cleared manually via Windows Credential Manager.
• Revoke access at the source: You can revoke the app's access to your calendar at any time from your Google Account or your Microsoft Account. After you revoke access, the app can no longer read your calendar.

Data Security

We rely on platform security to protect your information: sign-in tokens are held in the Windows Credential Manager (encrypted by the operating system), and all communication with Google and Microsoft uses encrypted HTTPS/TLS connections. No method of storage or transmission is 100% secure, but because your data remains on your own device and is never sent to our servers, the exposure surface is limited to your device.

Payments and Subscriptions

Meeting Alarm is distributed through the Microsoft Store, and any subscription you purchase is processed by Microsoft. We do not receive, see, or store your payment card details; those are handled entirely by Microsoft under its own terms and privacy statement.

Children's Privacy

Meeting Alarm is intended for general business and productivity use and is not directed to children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children.

International Users

Meeting Alarm stores your data locally on your device. Any data transfer that occurs is the direct connection between your device and Google's or Microsoft's services, which you authorize and which are governed by those providers' policies.

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. Material changes will be reflected here, and your continued use of the app after an update constitutes acceptance of the revised policy.

Contact Us

If you have any questions about this Privacy Policy or how Meeting Alarm handles your information, please contact us at:

Email: atomicdesignstudios2024@gmail.com