Privacy Policy

Last updated 25 October 2026

Omeletter has no accounts and no advertising. What you do inside a puzzle stays on your device. When you start a puzzle we are told that somebody started it, and when you finish one the time it took is sent so we can tell you how it compares with everybody else who finished it. Neither message has anything in it that identifies you. The website counts visits without cookies. The only personal information we hold is what you choose to give us: an email address to have the printable sheet sent to you, whatever you write in a message you send us, and your address if you email us.

This policy explains how Fisheggs Pty Ltd ("we", "us") handles information in the Omeletter app, for iPhone and iPad and for Android, and at omeletter.app. It is written to meet our obligations under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, and for players in the European Union and the United Kingdom, under the GDPR and the UK GDPR.

The app

Omeletter is an app for iPhone and iPad, from the App Store, and for Android phones and tablets, from Google Play. The two keep and send the same things, and where they differ this section says so.

What the app keeps

The app keeps these on your device:

• which puzzles you have opened, your part-finished answers, and which you have solved or revealed;
• your solve times, daily streak and progress history;
• the hints you have earned, used and bought, the days you have kept, and any day passes;
• your settings (sound and haptics), whether the daily reminder is on, and whether you have seen the tutorial;
• which of our notices you have already seen or closed, so each is shown only as often as it should be.

We have no way to read any of it. What leaves the device is the times and starts described under "Your times, and starting a puzzle", the challenges described under "Challenges", any message you send us, and a copy kept by your phone's own backup.

On an iPhone or iPad, that copy is a record the app saves to your own iCloud account if you are signed in to iCloud: your hints and day passes, including any you bought, your solve times and the hints you used, and which days and puzzles you have started and solved. That record is how your times and what you earned and bought follow you to a new phone, or from your iPhone to your iPad. All puzzles itself comes back through Restore purchases, from Apple. It belongs to your Apple Account and we cannot see it. Deleting the app deletes what is on the device. The iCloud record stays with your Apple Account; write to us if you want it gone and we will tell you how to clear it.

On Android, what the app keeps is included in Android's own backup if backup is turned on for your phone, and Android keeps that copy in your Google account. That is how your progress, hints and day passes come back when you set up a new phone from a backup. It belongs to your Google account and we cannot see it. Deleting the app deletes what is on the phone, and the backup is managed in your Google account's settings.

The daily reminder

If you turn on the reminder, the phone sets it for itself: iOS schedules it on an iPhone or iPad, and on Android the app sets an alarm on the phone for when the new puzzles arrive. Nothing is sent to us or to anybody else to make it happen, and we have no way to send you a notification.

Opening a picture

When you send a picture of a day's result to "Open in Omeletter" from the share sheet, the app opens that day. It looks first for the link the app or the website wrote into the picture. Some messaging apps strip that out, so if it is missing the app reads the link printed at the foot of the picture with text recognition that runs on the phone: Apple's on an iPhone or iPad, and on Android Google's ML Kit, which is built into the app. The picture is read on the phone and is not sent anywhere.

On Android, ML Kit and the Google Play Billing library (see "If you buy something") each keep a log of their own use that is meant for Google. The app is built without the part of Google's software that would send those logs, so they are thrown away on the phone without being sent.

What the app downloads

When it starts, and when it comes back to the front, the app fetches a few small files from omeletter.app: corrections to clue wordings, which optional features are switched on, a note saying whether this version of the app is still supported, and, when it needs one, the key that opens the next block of puzzles already inside the app. On an iPhone or iPad it also fetches the list of printable sheets. They are the same files for everybody and carry nothing about you. The file of optional features can also carry a notice from us, such as a correction to a clue or news of a new kind of puzzle, and the app works out on your device whether it is one for you. If a notice has a picture, the app fetches that picture from omeletter.app when it shows the notice. When it shows how your time compares, it also asks for the finishing times of that puzzle. We keep no record of any of these requests, and if one fails you lose nothing. The files are served by GitHub and the times by Cloudflare, and like any web host they see the IP address a request comes from.

If you buy something

On an iPhone or iPad, purchases go through the App Store. Apple takes the payment and tells the app only whether it went through.

On Android, purchases go through Google Play Billing. The prices you see come from Google Play, Google takes the payment and tells the app only whether it went through, and All puzzles comes back through Restore purchases from your Google account. Hints and day passes come back with the phone's backup, as described under "What the app keeps". A day pass carries the date it opens, so that the app knows which day you bought, and nothing about you.

