Legal · Last updated August 21, 2026
Privacy Policy
Longitude° is a local-first calendar client. This policy explains how the app handles information when you use device calendars, connect a provider, or purchase Longitude° Pro.
Summary
- Google Calendar and Microsoft 365 connections are optional.
- Longitude° has no application account, advertising, tracking, or application-operated analytics service.
- Calendar content is sent only to the operating-system calendar store or the provider you select.
- Longitude° does not request Gmail access or the device address book.
Calendars and events
Longitude° reads and, when you explicitly create or edit an event, writes to the calendar store already managed by your device. The app keeps no server copy. A short-lived display cache may keep event and calendar identifiers, titles, colors, and start/end values on the device so the current calendar can appear quickly after launch. It excludes descriptions, locations, guests, attachments, reminders, and meeting or provider URLs.
If you connect Google Calendar or Microsoft 365, Longitude° sends calendar requests directly to that provider. It can create, edit, or delete events only in calendars the provider marks writable. Event fields such as guests, reminders, recurrence, locations, links, availability, attachments, rooms, and supported online meetings are sent directly to the selected provider as part of an explicit save.
Google user data
When you connect a Google account, Longitude° accesses the account identifier, name, email address, and profile image returned by Google Sign-In so it can identify the connected account in the app. It accesses calendar-list metadata such as calendar identifiers, names, colors, visibility, time zones, and access roles so it can list your calendars and determine which ones are writable.
For calendars you enable, Longitude° accesses event identifiers, titles, start and end times, all-day status, time zones, descriptions, locations, recurrence, organizers, guests and response status, reminders, availability and visibility, conference links, attachments, and provider URLs when those fields exist. This information is used only to display your schedule and to perform calendar actions that you explicitly request.
Contacts, rooms, and availability
Longitude° does not request the device address book. If you open the provider contact picker while adding a guest, the app explains the request first. Only after you continue does it request Google's read-only Contacts scope or Microsoft Graph Contacts.Read and show matching names, email addresses, and available profile images. Results are used only to suggest guests. They are not uploaded to a Longitude° server or retained as a separate contact database.
Availability checks send the entered email addresses and time range directly to Google Calendar or Microsoft Graph. Microsoft room search may request the additional Place.Read.All permission when you open that feature.
Gmail-derived reservations
Google Calendar may contain travel or reservation events created from Gmail. Longitude° receives only event fields returned by Google Calendar. It does not request Gmail permission, read your mailbox, or parse email.
Locations and maps
When you choose to open an event location, its free-text location is passed to the map app or external map service you select. Longitude° does not request your device location for this feature.
Local preferences and credentials
Favorite time zones, labels, display order, active time zone, theme and calendar visibility are stored in the app's private on-device storage. Account display metadata may also be stored locally. OAuth credentials are managed by Google Sign-In or Microsoft MSAL in platform-secure storage rather than ordinary app preferences.
Disconnecting a provider removes its credential and calendars from Longitude°. Uninstalling the app removes local preferences and cache data but does not delete events stored by the device or provider.
Security, retention, and deletion
Requests to Google APIs, Microsoft Graph, and other supported providers are transmitted over HTTPS/TLS. OAuth credentials are kept in the operating system's protected Keychain or Keystore through the provider SDK, and local preferences and display cache are kept in the app's private sandbox.
The display-only event cache expires after no more than seven days and is replaced by live provider data after refresh. Connected-account display metadata and credentials remain only while the account is connected. Disconnecting the account removes them from Longitude°; clearing the app's data or uninstalling it removes local preferences and cache. Data stored by Google, Microsoft, the device calendar, or another service you selected remains with that provider and is controlled through that provider's settings.
Disclosure, sale, and Google API Limited Use
Longitude° does not sell Google user data or disclose it to advertisers, analytics providers, data brokers, or other third parties for advertising, marketing, creditworthiness, or profiling. Google user data is transferred only to Google APIs as needed to provide the calendar or contact action you requested, or to a destination you explicitly select—for example, sending an event's location to a map app after you tap the map action. Longitude° does not use Google user data for purposes unrelated to the app-facing calendar features described in this policy.
Longitude°'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. Google Workspace API data is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models.
Longitude° Pro
Longitude° Pro is a one-time, non-consumable in-app purchase. Apple App Store or Google Play processes payment and returns an entitlement result. Longitude° does not receive or store payment-card details. The last verified entitlement may be cached locally; the platform store remains authoritative and Restore Purchases refreshes it.
Diagnostics and third parties
Longitude° does not operate a remote analytics or advertising service. Technical error information produced by the app stays on the device and excludes calendar content. Optional Google Sign-In and Microsoft MSAL SDKs may process authentication, security, usage, and diagnostic information under their own privacy policies.
Your choices
You can deny or revoke calendar permission in system Settings, disconnect Google or Microsoft accounts inside Longitude°, revoke provider authorization from the provider's account settings, and uninstall the app to remove local data. Longitude° has no separate account to delete.
Changes and contact
If the app's data practices change, this policy and the App Store listing will be updated before the new collection begins. For privacy or support questions, email [email protected].