Privacy Policy

Summary

No server, no account, no telemetry. WinKlok runs on your PC. The developer operates no server that receives your data and has no access to it.
Google sync is optional. Nothing is sent to Google until you press Connect and approve Google’s consent screen.
Your Google data stays between your PC and Google. It is stored on your PC only (encrypted with Windows DPAPI), is never sold, shared, used for advertising, or used to train AI models.
You are in control. Choose which calendars to show, turn automatic sync off, or press Disconnect to revoke access and delete the stored data.

Who we are and what this covers

WinKlok is a free, open-source modification (“mod”) for the Windhawk (opens in a new tab) platform, written and maintained by Shifting Whistler (the “developer”, “we”). It runs inside Windows Explorer on your own computer and replaces the taskbar clock flyout with a calendar, stopwatch, timers, alarms, tasks, notes and a notification panel.

This policy covers WinKlok version 1.2.0 and this website (winklok.pages.dev). The program is open source: you can inspect exactly what it does in the public repository (opens in a new tab). We wrote this policy by reading that source code; where behavior depends on third parties (Windows, Windhawk, Google), we say so.

The developer does not run any WinKlok cloud service. WinKlok has no user accounts, no database and no backend of ours. When this policy says information is “stored on your PC”, it is stored on your device, not with us.

Data WinKlok keeps on your PC

WinKlok saves its data in the local storage that Windhawk provides to each mod. This data never leaves your PC unless a row below says otherwise.

Data	What it contains	Leaves your PC?
Settings	Visible tabs, 12/24-hour time, panel material and layout, notification panel mode, default sounds, preview options.	No
Stopwatch, timers and alarms	Elapsed time and laps, timer names, durations and presets, alarm times, days, labels, snooze and sound choices. While a timer or alarm is armed, WinKlok also saves a timestamp now and then so it can tell if the PC was off when something came due.	No
Tasks and notes	The text you write, plus creation times and your note zoom level.	No
Dismissed notifications	Identifiers (not the text) of notifications you dismissed inside WinKlok, so they stay hidden in its panel.	No
Google Calendar sync data	Only if you connect: the sign-in token, your calendar list and selection, cached events and unsent changes. See Google Calendar sync.	Only to and from Google

WinKlok does not encrypt settings, tasks, notes, timers or alarms; they are stored the way Windhawk stores mod data. Anyone who can use your Windows account or read Windhawk’s storage on your PC may be able to read them, so avoid keeping secrets in notes.

Other things WinKlok does on your PC

Notification panel. If you use WinKlok’s own panel for the taskbar bell, it reads the notifications that Windows currently holds for your user account. It does this from a private temporary copy of the Windows notification database (wpndatabase.db) made in your temporary folder and deleted again straight away, opened with the SQLite library that ships with Windows. The titles and text are shown only on screen. Dismissing a notification in WinKlok only hides it inside WinKlok. Nothing is sent anywhere.
Clipboard. WinKlok accesses the clipboard only when you paste into a note (to convert pasted web or chat content to Markdown) and when you press the Copy button (to copy the note text).
Links. When you click a link in a note, or one of the project links in Settings, your default web browser opens it. WinKlok does not fetch those pages itself.
Sync time now. This button runs the Windows Time tool (w32tm.exe /resync /force) and, if the Windows Time service is stopped, starts it, asking Windows for administrator permission when needed. Any request to a time server is made by Windows, using the time source configured in Windows, not by WinKlok.
Sounds. Alarm and timer sounds are generated in memory. WinKlok downloads nothing.
No telemetry or updater. WinKlok has no analytics, crash reporting, advertising or update checker of its own.
Logs. Only if you turn on logging for the mod in Windhawk, WinKlok writes technical diagnostic lines to Windhawk’s log on your PC. The Google sync code writes no log lines at all, so tokens and calendar content are never logged by it.

Google Calendar sync (optional)

This section describes how WinKlok handles data it receives from Google APIs. It applies only if you choose to connect a Google Account in Settings → Sync with Google Calendar.

Consent and sign-in

