Scorebook — Privacy

Scorebook runs on a league backend, so some data lives on the league's server. Here is what, and who can see it.

Last reviewed: 2 September 2026

At a glance

• Sign-in is by email one-time code: you enter your email, receive a 6-digit code, and enter it. There are no passwords. Your session stays on the phone until you sign out.
• Stored on the league's server: leagues, seasons, teams, rosters (player names, and email and phone if a manager entered them), lineups, the play-by-play log of every game, and the stats derived from it.
• Every read requires a signed-in account. Other signed-in users of your league backend see roster names and stats; they cannot see your email, phone, or claim code.
• Scoring history is permanent and auditable: plays are never deleted, and each one records who entered it and when. Corrections are new entries.
• Photo scorecard import sends the photographed page and the team's roster names to a server-side transcription service (which uses the Anthropic API) so the handwriting can be read. The app does not keep the photo. The feature is optional and limited to managers, coaches, scorekeepers, and league staff.
• On the phone: your signed-in session and an outbox of plays not yet sent, which empties as they sync.
• Camera and photo library are used only to photograph paper scorebook pages.
• No analytics, crash-reporting, advertising, or tracking SDKs.
• Without a league backend the app runs in demo mode with fictional teams: no sign-in, no network.

Contact

Questions about privacy in Scorebook: monarchprimelabs@gmail.com