YOUR DATA
Privacy policy
This policy covers Omarchy Calendar, operated by Jeruah at jeruah.dev, and its use with the Calendar for Omarchy desktop plugin. Contact for privacy questions: jeruah@unal.edu.co
Data accessed and why
The integration requests Google Calendar read-only permission (https://www.googleapis.com/auth/calendar.readonly) to retrieve the list of calendars available to your account and events from selected calendars. Calendar identifiers can include email addresses. Google API responses may include event descriptions, organizer and attendee details, recurrence information, and conference details in addition to the displayed fields.
The desktop sync extracts event identifiers, calendar names and colors, titles, dates, start and end times, all-day status, locations, meeting links, event links, event types, and your invitation response status. It uses these to show your calendar, agenda, countdowns, and meeting links. This permission does not allow the integration to change or delete your Google Calendar events.
Storage and retention
Calendar requests run from your computer using the Google Workspace CLI (gws). The normalized event file is stored locally at ~/.local/state/omarchy/calendar-events.json. Authorization credentials and token caches are managed by gws in its configured local profile, normally ~/.config/gws-omarchy-calendar.
By default, synchronization runs every five minutes and retrieves a window covering the previous seven days and the next sixty days. These settings can be changed. A successful sync replaces the event file; stopping sync or a failed sync can leave the last copy on disk indefinitely until you delete it. Local diagnostics may contain error messages and synchronization details. Your computer’s backups may retain older copies.
Sharing and use limits
Calendar data and tokens are not uploaded to this website or a server operated by Jeruah. Google processes authorization and Calendar API requests. Opening a meeting or event link sends your browser to the corresponding provider, whose own policies apply.
Google user data is used only to provide the visible calendar features. It is not sold, used for advertising, used to determine creditworthiness, or used to train general-purpose AI models. The integration does not provide the operator with remote access to your calendar data.
Omarchy Calendar follows the Google API Services User Data Policy, including its Limited Use requirements.
Security
Google authorization and API access use HTTPS. The plugin writes its event file using a temporary file with restrictive permissions before replacing the previous copy. The local event file is not encrypted by the plugin; device access controls, disk encryption, and backup security depend on your computer’s configuration. Keep credentials private and your device secure.
Disconnecting and deleting data
- Stop the desktop calendar synchronization timer to prevent new downloads.
- Remove Omarchy Calendar from your Google Account’s third-party connections to revoke access.
- Delete the local event file and the integration’s dedicated
gwsprofile if you no longer need its credentials. If you configured different locations, use those locations. Delete related backups separately if desired.
Revoking Google access does not delete files already saved on your computer. Removing local files does not delete your original Google Calendar events. The website operator cannot delete files stored on your device.
Website visits and support
This static website contains no analytics scripts, advertising, contact forms, cookies set by its own code, or Google sign-in flow. When hosted on Netlify, Netlify processes ordinary request information such as IP address, requested URL, browser information, and request time to deliver and protect the site under its privacy policy. Hosting logs have retention periods controlled by the provider and applicable hosting settings; they do not receive the desktop plugin’s calendar data.
If you email the operator, your email address and message are processed to respond to your request. Do not send authorization tokens or private calendar exports. You may request deletion of support correspondence using the contact above, subject to any required retention.
Changes to this policy
Updates will appear here with a revised date. New uses of Google user data will be disclosed and require consent before they begin.