Nothing happens until you press Connect. WinKlok then opens your default web browser at Google’s own sign-in and consent page (it does not embed a browser or ask for your password).
WinKlok uses the OAuth 2.0 authorization-code flow for installed desktop apps with PKCE (a random code verifier with an S256 challenge) and a random state value that is checked when the browser returns.
For the return trip, WinKlok briefly listens on a random free port of 127.0.0.1 (your own computer only). It accepts a single matching callback, shows a short confirmation page in your browser, and closes the listener, or gives up after five minutes or when you press Cancel.
Google may let you untick individual permissions. WinKlok needs both permissions listed below; if one is missing, it revokes the sign-in it just received and reports the problem.

Permissions requested (OAuth scopes)

Scope	What the permission allows	Why WinKlok needs it
`https://www.googleapis.com/auth/calendar.calendarlist.readonly`	See the list of calendars on your calendar list (read-only).	To show the calendars you can tick, with their names, colors and whether each is read-only; to find your account address (the identifier of your primary calendar) for the status display; and to color events that have no color of their own with their calendar’s color.
`https://www.googleapis.com/auth/calendar.events`	View and edit events on all calendars you can access.	To read the events of the calendars you tick, and to create, edit and delete events when you do so in WinKlok. It is used instead of the narrower “owned calendars” permission so that calendars shared with you can be shown and, where Google allows it, changed.

The permission as granted by Google is broader than what WinKlok does with it. In practice WinKlok fetches events only from calendars you have ticked in its settings, requests only the event fields listed below, and sends changes only for events you created, edited or deleted. WinKlok does not request the full calendar permission and cannot access your email, contacts, files or other Google services.

Google user data WinKlok accesses

Calendar list: each calendar’s identifier, name (or your own renamed label), color, whether it is your primary calendar, and your access level (owner, writer or reader). Calendars you can only see as free/busy are ignored.
Events of the calendars you tick, from about six months in the past to eighteen months ahead: identifier, version tag, status, title, description, location, color, start and end, last-updated time, the identifier of the repeating series an occurrence belongs to, event type (for example birthday or focus time), and whether you are the event’s organizer.
Not requested: attendees and their addresses, video-conference links, attachments, reminders and other event details. When you edit an event, WinKlok sends only the fields you changed.

How your Google data is used

WinKlok uses Google data only to provide the features you see: showing your events in its calendar (rings, hover cards and the event editor), creating, editing and deleting events at your request, and keeping the local copy in step with Google. It is not used for advertising, profiling, analytics or machine learning, and no person, including the developer, reads it.

Storage and protection

Long-lived token: encrypted with Windows DPAPI for your Windows user account (with an application-specific entropy value) and stored in Windhawk’s mod storage on your PC. If Windows cannot encrypt it, WinKlok does not connect.
Short-lived access tokens: kept in memory only, overwritten when you disconnect or the mod stops.
Calendar cache: your calendar list, your tick-box selection, a copy of your events (so they show instantly and while offline) and any changes not yet uploaded are encrypted with DPAPI in the same storage. If the copy would be large, only the unsent changes and your choices are kept and the rest is fetched again.
In transit: all requests use HTTPS (TLS 1.2 or newer) and go only to Google hosts. Redirects are never followed, so your token is never sent anywhere else.
Limits of this protection: DPAPI protects the data from other Windows users and from copying the storage to another PC. It cannot stop software running as you on your unlocked PC from reading it. Keep your PC secure.

Where the data goes

WinKlok communicates only with accounts.google.com (the sign-in page, opened in your browser), oauth2.googleapis.com (obtaining, refreshing and revoking tokens) and www.googleapis.com (the Google Calendar API). No other server is contacted, and nothing is sent to the developer.

When synchronization happens

Shortly after Windows Explorer starts with WinKlok connected; every five minutes (every minute while the panel is open); when you open the panel after it has been idle; when you press Sync now; and shortly after you save or delete an event.
With Automatic sync turned off, WinKlok no longer checks Google on a schedule: it syncs when you press Sync now, and still uploads changes you make.
Changes made while offline are kept on your PC and uploaded later. A temporary network failure is never treated as a deletion, and a failed sync never wipes your events.
Unticking a calendar stops showing and syncing it and removes its cached events from your PC (unsent changes to it are still uploaded). Ticking it fetches it again.

Shared calendars and other people’s information

If you tick a calendar shared with you, its events (which may include other people’s information) are handled exactly like your own: shown on your screen, cached in encrypted form on your PC and never passed on. Read-only calendars are never modified.

