timez

Privacy

What timez knows about you

timez has no accounts, no sign-in and no ads, and nothing it counts is ever used to follow you. The apps send us two things about how they are used: a crash report, and — only if you say yes — counts of which controls get used and which places get added. Anything you write to us with Send feedback reaches us only when you press Send. This website counts its page views and clicks, keeping nothing on your device. Updated 8 October 2026.

Your places

The places you keep, and what you call them, are stored on your device. If you use iCloud, Apple keeps them in step between your own devices — in your iCloud account, which we cannot see. None of it is sent to us.

The web app at timez.day/app keeps your list in your browser. If you sign in to iCloud there, it syncs through your iCloud account in the same way.

Crash reports

On iPhone, iPad, Mac and Vision Pro, timez collects crash, hang and performance-exception reports that the operating system prepares for every app. Each one holds a stack trace, the OS version and the device model. It holds none of your places, no location and nothing tying it to you. We use them to fix the crash, and for nothing else. The Watch sends none; Apple shares crash reports with developers only if you have allowed it in your device's settings.

Usage counts, only if you say yes

timez asks whether it may count which of its controls get used — dragging the time, adding a place, opening the editor — and on which platform: Mac, iPhone, iPad, Vision Pro, Apple Watch or the web app. The counts tell us which parts of timez earn their place and which can go. Nothing is counted until you say yes, on the web app and on TestFlight and App Store builds of the apps alike.

Each count is the name of the control, when it was used, the platform, the system and app version, and random identifiers the app makes itself — new on every visit to the web app, one per installation of the apps, and in the apps one more random number that your own devices share through your iCloud, so we can count people rather than installations. That number is made fresh, never from your iCloud account or anything else about you, and it reaches us only scrambled (salted and hashed), so we cannot turn it back into anything. When you add a place from the catalogue, the count also says which one — by the catalogue’s number for it, the same for everybody who adds that city — so we can see which places are added most, and only ever as totals across many people. It never includes what you call your places, the times you look at, anything you type or paste, your location or your iCloud account, and no identifier shared with other apps or other companies. The counts are not linked to you and are never used to track you, here or anywhere else; in the App Store’s terms they are Product Interaction, a random device ID and a random user ID, used for analytics only.

If you say no, we count that somebody said no — one number per day and platform, with nothing else attached — so that people who declined are not mistaken for people who never used a feature. You can change your answer at any time: under “Made of” in the web app, in About in the apps, and at the foot of the list on the Watch. Stopping throws away anything not yet sent.

Our server also counts how often each of its own features is asked for — a forecast, a waitlist sign-up — as a bare number, with nothing from the request. The counts are kept by Optic, our own analytics service, which runs on Cloudflare like the rest of timez.

This website

timez.day counts how it is used: that a page was viewed, which parts of it were scrolled to, which buttons and links were pressed, whether the demo was played with, and whether a waitlist sign-up went through. With each page view it notes the kind of place the visit came from — a search engine, a social site, another website, a link we shared, or nowhere — as one of those words, never the page or the address.

It keeps nothing on your device to do it: no cookie, nothing in your browser's storage, and the identifiers it sends are made fresh on every page, so two page views cannot be joined up, even from the same browser a second apart. That is why it does not ask first. It never includes anything you type, the address in your browser, the site that sent you, your location, or which cities you looked at in the demo. They go to Optic, like the counts above, and are not linked to you.

Feedback you send

Send feedback, in About in the apps and under “Made of” in the web app, sends us what you write, the kind you chose if you chose one (a bug, an idea, a question or a rating, and the rating itself), the email address if you give one, and which version of timez you are using — the platform, app version and system version. A bug report can also carry your device’s model, language, 12- or 24-hour clock and time zone: the form shows you exactly those values before you send, and you can untick them. You can also attach up to three screenshots you choose: they are redrawn on your device before they go, so a picture carries nothing but what it shows — no location, camera or date — and we strip that again when it arrives. A screenshot of timez shows your places, so the form says so while one is attached. Nothing else is sent: never your places, what you call them or anything else in the app. If you give an address we can reply, and if you are on the waitlist it joins what we already hold about you there; if you do not, we can read it but cannot answer it. Feedback you send through TestFlight reaches us the same way, from Apple, with the address you use for TestFlight. We keep it to read, answer and act on, and you can ask us to delete it at the address below.

Weather

To draw the sky and the weather beside a place, the app asks our server for a forecast at that place's map coordinates — the published coordinates of the city from the catalogue, never your own location. Our server fetches the forecast from MET Norway, or, if MET cannot answer, from Open-Meteo — asking each for that one place's coordinates, from our server's address rather than yours. We do not log the request beyond counting that a forecast was asked for, and it carries nothing about you or your list.

Your location

timez only asks for your location if you tap "Show my location" on the map, and only then. Your device answers, timez moves the map to you, and the answer stays in memory on that device for as long as the map is open: it is never stored, never sent to us or anyone else, and never counted beyond the tap itself. Say no and the map works exactly as before. The arrow that marks where you are in the list comes from your device's time zone setting, read on the device, and never from your location.

The waitlist

If you joined the waitlist on timez.day, we keep your email address, the first name if you gave one (and your surname, when your address plainly spells it out, as in amy.smith@), the platforms you picked, your country as reported by our network provider, the time zone your browser is set to (such as “Europe/Dublin”), and the website that sent you — the site's name only, never the page. We use them to email you about timez, and the time zone so those emails arrive in your working hours rather than in the middle of the night. Reply “remove” to any email, or write to the address below, and we delete them.

Who we are

timez is made by Conor Winders in Ireland, who is the controller of the waitlist data above. Our server runs on Cloudflare. For anything about your data, including a copy of it or deleting it, email app@timez.day. You can also complain to the Irish Data Protection Commission.

Changes

If this changes, this page changes, and the date at the top moves with it.