OmaCal is a free, open-source desktop calendar application for Linux (primarily Omarchy Linux), developed by Extreme Labs (“we”, “us”). OmaCal is a client for Google Calendar: it runs entirely on your computer, connects directly to Google’s APIs on your behalf, and stores its data locally on your device.
This policy describes what data OmaCal accesses, how that data is used, where it is stored, and the choices you have. It covers the OmaCal desktop application and the OmaCal pages on this website (extremelabs.io/omacal).
The short version: your calendar data never reaches Extreme Labs. OmaCal has no server component, no account system of its own, no analytics, and no telemetry. Your calendar data moves only between the application on your device and Google, over encrypted connections; the two narrow exceptions that carry no calendar data — the update check and the optional weather display — are described in section 4.
1. Data OmaCal accesses from your Google account
When you connect a Google account, you authorize OmaCal through Google’s standard OAuth 2.0 consent flow. OmaCal requests the Google Calendar scope (https://www.googleapis.com/auth/calendar), which grants read and write access to your calendars. Using that authorization, OmaCal accesses:
- Your calendar list: the names, colours and access roles of the calendars on your account, so you can choose which ones to display and fetch.
- Your events: titles, start and end times, recurrence rules, descriptions, locations, guest lists with each guest’s RSVP status, reminders, and conferencing links, so the application can display, search and notify you about them.
- Your account email address: used to label the connected account inside the application and to key its credentials in your operating system’s keychain.
Write access is used only when you act: creating, editing or deleting events, responding to invitations, and managing guests and reminders. OmaCal never modifies your calendar on its own initiative.
If a future version of OmaCal can provide the same features with narrower Google scopes, it will request those instead.
2. How OmaCal uses this data
Google user data is used solely to provide OmaCal’s user-facing calendar features: displaying your calendars in its views, searching your events, showing event details, firing reminder notifications on your desktop, and carrying out the create, edit, delete and RSVP actions you take. It is not used for anything else at all: no advertising, no profiling, no analytics, and no purposes unrelated to the calendar features you see in the application.
3. Where your data is stored
- Calendar data (your calendar list and events) is cached in a local SQLite database inside OmaCal’s application data directory on your device. It exists there so the application can render instantly and keep working between syncs.
- Credentials: the OAuth refresh token Google issues for your account is stored in your operating system’s secure credential store (on Linux, the Secret Service, e.g. GNOME Keyring or KeePassXC). It is never written to ordinary files.
- Settings (chosen colours, sync interval, notification preferences) are stored in the same local database. Colours you assign to calendars are local to OmaCal and are never written back to Google.
Nothing is stored anywhere else. Extreme Labs operates no servers for OmaCal, so we cannot access, view, collect or recover any of your data, and no copy of it exists outside your device and your Google account.
4. Data sharing and transfer
OmaCal does not share, transfer, sell or disclose your Google user data to anyone. The only party your data is exchanged with is Google itself, over TLS-encrypted connections to the Google Calendar API, at your direction; that exchange is the product. There are no third-party services, advertising networks, data brokers or analytics providers involved.
Two narrow, calendar-free requests exist alongside that. OmaCal checks GitHub's public release listing once a day to learn whether a newer version exists; the request carries the app's version number and your IP address, as any web request does, and nothing else. And when the weather display is on (it is by default; Settings → General turns it off), OmaCal fetches a forecast from Open-Meteo, a keyless public weather service, for coordinates taken from the Omarchy weather widget's setting when one exists or otherwise estimated from your IP address by wttr.in. No calendar data, account identifier or event detail is ever part of either request.
5. Google API Services User Data Policy
OmaCal’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.
In particular, OmaCal does not use Google user data for advertising, does not allow humans to read it (there is no path by which we could), does not sell it, and does not use or transfer it to determine creditworthiness or for lending purposes. Google user data is not used to develop, improve or train generalized artificial intelligence or machine learning models.
6. Data retention and deletion
Because all data lives on your device, retention and deletion are entirely in your hands:
- Revoke OmaCal’s access at any time from your Google account’s third-party access settings. Once revoked, OmaCal can no longer read or write anything on your account.
- Delete local data by removing OmaCal’s application data directory (which holds the SQLite database) and the
omacalentries in your keychain, or simply by uninstalling the application and deleting its data directory. This removes every locally cached copy of your calendar data.
Deleting local data does not affect the events on your Google account; those remain under Google’s own privacy policy and controls, as they were before you used OmaCal.
7. Security
OmaCal follows the security practices Google recommends for desktop (installed) applications: OAuth 2.0 with PKCE and a loopback redirect, so tokens are only ever returned to a process on your own machine; credentials kept in the operating system’s credential store rather than in files; and all communication with Google encrypted in transit with TLS. The application’s full source code is public, so these claims can be verified by reading it.
8. The OmaCal website
The OmaCal pages on extremelabs.io are informational. They set no cookies, run no analytics and include no third-party trackers. If you contact us through the website’s contact form or by email, we use what you send us only to respond.
9. Children
OmaCal is a general-audience productivity tool and is not directed at children under 16. We do not knowingly collect data from children; as described above, we do not collect personal data at all.
10. Changes to this policy
If we change this policy, the new version will be published at this address with an updated effective date. Material changes to what OmaCal accesses would also appear in the Google consent screen, which is re-approved by you.
11. Contact
Questions about this policy or about your data can be sent to info@x3me.net, or raised publicly on the OmaCal GitHub repository.