PlayNib

Cookie choices

Cookie policy

Last updated: 29 October 2026

This page explains how PlayNib uses cookies, localStorage, and similar browser storage. Core play works without accounts, so most saved game state stays on your own device.

Necessary browser storage

Necessary storage helps the site remember game progress, guest IDs, room participation, puzzle stats, streaks, quiz edit tokens, basic preferences, and—when Challenge Club is enabled—the last known Club challenge ID and visit time. This storage is needed for no-login play and is not used for advertising personalization.

You can clear this data in your browser settings, but doing so may remove local game progress, streaks, saved guest IDs, and no-login edit access to drafts.

If you voluntarily sign in to optional Challenge Club membership, PlayNib uses a secure HttpOnly session cookie and a short-lived CSRF protection cookie. A completed guest result may also use a short-lived HttpOnly claim cookie so that only the same browser can attach that one result after verification. These cookies are necessary for the account action, are not advertising consent, and are not required for guest game play.

The Club session lasts for up to seven days, the CSRF cookie for up to one hour, and the one-result claim cookie for up to 30 minutes. Logout, account deletion, successful claiming, and normal expiry end or clear these cookies as applicable. Clearing cookies may sign you out or prevent an unfinished guest result from being claimed, but it does not prevent ordinary guest play.

After Club account deletion, this browser stores a non-identifying deletion timestamp for up to 90 days. It contains no email address or account ID. It lets other open tabs sign out promptly and explains why the deleted email will not receive another sign-in code during the recreation hold. Clearing this browser marker does not remove the server-side hold.

Optional analytics cookies

PlayNib currently uses Google Analytics in production, but it loads only after a visitor accepts optional cookies. Visitors can reject optional cookies and continue to use core games. Analytics helps PlayNib understand page views and general site usage; it is disabled automatically if its deployment configuration is removed.

Optional event deduplication storage

After analytics consent, Daily Letter Hunt may keep up to 100 milestone markers in sessionStorage to avoid counting repeated starts, completions, or share outcomes in the same tab. These markers contain only a puzzle date, mode, word length, round number, and event category, not words or player identifiers. This storage ends when the browser tab session ends. If storage is blocked, the game still works and deduplication lasts only for the current page.

After analytics consent, Daily Trivia may separately keep up to 100 start or completion markers in sessionStorage. These contain only the puzzle version and date, daily or replay mode, difficulty, and event category, with no questions, answers, or player identifiers. They stay in the tab and are not sent to analytics. This storage also ends with the browser tab session; if blocked, the game still works and repeated events can only be prevented on the current page.

Curiosity game event markers

After analytics consent, Order Quest, Scale Sleuth, and Snakes and Ladders may keep up to 1,024 versioned play milestone markers in localStorage, used for up to 30 days; expired entries are pruned on the next consented marker write. They combine an existing game-run key with the game, mode, and event category; these local keys are not sent to analytics. Older compatible event markers are separately limited to 1,024 entries. No analytics marker is read or written before consent. A denied event is remembered only in page memory to prevent later backfill.

If storage is unavailable, duplicate prevention lasts only for the current page. Clearing storage, expiry, eviction, and simultaneous actions in different tabs can allow duplicates. These markers do not identify people or guarantee a unique count across browsers or devices.

Google advertising script and advertising choices

PlayNib can load Google's AdSense script separately from displaying an advertising placement. The script may be present while the site is being assessed. When Google's consent-management integration is enabled, the script can load before you make a choice in PlayNib's optional-cookie banner. Loading this script does not by itself mean that an ad has been displayed. Advertising placements must stay away from active gameplay controls.

Google and other third-party advertising vendors may use cookies or similar technologies to serve ads, measure ads, prevent fraud, and personalize ads where permitted. Visitors can reject optional cookies and still use core PlayNib features. Where Google requires a certified CMP, that CMP manages advertising consent separately from PlayNib's simple optional-cookie banner.

Before serving ads to visitors in the EEA, the UK, or Switzerland, PlayNib will use a Google-certified consent management platform where required by Google policy. Until that is configured, AdSense should remain disabled for those regions.

Consent management platforms

A consent management platform, or CMP, is a tool that asks visitors for legally required consent choices and passes those choices to advertising or analytics providers. PlayNib's simple cookie banner controls optional site cookies. Google AdSense Privacy & messaging, or another Google-certified CMP, should be used before serving ads in regions where Google requires certified consent handling.

Change your PlayNib choice

This button clears the optional-cookie choice saved by PlayNib in this browser and reloads the page. PlayNib's banner will appear again when configured. It does not reset Google's consent-management choices, remove other browser cookies or game progress, or undo information already sent.

Related pages

Read the privacy policy for more detail about data use and the terms of use for acceptable-use rules.