Privacy
Last updated 2026-11-04
Short version: Coronet has no accounts and doesn’t sell anything about you. Your progress stays in your browser. We only receive what you choose to send: a leaderboard handle and scores, a suggestion, a challenge result, notification settings (in the app, or for the website’s daily reminder), or a friends record — your display name, a friend code and your device’s random ID — the first time you use friends or challenges in the app. Each is explained below.
What we store, and where
Your game progress lives only in your browser’s local storage (or, in the app, on your device). That includes boards in progress, best times, streaks and settings such as colors and auto-mark. It never leaves your device, and nothing of ours receives or keeps it. Clearing your browser’s site data deletes it, and it doesn’t sync between devices. The app’s Share diagnostics button sends nothing by itself; a diagnostics report leaves your device only when you choose to share it. The exceptions are all below: the leaderboard, app notifications and the website’s daily reminder, only if you turn them on; your result on a challenge a friend sent you, when you finish it; a small record that lets the app alert you when a friend answers a challenge you created in the app; and achievement progress, if you’re signed in to Apple Game Center, which goes to Apple, not to us.
Leaderboard (optional)
If you pick a handle on a leaderboard, we store that handle, a random ID your browser makes for itself (so only this browser can post as you), and your scores on boards you play: your time on a daily, or how many boards you solved in a Beat the Clock run. Handles and scores are public on the boards. The random ID is never shown and isn’t derived from your device, and we don’t store your IP address, browser details or cookies with any of it. Don’t pick a handle and nothing is sent. Want yours removed? Email [email protected] and we’ll delete your handle and its scores.
Notifications (optional)
If you turn on notifications in the app, we store the push token your phone gives us (sent through Google’s Firebase Cloud Messaging, which also delivers to iPhones via Apple), your time zone, which games you muted, and for each game your current streak and whether today’s daily is done. That’s what lets us send two daily reminders: a morning heads-up and, only when a streak is about to end, an evening nudge. Those reminders are never more than two a day. It’s keyed to the same random ID as above, not to you.
Separately, if you create a challenge in the app with notifications on, we can send you an alert when a friend answers it. These alerts are not counted in the two-a-day limit of the reminders, and they only ever concern challenges you created in the app; challenges created on the website never trigger them. A game you’ve muted sends none. See “Links you share” for what we keep to make this work.
Turn notifications off in your phone’s settings and nothing more is sent; we keep the token on file in case you turn notifications back on, and tokens that stop working are deleted.
On the website, you can turn on one daily reminder for this browser. If you do, we store what your browser gives us to deliver it — the push address of its notification service (run by Google, Mozilla, Apple or Microsoft, depending on your browser) and the two keys that encrypt the message — together with your time zone and the hour you picked. We then send one reminder a day at that hour, naming that day’s puzzles, until you turn it off in Settings or block notifications for this site in your browser. Turning it off deletes that record straight away; a short log of which days a reminder went to that address is kept for 30 days and then deleted. It isn’t linked to a leaderboard handle, an account or anything else about you, and no cookies are involved. The website offers the reminder only after you’ve finished a daily puzzle, and stops asking once you answer; after that, it’s in Settings.
Apple Game Center (app only, optional)
If you’re signed in to Apple Game Center on your device, the app reports your achievement progress to Apple. That data belongs to Apple and is covered by Apple’s privacy policy. Nothing about Game Center comes to us: we don’t receive your Game Center name, ID or achievements. If you’re not signed in, nothing is reported.
Suggestions
If you use the “Suggest an idea” form, we keep what you send: your words, the handle and game you typed, and when you sent it. That’s how we read and act on suggestions. Nothing else goes with it: no IP address, browser details, cookie or device ID.
No accounts, no tracking
- No sign-up, login or email collection.
- No cookies, tracking pixels or ad trackers. We count visits with cookieless analytics (see below).
- No fingerprinting and no selling or sharing of personal data.
Pages are plain static files. Like any website, the hosting provider that serves them may keep standard server logs (such as IP address, browser and page requested) for security and reliability. We don’t use those logs to identify you.
Analytics
We use Cloudflare Web Analytics to count visits, so we know which pages people use and whether the site is growing. It’s cookieless: it sets no cookies, doesn’t use your browser’s storage, and doesn’t fingerprint you or follow you across other sites.
For each page view it records the page address, the referring site, your browser, operating system and device type, your country, and how fast the page loaded. Your country is worked out from your IP address, but the IP address isn’t kept as part of the analytics. We only see totals, never individual visitors. Blockingstatic.cloudflareinsights.com in your browser or an ad blocker turns it off, and the games work the same either way.
We also count a few game actions, such as starting an unlimited board or a Beat the Clock run. Each count is just the action, the game, whether it happened in the app or on the web, and, for a finished run, how many boards you solved. It carries no cookie, ID, IP address or device details, so it can’t be tied to you or to your page views.
Links you share
Share and challenge links contain only what you see in them: the puzzle (size and seed, a daily date or a catalog number) and, for challenges, the name you typed, your score (your time and hints, or clues or wrong guesses in the word games) and a random ID. We don’t keep a copy of the link.
There’s one thing we keep for every challenge. When a friend finishes a challenge you sent, their result is posted back so you can see how they did: the challenge’s ID (a random code in the link), the game, the name they typed, their score (the same time, hints, clues or wrong guesses the link carries), and when it was posted. Only the first result for each link is kept. The result carries no IP address, browser details, cookie or device ID. (That’s for link challenges — challenges sent to you inside the app work differently; see “Challenges & friends”.) The only way to look a result up is with that link’s ID, so in practice only you and the friend you sent it to can see it (and anyone either of you passes the link on to). After 30 days it can’t be looked up any more, and expired results are deleted as new results arrive.
If you create a challenge in the app with notifications on, we also keep one more record, purely so we can send you the answer alert: the challenge’s ID, your app’s random ID (the same one used for notifications) and your own result on that challenge, including your hints. It is never shown publicly and can’t be looked up from outside. It is deleted in the same 30-day sweep as the results. Challenges created on the website, or in the app without notifications, have no such record.
Your browser also remembers the challenges you’ve sent and answered in the last 30 days, in local storage like everything else, so it knows which answers to check for and doesn’t send your result twice.
Challenges & friends (app only, optional)
In the app you can add friends and send them challenges directly, instead of sharing a link. For that you get a friend tag: your leaderboard display name plus a short code, shown together like name#K7Q2PX. The first time you use the friends features — opening Challenges with a display name, adding a friend, or sending a challenge — the app registers that tag on our server. Registration is one record: your display name, your friend code, and the same random device ID described under “Leaderboard”. Nothing is registered just for opening the app or playing, and there is still no account, email or password. Your identity is kept in your iCloud Keychain when that’s on, so your own devices share one tag — and a phone handed down while signed in to the same iCloud account is still “you”. If iCloud Keychain is off, the tag lives only on that device.
Friends are mutual. Adding a tag sends a friend request; you’re only on each other’s lists once it’s accepted, and our server keeps the pairing so both lists agree. Removing a friend removes the pairing for both of you. Blocking is stronger: it removes the friend, and from then on the blocked code gets the same quiet “nothing there” as a tag that doesn’t exist — for lookups, requests, challenge sends and answers alike. Blocked players are listed under Settings → Challenges, and unblocking there doesn’t re-add the friend.
When you send a challenge to a friend, our server keeps a row for it: who sent it, who it’s for, the game and puzzle, and your result — your time and hints, or boards solved in Beat the Clock. It waits in your friend’s inbox in the app until they answer it or it expires; a challenge older than 30 days can’t be answered any more. When they answer, their result is posted back the same way, and both of you see the two results side by side. Answering a challenge that was sent to you works a little differently from answering a link: your answer travels with your random device ID and your friend code, so the server can check the challenge really was addressed to you and count the answer once. (A result posted from a link carries no device ID — see “Links you share”.) The app keeps your most recent 200 challenges on your device; hiding one just tidies your list.
Next to each friend you’ll see a rivalry tally: how many settled challenges each of you has won, per game and overall. The tally is a pair of counters kept on our server, one per pair of friends, and it’s the same number on both sides. It only moves when a challenge is answered — unanswered, hidden and expired challenges count nothing.
If notifications are on, friends activity brings its own pushes: a friend request, a new challenge, an answer to one of your challenges, and a morning summary. The message names who it’s from and the score to beat. Four limits keep them polite. Pushes that would land between 22:00 and 08:00 in your time zone wait until 08:00. You get at most ten of these pushes a day; anything beyond that is held back and rolled into one summary push the next morning. The Challenges switch in Settings → Challenges turns all four kinds off at once, and anything that arrives while it’s off is set aside for good, not saved up for when you turn it back on. Muting stops pushes, never the challenges themselves — your inbox in the app is unaffected.
Two controls in Settings → Challenges are yours at any time. Delete my challenge data removes your friends record from our server: your registration, your friend pairings and requests, your blocks, your rivalry tallies, the challenges you’ve sent and received, and the push token for this device. Your tag stops working and your list on this device is cleared. Start fresh instead gives you a new identity and a new tag, and clears your list on this device; your old tag stops working, so friends who saved it can no longer reach you. Starting fresh doesn’t delete the old record — it just leaves it behind — so if you’d rather it was gone, delete first, then start fresh.
Advertising
There is no advertising on the site today. If we add ads later, this page will be updated first and will explain what the ad provider collects. Where the law requires it, we will ask for your consent.
Children
The site is suitable for all ages and collects no personal information from anyone, including children.
Questions
Email [email protected] or see the contact page.