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:
- your settings, such as the egg size, the units, your altitude, how much water you use, how you cool the eggs, and the language;
- the timer in progress, so it survives the page reloading or the app closing;
- your results: when and how each egg was cooked and, if you said, how it came out, and what the app has learned from them. On the web, “when” includes the time you started, so that two tabs never count one egg twice; that time is never sent. Results the app cannot read are deleted, not kept. Version 0.5 starts your results afresh, and when it first opens it deletes the ones an earlier version kept: to keep them, save them first with Export my results in Settings;
- how long your water took to boil, for each amount you have timed;
- if you have turned sharing on: whether it is on, your random ID and any you used before (so that deleting reaches all of them), and how many of your results have been sent; on iPhone, also the name of the key the app signs with (below) and whether Apple has confirmed it.
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 day you cooked it (a date, with no time of day);
- the egg’s weight, whether you weighed it, measured it or picked a size, and for a size, whether the sizes were European or American;
- how you cooked it: into cold or boiling water, how cold the egg was and whether that was the fridge, the room or a temperature you typed, the room temperature the app worked with, for cold water the temperature of the water it started in, the temperature your water boils at, how long it took to boil and whether you timed that, how much water, how many eggs were in the pot, whether the heat stayed on, and how you cooled them;
- how you wanted the yolk, the time the app gave you, any change it made to that time on purpose (below), when the eggs came out and whether you said so, and how long the app counted for cooling;
- your answers: which of the slider’s words fits the yolk you got, how the white next to the yolk was, and a probe thermometer reading if you gave one (a result from an older version says instead whether the yolk was too soft, just right or too firm);
- what the app expected you to say, and which version of its reckoning and its starting guesses it used;
- which app it was (web or iPhone), its version, and the language and units you were reading it in;
- your random ID, and the result’s place in the order you sent them.
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
- To stop: turn Share results off in Settings. Nothing more is sent, and the time stays where the app would put it. Turning it off does not delete anything: what was already sent stays until you delete it.
- To delete what you sent: Delete shared results, in Settings, deletes every result your device has sent, under every random ID it has used, with the App Attest details, and turns sharing off. If you are offline, the app keeps asking until the server confirms.
- By email: write to forgetmyeggs@danmackinlay.name with your random ID, and I’ll delete the results sent under it. I need the ID, because nothing else tells me which results are yours. You’ll find it in Settings, under Sharing results, as Your random ID, and you can select it and copy it.
- On your device: on iPhone, delete the app, and everything it kept on the phone goes with it. A backup of the phone made before then still holds a copy, until that backup is deleted or replaced. On the web, clear this site’s data in your browser’s settings. Delete what you sent first, because once the app and its random ID are gone, I cannot tell which results were yours.
- Start learning again, in Settings, deletes your results and how long your water took to boil, on your device, and keeps your settings. It does not delete what you sent.
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.
- Who is responsible: I am, Dan MacKinlay, as a private person. Write to forgetmyeggs@danmackinlay.name about anything on this page. I live in Australia.
- Why: to improve the starting guesses every copy of the app begins with, and for nothing else. Nothing I do with your results decides anything about you.
- On what basis: your consent, which you give by turning sharing on. You take it back for new results by turning sharing off. Turning sharing off keeps the results already sent; to take your consent back for those, delete them, with the button or by email. Taking it back doesn’t make what was done before it unlawful.
- Who handles it for me: Netlify, Inc. hosts this site and stores the results, as my processor under the data processing agreement in its terms. Apple delivers the iPhone app and runs App Attest, under its own privacy policy.
- Sent to the United States: the results are stored in the United States. Netlify, Inc. is certified under the EU–U.S. Data Privacy Framework (with its UK and Swiss parts), which the European Commission has found protects data adequately. Its data processing agreement adds the Commission’s standard contractual clauses as a fallback.
- Your rights: you can ask me for a copy of your results, in a form another program can read, and ask me to correct them, delete them, stop using them for a while, or stop using them at all. You can take back your consent at any time. Write to me with your random ID. If you think I have handled your data wrongly, you can complain to a data protection authority, such as the one in the country where you live. Please write to me first, so I can put it right.
- Children: the app is not made for children. If you are under 16, please leave sharing off.
- In Australia: the Privacy Act’s principles generally don’t apply to a private person with a free app like this one, but I follow this page all the same.
What I don’t do
- No accounts and no sign-in.
- No analytics, no advertising, no tracking and no cookies.
- No code from other companies in either app: no libraries, kits or trackers. Both apps are built only from the code in the project’s public repository, on Apple’s and your browser’s own software. The part on this site that receives shared results uses Netlify’s own library for Netlify’s storage.
- The website loads only its own files, from this site, the font included, so no font service learns that you visited.
- Beyond the website loading itself, neither app connects to anything but this site, and then only to send or delete your results when you share. The one exception is App Attest, when the iPhone app first sends (above). While the website is open, it also asks this site, at most once an hour, whether there is a newer version of itself; that asks for one of the site’s own files and sends nothing about you.
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
- 6 October 2026: on the web, each result also keeps the time you started the egg, on your device only; it is not sent.
- 3 October 2026, version 0.4: sharing added, off unless you turn it on. What it sends, what I keep, where, for how long and who can see it, how to stop and how to delete, where to find your random ID, and your rights. Also the website’s offline copy of itself, and its font.
- 2 October 2026: first version.