The short version
- No accounts and no login. You never give us a name, an email, or a password to play.
- No ads, no behavioral advertising, no cross-site tracking, no tracking pixels, and no cookies set by us.
- Your saved game progress is kept in your own browser, on your own device.
- We use Vercel Web Analytics for page views and first-party aggregate counters for limited beta gameplay milestones.
- We don't sell, rent, or share player information, and we don't build player profiles or student profiles.
What's stored, and where
The Bill to Law Game saves your progress using your browser's local storage, a small amount of data kept on your device so you can close the tab and pick a run back up later. It holds the state of your bill and your current run. It is not transmitted to us or to anyone else, and we can't see it. Analytics counters do not include your saved run, bill name, run ID, or full bill text.
Because it lives in your browser, you're in control of it. You can wipe it any time by clearing site data for this site in your browser settings, or by starting a fresh run from the game's menu. Using a private/incognito window means nothing is kept after you close it. Saves are per-device and per-browser, so a run started on one device won't appear on another.
Analytics during beta
To understand whether the beta is working, we use Vercel Web Analytics for basic site metrics, such as pages viewed, referral source, country, browser, operating system, and device type. We do not use Vercel Custom Events.
For limited gameplay milestones, the game sends a same-site request to
our own /api/analytics/event endpoint. That endpoint
accepts only a small allowlist of milestone names and coarse gameplay
labels. The server immediately adds them to daily aggregate counters in
a private Neon Postgres database. It does not keep an individual event
record or the exact time of the event. The milestones are: when a run
starts, resumes, selects an issue category, reaches a stage, ends, or the
player leaves mid-run.
To avoid counting a refresh as another milestone, the browser keeps a limited list of milestones already reported for its saved runs. This list stays on your device and is removed when you clear this site's browser data. It is not sent with the counters. Exits include pauses and refreshes, so an exit does not necessarily mean someone quit. Reloading an active run also counts as a resume, not as another player.
The game milestone counters include only coarse labels: mode (Intro or Standard), stage, broad issue category, scope, difficulty, and final status. Internal QA runs may also be labeled as test traffic so they can be excluded from the main dashboard. These counters do not include names, emails, school names, student IDs, grades, assignments, free-text responses, bill names, run IDs, IP addresses, user agents, or full saved-game data. Because we do not store a player ID or run ID, "started but not finished" can only be estimated in aggregate by comparing starts and endings over a period.
Vercel says its Web Analytics stores anonymized data, does not use cookies, and identifies visitors with a generated hash that resets daily and cannot be used to track visitors between different days or websites. We use these page-view metrics and aggregate gameplay counters only to improve the product, not to contact players, advertise to players, or profile individual players.
Live gameplay counters are automatically deleted after 400 days, and counters marked as internal test traffic are deleted after 30 days. Deleted database records may remain briefly in provider backups used for disaster recovery before those backups expire.
Third-party requests
We keep the game and marketing site self-contained. Typefaces, images, and game assets are served from this site rather than loaded from ad or font providers. The page-view analytics script is handled by Vercel Web Analytics, the analytics service from our hosting provider. Gameplay milestone counters are handled by our first-party endpoint and stored as daily aggregate counts in a private Neon Postgres database. Players do not connect directly to Neon.
Hosting
The site is served by our hosting provider, Vercel, and the aggregate gameplay database is provided by Neon. As with any website, Vercel processes basic technical request data (for example, IP addresses) in server logs to deliver the site and protect it from abuse. We don't use that data to identify or build profiles of individual visitors.
Children and classrooms
The Bill to Law Game is built to be classroom-safe. There are no student accounts, no student profiles, no teacher dashboards, and no place to submit student names, emails, assignments, grades, or school records. Teachers and parents can use the game without creating student accounts, submitting student rosters, or uploading student work.
The game is designed for kids and adults, but the limited beta metrics described above are not used to contact children, advertise to children, or build profiles about children. If you believe a child has sent us personal information, contact us and we will delete it.
Feedback
For detailed beta feedback, we may ask parents, teachers, or adult players to contact us separately. Please do not send student names, student emails, grades, assignments, or other private student information.
Changes to this policy
If we change how the site handles data, we'll update this page and the "last updated" date above. Material changes will be reflected here before they take effect.
Contact
Questions about privacy? Email contact@billtolawgame.com.
Effective date: October 22, 2026.