Repository navigation
Steam: a privacy notice #150
Description
Part of #142 · Milestone 1: Clean to sell · plan item 1.7
Size: S · Owner-only step: yes
What
Selling the game makes GDPR apply. The web game collects (with Google sign-in): account id and display name, saves, scoreboard names, and reports (screenshots, save, device details, recent errors; kept 30 days), stored with Google Firebase. The Steam version collects nothing itself: saves go to Steam Cloud, scores to Steam leaderboards, and reports only reach us if the player posts or emails the report file.
Decision / recommendation
Claude drafts a one-page notice covering both versions, the owner checks it, it's published on the GitHub Pages site and linked from Settings and the store page. It says how to ask for deletion.
Done when
- Notice published and linked from both versions and the store page
Sources
Plan page (owner only): https://claude.ai/artifact/Cf5SWQHzAKTy2uHCC1UQgw
Activity
ChefControl commentedon Oct 27, 2026
The notice is in PR #211:
public/privacy.htmlon the Pages site, linked from Settings → About in every build, so the Steam build (#160) keeps the link. The store page link is added with the store page (#153): https://chefcontrol.github.io/floe-market/privacy.html, once #211 is merged. Keep this issue open until then.Privacy notice: the children section is only about data, not who may …
The privacy notice after the bundled fonts: a shield of the game's ow…
A privacy notice for the web game and the Steam version, linked from …
ChefControl commentedon Oct 28, 2026
To add before the Steam build ships (28 Oct, #170): the Steam build sends crashes, errors and player reports to Sentry. Reports carry the note, pictures and save. No name is sent, the IP address is dropped, and data is kept 30 days. Reports become issues in the private reports repo. There's an off switch in Settings for crashes and errors. Run
/legals-updateon that PR.