Last updated: 9 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: accounts are optional and guest play is unchanged — nothing about playing requires an account; we set no cookies ourselves, show no adverts, use no trackers from other companies, and we never sell data.
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 the copy on your device for you, because we never had it — the only exception is a record you chose to import into an account, as section 5 describes, and that copy is erased when the account is deleted.
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.
One of these counters is a host-interest count on the Rooms landing page: it records only that a visitor tapped "I'm interested in hosting" — no name, no email address, and nothing about who tapped. There is no list behind it, and nobody can be contacted from it.
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). The names of individual players — display names — exist only inside cohorts and are never published: not on any board, not in any season, under any setting. 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. Cohort boards are never public, never listed, and our API marks every cohort response "do not index." Treat the code like an invitation: share it with the people you mean to play with.
The one exception is Seasons, and it covers a cohort's own name — never its members'. A cohort's creator may choose to make the cohort public for the Seasons competition. A public cohort's name — never its code, never a member's name — appears on the public seasons board with its team results: wins, standings, streaks and best team scores, counted only from finished runs. Only results from after the choice is made are ever displayed; nothing a cohort did while private is published, then or later. Joining a public cohort tells you it is public before you join. The creator can end the listing at any time — it comes down at the next nightly update, and at once if a name report against it is upheld. Past-season honours (a line in the Hall of Fame: the cohort's name, the season, its wins) stay listed unless the cohort asks us to remove them through the contact route, in which case we do. Seasons have not opened yet: the first season begins on a date announced here and in the Updates log, and no cohort can be listed — and nothing can be displayed — before that day.
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. Sign-in, if you use it, is run by WorkOS (through its AuthKit sign-in page), which processes your sign-in only, as section 5 describes. In our own database, we store only what this page describes.
You may play exactly as before without an account — guest play is unchanged, and nothing about playing requires one. If you choose to sign in, sign-in is run by WorkOS on its own sign-in page (AuthKit), using Google or an email magic link. There are no passwords anywhere — we never see or store one. Before you can sign in, you must confirm that you are 16 or older.
If you sign in, we store on our server:
Your history. A Daily you finish while signed in is attached to your account — the date, the set, your total, and whether it was completed or conceded — so your record can travel with you. At your first sign-in you may choose to import this device's existing local record into the account. That import is one explicit, consented step: nothing is uploaded without your tap. Guests' records never leave the device, exactly as above.
Premium. An account can be linked to the premium unlock. The unlock also still lives on its restore code, separately from any account.
Export. While signed in, you can download everything your account holds — your profile, your attached history, and your premium link state — as a file, from the "Your Record" screen.
Deleting an account erases the identity record, the attached history, and all sessions. The premium unlock survives by its restore code: it is the buyer's property, so deleting the account erases only the account's link to it — the entitlement itself is untouched.
Account data is kept while the account exists and erased on deletion; expired sessions and sign-in tickets are cleaned up by the nightly job. Your email address is your login address only — it is never a marketing list, and it is never sold or shared. WorkOS processes sign-in, and Cloudflare hosts the service, as described above; nobody else receives it from us.
| 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 |
| Cohort records (team counters only — wins, days fielded, streaks, best scores; no member names, no per-round traces) | Kept while the cohort lives and as its honours afterwards; reachable only with the cohort code; deleted on request |
| Public Seasons listings (a public cohort's name and team counters, as above) | Current season: while the cohort is public. Past seasons: as Hall of Fame honours until removal is requested |
| Anonymous telemetry counters | Up to 400 days, as dated totals only — they contain no individual records |
| Rate-limit counters | About 2 days |
| Account record and attached history (for signed-in players only) | While the account exists; erased on deletion |
| Sign-in sessions (stored as one-way hashes only) | 30 days |
| Sign-in tickets | Hours; expired tickets are cleaned up by the nightly job |
| Anything in your browser's local storage | Until you clear it — it's yours |
| Support email you send us | Kept in the team's support mailbox until it is deleted; there is no automatic expiry |
The support mailbox is a team mailbox held with Google. Mail to support@linkprint.gg is forwarded to it by Cloudflare's email routing. A thread is deleted when it is no longer needed to handle the matter, and you can ask us to delete your support thread at any time. The support queue is currently paused — see Contact below — so mail may sit unread; the retention facts here are unchanged by the pause.
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. When the Seasons board opens, it also covers public cohort names: report the cohort name exactly as displayed and the season — no cohort code is needed, because the board itself is the evidence — and an upheld report takes the listing down at once.
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 to the address below.
Everything else — a privacy question, a score that looks wrong, a bug, or an idea: the same address, with whatever detail you have. A cohort code and a date help us more than anything else you could include.
The route, honestly: LinkPrint's support address is support@linkprint.gg — mail sent there is delivered to the team's mailbox. But the support queue is not currently being read: the daily queue passes are paused while the project is pre-launch and the audience is small, so a message may sit unread for a long time, and we do not promise a reply. We would rather say that here than print an address and pretend someone is watching it. When the queue reopens, this page will say so.
If the name you are reporting is your own real name, say so in the report — when the queue is next worked, those are removed first, no questions about the rest.
When you email us, we receive your email address and the contents of your message. They are kept in the support mailbox and used only to handle that message. We do not add you to a marketing list or sell your information. Please do not send passwords, payment details, or other sensitive information that support does not need.
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.