Privacy policy
Your calendar stays yours.
This policy covers the Calendar Wheel watch face, the calendar service behind it and this website. Last updated 17 November 2026.
The short version
- Calendar Wheel can read your Google calendars. It cannot create, change or delete anything in them.
- Your events are passed to your watch to be drawn. They are not kept on our server.
- We keep what the connection needs: your Google account's identifier and email address, an encrypted key to your calendar, and a hashed identifier of your watch, linked to your account. We also keep the settings you choose for your watch (your countdowns among them), and what it tells us about itself: its model, its display type, whether it has the on-watch editor, the face's version and its own 12/24-hour setting.
- No advertising and no tracking. Your data is never sold, and nothing from your calendar is used for advertising or to train AI. We count, without names, how the service is used, and which watches and settings are used across all watches, to keep it running and improve it. To fix a problem, we may look at one watch's own settings and what it reports about itself.
- You can disconnect at any time, and we delete what is left when you ask.
What Calendar Wheel reads from Google
When you pair a watch you sign in with Google and are asked for three permissions:
- See the list of your calendars (
calendar.calendarlist.readonly): each calendar's name, colour and whether it is shown, so the watch can colour the day by calendar. - View the events on your calendars (
calendar.events.readonly): the events from a few hours ago until the end of tomorrow, and of each event only its title, start, end, colour, status, whether you have declined it, its kind (so working-location and birthday entries can be left out) and its identifier (so an event that two of your accounts hold is shown once). It does not ask for descriptions, locations, guest lists, attachments or meeting links. - Your email address and account identifier (
openid,email), to know which Google account a watch is connected to and to name it on the page that confirms the pairing.
The permissions are read-only. Calendar Wheel has no way to add, edit or remove events or calendars, and asks for nothing wider: not your calendar settings, not who they are shared with.
How that information is used
Your calendar is used for one purpose: showing you your day, on your watch face and on Your watches. About every five minutes your watch asks our calendar service for the day. The service reads the events from Google, reduces each one to its title, its times, a colour and an all-day mark, and answers the watch. The watch keeps the latest answer in its own storage so it can draw the face between updates. When you open Your watches, the page lists your calendars so you can choose which ones the watch shows, and asks for the day once more to draw a preview of the face in your browser: every calendar included, so the preview follows as you turn calendars on and off. The service keeps nothing of that day, and your browser holds it only while the page is open.
No person reads your calendar. Nothing from it is used for advertising, profiling, analytics or the training of AI or machine learning models.
What is stored, and where
On our calendar service:
- your Google account's identifier and email address;
- the key Google issues for reading your calendar (a refresh token) and a short-lived copy of it that is replaced about every hour, both encrypted (AES-GCM) before they are written to the database;
- a one-way hash of an identifier your watch creates for this app, the six-letter pairing code, and three times: of the pairing, of the watch's latest request, and of the latest preview of its day on Your watches;
- which Google accounts are connected to which watch;
- while you sign in with Google, random one-time values that tie Google's answer to the browser and the watch that asked; they expire after ten minutes;
- the calendars you have chosen to leave off a watch on Your watches, by their Google calendar identifier, and while you are signed in there, a hash of the key in your browser's cookie;
- for each watch, the settings you choose for it on Your watches: which data it shows at which position on the dial, in which design (its style, its size, and whether it shows through an event or under it), the ring round the centre, its always-on brightness, and its time format (12 or 24 hours, or as set on the watch). Only the choices are stored. The readings are taken on the watch itself and never reach the service: the weather and its forecast, your steps, the battery level, heart rate, calories, intensity minutes, floors climbed, sunrise and sunset, stress, Body Battery, sleep score, VO2 max and Pulse Ox;
- the countdowns you set there: each one's name, its date (and time, for a countdown in hours), its icon, how it counts, and when its progress starts: the moment you saved it, unless you pick another start;
- the dials you keep under a name on Your watches (saved configs), up to ten for each watch: each one's name and the settings it holds (the data on the dial, the ring round the centre and the time format, with any countdowns in it). A saved config is deleted when you delete it, and with its watch;
- what kind of watch it is, as the face reports it: its model (Garmin's part number for it), its display type, whether it has the on-watch editor, the face's version, and the watch's own 12/24-hour setting;
- with nothing that identifies a watch or a person: the number of requests per hour to each part of the service, and for a day the times of pairing codes that were tried and opened nothing.
Calendar names, event titles, event times and any other content of your calendar are not stored there. The service's logs record counts and error messages, never calendar content. With each request your watch also sends its time zone, as an offset from UTC, so the service can work out your day. It is sent inside the request, not in its address, and is not stored.
On your watch: the latest day's events, the settings you chose for it (your countdowns among them), the pairing code and a few hours of the weather it has shown, in the watch face's own storage. Removing the watch face from the watch removes them. The face asks for four of the watch's permissions: to run in the background and to reach the internet, so it can ask the service for your day; your location, for one thing: to work out sunrise and sunset for the weather and the sun it draws; and the watch's own readings of Body Battery, sleep score, VO2 max and Pulse Ox, to show them on the dial. The position and those readings are read on the watch and never sent to the service.
How your watch's details and settings are used
What your watch reports about itself and the settings you choose for it are used for three things:
- to run the face and Your watches: the service sends each watch the settings it can show, and the page offers the settings that watch can use;
- to find and fix problems, for example a setting that misbehaves on one model of watch, which can mean looking at what is stored for one watch: its settings and details, the names and dates of its countdowns and the identifiers of the calendars left off it;
- to understand which watches and which settings are used, counted across all watches, so we know what to support and what to build next.
They are not sold and not used for advertising. They are put together with your day only to draw it for you. The service sends your watch the day and its settings in one answer, and the watch keeps both to draw the face; the preview on Your watches puts them together in your browser. The service itself stores no content of your calendar (its names, event titles and times), so it keeps none of it with them and uses none of it to fix problems or to count. When settings are counted across watches, no calendar's identifier is read, and a countdown counts as a countdown: its name and date are not read.
Who else is involved
Your data is not sold, rented or shared with anyone for their own purposes. Four companies process it on the way, only to provide the service:
- Google, whose Calendar API the service reads your calendar from;
- Supabase, which hosts the calendar service and its database;
- Vercel, which hosts this website and the address your watch asks (api.calendarwheel.app): requests and their answers pass through it on the way to and from the calendar service. It keeps ordinary request logs (described under This website) and not what the answers contain;
- Garmin, whose Connect IQ platform and phone app carry the requests between your watch and the service.
Google API Services: Limited Use
Calendar Wheel's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Keeping and deleting
The connection data is kept while your watch is connected and asks for its calendar. You end a connection yourself, at any time:
- Your watches on this website: sign in with a Google account that is on the watch and take any account off it, or the whole watch. An account left on no watch is treated as a disconnect, below; a watch left without an account is deleted.
- Disconnect on this website: sign in with the Google account, which tells the service only the account's identifier and address. Calendar Wheel's access ends at Google, everything stored about the account is deleted at once, and so is a watch that is left without an account. If nothing was stored about the account, nothing is kept from the sign-in either.
- Remove Calendar Wheel under your Google account's connections. From that moment the service can no longer read your calendar; at the watch's next request it deletes everything stored about that account.
- Write to hello@calendarwheel.app from the connected address and everything stored about your account and your watch is deleted within 30 days.
What nobody uses is deleted on its own: a Google account that no watch has asked for in 90 days, and a watch without an account that has been silent for 30 days.
This website
This site runs no analytics or advertising scripts. It sets three cookies, all only when you sign in with Google. One lasts while you sign in to pair, disconnect or open Your watches: it ties Google's answer to the browser that asked, and is deleted when you return, after ten minutes at most. The second keeps you signed in on Your watches for 30 days, or until you sign out; it holds a random key, not your address, and is deleted with the account. The third is a plain yes beside it, so the pages can show you a way to Your watches instead of a sign-in; it holds nothing else. Its host, Vercel, and the calendar service's host, Supabase, keep ordinary request logs (such as IP address, browser type and the address requested, which while pairing includes the watch's code, and for the preview on Your watches your browser's time zone) to operate and protect the service.
Your rights
You can ask what is stored about you, have it corrected or deleted, and object to its use. If you live in the EU, the EEA or the UK these are rights under data protection law, and you may also complain to your data protection authority. The service is not directed at children under 13.
The connection data is used because the service you asked for cannot work without it: pairing a watch is that request. Your watch's settings are used for the same reason, and so is what it reports about itself where the face or Your watches need it. Finding and fixing problems, and counting which watches and settings are used across all watches, rest on our legitimate interest in keeping the service working and improving it, and so do the request logs and the nameless counts, which also protect it. You can object to these uses, as above. The readings your watch draws on the dial (heart rate, stress, Body Battery, sleep score and Pulse Ox among them) are read by the face on the watch itself, only to show what you chose to see, and its position only to work out sunrise and sunset. Neither reaches the service, so we hold none of them. The database is in the European Union. The calendar service itself answers from the data centre nearest to you, which may be outside the EU, and Google, Supabase, Vercel and Garmin are companies based in the United States that may process data there under the safeguards they publish.
Changes and contact
If this policy changes, the new version is published on this page with a new date; a change in how Google data is used is put to you for consent before it applies. Calendar Wheel is made by Oskar Fransson, an independent developer, who is responsible for the data described here. Questions and requests: hello@calendarwheel.app.