Privacy Policy
For Omagenda, a calendar plugin for the Omarchy desktop on Linux.
Last updated 27 September 2026.
The short version
Omagenda runs entirely on your own computer. It has no server, no accounts and no analytics. Nobody — including its author — can see your calendar. If you choose to connect Google Calendar, your computer talks to Google directly, and everything it fetches is stored only on that computer.
Who is responsible
Omagenda is free, open-source software published by Andre (GitHub @Neaxic), who is the data controller for the purposes of this policy. Contact: andreas79001@gmail.com.
Data Omagenda handles
Events you create yourself
Stored as a plain JSON file at ~/.config/omagenda/events.json on your own computer. They are never transmitted anywhere.
Google user data, if you connect Google Calendar
Connecting is optional and off by default. Omagenda is fully usable without it, and without a Google account at all. If you do connect it, Omagenda accesses:
| Scope | Data | Why |
|---|---|---|
.../auth/calendar.events | The events on the calendars you choose: their titles, times, dates, descriptions, locations and recurrence. | To display them in the bar, the grid and the day agenda, and to create, edit and delete events when you do so in Omagenda. |
.../auth/calendar.calendarlist.readonly | The names, identifiers, colours and your access level for the calendars on your account. | To show you the list, so you can choose which calendars Omagenda should sync. |
Omagenda does not request the broad calendar scope, and therefore cannot create, rename or delete a calendar — only the events inside the calendars you selected.
How that data is stored
- Events fetched from Google are cached at
~/.config/omagenda/cache.jsonon your computer, so the calendar still draws when you are offline. - The cache is kept separate from your local events file. A sync cannot overwrite what you wrote locally, and a local edit cannot overwrite Google.
- Your OAuth tokens are stored at
~/.config/omagenda/google-tokens.jsonwith file permissions0600— readable only by your own user account. They are never logged or displayed.
How that data is transmitted
Omagenda makes HTTPS requests from your computer to Google's Calendar API (googleapis.com) and Google's OAuth endpoints, and to nowhere else.
There is no Omagenda server. Your calendar data is never sent to the author or to any third party, because there is nothing to send it to. Omagenda contains no analytics, no telemetry, no crash reporting and no advertising.
Limited Use disclosure
Omagenda's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, Google user data obtained through these scopes is used only to provide and improve the calendar features described above. It is not transferred to anyone else, is not used for advertising, is not sold, and is not read by any human — it never leaves your device.
Retention and deletion
You are in control of every copy, because every copy is on your own disk.
- Remove one calendar: click it on Omagenda's CALENDARS page. Its cached events are deleted immediately.
- Disconnect entirely: press DISCONNECT. Omagenda revokes its access token with Google, deletes the stored tokens, and deletes every cached Google event.
- Revoke from Google's side: remove Omagenda at myaccount.google.com/permissions at any time.
- Remove everything: delete the
~/.config/omagenda/directory and uninstall the plugin.
There is no retention period to state, because the author retains nothing.
Your rights
Omagenda is published from Denmark and available worldwide, so the GDPR may apply to you. Rights of access, rectification, erasure, restriction and portability are all exercised directly: the data sits in readable JSON files on your own machine, which you can inspect, edit, export or delete without asking anyone. The author holds no copy, and so has nothing to disclose, correct or erase on your behalf.
Children
Omagenda is not directed at children under 13, and collects nothing from anyone.
Changes to this policy
If this policy changes, the revised version will be published on this page with an updated date, and the change will appear in the project's public git history.