ClueSprint privacy notice
Open web beta · Version 2.14 · Effective 20 November 2026
In short
- You don’t need an account. If you choose Save progress, you can sign in with Google so your results follow you to other devices; we keep only a keyed code for that Google account, never your email address or name. We don’t ask for your name or an advertising ID. The game asks for your email address only if you turn on the daily email.
- Anyone can play; there is no invite. If you email us, we receive that email. The list from the earlier invite-only beta is deleted on 6 December 2026.
- There are no ads or purchases. You can choose whether to allow visit analytics on the game homepage and About page, and interaction recordings on the About page. Google sign-in in the game is separate and remains optional.
- We don’t sell your data or share it for advertising.
- You can delete your data from inside the game at any time.
Who we are
ClueSprint (cluesprintgame.com) runs this service (“we”, “us”) and decides how and why your data is used.
For any privacy question or request, write to support@cluesprintgame.com.
What we collect, and why
Earlier invites. Until 6 November 2026 the beta was invite-only. If you were invited, we sent you a personal invite link by email, and opening it saved two cookies in your browser (__Host-cw_invite, holding the invite code, and cw_invited, holding no code). The game is now open to everyone, so these cookies no longer let anyone in or change what you see; they are not read for anything and expire on their own. We keep the earlier list of invite codes and, separately, which code we sent to which email address, only until 6 December 2026, so that we can answer questions from earlier invitees, and then delete it.
A guest key instead of an account. The first time the game connects, your browser creates a key. Its private part never leaves your browser. We keep the public part and a random player number that we create, and use them to recognise your browser when it reconnects.
Sign in with Google (optional). In Game settings or under your Daily result you can choose Save progress and sign in with Google. When you open the game, your browser may also offer to continue with Google (Google’s “One Tap”, shown by your browser). Closing it sends us nothing; Google and your browser decide when to offer it again. After you sign this device out, or choose to keep this device’s results, the game doesn’t offer it on this device for 30 days. Google then tells us an identifier for your Google account and, with it, your email address, name and profile picture. We use only the identifier: we turn it into a keyed code with a secret key that never leaves our server, store that code with your player number, and discard everything else, including the email address, name and picture. When you sign in with the same Google account on another device, the code lets us connect that device to the same player number, so your results, statistics and streak are there. If that device already has results of its own, it asks you which to keep: choosing your saved progress deletes that device’s guest results (as “Delete my data” would for that guest); keeping them changes nothing. To make each sign-in usable only once and only by your browser, we also keep a one-use code for each sign-in until it expires (10 minutes) and a short-lived permission (5 minutes) when a device joins your saved progress. Sign out here removes only the device you use; your progress stays saved and other devices are not affected.
Your games. For each puzzle you play, we keep the letters you enter and clear, your submissions, the times the puzzle started and ended, how it ended and how many letter hints you used. This record is your result. We also keep whether you have seen or skipped the tutorial, and a last-seen time updated at most once a day when a connection ticket is issued. If we correct a puzzle or a result we recorded wrongly, we keep a record of how it was handled. Daily Tiles is a second daily puzzle. For it we also keep the tiles dealt to you, the tiles you place or swap, and a number that fixes the deal for that day's puzzle. Where the Archive is offered, you can replay an ended Daily. For a replay we keep the same record as for any puzzle, plus which Daily it came from and that it was a replay. A replay does not count toward your statistics or streak. Where Pass & play is offered, two people take turns on one device; both games are saved as your games, whoever was playing, and we keep nothing that identifies the second player.
Beginner course. The games in Learn and the lessons you complete are kept with your player record, so you can continue where you left off. We keep replies to requests to start a lesson with your game record so we can safely retry them. Your browser keeps an unconfirmed start in IndexedDB until the game receives a reply. Delete my data removes the browser record and clears your course records through the deletion process below.
Word Pix (when enabled). When you play Word Pix, we keep the letters you enter, your submissions, elapsed time, puzzle progress and request receipts with your player record. The receipts let us retry requests safely and are kept with your Word Pix game record. Your browser uses IndexedDB to keep a move while it is waiting for confirmation, so you can resume if the connection drops. Delete my data removes the Word Pix browser record and clears the server records through the deletion process below.
Reporting a puzzle problem. Where it is offered, you can report a problem with a puzzle from its result, or from a closed Daily on the home screen. You choose a category and, if you like, a clue. We keep your choice, which puzzle and version it is about, when we received it and whether we have dealt with it. It is stored with your player number so that the same problem counts once and we can limit reports to 20 a day. You can’t add text or screenshots. The people who review reports see counts for each puzzle, not who sent them.
Your statistics. We work out your statistics and streak from your own game records and show them only to you.
Your achievements. If achievements are available to you, we work them out from your own game records each time you open them and show them only to you. We don't store them separately. They earn nothing and aren't ranked.
Your daily goal. If a daily goal is available to you, we work it out from your own game records each time you open it and show it only to you. We don't store it separately. It earns nothing and isn't ranked.
Daily email (optional). Where it is offered, you can turn on a daily email in Game settings. We then ask for your email address and send one email to confirm it; nothing else is sent unless you confirm. Once you confirm, we send one short email on each day a new Daily is ready, with a link to the game and a link to unsubscribe. We use your address only for these emails: no marketing, no other messages. We store it encrypted, linked to your player number. The emails are plain text with no images or tracking pixels, the link to the game is our public address with nothing added to it, and open and click tracking is switched off at our email provider, so we don’t know whether you open an email or click a link. The confirm and unsubscribe links contain a random code that works only for that purpose; like any page request, opening them appears in our web server’s request log. An address that is never confirmed is removed after 48 hours.
To stop the feature being used to flood someone’s inbox, and to send at most one email to an address each day, we also keep keyed hashes of the address — not the address itself. One limits sign-up attempts (counted with your player number) and confirmation emails, and is kept for up to about 2 days. The other records the day an email was sent, and is kept for 3 days. A keyed hash can’t be turned back into the address without our secret key, but the same address always gives the same hash, so these records are pseudonymous, not anonymous.
You can stop the emails at any time: use the unsubscribe link in any of them, turn the daily email off in Game settings, or delete your data. Each removes your address straight away; the short-lived keyed hashes above then expire on their own.
Your network address. We use it to limit excessive requests. It also appears in our web server’s request log, which we use to fix problems. It is never saved with your player number or your games. Your browser also sends standard technical details (such as its type and version) with each request; our server configuration does not record those headers.
Diagnostic code. Each time the game starts it makes a random diagnostic code. Our operational game log stores a keyed reference to it, next to related request records. If you share the code with us, we can derive that reference to find those records and help you. These references are pseudonymous, not anonymous; the web request log described above is separate.
Emails to us. If you email us, we receive your message and your email address, and use them only to answer you.
Operational monitoring. Our services keep aggregate counts, errors and timings, together with server instance labels, to detect failures. We do not send them to an outside monitoring service. We also check from our own computer that the public pages respond; those checks involve no player data.
On your device. Your browser keeps the key, a token for reconnecting, which tutorial tips you have seen and your game settings (Smart Advance, haptic feedback, sound effects, high contrast and, if you chose one, the language). The settings are never sent to us. Deleting your data also removes the language you chose; the other settings stay. After you finish a Daily, your browser keeps that day’s date and your time, so the game homepage can show it as soon as it opens; it is replaced by what our server says, never sent to us, and removed when you delete your data. If you sign this device out of Google or keep this device’s results, your browser also keeps the date until which the game won’t offer Google sign-in here; it is never sent to us. When you start a Daily Tiles game, your browser keeps a small record of it: your guest number, a hash of your installation and ids for that game and puzzle. While a move waits for our reply, the record also holds that move (ids of the tiles and squares, never the letters), so you can retry it after closing the page. The record stays after the game ends. It is replaced when you start another Daily Tiles game and removed when you delete your data or clear site data. If you play a theme pack or chapter, your browser also keeps the puzzle you last started until the game confirms it. Where it is offered, your browser also keeps the display names of the last five friends you played with and which game it was, so that you can invite them again; a name is kept only when our server sent one (see “Friend groups”), the list is never sent to us, and it is removed when you delete your data.
Sharing a result. Where it is offered, a Daily result has Share result. Your device makes the text: ClueSprint, Daily and the puzzle’s date, your total time and, if you used hints, how many. It ends with our public address, https://cluesprintgame.com/, the same for everyone with nothing added to it. It has no puzzle title or identifier, nothing about it is sent to us, and our service takes no part. You choose where it goes, and whatever you send it through handles it under its own terms. If your browser has no share sheet, the text is copied instead and stays on your device’s clipboard, which your device manages.
Inviting a friend (when enabled). Invite a friend makes one link that works for 7 days. When your friend opens it, our server decides what it opens: if you are waiting in an Arrow duel lobby at that moment, your friend joins that duel; otherwise your friend plays the same puzzle as a result you already have, and the two of you see each other’s completion time and number of hints, with the result decided by fewer hints first and then the shorter time. Anyone with the link, and the preview a chat app shows for it, can see the kind of puzzle and your time and hints; they never show your name, account or any identifier. Your ordinary game records follow their existing retention schedule.
The link opens the game and, on a new device, creates a guest identity. Pressing Play on the first screen records that your friend opened your invite and, for a comparison, that they take part; we show you how many friends have done so, not who they are. We keep the invite, who opened it, participation and comparisons until the link expires and the next cleanup pass. A revoked link no longer opens anything.
We also count, per day and without any link, player or device identifier, how many invites were made and opened, how many openers were new players, and roughly how long it took from the link to the game (in a few time bands).
Earlier challenge links (cluesprintgame.com/c/…) keep working as before: their public page does not load the game or create a guest identity, and Accept challenge inside the game records participation.
Friend groups (when enabled). You can start a private group or join one through a link from someone you know. While you are in a group, its other members can see the name you chose for that group (or “Friend” and a number if you chose none), whether you have finished today’s Daily Mini, and, once you have, your time, the number of hints you used and your place in the group for that day. They cannot see your account, email address, player number, device, your unfinished game or your results from other days or other games. Nobody outside the group can see it, and it never appears on public pages. Anyone who has the link can join, up to 20 people, so share it only with people you know. We keep which groups you are in, your number in each group, when you joined and the name you chose. We do not keep copies of the rankings: they are worked out from each member’s own game record every time the group page is opened.
If you play an Arrow duel or a cooperative puzzle with a friend who is in one of your friend groups, that friend also sees the name you chose for that group in the game, and their device may remember it as described under “On your device”. People who share no group with you never see it.
You can leave a group at any time on its page. Your name and place disappear from it immediately. When the last member leaves, the group and its link are deleted.
Deleting your data immediately stops your invite and challenge results from being shown and removes you from every friend group at once; physical cleanup follows the normal deletion process. Copies you or friends make through the system share sheet or clipboard are managed by your devices and the services you choose.
Where it comes from
We get your data from you and your browser while you play. Our service creates some of it, such as your player number and the times in your game records. If you were invited during the earlier invite-only beta, your invite email address is the one we were given for your invite. If you turn on the daily email, its address is the one you enter. We get sign-in information from Google if you choose to sign in. If you allow website analytics, the providers below make reports available to us. We do not get data from data brokers.
Arrow duels
You can choose a random opponent or invite one friend to share a crossword grid. We keep your waiting place, an expiring invitation and each player’s private tiles, moves, scores, turns and result. Your opponent sees the shared grid, scores, turn and result, but never your private tiles, name, email address or player number. There is no chat or public profile.
An invitation can be joined by one other player and expires after 30 minutes. A random search expires after 30 seconds without a heartbeat. A waiting match closes after 10 minutes if play has not started. Closed and finished matches are removed after 7 days and the next cleanup pass; request receipts used to prevent duplicate invitations are kept for up to 30 days. Access credentials expire after 15 minutes and are held only in memory on your device. Moves awaiting confirmation are kept in your browser until resolved or your data is deleted. Deleting your data hides and removes the related shared match through the normal deletion process.
When you are matched with a random player, each of you sees the other only under a random name made of an animal and a number (for example “Owl 48”). The name is chosen by our server for that match and kept for a rematch with the same player; it is not linked to your player number, your device or your other matches. A friend you invite sees you as “Friend”, or, if you are both in the same friend group, under the name you chose for that group.
Your opponent can see that you left a match before it started, and that you asked for a rematch. If you type an invitation code that does not work, we record that it failed, with your player number and the time, to limit guessing; these records are kept for up to 30 days. Your network address is counted in memory for the same purpose and not stored. To vary the puzzles and keep them fair for newer players, we look at which puzzles you and your opponent played, how many of those matches you each finished, and how hard those puzzles were, using only matches we still keep (finished matches are removed after 7 days). If either of you is new, both of you get an easier puzzle when one is available. We don’t store a skill rating or a difficulty level for you, and puzzle difficulty is not shown.
Cooperative puzzles
When you invite a friend to solve a puzzle, we keep the shared room, a hash of the invitation code, both player numbers, the letters you enter, and replies that let us retry moves and submissions. Your partner can see the shared grid, whether you are in the room, and the result with the total time. The room has no chat and does not show your name, email address or player number; if you and your partner are in the same friend group, your partner sees the name you chose for that group.
Anyone with your link can take the second place until it is claimed. A waiting invitation expires after 15 minutes, and an unfinished game is playable for up to 24 hours after the room was created. A short-lived access permission expires after 15 minutes and the game keeps it in memory. You choose who receives the link and which service you use to share it.
Deleting your data closes any active room you joined, clears its shared board, and removes your membership, move receipts and access permissions. A completed room can retain the puzzle and total time after your membership is removed.
Optional website analytics
We use optional analytics to count visits to the game homepage and understand how people use our About page. The tools load only if you allow them: choose Allow in the question at the bottom of the game homepage, or Allow analytics on the About page. On the game homepage, Google Analytics counts a page visit and, if you share or copy an invite link from that page, that this happened and which of the two you used. Clarity and Umami count the visit from a separate browser frame that cannot read the game or record your interactions with it. The tools do not load on invitation or challenge links, or on other pages.
- Google Analytics 4 (Google LLC) receives page views, the referring site if available, browser and device information, and a pseudonymous browser identifier. Google uses your network address at collection to determine approximate location. We disable advertising signals and enhanced measurement. Google Analytics and privacy.
- Microsoft Clarity (Microsoft Corporation) measures homepage and About page visits, and records how people interact with the About page, including clicks, scrolling and changes on screen. It can use a pseudonymous browser identifier and browser or device information. We deny advertising consent. Microsoft Privacy Statement.
- Umami Cloud (Umami Software, Inc.) receives page views and technical information such as the referring site, browser, device and approximate location. Its analytics tracker does not set cookies. Umami privacy policy.
We do not send player numbers, puzzle answers, game activity other than the invite event described above, account details, group names, or invite, challenge or group codes or links to these tools. The tools may process data outside your country, including in the United States.
Open Analytics preferences on the About page at any time and choose Decline analytics to withdraw your consent. In the game you can also open Settings and choose Stop visit analytics under About, which has the same effect; that entry is shown only while this browser has allowed analytics. Either way this stops future analytics in that browser and removes the analytics cookies we can clear on our domain. It does not erase data already received by the providers. Global Privacy Control also prevents analytics from loading.
Cookies and browser storage
We no longer set any cookie to let you in. Browsers of earlier invitees may still hold the two invite cookies described above, and some may hold an entry cookie named __Host-cw_friend from a friend challenge; none of them is used any more, and each expires on its own. Everything the game keeps in your browser is listed under “On your device”. When the game opens (unless this browser is already signed in or you recently said no here) and on the Save progress page, the game loads Google’s sign-in script from accounts.google.com. Loading it lets Google know that your browser opened ClueSprint, even if you don’t sign in; Google may use its own cookies or similar technology for the sign-in, under Google’s privacy policy. We receive only what is described above.
We store your choice in this browser until you change it or clear site storage. If you close the question at the bottom of the game homepage without choosing (the × button, the Escape key, or by tapping or clicking anywhere else on the page), your browser keeps a note named cw-landing-analytics-later-v1 in session storage only until you close that tab, so that we don’t ask again during the same visit. Closing the question is not consent, loads no analytics tool and is not sent to us; we ask again on your next visit. After you opt in, Google Analytics may use first-party cookies such as _ga and _ga_<ID>, and Clarity may use _clck and _clsk on the About page, to recognise a browser or connect visits. Umami uses no analytics cookies. The other public information pages do not load these tools.
How long we keep it
| What | How long |
|---|---|
| Player number, public key and your games | Until you delete your data, or an inactivity deletion starts after 730 days (about 24 months) since the recorded last-seen time |
| Stored replies that let the game safely repeat a request | Eligible for batch cleanup after 30 days; game replies require the puzzle to have ended and its last event also to be over 30 days old (tutorial replies: 30 days). Beginner course start replies and Word Pix replies follow the retention of their game records. |
| Puzzle reports | 180 days after we receive them, or 30 days after we close them, whichever comes first |
| One-time sign-in codes and connection tickets | About 1 day after they expire |
| Operational game log (keyed diagnostic references) | 14-day target; logs rotate daily, so removal can lag by a day |
| Web server and process logs, including network addresses in web requests | 14-day target; logs rotate in whole files, so removal can lag by a day |
| Database backups, including the off-host copy | 14-day target |
| Record that a deletion happened (date, former player number, how much was deleted) | In the database: 90 days after deletion finished; in the separate deletion ledger: 30-day target, cleaned up by hand during the beta |
| Local browser deletion-protection records (linkable key/guest hashes and random generation markers) | No automatic expiry; until you clear site data or the browser clears it |
| Google Analytics event and user data | Subject to our property’s data retention setting; Google applies different rules to aggregate reports. Retention details. |
| Microsoft Clarity | Microsoft retains recordings for 30 days and heatmap or click data for up to 9 months. Retention details. |
| Umami Cloud | Subject to the retention period for our Umami Cloud plan. Retention details. |
| Earlier invite cookies in your browser (no longer set or used) | Up to 90 days after they were set |
| Invite and challenge links, who opened an invite, participation and comparison references | 7 days, then the next bounded cleanup pass; game results follow the game-record retention above |
| Daily invite counts (no link, player or device identifier) | No fixed limit; they cannot be linked to a person |
| Friend group membership and the name you chose for a group | Until you leave the group or delete your data; the group itself until its last member leaves |
| Earlier friend entry cookie (no longer set or used) | Until the original challenge expiry, at most 7 days |
| Arrow duel matches (closed or finished), with their moves and results | 7 days, then the next cleanup pass |
| Cooperative room membership and move receipts | Kept with your player record until its deletion. The invitation and the ability to keep playing have the shorter limits above. |
| Cooperative access permissions | Usable for 15 minutes. Expired records are removed when you next sign in to Coop or delete your data. |
| Records of invitation codes that did not work (player number and time) | 30 days |
| Daily email address (stored encrypted) | Until you unsubscribe, turn the daily email off or delete your data; an unconfirmed address 48 hours |
| Keyed hash of a daily email address, used to limit sign-ups and confirmation emails | Up to about 2 days (48 hours, then the next cleanup pass) |
| Record of the day a daily email was sent (keyed hash of the address and the date) | 3 days |
| Confirmation and daily emails, and their delivery logs, held by our email provider, Resend | Under Resend’s own retention terms; deleting your data in the game does not reach them |
| Earlier invite list (codes and email addresses) | Until 6 December 2026 |
| Emails you send us | Until 30 days after the beta ends |
| Google account link (keyed code and player number) | Until you delete your data, or an inactivity deletion starts after 730 days |
| One-use sign-in codes | About 1 hour after they expire (10 minutes after they are issued) |
| Permissions for a device to join your saved progress | About 1 hour after they expire (5 minutes after they are issued) |
Deleting your data
Open Game settings → Delete my data on the home screen. Your browser proves it holds the key, and then:
- your guest identity is revoked immediately and cannot obtain another connection ticket or make further game changes; existing connections are closed when the service detects revocation;
- we delete your player number, key and every puzzle you played, including one in progress, and your tutorial progress, within 30 days;
- your daily email subscription, its address and your record of sign-up attempts are deleted straight away; the keyed hashes that limit confirmation emails and allow at most one email a day stay until they expire (about 2 and 3 days), because removing them early would let those limits be reset;
- any puzzle report you sent stays until the period above ends, but without your player number or the time of day it arrived;
- backups follow the 14-day target above, and our outer limit is 35 days after game-data deletion (up to 30 + 35 days from the request). If we restore a backup, we replay deletion records before the service reopens;
- the link to your Google account is removed straight away, and every device signed in to it becomes a new guest;
- your browser deletes its key, reconnect token, tutorial tips, any local Social history and its encryption keys, any list of recent friends, any stored Daily Tiles record and any unconfirmed theme pack or chapter start; your game settings stay.
The browser retains local deletion-protection records, even if you have never used Social features. These include hashes derived from the public key and guest identity, and random generation markers. They can be linked to an identity and are not anonymous. This deletion-protection mechanism does not upload them. They have no automatic expiry and remain until you clear site data or the browser clears it. They prevent late writes only from builds that recognise these records; they cannot protect against every older build. Clearing site data also removes this local protection. These retained records contain no history content, answers, scores or encryption keys.
Afterwards your browser starts again as a new guest. Other browsers and devices that were not signed in to the same Google account are separate guests and are not affected.
If you clear your browser’s site data, the key is gone and nobody — including us — can tell which guest was yours. An automatic deletion starts once that guest has been inactive for 730 days (about 24 months), according to the recorded last-seen time; data removal then follows the deletion process above. A daily email subscription keeps working until you use the unsubscribe link in any of its emails or that guest is deleted. You can email us to request deletion of invite-list data even if you have lost the key. We cannot use that email to identify the unlinked guest game records.
Deleting a guest in the game does not itself remove the separate invite list, invite cookies or emails you sent us. Their retention periods are listed above; write to us for requests about them.
Who handles your data, and where
Our server and its database run at Alibaba Cloud in the United States (Virginia). Our website and our game connections pass through Cloudflare, which handles your network address and encrypted traffic on its global network. Our off-host backup copy is kept on a computer we control. Emails to us are received through Cloudflare Email Routing and kept in a Google Gmail mailbox; invite emails were sent from that mailbox. Daily emails are sent through Resend (Plus Five Five, Inc.), from its sending region in Tokyo, Japan (Amazon Web Services ap-northeast-1). Resend handles your email address and each email we send only to deliver it for us, and keeps its own delivery logs under its terms. This means your email address may be processed outside the country where you live, including in Japan; Resend handles it under its data processing terms with us. If you are outside the United States, your data is transferred there to run the game. Google LLC (or Google Ireland Limited in the EEA and UK) provides the sign-in under its own terms and privacy policy. Because its script loads when the game opens, it may learn that your browser opened ClueSprint; if you sign in, it learns that you signed in to ClueSprint.
The optional analytics providers are listed above. Microsoft processes Clarity data under its own privacy statement.
We don’t sell your data or share it for targeted advertising. Shared games and results are visible to other players only as described for each feature above. Puzzle reports are private. Apart from the providers above, we would disclose data only where the law requires it.
Legal basis
Where a law requires one, we rely on these reasons:
- playing and keeping your results: providing the game you asked to play;
- puzzle reports: our legitimate interest in correcting puzzles;
- Sign in with Google and keeping your progress across devices: providing the feature you asked for;
- deletion and its record: meeting your request, and our legitimate interest in being able to show it was done;
- security and limits on excessive requests: our legitimate interest in keeping the service working and safe;
- solving problems and answering you: our legitimate interest in fixing faults and helping you;
- the earlier invite list: our legitimate interest in closing the invite-only beta properly and answering earlier invitees, until it is deleted;
- daily email: your consent, which you give by confirming your address from the confirmation email and can withdraw at any time by unsubscribing, turning it off in Game settings or deleting your data;
- optional website analytics and recordings: your consent, which you can withdraw in Analytics preferences on the About page or with Stop visit analytics in the game’s Settings.
Automated decisions
The service applies some checks automatically: it checks your answers, and it applies fixed limits, such as on excessive requests or 20 puzzle reports a day. We don’t make decisions about you with legal or similarly significant effects by automated means, and we don’t build a profile of you.
Your rights
Depending on where you live, you may have the right to access, correct or delete your data, to restrict or object to how we use it, to receive a copy of it, and to complain to the data protection authority where you live. To use these rights, write to us at support@cluesprintgame.com; we aim to answer within one month. You can delete your data in the game at any time, as described above.
If you have not signed in with Google, we can reach your game records only through your guest key, in the game. If you have, we can also reach them when you sign in with that Google account in the game. We don’t look them up from an email request, even if you gave us that address for the daily email. To stop the daily email, you don’t need the game: use the unsubscribe link in any of the emails. For requests about invite data or emails you sent us, we may ask for details to confirm the request is yours.
US state privacy laws. We don’t sell your personal information, don’t share it for targeted (cross-context behavioural) advertising and don’t use it for profiling. We honour Global Privacy Control for the optional website analytics. Using your rights doesn’t change how the game works for you.
Children
ClueSprint is meant for people aged 16 or older. If you think someone under 16 is playing, write to us: we will delete any invite details we hold for them. Their game data can be deleted in the game; otherwise it is deleted after the inactivity period above.
Security
The beta uses encrypted public game connections, and the connection between our server and its database is also encrypted. The server’s internal services accept connections only from the server itself. Your private key never leaves your browser. Daily email addresses are stored encrypted, with the encryption key kept outside the database. The Google account link is stored only as a keyed code; the key is kept outside the database. The operational game log uses keyed references for request identifiers; the web request log also contains network addresses. No system is perfectly secure.
If a security incident affects your data, we will notify the authorities and the people affected where the law requires it. Because you can play without an account and we don’t keep the email address of a Google sign-in, we may only be able to reach you through this page (or, for an earlier invitee, their invite email address).
Not in this beta
Public rankings, ads and purchases are not part of this beta. Your time is compared with other players only in the friend features described above. If we add any of them, we will update this notice first.
Changes
We will post any change here, with a new version and date, before it takes effect.