Privacy policy
Last updated: November 13, 2026
What we collect
When you sign in to bgladder, we store:
- Google account data: your name, email address and profile picture, from Google sign-in.
- Generated identifiers: a username and an internal user ID created when you sign up.
- Online game records: moves, dice rolls, results, clock settings and timestamps for the online games you play.
- Games saved to your account: engine and pass-and-play games you finish while signed in, and their engine reviews.
- Ratings and statistics: your match rating and its history, win and loss record, and performance rating (PR) from reviewed games.
- Puzzle progress: your first attempt at each puzzle (rated, except the daily puzzle on its day), your puzzle rating, your daily puzzle results (the daily streak is counted from them) and your best puzzle streak run.
- Saved analysis positions: positions and notes you save while signed in.
- Rollouts: the rollouts you start on the analysis board or in a game review: the position, the settings, the progress and the result, stored with your account.
- Subscription data: a Stripe customer ID and subscription status, only if you subscribed before bgladder became free.
Settings, and games or positions you haven't saved yet, are kept in your browser until they are saved to your account. Without an account, only the usage events and error reports described below are sent to us, plus your play when you check today's daily puzzle: it is checked and not stored. That result stays in your browser until you sign in, when it is saved to your account and removed from the browser. Before an account was required, your first answer to each puzzle (right or wrong) and your practice rating at the time were stored against a one-way, salted hash of your visitor ID (or of your IP address when there was none), so the same answer was counted only once. We no longer collect these, and the hash cannot be turned back into the ID or address.
Usage analytics
To learn which parts of the site help people and which don't, and to fix what breaks, we keep the usage data below. None of it uses cookies.
- Vercel Web Analytics counts page views and a few site events (for example "a game finished", with at most two details such as the game mode and the result). It is cookieless and its reports are aggregate: no account, name or email is attached. Addresses are sent without their query strings, and admin pages are not counted.
- Our own usage events record what you do on the site in broad strokes: a session starting (the page you landed on, the site that linked you here and any campaign tags in the link), a game starting and finishing (mode, engine level, match length, result), puzzle answers, analysis and review requests, rollouts started, finished or canceled, match imports, sign-ups and sign-ins. Each event carries a random visitor ID kept in your browser's local storage, a session ID that resets after 30 idle minutes, the page, your country (from our host's network data) and whether you are on a phone, tablet or desktop. When you are signed in, events are linked to your account.
- Error reports: when a page or the server fails, we store the error message, a shortened technical trace, the page, the browser type and, if you are signed in, your account. Never the content of your requests or any password or token.
We use these only to fix problems and decide what to build. Usage events and error reports are kept for up to 12 months and older ones are deleted automatically. Browsers with automation turned on and known search-engine bots are not tracked.
What we don't collect
- No IP address logging on our website: to stop abuse of the analysis engine, we count requests per visitor for a few minutes using a one-way, salted hash of your IP address, and those counters are deleted when they expire (the analysis engine's own server is the one exception, see Third-party services)
- No browser fingerprinting
- No advertising cookies or ad networks
- No third-party tracking scripts other than Vercel Web Analytics described above
- We never sell your data to anyone
Cookies and local storage
bgladder uses authentication cookies to keep you signed in and to protect the sign-in flow. Settings, device games, today's daily puzzle result before you sign in, saved positions and the random analytics visitor ID use your browser's local storage. Clearing your browser storage removes those device records and gives you a new visitor ID.
How we use your data
Your data is used only to run the service:
- Authentication: verifying who you are when you sign in.
- Gameplay: recording game state, moves and results.
- Matchmaking: pairing you with opponents of similar rating.
- Engine analysis: evaluating positions, grading moves and running rollouts.
- Shared match reviews: the review of a match file you upload opens for anyone you send its link to, signed in or not, with the player names and the result from the file. The reviews of games played here open only for their players.
- Shared rollout results: a finished rollout is shown to anyone who opens the same position, with its date and the engine version, but never your name, username or account. Starting the same rollout again returns the stored result instead of running it twice.
- Profiles and leaderboards: showing your display name, picture, ratings, game history and PR on your public profile and on the leaderboards.
- Improving the site: usage events and error reports, as described under Usage analytics.
Third-party services
- Google OAuth for sign-in.
- Stripe for managing subscriptions started before bgladder became free. New checkout is disabled. Stripe handles all payment details; we never see or store your card number.
- Neon for database hosting.
- Vercel for hosting the site and for Web Analytics.
- Cloudflare for the real-time online game server.
- Hetzner for hosting our analysis engine at engine.bgladder.com.
The analysis engine receives board positions and analysis settings. For live analysis and rollouts it also receives a one-way-hashed code for each visitor, so it can share its time fairly and run one rollout per player; the code cannot be turned back into your account. No names, emails, user IDs or other personal information are sent to it. When the analysis board streams live results or rollout progress, your browser connects to the engine directly, so the engine's web server sees your IP address, as any web server does. It may appear in that server's logs and is never linked to your account.
Online play
When you play online, your display name, picture, rating and moves are shared with your opponent in real time. Your email address is never shared with other players.
Data retention and deletion
You can delete your account at any time from your profile. When you do:
- Your profile, sign-in data, ratings, rating history, puzzle progress, saved positions and the engine and pass-and-play games on your account are permanently removed.
- An active subscription is canceled first.
- Online games are kept without your name or account, so your former opponents keep their history and ratings stay consistent.
- Finished rollouts you started are kept without your name or account, so the results stay available to every member who opens those positions.
- Usage events and error reports are unlinked from your account and deleted on the normal 12-month schedule.
Children
bgladder is not directed at children under 13. We do not knowingly collect personal information from children under 13.
Changes to this policy
We may update this policy from time to time. Material changes will be announced on the site. Continued use of bgladder after changes means you accept the updated policy.
Contact
Questions about this policy? Email legal@bgladder.com.