Removing the account is not a missing feature. It removes a whole category of failure from a ten-minute game.
Every game with an account has a fake first move: signing up, confirming an email, choosing a username. For a daily puzzle played in ten minutes, that fake first move is often longer than the game itself, and the design question is whether it buys anything the player wants.
In a small daily puzzle it usually does not. Progress can live in a browser, a share card can encode the result in text, and the archive can be browsed without identity. What the account adds is cross-device continuity and leaderboards, which are valuable to a tiny minority of players and costly to everyone else in friction and privacy. The design choice is to serve the ten-minute player first and let the identity features wait.
The choice has real consequences worth naming. Without accounts, there is no password reset queue and no email deliverability problem, which for a small operator is a whole category of work deleted. There is also no user table to breach, and no consent flow to maintain. Those are not marketing points; they are the reason a one-person project can keep a daily game running for years.
The cost is that some player somewhere will want their streak on a second device, and the answer will be no. That is a legitimate limitation and it should be stated plainly rather than discovered. A design that says what it does not do is more trustworthy than one that quietly omits features.
There is a second benefit that is easy to miss: without an account, the daily puzzle cannot nag. No email series, no reactivation prompt, no push notification. The game has to be worth returning to on its own, which is a healthy constraint on the design.
The test of the choice is the first visit: how long from clicking a link to the first accepted word? On a no-account design it should be seconds. Open the practice page on a device that has never seen the site and measure it. That number is the feature.