Either way, we never see your name, your address, your card number or any other payment detail. A purchase on one platform does not carry over to the other.

Apple gives us totals from the App Store and TestFlight, downloads and crash counts and the like, with nobody named in them, except that feedback sent from a TestFlight beta reaches us with the tester's name and email address. Their handling of your information is covered by Apple's privacy policy.

Google gives us figures from Google Play in the same way, installs and crash counts and the like, and a list of orders. Their handling of your information is covered by Google's privacy policy.

Your times, and starting a puzzle

When you finish a puzzle, we are sent the date of the puzzle, which game it was, how long it took and how many hints you used. When you finish all of a day's puzzles, the day's total time and hints go the same way. Two more things go with it that are not about you: a short code showing the app or the website really had that day's puzzle, and a small sum the device works out that makes the message expensive to fake in bulk. The message carries no name, account, device identifier or cookie. Our service reads the IP address it arrives from to limit how many messages one place can send in a minute, and does not write that address down. There is nothing in these records that could tie two of them to the same person.

What you get back is how that compares: how many people have finished the same puzzle, the middle time, the fastest tenth, and how many used no hints. Everybody sees the same figures.

The first time you put a letter into a puzzle, we are also told the date, the game and that it was started, with the same code and sum and nothing else, so that we can see how many of the people who start a puzzle go on to finish it. Playing a puzzle again sends nothing. Times and starts are deleted after 120 days.

Challenges

When you open the share sheet for a day, the app or the website asks our service for a short code, so that the link you send can be taken up as a challenge. To make the code it sends the date of the puzzles and your result for that day: which puzzles you solved, how long each took, how many hints each used, the day's total and your streak. The same check that the day's puzzles were really there, and the same small sum, go with it. We keep the date, that result, a count of how many people have used the code, and the date it was made. Nothing else is kept with it: no name, no account, no device identifier and no IP address, so two challenges cannot be linked to each other or to you. Anyone who has the link can see the result it carries, which is what it is for. A challenge is deleted 14 days after it was made.

Opening a challenge you were sent asks the service what the code is for. If it opens a day in the app that you have not bought, the app tells the service so it can count the use. Neither request carries anything about you.

Sending your result back to the person who challenged you makes a code of its own in the same way. That one also records the code of the challenge it answers, so their device can show the two results side by side. If the code cannot be made, your result goes in the link itself instead and does not pass through our service.

The website

What the website keeps

Your answers, what you have solved, your streak, your hints, your settings and which of our notices you have seen or closed are kept in your own browser so the site can show them when you come back. They stay there. Only this site can read them and clearing your browsing data clears them.

A shared result is carried in the part of the link after the #, which browsers never send to a server, so we do not see what you share or who you share it with. A challenge link carries a code there instead, and what that code holds is described under "Challenges".

How the website counts visits

We count visits with Cloudflare Web Analytics. It sets no cookies, stores nothing in your browser and uses no identifier of any kind, so what we see is totals rather than people: how many came, which pages they read, and roughly where, on what, in which browser. Nothing about your puzzles or your results is sent, and neither is any part of a shared link after the #. Cloudflare's own handling of it is covered by their privacy policy. The app uses no third-party analytics service and has no visit count. The only counts it makes are the starts and times described under "Your times, and starting a puzzle", and on an iPhone or iPad the sheet downloads described under "The printable sheet". They go to our own service on Cloudflare and carry nothing that identifies you. The website sends the same starts and times. The count of starts, and of sheet downloads, is why the app's App Store privacy label lists product interaction for analytics, marked as not linked to you, and why its Google Play data safety section lists app interactions for analytics.

The site's typeface, Archivo, is served from omeletter.app itself. The other places a page reaches are Cloudflare, for the visit count, the solve times and challenges, and Turnstile if you open the sign-up form.

The printable sheet

The sheet link on the website, and the one in the app for iPhone and iPad, go through us, so that we can count how many sheets are opened. We write down the date of the puzzle, the date it was opened, and a number. The record holds no email or IP address, cookie or other identifier. The link in the emailed sheet goes to the sheet's page on the website and is not counted.

The sheet by email

You can have the sheet emailed to you on the mornings you choose. It is the only part of Omeletter that asks you for anything about yourself, and everything else works without it.

• Kit holds the list and sends the emails. Your address and the days you picked are stored with them, under Kit's privacy policy, which includes their record of whether you opened one.
• Your address reaches Kit through us. We do not write it down and we keep no copy of the list.
• You confirm the address before anything is sent to it.
• Every email has two links at the foot: one stops them, one changes which mornings you get.
• Nothing about your puzzles, times or results is attached to your address. Everybody gets the same sheet.
• We use the list for the sheet and nothing else. It is not sold, rented or given to anybody.

