sudokUI

sudokUI › Privacy

What sudokUI sends, and what it keeps

sudokUI runs on your device. It has no account, no cookie banner and no advertising, and by default it sends nothing about you. This page lists everything that leaves the device, exactly.

By default: two lines per game, while online

When you make the first move of a game and when it is solved, the app sends one short line to sudokui.app: which of the two it was, what kind of game it is (the daily puzzle, a new puzzle, a practice puzzle, or one opened from a link someone shared; or a door of the advent calendar, with which door it is, 1 to 24), the language the app is set to, the puzzle’s difficulty level, the solve time rounded down to a 15-second step (two hours and up count as one step), for a solved game whether any help was used (only yes or no, never which help), whether the app runs installed or in a browser tab, and the app’s version. The server adds the country the connection came from, as Cloudflare reports it, and keeps the counts for three months in Cloudflare’s Workers Analytics Engine.

That is all. The line carries no name, no account, no cookie, no device ID and no IP address: the server reads the address only to refuse floods, in memory, and the user agent your browser sends (its name and system, sometimes the device model) only to leave out robots: search engines, link previews, headless browsers and test tools. It writes down neither. One game cannot be linked to another. Nothing is stored on your device for this. Offline, nothing is sent and nothing is kept.

A game you open but never play sends nothing. Anything you put on the board is a first move: a digit, a mark, a colour, or candidates shown. A practice puzzle may open part-way through, with digits and candidates the app put there; it counts at your own first move on it. A position someone shares with you, or a grid you paste, that opens with any of these on it counts as begun when it opens. Restarting the puzzle you are playing before you have solved it, or choosing it again while it is still on the board, does not count as a new game; playing a puzzle again after solving it does, even if you undid the last digit.

If you ask: counting your offline plays too

Settings has a switch, “Help count plays, including offline ones”. It is off until you turn it on. On, the app keeps the same lines on your device while you are offline and sends them, marked as sent late, the next time it is open online. It also remembers the day it first counted a game with the switch on, so a line can say whether this device had played on an earlier day. Both are deleted the moment you turn the switch off.

Still no identifier: the lines are the ones above, plus “sent late”, “counting on” and “played before”. They let the counts estimate how much is played offline without following anyone.

If you ask: leaving this device out of the counts

Settings also has “Leave this device out of the counts”. On, the app sends none of these lines from this device, nor the line for a link or a picture you share (below), online or offline, and deletes anything the other switch had kept. The setting itself is remembered on your device, like your other settings, because you asked for it. It holds in every ordinary window of the browser you turn it on in, not in a private one; an app added to a home screen may keep its own settings, so turn it on there too. Two things it does not change: a share or daily link, or the home page, opened from outside sudokui.app in a browser or app where the switch is not on can still count as a landing, because the server counts it from the request and cannot see any switch; and daily times are still sent when you tap the button, or by themselves once you have switched that on (below).

The daily puzzle’s times

After an unassisted solve of the daily, the win screen offers “Send my time and compare”. Only if you tap it, or have switched on sending your times automatically (below), the app sends your time, the finished grid, that you solved it without help, and a random token it keeps for that day, so the same time is not counted twice. Until the server has taken it, the time waits on your device with the token: if the app cannot send it or hear the answer, because you are offline, the server is busy, or the app was closed or went on in another of its tabs first, it sends the same again, with the same token, the next time it is open online, and the server counts it once. The server keeps the time in its 15-second step with the day’s other times, and with it the token and the day it arrived. Nothing links one day’s token to another day’s. To show how many have solved the day’s puzzle, the win screen also asks the server for the day’s numbers, and so does the Share dialog when it offers your daily result again; that request carries nothing about you.

Once you have sent a time, the win screen offers a switch, “Send my daily times automatically”, and Settings has the same switch. It is off until you turn it on. On, the app sends exactly what the button sends, by itself, after each later unassisted solve of a daily, and shows where your time stands at once; never an assisted solve. Off again, a time goes only when you tap the button. The switch is remembered on your device, like your other settings. Your own daily solves, their time and whether you had help, are kept on your device too, at most 31 days of them, so that their share line can be sent again after the win screen has closed; they leave the device only in the ways this page describes. A daily you solve again keeps your first solve as its result, and no other time of yours goes in for it, unless the first had help and the new one did not. If that first time was never sent, the new solve’s win screen offers to send it, and with the switch on it goes by itself after an unassisted solve.

The advent calendar’s doors

From 1 to 24 December the app has an advent calendar: door 1 opens on 1 December, by your device’s date, and one more each day, with the same puzzle for everyone. A door’s time goes in as a daily’s does, and only when you tap “Send my time and compare” on its win screen, on the door’s day or up to a week late, and never after 31 December: your time, the finished grid, that you solved it without help, and a random token kept for that door. The switch that sends daily times by itself never sends a door’s. The server keeps it as it keeps a daily’s, under the door’s own number, and the win screen and the Share dialog ask for the door’s numbers in the same way, with nothing about you. The start and solve lines above say that the game was a door of the calendar, and which door; nothing else. A door’s link opened from outside sudokui.app counts a landing as a shared link does (below), with the door’s level once it is open. A door’s line, shared from its win screen or the Share dialog, counts as a challenge after a solve. Your own door solves, their time and whether you had help, are kept on your device with your daily solves, at most 48 of them, so that the calendar can mark the doors you solved and their line can be shared again; they leave the device only in the ways this page describes.

