Actual Egg Timer

Privacy

Last updated 6 October 2026

Actual Egg Timer is a free app that I, Dan MacKinlay, make on my own as a personal project. It comes as a website and as an iPhone app.

In short

By default, nothing you put into Actual Egg Timer leaves your phone or your browser.

If you turn on Share results, under Sharing results in Settings, the app sends me a result for each egg you cook: how it was cooked and how you said it came out, with a random ID in place of your name. Turn it off and nothing more is sent, but what was already sent stays. Delete shared results, in the same place, deletes every result that device or browser sent.

Sharing came with version 0.4. If your app has no Sharing results in Settings, it is an earlier version, and it sends nothing at all.

What stays on your device

So that they work the same way next time, both apps keep:

On iPhone, these are kept in the app’s own storage on the phone. If you back up your iPhone, the backup includes them, as it does any app’s data. If you share, the iPhone app also makes a key in the phone’s secure chip (below), whose secret half never leaves the phone.

On the web, they are kept in your browser’s storage for this site. The website also keeps a copy of its own files (the page, its code, its words and its pictures) in your browser, so that it opens with no signal. That copy holds nothing about you, and is replaced when the site changes.

Export my results, in Settings, saves your results to a file wherever you choose. The file also holds your random ID if sharing has been on, so anyone you give it to could match it to what you sent. The app itself sends the file nowhere.

What sharing sends

One result for each egg you cook, including the ones you rated before you turned sharing on. A result holds:

The iPhone app also signs each result it sends (below).

What is not sent: your name, an email address, an account, your location, your contacts, your device’s name or any of its identifiers, an advertising identifier, or anything from outside the app.

Two things in a result say a little about where you are. The temperature your water boils at says roughly how high up you are. Your language, your units and whether you picked European or American egg sizes may suggest a part of the world. Nothing sent says more than that.

The random ID is made on your device, from nothing about you, the first time you turn sharing on. It groups your results together, so that I can tell how one person’s kitchen differs from another’s, and it is what lets you delete them. Settings shows it, under Sharing results, as Your random ID. After Start learning again, the app uses a new one, and your next results count as a new person’s.

The time may move a few seconds. While sharing is on, the app moves the time it gives you by up to ten seconds either way, chosen at random for each egg, small enough to stay within “just right”. Results from people who all follow the app’s usual times say nothing about other times. A few seconds either side shows what happens near them. A small Learning mark beside the time says so while sharing is on.

On iPhone, the first time the app sends under a random ID, it makes a key in the phone’s secure chip and asks Apple’s App Attest service to confirm that the key belongs to a genuine copy of the app on a real iPhone. That request goes to Apple and carries none of your results. It carries a scrambled form of your random ID that cannot be turned back into it. After that, the app signs every result it sends with the key. This lets me count results from the app, as installed from the App Store or TestFlight, for more than results from anywhere else. If your phone cannot do this, your results are sent anyway. If it fails only for a while, say with no signal, they wait and go once it works. If it still fails after three days, they are sent anyway.

What I keep, where, and for how long

I keep each result exactly as it was sent, with only the details listed above. Anything else in a request is dropped. For the iPhone app I also keep, for each random ID, the key’s public half and its name, a count of the results it has signed, whether that copy of the app came from the App Store, TestFlight or a developer’s build, and its build number. The code that receives results writes down no address, no device and no time.

Where. In Netlify’s storage for this site, in the United States (the region Netlify calls us-east-2).

How long. For as long as I use them to work out the app’s starting guesses: until you delete them, or until I stop making the app, when I delete them all. The App Attest details for a random ID go when you delete its results.

Who can see them. Only me, through my Netlify account, and Netlify, which stores them for me. I don’t publish anyone’s results or give them to anyone. To work out better starting guesses, I copy the records to my own computer, never into the app’s public code. Each time I do, the copy is replaced with a fresh one from the server, so once you delete your results, they leave my computer too the next time. What I publish is what I worked out: a handful of numbers about eggs and kitchens in general, which every copy of the app starts from.

Your IP address. The code that receives results does not store it. Netlify’s request logs record it, with the time and the page asked for, for about a day (a week on paid plans). When you delete what you sent, the page asked for includes your random ID. Netlify also counts requests by address to turn away floods. I don’t use these logs for anything. They are under Netlify’s own privacy policy.

Stopping and deleting

The legal part, in plain words

This is a personal project, but the app is open to anyone, so I treat the results people share as the data protection law of the EU and the UK expects. Sharing is optional, and the timer works the same without it.

What I don’t do

Both apps have links, in Help and to the code, that open in your browser only when you follow one.

Alarms and the Lock Screen

On iPhone, the alarm is a notification that your phone schedules itself, and the timer on the Lock Screen and in the Dynamic Island runs on your phone. Neither goes through any server, mine or Apple’s. On the web, the alarm is a sound the page plays.

Apple

If you have agreed, in your iPhone’s settings, to share analytics with app developers, Apple may pass me crash reports and overall numbers. If you send feedback through TestFlight, it comes to me. Both come from Apple, not from the app.

Contact

Questions about any of this: forgetmyeggs@danmackinlay.name.

Changes