1. Overview
Helm is a native macOS application that combines calendars from multiple Google accounts into focused Today and Monday–Friday Week views. Helm does not operate a hosted backend, advertising network, analytics service, or AI integration.
Helm connects directly from your Mac to Google, uses your calendar data only to provide features you request, and keeps its working data locally on your device.
2. Information Helm accesses
Google account information
When you connect a Google account, Helm receives the account's stable Google identifier, email address, and profile name so it can identify and label the connection.
Calendar information
Helm accesses the calendars available to the connected account and their metadata, including names, colors, access roles, visibility, and synchronization state.
Event information
Helm accesses event information needed to display and manage your schedule. Depending on the event, this can include titles, dates and times, recurrence, descriptions, locations, attendees and their responses, organizers, reminders, conferencing links, attachments, availability, visibility, update timestamps, and identifiers.
Local preferences and diagnostics
Helm stores settings such as enabled calendars, reminder timing, sound preferences, automatic refresh, and launch-at-login status. Helm also writes local diagnostic logs for authentication, synchronization, reminders, and app lifecycle events. Tokens, authorization codes, PKCE verifiers, full meeting URLs, and event descriptions are not logged; account and event identifiers are privacy-masked.
3. How information is used
Helm uses the information above only to provide and maintain user-facing calendar features, including:
- identifying connected Google accounts;
- listing calendars and letting you choose which ones are enabled;
- displaying events across accounts in unified Today and Week views;
- creating, updating, moving, and deleting events when you direct the app to do so;
- opening supported meeting links through the system default handler;
- scheduling local macOS notifications and in-app meeting reminders;
- detecting conflicts and synchronizing changes with Google Calendar; and
- diagnosing local failures without logging sensitive event content or OAuth secrets.
Helm does not use Google user data for advertising, profiling, credit decisions, data brokerage, or training generalized artificial intelligence models.
4. Storage and security
Helm stores normalized calendar and event data in a local SQLite database inside the app's macOS container. This local cache allows the interface to remain responsive and show recent information when a live refresh is unavailable.
Distributed release builds store OAuth credentials in the macOS Keychain. Helm uses Google's installed application authorization flow with PKCE and a temporary callback listener on your own computer. Helm communicates with Google APIs over encrypted HTTPS connections.
No method of local storage or electronic communication is completely secure. You are responsible for maintaining the security of your Mac, macOS account, Google account, and device backups.
6. Retention, removal, and deletion
Helm retains its local calendar cache and settings for as long as the app and account connection remain on your Mac. Disabling a calendar removes that calendar's local event cache and pending reminders. Removing a connected account from Helm deletes its locally stored credentials, calendar and event cache, synchronization state, and pending reminders from that Mac.
You may also revoke Helm's access from the third-party connections page in your Google Account. Uninstalling the application may not automatically remove every file in its macOS application container; you can contact support if you need help locating local application data.
7. Google API data
Helm requests the standard OpenID Connect identity scopes and the Google Calendar event and calendar-list scopes needed to identify connections, discover calendars, and let you view and manage events.
Helm handles information received from Google APIs according to the Google API Services User Data Policy, including its Limited Use requirements.
8. Children
Helm is not directed to children under 13, and the developer does not knowingly collect personal information from children through a Helm-operated service.
9. Changes to this policy
This policy may be updated when Helm's features, data practices, or legal obligations change. The effective date at the top of this page will be updated when a material revision is published.
10. Contact
For privacy questions or requests, visit the Helm support page. Please do not include OAuth credentials, private calendar content, or other sensitive information in a public issue.