1. The beta access cookie
| Name | Purpose | Lifetime | Properties |
|---|---|---|---|
__Host-hbl_beta | Remembers that this browser successfully entered the shared closed-beta code. The value is a random signed token with a version and expiry. It contains no name, email, player identity or copy of the beta code. | 30 days, or until you lock access or clear cookies. | HttpOnly, Secure, SameSite=Lax, Path=/, no Domain attribute. JavaScript cannot read it. |
This cookie is strictly necessary to provide the 30-day access you ask for. Without it, every protected game file would have to ask for the beta code again.
2. Local game storage
When you play, the game uses browser local storage to keep a world save, settings, key bindings, high scores and your chosen player name. This is not used to track you across sites. The data stays on the browser and device unless you choose online room play or send it to support.
Local game storage remains until you clear site data, use a game reset, or the browser removes it. This domain launch starts with fresh worlds; data from the old GitHub Pages origin cannot be read here. These storage operations are necessary for the save and preference features you request.
3. Public analytics
Cloudflare Web Analytics is not currently enabled, so no analytics beacon is included on these pages. If STOIC enables it later, this notice will remain the source of truth: the cookie-free beacon will run only on public marketing and legal pages, never inside /play/.
When enabled, the beacon measures public page paths and performance without storing or reading cookies, localStorage, sessionStorage, IndexedDB or an advertising identifier. Cloudflare says it discards the request IP address at the nearest data centre and does not use IP address or browser fingerprinting to follow a person across visits.
4. Why there is no consent banner
If the site later adds optional analytics, advertising, personalisation or another non-essential browser technology, STOIC will reassess this notice and add a real consent choice before that technology runs.
5. How to control or remove data
- Use Lock beta access in the site footer after unlocking to expire the access cookie immediately.
- Use browser settings to remove cookies or site data for hardblocklife.com. Removing all site data also deletes local game saves and settings.
- Blocking the strictly necessary cookie means protected game access cannot remain unlocked.
- Browser privacy tools may block the Cloudflare beacon when it is enabled; the public site and game gate still work.
Questions: support@hardblocklife.com.