Updated October 8, 2026

Privacy in the beta.

This page explains the current beta’s behaviour. Hearthside’s account and friends features have not been launched.

This website

The page does not add advertising trackers, analytics scripts, or newsletter forms. The hosting service processes requests to serve the site and may retain operational logs. The website and downloads are public; no sign-in is required to read the page or download the game. Downloads are served by GitHub, which processes those download requests under its own privacy policy.

Your study history

Study totals and recorded blocks are stored locally on your computer. They are not cloud-synced to an account. You can inspect a day and delete accidental study blocks in the game’s calendar.

Multiplayer rooms

Rooms exchange your chosen name, character, position, seat state, shared room changes, whiteboard strokes, and messages. A private message is delivered to its intended recipient through the room server; it is not end-to-end encrypted. Hosts and service operators may have access to server-side data. Public room lists show shared room details and population. Avoid putting private or sensitive information in your name, messages, or drawings.

Optional camera checks

Camera checks are off by default. When enabled, frames are processed locally on your Mac. Camera images and the camera check’s status are not sent to the multiplayer room server. The experimental detection can make mistakes; you can keep it disabled and still use study features.

Beta services

Internet rooms use hosting and relay services. The main-hall gateway uses incoming network addresses to limit connection abuse. It keeps short-lived, keyed network identifiers for rate limits; temporary network-ban enforcement lasts at most seven days. Expired keyed ban records may remain on disk until the next saved state or service restart. These identifiers are not shown to players. Raw addresses, invitation secrets, reconnect tokens and chat contents are not written to application access logs by the gateway. Hosting and relay providers may keep their own operational logs under their policies. Room membership and whiteboard data are held in memory and end when the room process stops. The operator can disconnect visitors and clear a board; halls are not watched continuously. There are no verified player accounts yet.

Questions and reports

Use the project issue tracker for general bugs and service problems. Reports there are public: do not include private invitations, personal information, or private chat transcripts. A dedicated private player-report channel is not available yet.

Related policies

GitHub privacy statement · Vercel privacy policy · Tailscale privacy policy