Perfect Clock — Privacy Policy

Last updated: November 18, 2026

Perfect Clock is a world-clock timeline app (available as a web app and as a browser extension). This page explains what data it handles and how. Without Google Calendar connected, Perfect Clock has no account for you and keeps nothing about you on its server, unless you join the Pro waitlist.

Data stored locally

Your selected cities, per-city work-hour settings, display preferences (time/date format, notification toggles, including which public calendars notify you) and whether you removed the demo week are stored only in your browser's local storage (or, for the browser extension, its local extension storage). None of this is transmitted to our server; Google Analytics receives only the fixed feature-usage events described under Analytics. Uninstalling the extension, or clearing site data for the web app, removes it immediately. Google Calendar events are not stored on your device at all — see below.

City search

City search runs entirely on your device: the list of cities is built into the app (city data from GeoNames, CC BY 4.0), and the text you type in the search box is not sent anywhere.

Notifications

Event-start notifications use your browser's own built-in Notification API. This is entirely local to your device; no notification content is sent anywhere.

Google Calendar

If you explicitly click "Connect Google Calendar", Perfect Clock requests read-only access (calendar.readonly) to your primary Google Calendar, solely to display your events on the timeline and in their details card, together with your Google account's ID and email address (openid email) to recognise your connection.

Web app. You sign in on Google's own page once. On the first sign-in a Perfect Clock account is created for you automatically, identified by your Google account ID and email address — there is no separate registration. Our server then keeps a Google refresh token for your account, encrypted, so you don't have to sign in again on every visit; your browser only holds a Perfect Clock session cookie (HttpOnly, valid for 180 days of inactivity). When the timeline needs your events, our server requests them from Google and passes them to your browser without storing them; the browser keeps them in memory only and never writes them to its storage. Only the fields needed for the timeline and the event's details card are requested: event ID, title, start, end and status, and — shown when you open an event — its location, description, video-call link (Google Meet or another provider's) and link to the event in Google Calendar. Attendees and organizer are not requested.

Browser extension. The extension uses the same Perfect Clock account and server as the web app. You link it once in a Google sign-in window opened by the browser (identity.launchWebAuthFlow); if you are already signed in on perfectclock.cc in the same browser, it is linked without that window. In Chrome it can also recognise the Google account of your Chrome profile (chrome.identity) to sign in to an existing Perfect Clock account without any window. The extension keeps only a Perfect Clock session token in its own extension storage — never a Google token; calendar events come through our server, as in the web app, and are kept in memory only.

You can revoke access at any time using the app's own "Disconnect" button, or from your Google Account permissions page.

What our server stores

For a connected account our database holds only:

Calendar events are never written to our database, files or logs. Google tokens are never sent to your browser or the extension.

Retention. Sessions expire after 180 days without use. Google tokens are deleted when you click "Disconnect", when you revoke access in your Google account (on the next request), or when you delete the account. The account record (Google account ID and email) is kept until you click "Delete account".

Where. The server runs on Vercel, which keeps standard request logs (IP address, requested address, time) for up to one day; the database is a managed PostgreSQL service. Both act only as processors on our behalf.

How we protect your data

All communication between your browser, our server and Google's servers happens over HTTPS/TLS, so your calendar data is encrypted in transit. The session cookie of the web app is HttpOnly and Secure, so scripts on the page can't read it. In Chrome, a Google access token for the extension may also be held in Chrome's own chrome.identity token cache; it expires on its own after about an hour and is used only to recognise your account.

Limited Use disclosure

Perfect Clock'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. Google Calendar data is used only to display your events on the timeline and to show event-start notifications. It is not transferred to anyone, not used for advertising, not read by humans, and not used to develop, improve, or train generalized AI or machine-learning models.

Analytics

The web app at perfectclock.cc and the browser extension use Google Analytics 4 to count visits, see which countries the app is used from (and, for the website, which browsers and screen sizes), and which built-in features are used.

