Cookies & storage

Storage essential to gameplay

The current code uses localStorage for the visual theme, to remember that the privacy notice was seen, for a short match-recovery journal, for an optional stories journal and, when you have chosen, for the analytics preference. IndexedDB stores matches, preferences, challenge and lesson progress, statistics, the collection, memories, stories and moments. The installable app (PWA) may also keep game assets in the browser cache for offline use. While a Reserve Entry tile is on the board, the match and the recovery journal are updated about once a second so the time left survives a reload; this creates no new cookies or keys and sends nothing to a server. These are not automatically advertising cookies. Clearing site data may remove offline progress and that cache.

Online room storage

Only when you create or join an online room: a random credential for your seat is kept in sessionStorage, mirrored in localStorage (key roll-n-roast:online-seat:v1: followed by the room code), so you can return to the same seat after a reload or a dropped connection. It is removed when you leave or the room closes, and credentials older than 24 hours are deleted. IndexedDB also keeps a small online-session record (room code, server address, seat identifier, match and phase, without the credential) to offer a way back to the room; it never replaces your saved offline match. This storage is strictly necessary for the service you asked for, is not used for tracking and therefore does not depend on consent. The multiplayer server sets no cookies.

Cloudflare Turnstile check

When bot verification is enabled, the Cloudflare Turnstile widget loads only on the Play Online screen when you create or join a room. It may use local storage or cookies on the challenges.cloudflare.com domain solely for the security check. It is strictly necessary for room security, is not used for advertising and never loads in offline play.

Turnstile privacy addendum

Optional cookies

The game can optionally integrate Google Analytics 4 and Ahrefs Web Analytics only when the operator configures them and you actively opt in. Google Analytics can use analytics cookies; Ahrefs states that its Web Analytics is cookie-free and does not store IP addresses with analytics data. Both vendors are blocked before consent, with equivalent accept/reject choices, separate vendor controls and consent withdrawal. When allowed, measured game events are only match start, finish or resume and challenge start, with mode and player count when applicable. Online room events and invite codes are not measured.

Hosting

The website’s web hosting (Hostinger) and the multiplayer VPS may use technical mechanisms necessary for communication and security, such as connection logs. The game adds no cookies of its own to those services.

Your choices

You can configure or clear local site data in your browser, including local storage, sessionStorage, IndexedDB and the app cache. Clearing a room credential stops this device from returning to that seat. Optional bot learning, rivalries and recorded moments have in-game controls. Lessons, challenges, statistics and looks are part of that local data. You can review analytics choices at any time from the game footer and these pages. Withdrawing consent prevents future optional requests; if a vendor was already loaded, the page reloads to stop its active runtime.