Dice Lock's daily puzzle gets a clock, a leaderboard, and honest privacy pagesDice Lock's daily puzzle gets a clock, a leaderboard, and honest privacy pages
September 15, 2026 · Dice Lock's daily puzzle now has a timer, a leaderboard, and a nickname you set once, while two privacy pages stopped making claims the site couldn't back up.A puzzle game's daily challenge now has a timer, a leaderboard, and asks your name once, while two privacy pages stopped stating things that weren't actually true.
The Daily puzzle now has a clock, a leaderboard, and a name to post under
Dice Lock's Daily used to be one tile at the bottom of the Puzzles screen, indistinguishable from the thirty fixed puzzles sitting above it, except that it expires. It now leads the page: a card with the scene, a streak line, and the puzzle's own date, in three states depending on whether you've started, solved, or not touched today's board. The thirty fixed puzzles moved one press deeper, into six world pages, unchanged.
Behind that card is a clock that starts on your first move rather than the moment the board loads, so lining the cursor up before pressing start buys nothing. It only counts time you're actually playing: a pause, a backgrounded tab, or a closed browser doesn't run it, and leaving mid-puzzle and coming back the same day resumes where it left off. Pressing Solve disqualifies the run for good, with a dash where the time would be, because anyone who's seen the answer has nothing to rank.
A finished time posts to a new server-side leaderboard, alongside a nickname you're asked for once, on your first clean solve. Posting doesn't prove you played fast, only that you had the actual board: the server checks a hash built from the puzzle's date, seed, and solution, which a script pulling the puzzle can compute just as well as a browser can, so what it rules out is a bot posting times for dates it's never loaded, not a bot posting a suspiciously fast one. Streaks are walked back through your dated history on every post rather than incremented, so a late post backfilling yesterday's board can't accidentally count as two days in a row.
The nickname is kept apart from the id Dice Lock already uses for play analytics, on purpose: posting under the analytics id would let a chosen name be joined to every event that browser has ever sent the game. Two ids, two databases, and neither leaderboard route returns the other one.
Two privacy pages stopped saying things that weren't true
jiolab.dev's policy claimed nothing collected here is used for analytics. That was false for the one project on the site with visitors who aren't its owner: the playable Dice Lock build at jiolab.dev/dicelock posts play events to dicelockgame.com. The policy now names what those events actually carry (a random browser id, a per-page-load id, a timestamp, mode, puzzle, duration, outcome) and what they don't: no IP, no user-agent, no referrer, nothing typed except a leaderboard nickname. Retention is split per project instead of one averaged sentence: Big Brain's logs as before, Dice Lock's raw events for 30 days and then daily counts.
Both jiolab.dev's and Dice Lock's privacy pages had carried a literal "[contact email]" placeholder, readable on the live site since August. It can't be filled in: every @jiolab.dev address is a catch-all forwarding into an inbox with no login, so publishing one would invite a reader to send an id request somewhere unread. Both pages now say plainly that there's no address yet and name the one thing a reader can do without one. For Dice Lock, that's a page that shows you your own stored ids so you can at least confirm what's there.
Dice Lock's own /privacy page is no longer hand-written HTML. It's built from a markdown file kept next to the analytics code, and a test compares the rendered page against the actual list of tracked events, the retention window, and every storage key the game writes. So a policy that drifts from the code now fails the test suite instead of quietly becoming a false promise on a published page. Building it caught three claims that were already wrong: the data isn't in a backed-up Postgres database, it's two SQLite files with no backup at all; it isn't kept indefinitely, raw events expire at 30 days; and deletion doesn't work by a visitor id the settings screen shows, because that screen has never shown one, and a posted Daily time is filed under a separate id entirely.
The daily puzzle now has a timer, a leaderboard, and asks your name once
Dice Lock, the puzzle game I'm building, gives everyone the same puzzle each day, the Daily. Until today it was just one tile at the bottom of the puzzles screen, no different to look at than the thirty practice puzzles above it, except that it disappears after the day it's for. It now leads the screen: a card with the day's artwork, your streak, and a note on whether you've started, solved, or not touched today's puzzle. The thirty practice puzzles moved one tap deeper, into six themed worlds.
Behind that card is a timer that starts on your first move, not the moment the puzzle appears, so staring before you touch anything costs nothing. It only counts time you're actually playing: pausing, switching tabs, or closing the game stops the clock, and coming back later the same day picks up where you left off. Pressing the button that shows you the answer marks that run unable to rank, with a dash where the time would go, because seeing the answer leaves nothing left to time.
A finished time now posts to a leaderboard the game's server keeps, along with a nickname it asks for once, the first time you solve a Daily without cheating. Posting doesn't prove you played fast, only that you had that day's puzzle: the server checks a code built from the date and its solution, which stops a program posting fake times for puzzles it never loaded, though it can't spot a player who already knew the moves. Your streak is recalculated from your full history each time you post, rather than adding one to a running count, so a late time posted for yesterday's puzzle can't count as two days in a row by accident.
The nickname is kept separate from the id the game already uses to count how people are playing. Attaching a chosen name to that id would link it to everything that browser has ever done in the game, so there are two ids in two places, and neither the leaderboard nor the streak list ever shows the other.
Two privacy pages stopped saying things that weren't true
This website's privacy policy claimed that nothing it collects is used for tracking. That was false for the one project here with visitors who aren't me: the playable copy of Dice Lock on this site sends play information back to the game's own website. The policy now spells out what that contains (a random browser id, a second id for that visit, a timestamp, mode, puzzle, how long you played, how it ended) and what it doesn't: no address identifying your device, no browser type, nothing typed except a leaderboard nickname. How long it's kept is now stated per project instead of one vague sentence: this site's own logs as before, Dice Lock's raw records for 30 days and then daily totals.
Both privacy pages had literally said "[contact email]" where an address belonged, visible since August. It can't be filled in: every address at this domain funnels into a shared inbox with no password on it, so publishing one would just point visitors somewhere anyone could read their message. Both pages now say plainly there's no working contact yet, and Dice Lock's page instead shows you something checkable: your own stored ids.
Dice Lock's privacy page is also no longer typed out by hand. It's generated from a plain text document kept next to the code that collects the data, and an automated check compares the finished page against the real list of things tracked, how long they're kept, and every piece of data stored in your browser. A disagreement now fails the check before it reaches a visitor. Building it caught three claims that were already wrong: the data isn't in a backed-up database, it's two plain files with no backup; it isn't kept forever, records expire after 30 days; and deleting your data doesn't work by an id the settings screen shows, because that screen has never shown one, and a posted Daily time is filed under a separate id anyway.