Privacy Policy

For the Omarchy Calendar installation described on its homepage. Effective 27 September 2026.

Who this covers

This policy applies to a private installation of the open-source program Omarchy Calendar, operated by Jon Spinks for personal use. The application has a single user, who is also its operator and the owner of the Google Account it connects to. It is not offered to other people.

What data is accessed

With the operator's consent, the application uses the Google Calendar API to read and write the events in the operator's own calendars. It requests the calendar scope, which is needed to show events and to create, edit, delete and respond to them from the desktop, plus the operator's email address, to show which account is signed in. It does not access Gmail, Drive, Contacts, or any other Google service, and it does not access any other person's account.

How the data is used

Calendar data is transferred directly between Google's servers and the operator's own computer, so that events can be shown in the desktop's calendar, used for meeting reminders, and changed when the operator asks. The data is used for no other purpose. In particular it is never sold, never shared with third parties, never used for advertising, and never used to train machine-learning models. No human other than the operator reads it.

Where the data is stored

Events stay in Google Calendar and on the operator's computer. A local copy of upcoming and recent events is kept in the operator's user cache, readable only by the operator, so that the calendar can show them instantly. The OAuth tokens that let the application act on the operator's behalf are stored in the system keyring, not in a plain file. Nothing is stored on any server run by the operator or by anyone else.

Sharing

No Google user data is transmitted to anyone. The only parties involved in a transfer are Google and the operator's own computer.

Limited Use

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

Retention and removal

The operator can revoke the application's access at any time at myaccount.google.com/permissions. Revoking access immediately stops all further data transfer. Removing the account from the application deletes its keyring entry and settings, and removing the application deletes its local copy of events, which ends all retention of Google user data.

Changes

If this setup changes in a way that affects the above, this page will be updated and the effective date changed.

Contact

Questions about this policy: jon.spinks@gmail.com