On the website, Google Analytics sets its own first-party cookies (_ga, _ga_*) to recognise repeat visits. You can block or delete them in your browser settings, or opt out of Google Analytics on all sites with Google's browser add-on.

Google Analytics receives the page address, referrer, browser and device details (including a shortened copy of your browser's user-agent string, which we use to tell automated visits from real ones), and your approximate location derived from your IP address (Google Analytics 4 does not log or store IP addresses themselves). It also receives a small number of feature-usage events — for example, that a built-in city was added or removed (identified by its fixed catalog name/timezone, e.g. "Europe/London"), which keyboard shortcut was pressed, which setting was changed (and its new value, e.g. time format or theme), that the free-tier 3-city limit was reached, or that a Google Calendar connection attempt started, succeeded, or failed. It never receives any Google Calendar data (event titles, times, or attendees), anything you type into the city search box, or any other content — only these fixed, non-personal event names. Advertising features and Google signals are turned off.

In the browser extension, no Google script is loaded and no cookies are set. The extension generates a random identifier on install, keeps it in its local extension storage, and sends the same kind of fixed feature-usage events, plus a side-panel (in Firefox, sidebar) open, the extension's installation and updates (with its version number), to our server at perfectclock.cc. Our server accepts only that fixed list of event names and parameters, adds the country it derives from your IP address, and forwards the events to Google Analytics; your IP address itself is not forwarded. When the extension is removed, the browser opens perfectclock.cc, where that visit is counted by the website's analytics as above. Uninstalling the extension deletes the random identifier. In Firefox, the extension sends these events only if you allowed "technical and interaction data" when installing it, and our server adds the country only if you also allowed "location"; you can change both at any time in the extension's permissions in Firefox's Add-ons Manager. See how Google uses data from sites that use its services.

Perfect Clock in ChatGPT and Claude

Perfect Clock is also available as an app in ChatGPT and as a connector in Claude. When you ask the assistant to plan a meeting or find a time to meet, the assistant sends our server (perfectclock.cc/mcp) only what is needed for that request: the meeting title, date, time, duration and how it repeats, and for each participant the label used in the conversation (a name or a place), their time zone and, optionally, their working hours. Participant names, if used as labels, and anything you put in the meeting title are the only personal data involved. We don't ask for and don't use your conversation, your ChatGPT or Claude account details, your location or your contacts; approximate location or locale hints that an assistant may attach to a request are ignored and not stored.

Fonts

The app's typefaces (Inter and Michroma) are served from perfectclock.cc itself, together with the rest of the app; loading them sends no requests to Google Fonts or any other third party.

What we don't do

Pro waitlist

If you leave your email address to hear when Perfect Clock Pro launches, our database keeps that address, the place on the site where you left it (for example, the "page not found" page) and the time. It is used only to send you one email when Pro launches, is not tied to your Perfect Clock account and is not shared with anyone. The address is deleted after that email is sent, or earlier at your request to the address under Contact.

Data deletion

Settings and your own events are stored locally on your own device, so you can delete them at any time using your browser's standard, built-in tools — clearing site data / browsing data for this app in your browser's settings, or uninstalling the browser extension — with no need to contact us. Disconnecting Google Calendar from within the app revokes Google's access right away, deletes the stored Google tokens and removes the calendar events from the timeline; you stay signed in to your Perfect Clock account. "Sign out" ends the session in this browser or extension. "Delete account" (in the settings) revokes Google's access and deletes everything our server holds about you: the account record, the encrypted Google tokens, the meeting schedules saved to your account and all sessions on all your devices. Revoking access from your Google Account page also stops our server from reading your calendar; the stored Google tokens are deleted on the next request.

Changes to this policy

If this policy changes, the updated version will be posted at this same URL with a new "Last updated" date.

Contact

Questions about this policy or requests about your data: support@perfectclock.cc. General questions can also be raised via the project's GitHub issues.