Omagenda Privacy Policy

Effective: 2026-09-15 · Last updated: 2026-09-17 (v0.3.0)

Fixed Supply is operated by Calvin Symes.

What Omagenda is

Omagenda is a plugin for the Omarchy Linux desktop, written and maintained by one developer, published under the Fixed Supply name. It shows the next calendar event in the desktop’s top bar, a seven-day agenda panel, and a Quick Add box that turns a typed sentence into an event. It is free and open source under the MIT license.

How data is handled

Omagenda runs entirely on your own computer. There is no Omagenda server. The developer receives no calendar data, account data, usage data, or crash reports. There is no telemetry and no analytics.
Calendar events are stored as standard .ics files in a folder on your computer.
When you delete or edit an event, or when a sync conflict keeps the server's version, Omagenda saves a private copy of the previous version under ~/.local/state/omagenda/, in folders readable only by you, so a mistake can be undone. These copies never leave your computer.
Sign-in tokens and passwords are stored in the desktop’s system keyring. If no keyring is available, they are stored in a file readable only by you.
Omagenda connects only to the calendar services you choose to add: Google (accounts.google.com, oauth2.googleapis.com, www.googleapis.com), Apple iCloud’s CalDAV service through the separate pimsync tool, and any calendar subscription addresses you enter.

Google data

From Omagenda 0.3.0, it requests two Google Calendar permissions: https://www.googleapis.com/auth/calendar.events (view and edit events on your calendars) and https://www.googleapis.com/auth/calendar.calendarlist.readonly (see the list of calendars you use). It does not request permission to create, delete or share calendars. Earlier versions requested https://www.googleapis.com/auth/calendar.
It uses that access only to show your own events on your own computer, and to create, change, and delete events when you ask it to.
Google data is never sent anywhere except back to Google, never sold, never used for advertising, and never used to train any AI or machine-learning model.

Omagenda'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.

How to stop and delete

Revoke Omagenda’s access at https://myaccount.google.com/permissions.
Remove the account in Omagenda with omagenda account remove <id>.
Delete the local calendar folder, by default ~/.local/share/calendars/<id>/, and the saved copies under ~/.local/state/omagenda/.

From Omagenda 0.2.1, removing an account deletes its sign-in token from that computer only, so other computers you use Omagenda on stay signed in. To revoke Omagenda's access to your Google account everywhere, use the link above, or remove the account with omagenda account remove <id> --revoke. In Omagenda 0.2.0, removing a Google account also revoked access at Google.

Omagenda 0.1.0 did not delete the token. To clean up one it left behind, run the commands below; omagenda doctor reports any leftover token.

secret-tool clear service omagenda account <id>-refresh-token
rm -f ~/.local/state/omagenda/secrets/<id>-refresh-token

This website

This site is hosted on GitHub Pages, which may keep standard server logs such as IP addresses under GitHub’s own privacy statement. The site sets no cookies and has no analytics.