Calendar data stays on your workstation.

01 / Provider access

The provider grants are narrow and read-only.

Google authorization requests openid, email, https://www.googleapis.com/auth/calendar.events.readonly, and https://www.googleapis.com/auth/calendar.calendarlist.readonly. It also requests offline access so the local service can refresh in the background.

Personal Outlook.com authorization uses Microsoft's /consumers authority and requests openid, profile, offline_access, User.Read, and Calendars.Read.

Flight Deck uses Google Calendar data only to display calendars and events, select the current or nearest event, and open a meeting or source link when you ask it to. The developer cannot access your calendar data or tokens because the app sends neither to a Flight Deck server.

Flight Deck does not sell, share, or transfer Google user data to the developer, advertisers, analytics services, AI systems, or other third parties. Your workstation communicates directly with Google and Microsoft only to authorize the account, read the calendars you selected, and refresh the local cache.

Flight Deck requests no calendar write scope and provides no route for event creation, editing, deletion, invitations, or scheduling.

Flight Deck Calendar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

02 / Local storage

Secrets and calendar data have separate local homes.

OAuth tokens

Flight Deck stores access and refresh tokens in the desktop Secret Service keyring under the omarchy-calendar application attribute.

Google app credential

Flight Deck stores an imported Google Desktop app credential as a separate Secret Service item instead of writing it to the repository or a dotfile.

Calendar cache

Flight Deck stores account identifiers and labels, calendar identifiers, names, and colors, event titles, times, locations, descriptions, organizers, status, and meeting and source links, plus provider refresh health. The local SQLite cache is ~/.local/state/omarchy-calendar/calendar.db with private permissions.

Provider overrides

Local developer builds may store public client IDs at ~/.config/omarchy-calendar/providers.json with private permissions.

03 / Refresh and disconnect

A failed refresh does not erase the last good view.

One singleton Omarchy service refreshes providers every 5, 15, or 30 minutes according to the local setting. When the network is unavailable, Flight Deck keeps the last successful local cache visible and marked stale.

Disconnecting Google or Outlook deletes that provider's OAuth tokens from Secret Service and removes its cached accounts and events immediately. Disconnecting does not change the provider calendar.

04 / Deletion

Reset local data before uninstalling.

The in-app flow uses two activations: choose Reset local data, then choose Confirm reset. The terminal command calendarctl reset-local-data runs immediately when invoked.

Both paths delete all Flight Deck provider tokens, imported Google app credentials, cached events, provider health records, and local provider client-ID overrides.

Both paths preserve appearance settings and do not change Google or Microsoft calendar data. Uninstalling the plugin alone does not delete data, so run the terminal command first when complete local removal is wanted.

05 / This website

The verification site is static.

The site code contains no JavaScript, analytics, cookies, tracking, forms, advertising, backend, or database. It loads its stylesheet and product image from relative paths in the same public site.

The Terms of Service describe the software license, provider boundaries, and preview status.