Privacy

Updated October 19, 2026. This policy covers Cutsies at cutsies.dev and www.cutsies.dev, operated by Isaac Audet. No account is required to play. The game is intended for a general audience.

Progress on your device

Progress, streaks, collection and settings are saved in browser storage. A random player identifier is also saved on your device. Clearing that storage removes local progress but does not delete server records. Recent unsent results may be stored locally for retry; expired retries are removed when the game checks its queue.

Results and leaderboards

The game sends completed results and gameplay samples to its server so players can compare results. Random result receipts prevent retries from being counted twice. Leaderboards store a persistent pseudonymous player identifier, a generated or chosen display name, scores and gameplay proofs used to check results. Names and scores appear on leaderboards, and leading runs’ proofs can be made available for playback. Please avoid using your real name if you prefer not to.

Shares

Sharing uses the destinations you choose on your device. When optional analytics are allowed, the website counts share and copy actions by day, mode, method and content type. Those aggregate counters do not identify a recipient. A successful share does not tell us whether a recipient opened a link.

DLE Club and optional sign-in

Cutsies is part of DLE Club and loads the club’s script from dleclub.com. The club uses a random player identifier, and your day’s result here can count toward its gauntlet. If you choose to sign in to the club, supported progress can sync across devices. Public club boards can display your chosen name and scores. See DLE Club’s privacy policy for its account, sign-in and syncing practices.

Hosting and abuse prevention

Vercel hosts the website and API; the configured server storage uses Neon. Hosting providers process network information such as IP addresses to serve requests. The application’s write-rate limiter stores a salted hash that changes daily rather than the address itself. Hosting logs and provider backups are separate from application database cleanup.

Website analytics and reliability

Optional Google Analytics counts visits, games started and finished, and shares. It keeps a first-party cookie with a random id to recognise a return visit. The game does not send your name or email to Google Analytics, and Google signals and ad personalisation are off for it. In Europe, including the UK, it starts only after you say yes; elsewhere it is on unless you turn it off. Global Privacy Control keeps these optional analytics off. You can change your choice in Stats.

The same choice controls Sentry crash reports and first-party activity measurement. Sentry reports exclude saved games, user details, request data and breadcrumbs. First-party activity records use the saved random player identifier, day, a broad source category and steps such as starting or finishing a day and sharing, to measure visits and returns. These records do not include your name, email or full referring URL. Game result and leaderboard requests operate independently of optional analytics.

Vercel Web Analytics separately counts page views, including the page, referring site, country, browser and kind of device. It uses no cookies or persistent browser identifier. See Vercel’s Web Analytics privacy information and Google’s Privacy Policy.

Playwire website advertising

We are preparing to use Playwire for website advertising. This disclosure applies to the website.

All or partial advertising on this Website or App is managed by Playwire LLC. If Playwire publisher advertising services are used, Playwire LLC may collect and use certain aggregated and anonymized data for advertising purposes. To learn more about the types of data collected, how data is used and your choices as a user, please visit https://www.playwire.com/privacy-policy.

Retention and requests

The server periodically cleans older daily results, samples and daily leaderboard runs using a 45-day cutoff. Cleanup is triggered by traffic, so this is not a guaranteed deletion deadline. Leaderboard cleanup also limits the scores kept per board and removes orphaned player records. First-party activity records use a 60-day retention window. Aggregate optional gameplay counters use a 90-day cutoff, retry receipts also have a seven-day cleanup path, and expired rate-limit counters are periodically cleaned after approximately two days. Some non-daily board records and aggregate share counts have no time-based deletion rule in the game code.

For help, privacy questions or deletion requests, contact support@dleclub.com. Include the game, display name, puzzle day and enough information to locate the relevant record. Aggregate counts cannot necessarily be attributed to a particular player. Clearing local data alone does not request server deletion.