Share links and pictures, and visits from other sites

A link you share carries the puzzle, its level and HoDoKu rating, up to three technique names and, if you choose to challenge someone, your time in seconds.

When a link or a picture of the board goes from the app to someone, because it went through your device’s share menu, was copied or, for a picture, was saved as a file, the app sends one more line while online: that something was shared, which kind (a puzzle, a position, a challenge after a solve, the daily puzzle’s line, or a picture of the board: one kind, whether or not a hint is drawn on it, and the line does not say which), whether it went through the share menu, was copied or was saved, the puzzle’s level, whether the app runs installed or in a browser tab, and the app’s version. Not the link, not the text, not the picture, not where it went or to whom. The picture is made on your device and is never sent to sudokui.app; whether it shows the candidates or your pencil marks, your colours and the line under it naming sudokui.app is remembered on your device for the next picture, and nowhere else. Copying the puzzle string, or the position as text (the pencil-mark grid), sends nothing. As with the lines above, the server adds the country and keeps the count for three months, reads the address only to refuse floods and the user agent only to leave out robots, and writes down neither. Nothing is kept on your device for the line: offline, or with this device left out of the counts, nothing is sent.

When someone opens a shared link, a daily puzzle’s link or the home page, in any of its three languages, from outside sudokui.app, the server counts one landing, with which of these it was, the puzzle’s level where there is one, the country and one word for where it was opened from. The word comes from what the browser reports about where the link was opened from: for another site, usually just that site’s address; on Android, sometimes the name of the app. When the browser reports nothing, the server reads one tag in the link itself, utm_source, which some AI assistants add to the links they give (ChatGPT’s is utm_source=chatgpt.com): if it is the address of ChatGPT, Perplexity, Claude, Gemini or Copilot, the word is “an AI assistant”. Nothing else in the link is read for this word, and the tag is not kept. The word is one of these: none (a link typed or bookmarked, or opened from an app that reports nothing, as most do), a search engine, an AI assistant, Reddit, the Enjoy Sudoku forum, Hacker News, Facebook, Discord, Lemmy or Mastodon, another social site or app, a chat app or site, a mail app or webmail, GitHub, another sudoku site, an app directory such as AlternativeTo, a news site, or another site or app. The address itself is not kept. No landing is counted when the browser already holds sudokUI and opens the link or the page itself, and who opened it is not recorded.

If you write: reports and letters

“Send feedback”, in the footer and in Info, and “Looks wrong?”, under a hint, open a form. Only when you press Send does the app send what you wrote, the kind of report, the app’s version and language, how long the form was open (which the server uses only to tell people from robots, and does not pass on) and, if you give one, your e-mail address for an answer. A hint report also carries the hint: its technique, its line of notation, the uniqueness and marks settings it was found under, and whether the app found it agrees with the solution. While “Include the board” is ticked, the report carries the board as it stands, as a position link; only if you tick “Include my browser’s details” does it carry your browser’s user agent (its name and system, sometimes the device model).

The server checks the report and passes it on as an e-mail to Anders Imenes, who runs sudokUI; it keeps no copy itself. The IP address the report came from is read only to refuse floods, in memory, as above. Letters to feedback@sudokui.app reach the same inbox. Cloudflare carries the mail through its Email Routing and keeps a log of each letter it handles, with its sender, recipient and subject, for 31 days; that log clears itself, and deleting cannot reach it sooner. Cloudflare, Inc. is in the United States, and the mail passes through it under its data processing terms (the EU–US Data Privacy Framework and the EU’s standard contractual clauses). The inbox itself is with an ordinary mail provider. A report or a letter is kept there until it has been dealt with, at most 12 months, and then deleted, together with any answer to it.

Anders Imenes, in Norway, is responsible for this (the data controller). A report is handled on the basis of your consent, given by sending it, to fix what it describes or to answer you; you can withdraw it at any time, and what you sent is then deleted. You can ask for a copy of what you sent, also in a machine-readable form, to have it corrected or deleted, or its handling restricted, by writing to feedback@sudokui.app, and you can complain to Datatilsynet, the Norwegian Data Protection Authority.

What is never collected

No account, no password, no cookie, no fingerprint, no advertising, no third-party script, and no e-mail address unless you give one in a report or write to feedback@sudokui.app. Your games, pencil marks, statistics, technique record and daily streak stay in your browser’s storage, on your device, and leave it only in the ways this page describes. With the app open in more than one tab or window, one of them plays at a time and the others write nothing: the one that plays keeps a random name for itself in the same storage, so a tab that wakes up after the browser paused it can tell at once that it no longer plays. That name is never sent, and the tabs pass the play to each other inside the browser alone. In each tab’s own history the app also notes whether it has started on that page and, when it reloads itself, why; the browser keeps these notes with the tab’s history, they say nothing about you, and they are never sent. Your settings are kept in the same storage, and among them whether you have ever chosen a theme yourself, the year the Christmas look last came on by itself and, while it is on, the year of its season and the theme it took the place of: so the look comes on by itself in December only if you never chose one, once a season, and your own theme comes back on 1 January. Which theme you use is never sent.

Who runs this, and how to check

sudokUI is run from Norway by its author, Anders Imenes, and served by Cloudflare. The source code, including everything this page describes, is public: github.com/AImenes/sudokUI. Questions and corrections are welcome at feedback@sudokui.app, or as an issue there.

Last changed: November 2026.