Who We Are
This Privacy Policy applies to Callisto, a menu bar app for macOS that shows and manages your meetings from Google Calendar, and to the Callisto website at callisto.frami.dev. Callisto is developed and maintained by Federico Ramirez ("we", "us"). You can contact us about this policy at support@frami.dev.
Summary
- Callisto runs entirely on your Mac. We do not operate servers that receive, store, or process your Google user data, and we never see it.
- Callisto reads your Google Calendar data only to show your meetings in the menu bar, and changes events only when you ask it to.
- Your Google user data is not sold, not used for advertising, not shared with third parties, and not used to train AI or machine learning models.
- You can delete all of it at any time by removing the account in Callisto and revoking access in your Google Account.
Google User Data Callisto Accesses
When you connect a Google account, Callisto asks Google for the permissions (OAuth scopes) listed below. Google lets you grant or decline each one on the consent screen. Callisto accesses only the data covered by the permissions you grant.
- Basic profile (
https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/userinfo.profile): your Google account ID, email address, and display name. - Calendar list (
https://www.googleapis.com/auth/calendar.calendarlist.readonly): the calendars in your Google Calendar list, with their IDs, names, colors, time zones, and your access role on each calendar. - Calendar events, read (
https://www.googleapis.com/auth/calendar.events.readonly): the events on those calendars from the start of today through about the next 31 days. For each event this includes the title, description, start and end times, time zone, location, status, recurrence rules, organizer, attendees (names, email addresses, and their responses), your own response, reminders, attachment names and links, conference and meeting links (for example Google Meet or Zoom), and the event's Google Calendar link. - Calendar events, write (
https://www.googleapis.com/auth/calendar.events): optional. Used only when you choose an event action in Callisto. If you decline it, Callisto still shows your events and hides the edit actions.
Callisto does not access your Gmail, Google Drive, contacts, or any other Google service. It does not read the contents of attachments.
How Callisto Uses Google User Data
Callisto uses Google user data only to provide the features you see in the app:
- Your profile data identifies and labels each connected account in the Settings window, and lets you connect more than one account.
- Your calendar list lets you choose which calendars to show, and gives each event its calendar's color.
- Your events are shown as a list of upcoming meetings in the menu bar, with the next meeting in the menu bar title. Meeting links let you join a call with one click. Attendee responses show who is coming.
- With the optional write permission, Callisto changes an event only when you choose an action:
- RSVP: sets your response to Accept, Maybe, or Decline.
- Delete or remove: deletes the event, or a single occurrence of a repeating event. For "this and following events", Callisto ends the series before the chosen occurrence by updating its recurrence rule.
Callisto never creates events, and never changes events without an action from you. We do not use Google user data for advertising, for credit or lending decisions, to build user profiles or databases, or for any purpose that is not part of the features above. No person reads your data. Callisto has no servers, so we cannot access it.
AI and Machine Learning
Callisto does not use Google user data, or any data obtained through Google Workspace APIs, to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models. Callisto does not transfer Google user data to any third-party AI tool or model.
Limited Use
Callisto's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
How Google User Data Is Stored
All Google user data stays on your Mac:
- OAuth access and refresh tokens are stored only in the macOS Keychain.
- Account, calendar, and event data are stored in Callisto's local database (SwiftData) in your user account's app container on your Mac.
- Your choices about which accounts and calendars to show are stored in the same local database. Settings such as sync interval and days to show are stored in the app's local preferences (UserDefaults).
Callisto has no backend. Your Google user data is never uploaded to us or to any server other than Google's.
Sharing, Transfer, and Disclosure
Callisto sends requests directly from your Mac to Google's servers to sign you in, refresh your access, read calendars and events, and apply the changes you choose. That is the only place your Google user data goes.
We do not sell, rent, share, transfer, or disclose Google user data to anyone, including advertisers, data brokers, information resellers, or analytics providers. We would disclose data only if the law required it, but because we never receive or hold your Google user data, we have none to disclose.
Data Protection
- All traffic between Callisto and Google uses HTTPS (TLS). Sign-in uses Google's OAuth 2.0 flow with PKCE in your default browser, so Callisto never sees your Google password.
- OAuth tokens are kept in the macOS Keychain, which encrypts them, and are never written to the database, preferences, or logs.
- Local data is protected by macOS user-account isolation and, when enabled, FileVault disk encryption.
- Callisto asks for the narrowest scopes it needs, and makes write access optional.
- Diagnostic messages that Callisto writes to the local macOS system log never contain event details or tokens. They can contain Google account and calendar identifiers (a calendar identifier can be an email address). They stay on your Mac and are not sent to us.
Retention and Deletion
Callisto keeps Google user data on your Mac only while the account is connected. Each sync replaces the cached data with the current data from Google, so events deleted in Google Calendar are also deleted locally.
You can delete your data at any time:
- Remove the account in Callisto: open Settings, find the account, and choose Remove. Callisto immediately deletes that account's OAuth tokens from the Keychain and its profile, calendars, and events from the local database.
- Revoke Callisto's access in Google: go toGoogle Account → Third-party apps & services, select Callisto, and remove access. Removing the account in Callisto does not revoke this permission on its own, so do this too if you stop using Callisto.
- Uninstall: quit Callisto, delete it from Applications, and delete its data folder,
~/Library/Containers/dev.frami.callisto. Then remove any Callisto items from Keychain Access.
Because we hold no copy of your Google user data, there is nothing for us to delete on our side. If you need help deleting your data, emailsupport@frami.dev and we will walk you through it.
App Updates
Callisto checks for updates with the Sparkle framework, which downloads an update feed and update files from GitHub. These requests contain the app version and normal connection data, such as your IP address. They contain no Google user data. GitHub handles them under theGitHub Privacy Statement.
Analytics and Tracking
Callisto has no advertising, analytics, crash reporting, or tracking code.
This Website
callisto.frami.dev is a static website hosted on Cloudflare. It sets no cookies of its own and runs no analytics. Cloudflare processes ordinary connection data, such as IP address, user agent, and requested URL, to serve and protect the site, under theCloudflare Privacy Policy. Downloads are served from GitHub.
Children
Callisto is not directed to children under 13, and we do not knowingly collect data from them.
Changes to This Policy
We will update this page when Callisto changes how it accesses, uses, stores, or shares Google user data, and change the "Last updated" date above. If a change is material, we will publish it here and announce it in the app's release notes before the new use takes effect, and ask for your consent where required.
Contact
For privacy questions or data requests, emailsupport@frami.dev. You can also open an issue on GitHub, but do not post personal data there.