Privacy Policy

CalendarWidget

Effective Version 1.2 Applies to Windows desktop app

CalendarWidget is a desktop calendar widget for Windows that can optionally connect to your Google Calendar. This page explains exactly what the app does with your data, and what it does not do.

At a glance

01

What CalendarWidget stores locally

CalendarWidget keeps its data as files in your Windows user profile, inside the app's own local storage folder. None of this leaves your computer unless you choose to sync with Google.

events.json
Calendar events you create in the app (and, for events that were also created in Google Calendar, the Google event ID). Events fetched from Google are also saved on your PC, encrypted with Windows data protection (DPAPI), so that they can be shown while you are offline. You can turn this off in the Google settings, and the saved copy is deleted when you sign out.
settings.json
Your app preferences: display mode, window position, colors, and similar options.
Google sign-in credentials
The access token and refresh token issued by Google after you sign in, kept so that the app does not ask you to sign in every time. They are encrypted with Windows data protection (DPAPI) for your Windows account, so other Windows accounts and other PCs cannot read them. They are not your password; see section 03.

Events and settings are ordinary files protected by the permissions of your Windows account. If a credentials file in the older, unencrypted format is found, it is converted to the encrypted format automatically.

02

What happens when you connect Google Calendar

Connecting Google Calendar is optional. It starts only when you press "Log in" in the Google settings of CalendarWidget. CalendarWidget requests two Google API scopes:

https://www.googleapis.com/auth/calendar.events.owned

https://www.googleapis.com/auth/calendar.events.public.readonly

Google describes these as "see, create, change, and delete events on Google calendars you own" and "see events on public calendars". CalendarWidget uses them only for the following, and for nothing else:

Fetching events (at startup and every 3 minutes, from 12 months back to 6 months ahead) and reading the holidays calendar (once at startup) happen only while you are signed in and automatic sync is turned on. Changes you make to events in the widget (create, edit, delete) are sent to Google immediately whenever you are signed in. These scopes do not grant access to your Gmail, Drive, contacts, or any other Google service. Events fetched from Google are sent directly from Google to your device, and events you create or edit are sent directly from your device to Google; no calendar content passes through, or is stored on, any server operated by the developer.

03

Sign-in, sign-out, and revoking access

Sign-in uses Google's standard OAuth consent flow in your browser. CalendarWidget never sees or stores your Google password. Each person who runs the app signs in individually and receives their own credentials; one user's sign-in never grants access to another user's calendar.

Signing out inside CalendarWidget asks Google to revoke the permission you granted, and then deletes the credentials and the saved copy of your events from your PC. If the revoke request cannot be completed (for example, when you are offline), the permission can remain in your Google Account until you revoke it there. To remove it completely, revoke access at Google Account → Security → Third-party access.

04

What CalendarWidget does not do

05

Google API Services User Data Policy

CalendarWidget's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

06

How long your data is kept

Local files remain on your PC for as long as CalendarWidget is installed. Uninstalling the app removes its local storage folder, including events, settings, and the encrypted Google credentials. Your Google Calendar events are unaffected by uninstalling; they continue to exist in your Google Account under Google's own retention policies, and the permission you granted stays in your Google Account until you revoke it (section 03).

07

Changes to this policy

If this policy changes, the "Effective" date at the top of this page will be updated. Material changes, such as new data collection, will be reflected here before they take effect.