Last updated: 8 November 2026
LinkPrint is a daily guessing game built from Wikipedia. This page says, in plain words, what information the game handles, where it lives, and how long it stays. The short version: no accounts, no cookies, no adverts, no trackers from other companies, and we never sell data — there is almost no data here to sell.
The game keeps your record in your own browser's local storage, in entries whose names start with lp_:
Clearing your browser's site data deletes all of this. We can't delete it for you, because we never had a copy.
When a game finishes or is abandoned, the game sends one small summary: the date, the mode (Daily or Custom), whether the game was finished, and — for each round — the clue stage it was solved at, or that it wasn't solved. A score bucket is worked out from those clue stages on our side.
That is the whole message. It carries no name, no account, no device ID, no guesses, and nothing that identifies you — and the server is built to refuse anything extra: a message containing any field beyond the list above is rejected outright (error 422), not quietly stored. These summaries are kept only as running totals — how many games finished, how rounds were solved — which is how we balance difficulty and work out the "better than X% of today's players" comparison. We cannot pick your game out of them, because there is no "your game" in them to pick out.
Playing solo, your score stays on your device (above). If you play as part of a cohort — a small group sharing a 6-character code — your finished run is submitted so the cohort board can exist. A submission contains:
The total on the board is recomputed by our server from the round trace — the total your browser claims is ignored. Submissions also feed two aggregate counts: the score histogram behind the percentile comparison (completed runs only) and per-round solve statistics we use to spot broken or leaked sets.
Cohorts themselves are stored as: the code, an optional cohort name, the display names of members and when they joined, and board entries (name, date, total, when submitted). Display names exist only inside cohorts. Anyone who holds the cohort code can see the names on that cohort's boards and member list — including members who have joined but haven't finished today. Boards are never public, never listed, and our API marks every response "do not index." Treat the code like an invitation: share it with the people you mean to play with.
Please don't use your real name — or anyone else's — as a display name. The game suggests generated names (like "Swift Otter") for exactly this reason.
To stop automated abuse, our server keeps a short-lived counter for requests. The counter is labelled with a one-way hash made from your IP address, the date, and a fixed public label — your raw IP address itself is never written to our database, and the counters are deleted within about two days. This is a counting device, not a profile: it cannot be used to follow you, and it holds nothing about how you played.
The site and the API are hosted by Cloudflare (Cloudflare Pages for the site, Cloudflare Workers and its D1 database for the API), which processes connection data — such as your IP address — to deliver and protect the service, the way any host does. In our own database, we store only what this page describes.
| What | Kept for |
|---|---|
| Score submissions, board entries, score histograms, per-round statistics | 90 days, then deleted by a nightly cleanup |
| Cohorts and their member lists | The cohort expires 90 days after it is created; expired cohorts and their members are deleted by the same nightly cleanup |
| Anonymous telemetry counters | Up to 400 days, as dated totals only — they contain no individual records |
| Rate-limit counters | About 2 days |
| Anything in your browser's local storage | Until you clear it — it's yours |
If a display name in a cohort impersonates someone, is profane, or shouldn't be there, report it through the contact route below and we will remove it — from the member list, the boards, and the stored submission. Say which cohort code, which name, and roughly when, so we can find the right entry. The same route covers any other privacy question about a submission.
If what we collect ever changes, this page changes first or at the same time, with a new date at the top. Per-player data of any new kind would be a bigger change than a page edit, and we would say so plainly, here and in the Updates log.
LinkPrint is a small project, run in the open by a small team. There are two reasons people usually land here:
Report a display name. If a name in a cohort impersonates someone, is profane, or shouldn't be there, we will remove it — from the member list, the boards, and the stored score. To report one, we need three things: the cohort code, the exact display name, and the date it appeared. Send them via the channel below. You don't need an account, and you don't need to give your own name.
Everything else — a privacy question, a score that looks wrong, a bug, an idea: the same route, with whatever detail you have. A cohort code and a date help us more than anything else you could include.
The route, honestly: LinkPrint does not have a support inbox yet. The project's public home is its builder's GitHub profile — github.com/derksen-sam — where the project's public pages and updates live. A monitored support address is planned furniture, not present furniture, and we'd rather say that here than print an address nobody reads.
If the name you are reporting is your own real name, say so in the report — those are removed first, no questions about the rest.
For a name report, the Privacy-relevant details are the cohort code and the exact display name — nothing else is needed.
Case note, in our register: the file on you is nearly empty, and that's the design, not an oversight.
Privacy · Terms · Contact
Data: Wikipedia / Wikimedia (CC BY-SA) · LinkPrint is not affiliated with Wikimedia.