Desktop Calendar ("the app") is a personal, self-built calendar application for Linux desktops and Android phones. It displays and manages your calendars on your own device. This policy explains what data the app accesses, what it does with it, and where it goes.
Who runs the app
The app runs entirely on your own device. There is no Desktop Calendar server, backend, or hosted service, and the developer receives none of your data. The app talks directly to Google's APIs from your device, signed in with your own Google account.
Google user data the app accesses
Calendar events — https://www.googleapis.com/auth/calendar.events. The app reads the events on the calendars you choose so it can display them, offer reminders, and estimate travel times. It creates, edits, moves, or deletes an event only when you do so in the app. When you put one event on several of your calendars, it stores a random identifier in that event's private properties so it can recognise the copies as one event.
Your calendar list — https://www.googleapis.com/auth/calendar.calendarlist.readonly. Read-only: the names and colours of the calendars in your account, so you can choose which ones to show.
The app's own settings file in Google Drive — https://www.googleapis.com/auth/drive.appdata. One small file in the hidden app-data folder that only this app can see, so your settings follow you between your devices. It holds the calendars you chose and their colours, any iCal feed addresses you added, your home address, travel and reminder preferences, and the starting points you picked for individual events. The app cannot see any of your other Drive files.
Your account email — openid and email. Used only to show which Google account is connected.
Other services the app uses
Travel-time and address features use Google Maps Platform. They make requests to Google with the app's own API key; the requests go directly from your device to Google and are covered by Google's Privacy Policy.
Address suggestions (Places API) — the text you type into a location field.
Travel times (Routes API) — only if you turn travel times on: the location of an upcoming event and where the journey starts (your home address, the previous event's location, or a place you chose).
Current location (Geolocation API) — only when you choose "Current location" on the laptop: the hardware addresses and signal strengths of the Wi-Fi networks nearby, from which Google estimates where you are. Your IP address is not used to locate you. The result is used as that event's starting point.
Google Maps links — when an event's location is a Google Maps short link, the app opens the link to find the place it points to.
iCal feeds — calendar feeds you subscribe to are downloaded directly from the address you entered.
How your data is stored and used
Events are cached locally on your device so the calendar works offline and opens quickly.
On Linux, your Google sign-in tokens are kept in the system keyring. On Android, they are kept in the app's private storage, which no other app can read.
Your data is used only to provide the app's features to you.
Your data is never sent to the developer, sold, shared with third parties, used for advertising, or used to develop, improve, or train artificial-intelligence or machine-learning models. The app collects no analytics and does no tracking.
No person reads your data; there is no server where anyone could.
Desktop Calendar'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.
Revoking access and deleting data
Sign out inside the app (Settings → Calendars → Sign out) to remove that account's tokens from your device.
Delete the synced settings file in Google Drive under Settings → Manage apps → Desktop Calendar → Options → Delete hidden app data.
On Android, uninstalling the app removes everything it stored on the phone. On Linux, signing out removes the tokens; the cached events and local settings are in the com.lucanepa.desktopcalendar folders under ~/.config and ~/.local/share, which you can delete.
Changes to this policy
If this policy changes, the "Last updated" date above will be revised.