At a glance
- We don't sell personal information, and we don't use it for advertising.
- The Service is offered to adults in leagues in the United States.
- Our apps contain no advertising, analytics or crash-reporting SDKs, and we don't track you across other companies' apps or sites.
- Card and bank details are entered on Stripe's pages and never reach us.
- AI game summaries send the AI provider game facts with player and team names replaced by codes. New leagues start with summaries on, naming teams only.
- A league can make itself members-only, so signed-out visitors can't see its game information.
- Team portal and Family & Friends accounts can be deleted by their owner without contacting support.
- We keep a record of when you confirm you're 18 or older and accept our Terms and this policy.
1. Who we are and what this covers
This policy covers the Softball-League website, league and tournament pages, the team portal, the administration tools, our APIs, and our iOS and Android apps, listed in the stores as "Softball League" (together, the "Service"). The Service is operated by SJSR Labs, LLC, a Massachusetts limited liability company ("SJSR Labs", "we", "us"). Contact details are at the end.
A participating league or tournament host ("League") controls the records it enters: rosters, schedules, registrations, eligibility, statistics, documents and media. League administrators decide who may use those records and what is public. SJSR Labs hosts and processes them on the League's behalf to provide the Service. A League's own privacy notice may add to this one.
2. Information we collect
| Category | Examples | Why we use it |
|---|---|---|
| Account and sign-in | Display name, username, email, password hash, roles, invitation status, passkey public credentials and device details, encrypted multi-factor secrets, recovery codes, one-time email codes and links | Signing in, account recovery, access control, invitations and service emails |
| Agreements and acknowledgements | When you confirm you're 18 or older and accept our Terms and this policy, or a League administrator accepts our League Agreement: which document and version, where (for example registration or a team invitation), your name and email, your title for the League Agreement, your browser, a coded (hashed) form of your IP address, and the time | Showing what was agreed and when, and meeting legal obligations |
| League, roster and participation | League and team memberships, roster name, position, batting side, jersey number, uniform size, eligibility, a league-configured gender classification, availability and lineups | Running teams, schedules, scorekeeping, lineup rules, eligibility and statistics |
| Registration | Name, email, phone, notes, team name, teammates you list, emergency contact, eligibility answers, answers to the League's own questions, uploaded files, and who accepted the League's waiver, medical release or other policy and when | Processing your registration for the League and keeping its records |
| Eligibility, safety and conduct | A League's requirements and the evidence recorded against them, such as medical release or background screening status; injury or safety reports, protests, discipline cases and player evaluations. We ask people not to enter Social Security numbers. | Letting a League check who may play and handle safety, conduct and team formation |
| Officials and workers | Directory details, roles, certifications, assignments, availability, reports and amounts owed | Scheduling officials and tracking offline payments |
| Messages and content | Team chat messages, attachments, reactions, read state, reports, support requests, and anything typed into free-form fields | Team communication, notifications, support, safety and moderation |
| Games and statistics | Schedules, attendance responses, lineups, plays, scores, pitch counts, statistics, league ranks, spray locations, awards, weather at the field, game summaries, and which scorekeeper recorded or handed off a game | Running games, publishing results, keeping league history and reporting |
| League documents | Public rulebooks and private waiver PDFs uploaded by a League administrator | Publishing league rules and keeping the League's waiver records |
| Payments | Fee charges, balances, invoices, receipts, payment and refund status, and Stripe identifiers. For a League's own Stripe account: its account ID and verification status. For our subscriptions: the Stripe customer and subscription IDs, plan, billing method, renewal date and invoice status. | Collecting League fees and our subscription fees. Stripe collects card and bank details on its own pages, and they never reach us. |
| Photos, video and audio | Overlay logos, live camera and microphone streams, server recordings, replays and highlight clips | Broadcasting games, League branding, replays and highlights |
| Connected services | For a League's YouTube channel: channel ID, title, handle, granted permissions, an encrypted refresh token, connection health and defaults | Delivering broadcasts and replays to the League's own channel |
| Family & Friends | The name you give yourself, your email, who invited you, the label a player gave the invite, a masked copy of an emailed invite address, the players you follow, your alert choices, and a record of alerts sent | Showing followed players' games and sending the updates you chose |
| Email sign-ups | Your address, the League and any team you chose, confirmation status and your email preferences | Sending the emails you asked for and honoring opt-outs |
| Device, session and security | Session and device identifiers, device name, push and Live Activity tokens, sign-in activity, IP address (hashed in the security log; as submitted on some forms, to limit abuse), security and delivery events, and sanitized broadcast connection diagnostics | Keeping you signed in, sending notifications, preventing abuse, protecting the Service and fixing failures |
| Website use and inquiries | Page views measured by our analytics (section 7), calendar feed requests, and what you send through contact, sales or player-pool forms | Answering inquiries, measuring reliability and improving the Service |
We get information from you, from League administrators, coaches and scorekeepers, from other authorized team members, from files or systems a League imports, and automatically when the Service needs to keep a secure session or deliver a feature you asked for.
We never see your password in readable form. Face ID, Touch ID and Android biometrics stay with your phone's operating system. We get only the passkey result.
3. How we use information
- To provide the Service: accounts, registration, League administration, documents, schedules, rosters, scorekeeping, statistics, team chat, notifications, Family & Friends, streaming, replays, highlights, tournaments, fees and payments.
- To check who may do what, enforce League and team permissions, and protect accounts and systems.
- To send the emails and notifications a feature needs or that you or your League turned on, such as invitations, receipts, game changes, recaps, registration and balance reminders, Player of the Week and next-season sign-ups.
- To bill Leagues and tournament hosts for their plans.
- To keep a record of who accepted our Terms, this policy and the League Agreement, and when.
- To keep League history and publish results the League has made public.
- To monitor reliability, investigate abuse and security problems, back up the Service, and meet legal obligations.
- When a League connects YouTube: to deliver its live games, replays and selected highlights to its own channel.
- When a League has AI summaries on: to write short recaps of finished games (below).
We don't sell personal information, and we don't use it for advertising.
AI game summaries
New Leagues start with AI summaries on, naming teams only. A League can turn them off or let them name players. When they're on:
- We send the AI provider game facts built from scoring data: innings, plays, and batting and pitching lines.
- Players and teams appear only as codes such as P1 and T1. Player names, team names, field names, notes and chat aren't sent.
- Batter strikeouts and fielding errors are left out of player lines.
- Our server puts the real names back when a checked summary is shown.
- A summary appears on the game page, labeled "AI summary", or "edited by the league" once a League changes it.
- Opting out: you can choose not to be named in your account's summary privacy setting. For a player without an account, a League administrator can set it. Summaries that named that player are hidden and rewritten.
- Provider: Anthropic writes the summaries. Anthropic doesn't keep the game facts we send (zero data retention) and doesn't train on them. If we use another provider, we'll require the same first. Each call record on our side keeps no game content and is deleted after 13 months.
4. Who can see information
- Public visitors: A League may publish schedules, teams, rosters, player names and profiles, statistics, league ranks, scores, awards, game summaries, broadcasts, replays and highlights. What's public depends on the League's settings.
- Members-only Leagues: A League can require sign-in. Signed-out visitors then can't see its games, statistics, highlights, replays, streams, embeds or calendar feeds, and it's left out of public directories. Its videos go only to its own YouTube channel.
- Team members: Active members see their team's chat, lineups, availability, roster and team reports. Team chat is never public.
- Coaches: A team's coach sees which of their players still have waivers, policies or eligibility forms to finish, by form title only, plus a count of players with no active registration. They don't see the answers or uploaded files.
- Family & Friends: If a League allows it, a player can invite people to follow them. Followers see that player's games and the alerts they choose: game start, final, hits and home runs, and a live game on the Lock Screen. They don't see contact details, chat, RSVPs, lineups or other followers. Only the inviting player sees a follower's name.
- League staff: Coaches, scorekeepers and League administrators see what they need for their role. Private waiver PDFs, chat reports and moderation history are limited to League administrators and the platform operator.
- What League staff don't see: saved registration drafts. For next-season sign-ups, administrators see only how many addresses are confirmed.
- People you contact: When you send an inquiry, player-pool request, invitation or message, its recipients see what they need to respond.
- Tournaments: When a host accepts a team into a tournament, the team's captain is invited to the team portal as a coach for that event.
- League integrations: A League can issue credentials to its own outside systems and export its data. Those credentials reach only the data the League selects.
5. Service providers and other disclosures
We share information only as needed for the purposes above, including with:
- Cloudflare: traffic passes through it. It also provides our DNS, inbound email routing and Web Analytics.
- Resend: sends our emails: invitations, sign-in codes, alerts, recaps and receipts.
- Stripe: processes League fee payments through each League's own Stripe account, and our subscription payments.
- Push notifications: Apple Push Notification service and Firebase Cloud Messaging, when you turn on notifications. A notification may show a team name, a message author and preview, or a followed player's first name and game update.
- Anthropic: receives the coded game facts described in section 3.
- Google Drive: stores our encrypted off-site backups. Our database, messaging, streaming and storage run on equipment we operate in the United States.
- Weather: to show the weather on a box score, we send a field's address to OpenStreetMap Nominatim and its coordinates to Open-Meteo. No account or player data is sent.
- Google and YouTube: when a League administrator connects a League-owned channel. An embedded YouTube player sends your playback request to YouTube. YouTube's terms and Google's Privacy Policy apply.
- Advisers and authorities: when reasonably needed to follow the law, protect people, investigate abuse, or keep the Service secure.
- Business transfers: a successor in a merger, financing, reorganization or sale, under this policy or after notice of materially different practices.
We don't send text messages. If a coach shares a team invitation by text, it goes from the coach's own phone, and we don't receive the phone number.
If you open a field address in a maps app, that provider's privacy policy applies.
6. The mobile apps
- No tracking SDKs: the apps contain no advertising, analytics or crash-reporting libraries.
- Camera and microphone: used only when you start a broadcast, record a game, or scan a scoring handoff code. A broadcast is sent to us only after you start it, and we may keep it as a recording, replay or highlights.
- Recording to your phone: a signed-in member can record a game their account lists. The app saves the recording to the phone's Photos or Gallery, or keeps it in the app. It isn't sent to us, and it stays until you delete it.
- Photos: you can choose an overlay logo with the system picker. It stays on the phone and may appear in your broadcast.
- Notifications: asked for when you turn on alerts, such as team chat or Family & Friends. On supported phones, a followed game can appear as a Live Activity or live notification. You can turn these off in the app or in phone settings.
- Passkeys and device security: your phone may use Face ID, Touch ID or Android biometrics. We get the passkey result only.
- Broadcast diagnostics: when you broadcast, the app may send a short connection log: game and session, platform, app and system versions, device model, network type, video profile, retry step, timing and a cleaned-up error. It never includes stream keys, passwords, media, contact details, advertising IDs or full device logs.
- Stored on your phone: your preferences, plus a sign-in session (not your password) in the iPhone Keychain or Android encrypted storage if you choose to stay signed in. A scorekeeper who downloads a game for offline scoring keeps that game's rosters and unsent plays on the phone until they sync, and a download stays usable for 24 hours. Leagues using "save plays on the phone first" also store the live game on the scorekeeper's phone while it's scored. Game data may stay on the phone after you sign out, so unsent plays aren't lost; deleting the app removes it.
8. How long we keep information
We keep information only as long as it's reasonably needed for the purposes in this policy.
- Sessions: expire, and end when you sign out, remove a saved device, or change your security details.
- Team chat: deleted when the team's conversation ends, after playoffs or when the season becomes inactive. Unsent attachments are removed after 24 hours, and files on a deleted message after 30 days. Chat reports are deleted with the reported message or the reporting account.
- Registration drafts: if you choose "Save and finish later", we keep what you typed and email you a private link. A draft is deleted 14 days after you last saved it, or sooner if you clear it or submit. Uploaded files and medical consent aren't saved in drafts, and League staff can't see drafts.
- Registrations: unconfirmed submissions and their files are removed after the seven-day confirmation window, and unclaimed uploads after 24 hours. Confirmed registrations and accepted policies stay as League records.
- Next-season sign-ups: an address is deleted 30 days after its last confirmation email if it isn't confirmed, and as soon as you unsubscribe.
- Game alerts and team Email updates: an unconfirmed sign-up is deleted after 30 days. If you unsubscribe, the address is deleted 30 days later, keeping only what's needed to honor your opt-out.
- League emails: an opt-out is kept so it keeps working. Delivery results stay with the email campaign.
- Family & Friends: link invitations expire after 14 days, and code invitations after 48 hours. An account that never finishes signing up is removed after 48 hours.
- Account deletion: deleting a team portal or Family & Friends account immediately removes that account's messages, reactions, read state, RSVPs, sessions, devices and lineup notes. Attachment files go in a sweep within the hour.
- Agreements and acknowledgements: kept after an account or League is deleted, for as long as we may need to show what was agreed and when.
- Game results and statistics: stay as League history unless an authorized administrator corrects or removes them.
- League documents: private waiver PDFs stay until a League administrator removes them. Rulebooks stay until replaced.
- Recordings and highlights: server recordings and highlight files stay until a League administrator deletes them, or until an enabled League setting retires a local highlight after its YouTube copy is confirmed. Videos on a League's YouTube channel follow that channel's controls. Disconnecting the channel doesn't delete them.
- YouTube connection: stays until an administrator disconnects it or Google revokes it.
- AI summaries: call records are deleted after 13 months.
- Security and delivery records: security events, email and alert delivery records, and calendar feed requests are deleted after 13 months. IP addresses on contact, sales and player-pool forms are removed after 90 days. Broadcast diagnostics are deleted after 30 days. Completed scheduled-job records are deleted after 90 days.
- Backups: local database backups are deleted after 30 days. Encrypted off-site backups, which also hold uploads and recordings, are kept for about 12 months. Information deleted from the Service can remain in a backup until that backup is removed.
We may keep information longer when the law requires it, to resolve a dispute, to protect the Service or people, to enforce an agreement, or to keep a legitimate League record.
9. Your choices and requests
Depending on where you live, you may have rights to see, correct, get a copy of, restrict, object to the use of, or delete personal information about you.
- Emails: optional emails have a link to manage or stop them. Your choices apply across the League. Some account and security emails can't be turned off.
- AI summaries: you can choose not to be named (section 3).
- Family & Friends: a follower can leave, and a player can pause or remove followers.
- Notifications and broadcasts: turn off notifications in the app or phone settings, stop a broadcast at any time, or sign out.
- Deleting your account: team portal and Family & Friends accounts can be deleted from the account deletion page (www.softball-league.com/team/delete-account), which the app links to. Players and coaches confirm with their password, and Family & Friends with an emailed code. League records such as rosters, staff assignments, documents, results, statistics and media are the League's and stay after your account is deleted. Administrator accounts are managed by their organization and deleted by the platform operator.
- Other requests: to see, export, correct or delete a League-managed record, email [email protected]. We may need to verify your identity and work with the League that controls the record. We aim to respond within 45 days, and we'll explain if a legal or record-keeping duty stops us from deleting something.
- Appeals: if we decline a request, you can ask us to reconsider by replying to our answer or emailing [email protected] with "Appeal" in the subject. We'll tell you the outcome, and how to contact your state attorney general if you're still unhappy.
- Selling, sharing and Global Privacy Control: we don't sell personal information or share it for targeted advertising, so there's nothing to opt out of. We treat a browser's Global Privacy Control signal as a request not to, all the same.
- YouTube: a League administrator can disconnect YouTube in the League's media settings. That deletes our stored credentials and asks Google to revoke access. Videos already on YouTube aren't deleted. You can also review access at https://myaccount.google.com/permissions.
We won't treat you differently for using these rights.
10. Security
Our measures include encrypted connections, hashed passwords and session tokens, role-based access, revocable sessions, passkeys, multi-factor sign-in for the platform operator, restricted administration tools, network isolation, security logging and encrypted off-site backups. YouTube tokens are encrypted with a dedicated key, tied to the League and channel, and never sent to a browser or phone. No system is perfectly secure, so please tell us promptly about any suspected account or privacy problem. If a security incident affects your personal information, we'll notify you and the authorities as the law requires.
11. Children
The Service is for adults. You must be 18 or older to create an account, register for a League program, or follow a player, and you confirm this when you sign up. Youth programs aren't offered, and Leagues may not register players under 18. The Service isn't directed to children under 13, and we don't knowingly collect their information. If you believe a child's information is on the Service, email [email protected] and we'll delete it.
12. Changes to this policy
We may update this policy when the Service, our providers or the law change. The current version stays at this address with its effective date. Before a change that materially affects how we use personal information takes effect, we'll show a notice on the website and email League administrators, at least 30 days ahead.
13. Contact
SJSR Labs, LLC (Softball-League)
45 Hopewell Farm Road, Natick, MA 01760
Privacy: [email protected]
Support: www.softball-league.com/support