Google API Services User Data Policy: Limited Use

WinKlok’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements. In particular:

WinKlok uses Google user data only to provide and improve the user-facing calendar features described above.
We do not transfer Google user data to others, except as needed to provide those features, to comply with applicable law, or as part of a merger or sale with notice to you. Because the data never reaches the developer, there is currently nothing to transfer.
We do not use or transfer Google user data for serving advertisements, including retargeting or interest-based advertising.
No human reads Google user data, unless you explicitly ask us to look at specific data for support, it is needed for security or to comply with law, or it is aggregated and anonymized for internal operations. WinKlok collects no such data.
We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.

We do not sell, rent, trade or share your information. Because WinKlok has no backend, the developer does not receive your settings, notes, tasks, alarms, notifications, Google tokens or calendar data, and so cannot disclose them, for example in response to a legal request. The only parties your Google data is exchanged with are you and Google, directly from your PC. The source code is public and contains no hidden network destinations beyond those listed here.

Retention, disconnecting and deletion

Local data stays in Windhawk’s storage until you delete the notes, tasks or alarms concerned, or remove the mod’s data in Windhawk. Whether Windhawk also removes a mod’s stored values when you uninstall the mod is up to Windhawk, so remove data you care about first.
Google data: press Disconnect in Settings → Sync with Google Calendar. WinKlok asks Google to revoke the token, then deletes the stored token, calendar list, selection, cached events and unsent changes from your PC. If you have unsent changes it asks you to confirm first. If Google cannot be reached, the local data is still deleted and WinKlok tells you to remove access yourself.
You can always revoke access at Google at myaccount.google.com/permissions, independent of WinKlok. If you do, WinKlok will report that sign-in expired and keep your cached data on your PC until you reconnect or disconnect.
Google may expire or revoke tokens by itself (for example after a password change). WinKlok then asks you to connect again.
Events you created or edited are changes in your Google Calendar. Disconnecting does not undo them, and deleting WinKlok’s local data never deletes anything from Google.

This website

This site is made of static files. It has no accounts, forms, comments, cookies, analytics, advertising, tracking pixels, third-party scripts, fonts or embedded content, and it stores nothing in your browser. It is hosted on Cloudflare Pages (opens in a new tab); like any web host, Cloudflare processes technical request data (such as your IP address and browser type) to deliver the site and keep it secure, under Cloudflare’s privacy policy (opens in a new tab). We do not receive or use that data to identify visitors. Links to GitHub, Windhawk, Google and others lead to sites with their own policies.

Third-party services

Google processes your Google Account and calendar data under the Google Privacy Policy (opens in a new tab). Signing in to Google happens on Google’s pages in your browser.
Windhawk is a separate application that installs and runs WinKlok. Its handling of your data is governed by its own documentation and policies; see windhawk.net (opens in a new tab).
GitHub hosts the source code and issue tracker. Anything you post there is public and subject to GitHub’s terms and privacy statement.

Your choices and rights

You decide whether to use Google sync, which calendars to show, whether sync runs automatically, and when to disconnect. You can read, change or delete your local data with WinKlok and Windhawk, and you can disable or remove WinKlok at any time. Because the developer holds none of your personal data, requests to access, correct or delete it are answered by those controls and by Google’s own account tools. If you are in a region with data-protection rights (for example the EU, UK or California) and have a question or request, please use the contact options below.

Security

WinKlok runs inside Windows Explorer, so it is written conservatively: network access happens on a separate background worker, tokens are encrypted at rest and wiped from memory when no longer needed, and all network destinations are fixed. No software is perfectly secure. If you find a vulnerability, please follow the guidance on the Contact page rather than posting details publicly.

Children

WinKlok and this website are general-purpose tools and are not directed to children. We do not knowingly collect personal information from anyone, including children. A Google Account used with WinKlok is subject to Google’s own age requirements.

Changes to this policy

If WinKlok’s behavior or this policy changes, we will update this page and its effective date, and the changes are visible in the public repository history. Before any release that would use Google user data differently than described here, this policy will be updated first and, where required, Google will ask you to consent again.

Contact

Questions or requests about privacy: open an issue on GitHub (opens in a new tab) (public: please do not post personal information) or see the Contact page for all options.