Back to login

Alpha policy draft

Privacy Policy

This page explains, in practical terms, what Chessparring currently collects and stores while the product is in alpha/beta. It should be reviewed before public launch.

Account data

  • Chessparring stores account identity information such as your email address so you can log in.
  • If you sign in with Google, Chessparring receives and stores the Google OAuth account data needed for login.
  • If you use email/password login, Chessparring stores a secure password hash, not your original password.

User chess content

Repertoires, openings, lines, and training data are stored so Chessparring can provide the training service.

Internal product analytics

Chessparring uses internal product analytics to understand alpha/beta usage and improve the product. This data is pseudonymous, not anonymous, because userId and clientSessionId can distinguish users and browser sessions internally.

Examples include pages visited, feature usage, and coarse outcomes.

Analytics events do not store PGN, FEN, SAN/UCI moves, full move lines, opening or line names, notes, comments, user text, raw URLs, query strings, emails, passwords, tokens, or secrets.

Retention

Raw internal product analytics events are retained for at most 12 months during alpha/beta. Retention should be revisited before broader public beta or launch.

External analytics

Chessparring does not currently use external analytics tools for this internal product analytics layer.

Policy status

This is an alpha/beta policy draft and practical product disclosure, not a final public-launch legal policy.