When you open the form to subscribe, the page loads a check from Cloudflare Turnstile, which tells a person from an automated program so that nobody can sign up somebody else's address in bulk. It sees your IP address and some details of your browser, under Cloudflare's privacy policy, and tells us only whether the check was passed. It is not loaded unless you open the form.

What we do not do

• We do not ask you to make an account.
• We do not carry advertising, and there is no advertising software in the app or on the site. There is no analytics software in the app. The counts we keep are the ones described above, of puzzles started, times and sheet downloads, and none of them identifies anybody.
• We do not track you across apps or websites. The app declares no tracking in its App Store privacy manifest, and its Google Play data safety section says no data is shared.
• We do not sell, rent or hand over personal information. The only personal information we hold is what you give us: an email address for the emailed sheet, a message you send, and the address you email us from.
• We do not use the times to work out who anybody is, and we could not: there is nothing in them to go on.

Children

Omeletter suits all ages. It asks nobody for anything beyond the optional email address for the printed sheet, and there is no chat, nothing written by other players, and no way for one player to reach another.

If you write to us

The form on the support page, and the report button inside a puzzle, send us your message. They ask for no email address and send nothing that says who you are, so we cannot reply to them. Messages are stored encrypted, and we keep them for six months and then delete them. If you would like an answer, email us at hello@omeletter.app; we keep that email thread for six months as well. Either way it is used to answer you and for nothing else, and you are not put on any list. Ask us to delete yours sooner and we will.

A clue report sends the date, the game and the clue with it, so we can find the clue you mean. Nothing else about your play goes with it.

A message sent from inside the app also carries the app's version and build number and what it is running on: on an iPhone or iPad, which phone or iPad it is and which version of iOS; on Android, the phone's maker and model and which version of Android. Those are the first things we would have to write back and ask you for. On an iPhone or iPad, if something has gone wrong, you can switch on a diagnostic log before you send, which adds a short list of what failed: a file that would not load, a time that would not post. That list is held in memory while the app is open and never written down anywhere, and it goes only if you switch it on. A message sent from the website carries none of this.

Where it is held

The services we use are Cloudflare (the times, the messages and the visit count), GitHub (which hosts the website), Kit (the emailed sheet), Apple (our email and the App Store) and Google (Google Play). Their servers may be in the United States and other countries, so an address or message you give us may be held outside Australia.

Your rights

You can ask us for whatever we hold about you, ask us to correct it, or complain about how we have handled it. Email the address below and we will answer within 30 days. In most cases the answer will be that we hold nothing. If our answer does not satisfy you, you can take it to the Office of the Australian Information Commissioner at oaic.gov.au.

If you are in the European Union or the United Kingdom

For people in the EU and the UK, Fisheggs Pty Ltd is the controller of the personal information in this policy under the GDPR and the UK GDPR. These are our reasons for using each part of it:

• your email address for the emailed sheet: your consent, which you give when you confirm the address and can take back at any time with the link at the foot of every email;
• a message you send us, the address you email us from, and the device details and diagnostic log that may come with it: our legitimate interest in answering you and fixing what you report;
• the IP address a request comes from, which is used to limit how many messages one place can send and is not written down, and the website's visit count: our legitimate interest in keeping the service running and protecting it from abuse;
• your purchases: needed to give you what you bought, with Apple or Google handling the payment under its own policy.

You can ask us for a copy of what we hold about you, and ask us to correct it, delete it, give it to you in a form you can take elsewhere, or limit how we use it. You can object to any use that rests on our legitimate interests. Taking back your consent does not affect anything done before you took it back. Write to hello@omeletter.app and we will answer within one month. We make no decisions about anybody by automated means.

You can also complain to the data protection authority in the country where you live, or in the UK to the Information Commissioner's Office at ico.org.uk.

Where Cloudflare, GitHub, Kit, Apple or Google hold your information outside the EU or the UK, it is covered by the safeguards those companies offer for that purpose, such as standard contractual clauses or the EU-US Data Privacy Framework.

Changes

If this policy changes, the date at the top of the page changes with it. If we ever start collecting something we do not collect now, we will say so in the app before it happens.

Contact

Fisheggs Pty Ltd
Sydney, New South Wales, Australia
hello@omeletter.app