Privacy Policy
Last updated · November 8, 2026
Who this policy covers
DugoutOps is used by two kinds of account holders: coaches, who run teams, score games, and livestream, and parents and followers, who follow a team, watch games, and access highlights. Only coaches, parents, and followers create accounts. A coach can also be a director or admin of an organization that runs several teams; see Organizations below.
Players are not account holders. Player information (name, jersey number, position, and game statistics) is entered by a coach or parent on the player’s behalf. See Children’s data below.
Information we collect
- Account information — your name, email address, and the teams you coach or follow. Created when you sign up.
- Game data — scores, lineups, play-by-play events, pitch counts, and statistics you enter while scoring a game.
- Player information — names, jersey numbers, positions, and stats you enter for the players on your roster.
- Video and media — livestreams, highlight clips, and reels you record or generate, processed and hosted by our video provider (Mux).
- Messages — the content of messages you send in team chat or in a direct message to a coach, a family, or another parent on a team you share, and who you sent them to. Used to deliver the conversation, to screen it automatically for slurs and sexually explicit content, and — when a message is reported or flagged — to let it be reviewed. A report from a team chat or a coach conversation goes to that team’s coaches. A report from a private chat between two parents goes to DugoutOps instead, because coaches can’t see those chats: our staff read the reported message and the three messages before it, and nothing else in the chat. The automatic screening happens on our servers as the message is sent; it is not sent to any third party, and it is not used to profile you or to target anything at you.
- Photos in chat — photos you post in a team chat or a private chat. Location and other camera details are removed on your phone before a photo is sent, and again on our servers. Photos are kept in private storage and shown only to the people in that chat, through links that expire; a photo that is removed or reported stops showing at once. Anyone in the chat can save a photo to their own phone. A saved copy is theirs, and we can’t remove it from their phone.
- Push notification token — if you enable notifications, a device token so we can alert you to game events. You can revoke this anytime in your device settings.
- Your phone’s calendar — if you turn on “Add Schedule to My Calendar” in the app, it asks for access to your phone’s calendar and writes your teams’ games and practices there, then updates or removes those events when the schedule changes. The app only changes the events it added. It reads your list of calendars so you can pick one, and never reads, uploads or shares your other events. Which calendar you picked and which events it added are kept on your phone, not on our servers; we only store that the feature is on, so we can tell your phone when the schedule changes. Turning it off removes the events it added. You can also revoke calendar access anytime in your device settings.
- Payment information — if you purchase a subscription or à la carte content, payment is handled by Stripe (web) or Apple / Google in-app purchase (mobile). We never see or store your full card number.
- Device and usage data — basic technical information (device type, app version, error logs) needed to operate and improve the Service.
How we use information
- Provide the Service — score games, stream video, generate highlights, track stats.
- Send transactional messages (welcome email, game digests, account notices) via our email provider, Resend.
- Process subscriptions and purchases through Stripe and the app stores.
- Keep the Service secure, prevent abuse, and debug problems.
- Improve features based on aggregate, non-identifying usage.
We do not sell your personal information, and we do not use player data for advertising.
Children's data (COPPA)
DugoutOps is intended for use by adults — coaches, parents, and other followers. We do not knowingly allow anyone under 13 to create an account or provide personal information directly to us.
Players on a roster are frequently minors, but they do not create accounts and do not provide information to us themselves. A coach or parent enters a player’s name, position, and game statistics in their capacity as the team’s operator or the child’s guardian. If you are a coach or parent entering a player’s information, you confirm you have the authority to do so.
A parent or guardian can set up a view-only player login on their child’s phone, with a one-time code from their own account. The player does not create an account and gives us nothing: no name, email address or password. The phone keeps a key that we store only in scrambled form, with the phone’s model name (so the parent can tell their child’s phones apart) and when it was last opened. On that phone the player sees only their own statistics, schedule and the clips their family’s plan covers; there is no chat and nothing to buy, we record no usage events, and crash reports are not tied to any account. Any of the player’s guardians can turn the login off at any time, and it stops working at once.
Video of a player is not shared publicly unless that player’s parent or guardian has told us it may be — see Sharing a player’s video publicly below, which also explains the one case that setting does not cover.
A team can also have a public page on our website. Those pages carry no player names, photos or statistics — see Public team pages below for exactly what appears and who controls it.
Some features send a player’s name, jersey number or statistics to an AI service to read, transcribe or summarize them — see AI-assisted features below for exactly which features and what is sent.
If you believe a child has provided us personal information directly, contact us at support@dugoutops.com and we will delete it.
Sharing a player's video publicly
Highlight clips and reels are visible inside a team by default — coaches, and the parents and followers of that team. Sharing one publicly is different: a public link can be posted to social media or forwarded to anyone.
We do not publicly share a clip of a player’s play unless that player’s parent or guardian has told us we may. The setting starts turned off. We ask when a parent or guardian links to their player, and a coach cannot answer on a family’s behalf — they can ask, but the decision is the family’s. It can be changed at any time in the app, and it applies to that child on every team they play for.
What that setting covers, and what it does not. A highlight is a record of a single play, and a play belongs to the player who made it — the batter on a hit, the pitcher on a strikeout, the runner on a stolen base. The setting governs clips where your player is that person.
It does not cover every clip your player happens to appear in. A teammate’s home run is that teammate’s highlight even if your player was on base and scored on it, and their family’s decision governs it. We think that is the honest arrangement — one play cannot be split between families, and these games are played in public, in front of spectators and parents filming from the stands. But we would rather state it plainly than leave you to discover it.
If a video featuring your child concerns you, whether or not they are the subject of it, email support@dugoutops.com or speak to the team’s coach. Team staff can remove any recording, clip, or reel directly, and we will act on a parent or guardian’s request.
Public team pages
Every team can have a page on our website at dugoutops.com/team/…, listed in a public directory and visible to anyone, including search engines.
What appears on it: the team name and organization, city and state, age group and sport, the schedule of upcoming games with dates and venues, opponents, final scores, and the season record.
What never appears on it: player names, photos, or statistics. These pages describe a team, not the children on it. A player’s name is not published here by any setting, at any tier, for any reason.
This starts turned on, and the coach controls it — not the family. We think that is the right allocation, because the page contains the team’s information rather than any child’s, and a schedule is the coach’s to publish in the way a roster is not. But we would rather say plainly who holds the switch than let a parent assume it is them. A coach can turn the page off at any time in Team Settings → Discovery. If you are a parent and the page concerns you, ask your coach, or email us and we will help.
Game schedules are ordinarily public already — on league sites, tournament brackets, and other scoring apps — and these games are played in front of spectators. That is why we publish this much and no more, and why we do not treat a schedule as private information while treating a name as one.
What turning it off can and cannot do. We stop serving the page immediately. We cannot remove a copy a search engine has already stored, and we will not pretend otherwise — those caches clear on their own schedule, and we will help you ask if you need us to.
Organizations
A team can belong to an organization, such as a club that runs several teams. A team joins only when its own head coach agrees. Parents are not asked, in the same way they are not asked before a coach adds an assistant. We would rather say that plainly than let a family assume otherwise.
What organization staff can see. The organization’s directors and admins see what that team’s coaches see: the roster, players’ names, jersey numbers and positions, schedules, statistics, recordings, clips and reels. They do not see a team’s chat, coach-to-family messages, or private chats between parents, unless they are also staff on that team.
Organization chat. An organization has two rooms of its own: one for its directors and admins, and one that also includes the head and assistant coaches of its teams. Messages there follow the same 90-day deletion and automatic filtering as team messages.
When a team leaves. The head coach can take the team out, or the organization can remove it. Organization staff lose access to that team immediately. The team’s data stays with the team.
Billing. An organization’s subscription is paid on our website through Stripe. We keep the organization’s plan, price per team, number of teams and payment status, but never a card number.
Third parties we share data with
We share only what each provider needs to deliver part of the Service. We do not sell data to anyone.
- Supabase — database, authentication, and file storage (where your account and game data live).
- Mux — livestream and video processing/hosting.
- Stripe — payment processing for web subscriptions.
- Apple & Google — in-app purchases and, if enabled, push notification delivery.
- Expo — mobile app infrastructure and push token handling.
- Resend — transactional email delivery.
- Google Analytics and Vercel Analytics — website traffic measurement. See “Analytics and cookies” below for exactly what these are and are not told.
- Anthropic — the AI service behind lineup-card scanning, voice scoring, game recaps, player summaries, lineup suggestions and bracket import. See “AI-assisted features” below.
- OpenAI — turns the audio of voice scoring into text. See “AI-assisted features” below.
- Sentry — crash and error reporting in the mobile apps, so we can find and fix bugs. It receives the error itself plus device and app version information.
We may also disclose information if required by law or to protect the rights, safety, and security of our users and the Service.
AI-assisted features
Some features use an AI service to read, transcribe or summarize information. Each sends only what that feature needs. Most run only when you use them; two run on their own, and are marked below.
- Lineup card scanning — the photo you take of a lineup card, which shows players’ names, jersey numbers and positions, is sent to Anthropic to read. You confirm the list before anything is saved.
- Voice scoring — the audio of what you say is sent to OpenAI to turn into text. That text, with your roster’s names and jersey numbers so it can tell which player you mean, is sent to Anthropic to work out the play. You confirm the play before it is recorded.
- Game recaps (automatic, when a game is marked final) — the names, jersey numbers and statistics of the players in that game are sent to Anthropic to write the recap.
- Player summaries (automatic, weekly) — a player’s name and season statistics are sent to Anthropic to write a short summary of their season.
- Lineup suggestions — your roster’s names, jersey numbers and season statistics are sent to Anthropic to suggest a batting order.
- Bracket import — the image of a tournament bracket you upload is sent to Anthropic to read the teams and games.
These providers process the data on our behalf to return the result. Under their terms for business customers, they do not use the data we send them to train their models. We do not send them your email address, payment information or team chat messages, and nothing they return is used to make decisions about you or a player.
Analytics and cookies
We measure website traffic on dugoutops.com using Google Analytics and Vercel Analytics, so we can see which pages people find useful. Google Analytics sets cookies on this website. Vercel Analytics does not.
We deliberately do not send Google the address of a page that identifies you or your player. Several links on this site — invitations, roster join codes, shared games and shared player pages — contain a private token in the web address, and some pages contain the identifier of one player’s video or career record. Before anything is reported, we replace those parts of the address with a placeholder. Google is told that “an invitation page was opened”, never which invitation. Anything after a ? or # in a web address is never sent at all.
We do not run advertising, we do not use advertising cookies, and we do not allow analytics data to be used to build advertising profiles. IP anonymisation is enabled. Analytics runs on the public website only — the mobile apps contain no analytics or advertising SDK.
Most browsers let you block or delete cookies in their settings, and Google publishes a browser add-on that opts you out of Google Analytics entirely. Blocking either will not affect your ability to use the Service.
Data retention
We keep account and game data for as long as your account is active. Video is treated differently: recordings, highlight clips, and reels are storage-intensive derivative artifacts, and how long we keep each one depends on the plan the team is on.
- Livestream recordings — kept for 7 days after the stream ends on the Free plan, 90 days on Team, and for as long as the team’s Pro plan stays active. A team’s plan here means the plan it gets, whether a coach or an organization pays for it.
- Highlight clips — kept for 30 days by default. This extends to 90 days if the team is on the Team plan, or if a player featured in the clip has a parent or guardian on a paid plan, and for as long as the team’s Pro plan stays active.
- Purchased clips and season recaps — kept for 18 months from the date of purchase, about a season and a half. You can download your copy at any time to keep it permanently.
- Season and game reels — kept for roughly 30 days from the date they are generated.
- Messages — kept for 90 days after they are sent, then deleted, on every plan. Deleted for real, not hidden. If a coach removes a message before then, its text is cleared at that point. A photo is deleted with its message, or sooner if it is removed or deleted, or if the person who sent it deletes their account.
A highlight clip is kept under whichever is more generous: the plan the team is on now, or the plan it was on when the clip was created. Changing to a lower plan does not shorten the window on clips you already have.
If a Pro subscription ends — because it is cancelled or a payment lapses — the team’s video is kept untouched for a further 90 days, so an interrupted subscription or an off-season gap does not cost anyone their archive. After that period, recordings and clips are kept for 90 days from when each was created, the same window as the Team plan. This is the one thing a Pro plan does not do forever: we do not keep children’s video indefinitely once nobody is using the service.
These windows describe how long we store the video. Deleting a game, a player, or your account removes the associated media sooner. Team staff can also remove any individual recording or clip directly, at any time. If you are a parent or guardian and want your child’s video removed, email support@dugoutops.com or ask the coach, and we will take it down. When you delete your account, we remove your personal information as described below.
Removing media stops us hosting and serving it. It cannot recover a copy that has already been downloaded to someone’s device.
Your rights and choices
- Access — you can view your account and game data in the app at any time.
- Deletion — you can delete your account and personal information at any time, either in the mobile app (Settings → Delete Account) or on the web at dugoutops.com/delete-account. No login is required for the web flow — we verify by email.
- Export — to request a copy of your data, email support@dugoutops.com.
- Messages from other parents — on unless you turn it off in the app under Message privacy. Off, you don’t appear in other parents’ list and no parent can message you privately. Coaches can always message you.
When you delete your account we remove your personal information (name, email, profile, push token) and your personal content. To avoid breaking shared records — for example, a game another coach also scored — we anonymize rather than delete your contribution to shared game history.
Messages you have sent are treated the same way: your name comes off them, but the text stays until its 90 days are up, because deleting it would remove one half of a conversation someone else is still having.
Security
We use industry-standard measures including encrypted connections and row-level access controls to protect your data. No system is perfectly secure, but we work to keep your information safe and to notify you of material incidents as required by law.
Changes to this policy
We may update this policy from time to time. When we do, we’ll revise the “Last updated” date above and, for material changes, notify account holders by email or in-app.
Contact us
Questions about this policy or your data? Email support@dugoutops.com or visit our contact page. DugoutOps is operated by Lumvre LLC.