Privacy Policy

Effective date: October 22, 2026 · Applies to the Kwalendar desktop application for Windows (“Kwalendar”, “the app”), developed by maxpowerart (“we”).

Kwalendar is a desktop calendar client for Google Calendar. This policy explains what information the app accesses, why, where it is stored, and how you can control and delete it. In short: your calendar data stays on your computer and is shared with no one.

1. Information the app accesses

Data	Source / permission	Why the app needs it
Your Google account’s e-mail address, name and account ID	Google Sign-In (`openid`, `email`, `profile`)	To show which account is connected and to keep several accounts apart.
Your calendar list (names, colours, time zones, default reminders, access level)	Google Calendar API (`https://www.googleapis.com/auth/calendar`)	To display your calendars and let you choose which ones are shown.
Events: title, time, location, description, attendees and their responses, reminders, recurrence, conference (Meet/Zoom) links	Google Calendar API (same permission)	To display events, remind you before they start, open meeting links, and let you create, edit, move, delete and answer events.

The write part of the permission is used only when you act in the app — for example when you create an event, drag it to another time, delete it or answer “Yes/No/Maybe” to an invitation.

2. How the information is used

To provide the calendar features you use in the app: showing events, reminders, search, creating and changing events.
Kwalendar does not use your data for advertising, profiling, analytics, or to train artificial-intelligence or machine-learning models.
Kwalendar does not sell, rent, share or transfer Google user data to anyone.
No human reads your data. The developer has no access to it.

3. Where the information is stored

On your computer only. Calendars and events are cached in a local database at %APPDATA%\com.kwalendar.app\kwalendar.db so the app opens instantly and works offline. App settings are in config.json in the same folder.
Sign-in tokens (OAuth refresh tokens) are stored in the Windows Credential Manager, protected by your Windows account.
There is no Kwalendar server or cloud: the app communicates directly with Google’s servers over HTTPS.

4. Sharing and third parties

Google. The app sends requests to Google Calendar and Google Sign-In to read and change your calendar data, as described above. Google’s own privacy policy applies to data held by Google.
GitHub (update checks). The app downloads release information and installers from GitHub (github.com/maxpowerart/Kwalendar). No personal or calendar data is included in these requests.
Optional push relay. If you deploy your own relay and enter its address in the settings, Google sends that relay a short signal that “a calendar changed”. The relay never receives event contents and stores only a counter. This feature is off by default.
No other third parties receive any data.

5. Google API Services User Data Policy

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

6. Retention and deletion

Local data is kept while the account is connected, so the calendar stays available offline.
Disconnect an account: Settings → Accounts → delete icon. This removes the account’s local calendar copy and its sign-in token.
Remove everything: uninstall Kwalendar and delete the folder %APPDATA%\com.kwalendar.app.
Revoke access at any time at myaccount.google.com/permissions. The app then can no longer access your Google data.

7. Security

All communication with Google uses HTTPS. Sign-in uses Google’s OAuth 2.0 flow for installed apps with PKCE; your Google password is never seen or stored by the app.

8. Children

Kwalendar is not directed at children under 13 and does not knowingly collect their data.

9. Changes

If this policy changes, the new version will be published on this page with a new effective date.

10. Contact

maxpowerart — thepowerart@gmail.com · GitHub issues