Privacy and data

CatchClock Editorial, Editorial and data team

CatchClock collects nothing that identifies you. There are no accounts to create, no forms to fill in, no email field anywhere on the site and no payments. This page describes what actually happens when you open a page here, in the order it happens.

What we collect from you

Nothing you type, because there is nowhere to type. The site is a set of static pages; it has no login, no comment box, no newsletter signup and no contact form. We do not ask for your location either — city pages are pre-computed for a named city, not generated from your position, so the browser permission prompt for location never appears.

Because we hold no personal data, there is no access, export or deletion request to make: there is nothing on our side with your name on it to hand over or erase.

Cookies and analytics

CatchClock sets no cookies. Nothing on this site stores a value in your browser in order to recognize you on a later visit, which is also why you will never see a consent banner here — there would be nothing for you to consent to.

We do count page views, using Ahrefs Web Analytics. It is cookieless: it records that a page was opened, roughly where in the world from and what referred you, in aggregate, without setting a cookie and without an identifier that follows you to another site. We use it for one thing — to see which pages people actually read — and it is the reason the site can exist without advertising.

What a page loads, and from where

Pages are plain HTML and CSS with a small amount of JavaScript of our own. There are no advertising networks, no social embeds, no comment platforms, no chat widgets and no web fonts pulled from a third party — the type you are reading is whatever your own device provides. Nothing on the page calls a live weather or forecast service, which is a design decision explained on how we calculate bite times: every number is computed before the page is published.

Serving the site does involve our host, a content delivery network, and like every web host it keeps short-lived request logs — IP address, user agent, the URL requested — for security and abuse prevention. We do not use those logs for analytics, and we have no way to connect them to a person. Your host or browser may receive a security cookie from the CDN itself; we do not read it and it tells us nothing about you.

The app, and changes to this page

There is no CatchClock app in the App Store or on Google Play yet, so there is nothing about an app to disclose here. When one is submitted, this page will carry an app section describing exactly what it stores and what leaves your phone — published before the store listing goes live, not after, because the listing points at this URL.

We do not run a support inbox yet, and we would rather say that than print an address nobody reads. A contact address will appear on this page before the app is submitted. Any change to what is written here changes the date at the top of the page; the practice described above is the practice as of that date. If you want to know who is behind the site and what it deliberately does not publish, that is on the about page.