Privacy Policy

At CalAlarm Sync, we take your privacy seriously. This policy outlines our commitment to your data security.

1. Data Collection

No Remote Data Collection: We do not collect or transmit your personal data to any external servers. Calendar details from Google and Outlook are fetched strictly to be stored and processed locally within the app to schedule your alarms.

2. Local Processing & Open Source Code

All calendar synchronization and alarm scheduling are performed locally on your device. The app reads your calendar events (such as Google and Outlook calendars) solely to calculate and manage alarm times. None of this data is ever sent to or stored on any external servers.

For complete transparency, the application source code is fully open-sourced under the MIT license, allowing anyone to inspect the security and privacy mechanisms of the implementation.

3. Google API Scopes and User Data

Our app connects to Google APIs to fetch your primary calendar events. Specifically, the app requests the following scopes/permissions:

https://www.googleapis.com/auth/calendar.readonly (Calendar Events): Used to retrieve event titles, start times, and recurrence rules to automatically schedule local alarms on your device.
https://www.googleapis.com/auth/userinfo.email (Gmail Account Details): Used to obtain your Gmail address to identify and manage your connected account in the app interface.

Google API Services User Data Policy Compliance: CalAlarm Sync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. Microsoft Graph API Scopes and User Data

Our app connects to Microsoft Graph APIs to fetch your primary Outlook calendar events. Specifically, the app requests the following permissions:

Calendars.Read: Used to retrieve event titles, start times, and recurrence rules to automatically schedule local alarms on your device.
openid, profile, email: Used to authenticate and obtain your Outlook email address to identify and manage your connected account in the app interface.
offline_access: Used to obtain refresh tokens, allowing the app to keep your alarms synchronized silently in the background.

Microsoft APIs Compliance: CalAlarm Sync's use of information received from Microsoft APIs will adhere to the Microsoft APIs Terms of Use and Microsoft Developer Code of Conduct. All data fetched is processed and stored locally on your device.

5. Third-Party Services

The app does not use any third-party analytics or tracking SDKs. We do not share any information with advertisers or data brokers.

6. Permissions

The app requires the READ_CALENDAR permission solely to provide its core functionality. You can revoke this permission at any time through your device settings.

7. Data Protection Mechanisms

We employ strict data protection mechanisms to secure your sensitive information. All Google and Microsoft Outlook user data, including calendar events, is stored securely within the app's local sandbox. This data is protected by your device's native operating system security and encryption protocols. We do not transmit sensitive data over the internet or store it on any external servers.

8. Data Retention and Deletion

Google and Microsoft Outlook user data is retained locally on your device only for as long as it is necessary to provide the alarm scheduling functionality. Because all data is stored locally, you have full control over its retention and deletion. Upon account deletion, removal of your account from the app, or uninstallation of the CalAlarm Sync application, all associated account data and calendar details are completely removed from your device. You can also manually delete your Google or Microsoft Outlook user data at any time by clearing the app's local storage/cache in your device settings.