Small Swope

Calix privacy policy

Effective October 21, 2026

Calix is a desktop calendar published by Ian Swope. This policy describes what happens when you connect a Google account to Calix. It covers the Calix application. It does not cover the notes published on this website.

Calix’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Who to contact

Ian Swope, ian@smallswope.com. That is the support address shown on the Google sign-in screen.

What Calix reads from Google

If you connect Google Calendar, you grant Calix two permissions:

  • Your calendar list. The names of the calendars on that Google account, and which ones you can see. Calix does not change the list itself.
  • Your events. For the calendars you leave visible: title, start and end, time zone, location, description, guests and their replies, recurrence, and reminders. Calix can create, change, and delete an event when you do that in the app, and it can send the reply you choose to an invitation.

Calix does not ask for your Gmail, Drive, contacts, or any other Google product.

How that information is used

Calix uses Google Calendar data to show your calendar and to carry out the edits you make. A change you save is sent back to your Google account so the calendar stays in step. An invitation or an RSVP is sent through Google because you asked for it.

Calix does not use Google user data for advertising, does not sell it, does not share it with a data broker, and does not use it to train a general-purpose model. Nobody reads your calendar in order to run Calix. If you write for help and choose to include an event, that message is the exception, and it is used only to answer you.

Where it is stored

On the computer where Calix is installed, and not on a server run for Calix. There is no Calix account.

  • A copy of the events Calix has synced sits in a database file on that computer, so the calendar opens when you are offline and so your edits have somewhere to land before they are sent back.
  • The sign-in Google gives Calix is a refresh token. It is stored in the system keyring (the same place the operating system keeps passwords), not in a file Calix uploads anywhere.

Disconnecting the account in Calix deletes that token from the keyring and removes the account’s calendars and events from the local database. You can also revoke Calix from your Google Account at myaccount.google.com/permissions. Revoking it stops Calix from signing in again. A copy already on the computer remains until you disconnect the account in the app or delete Calix’s data file.

What leaves the computer

Sync is a conversation with Google, using the sign-in you gave Calix. That is the transfer of your calendar data: from Google to this computer, and from this computer back to Google when you change an event.

Opening a link in an event opens your web browser to that address. Calix does not send the rest of the event with it.

While you type in a location field, Calix can ask a public address search (Photon, at photon.komoot.io, which uses OpenStreetMap) for suggestions. The request is the text you have typed, and only once it is at least three characters. It is not your calendar, your guest list, or your sign-in. You can turn that search off and keep suggestions from places you have already used. In Calix’s config file, set [places] enabled = false.

How long it is kept

The local copy stays until you delete the event, disconnect the Google account, or delete Calix’s data on that computer. The sign-in stays in the keyring until you disconnect the account, revoke it at Google, or Google expires it. Calix does not keep a separate copy anywhere else.

Children

Calix is not directed at children under 13, and it does not knowingly collect personal information from them.

Changes

When this policy changes, the date at the top of this page changes with it. The page at this address is the one linked from the Google sign-in screen.