Youth League Software
Book a conversation

Youth League Software · Soccer, baseball, lacrosse, and more · Early access · 2026

Your team’s photos stay with your team — the privacy-first platform for youth sports leagues and club programs

Youth League Software is built around one promise: a player’s image, name, and record go nowhere without a guardian’s consent, and consent can be withdrawn and deleted at any time. Private rosters, consent-gated galleries locked to the team, professional team photos and team books assembled only from consented players, and the no-skim split engine for league fundraisers — all on one platform whose privacy rules are enforced at the engine layer, not by a policy document. Early access — no pricing commitment, no signup, no live payments today.

Book a conversation How it works
Private by defaultroster never public, gallery locked to the team, no search index
Consent-gatedunconsented player excluded at the engine layer — not cropped, excluded
Delete-on-requestlogged at intake, processed within a stated window, confirmed in writing
No-skim exact centfee off gross first, largest-remainder reconciliation, no platform margin inserted

The data pledge — four commitments, in writing, enforced by code

No data sales. No tracking. No secondary markets. Your data leaves with you.

Most team and league software makes money in two ways: the subscription fee you pay, and the data value of the players on your roster. The second revenue line is rarely disclosed. Roster data, player images, family contact information, and participation records have commercial value outside your league — to insurance vendors, recruiting platforms, equipment sponsors, and anyone building a database of youth sports participants. That is the secondary market. Youth League Software does not participate in it.

The data pledge has four parts. One: no minor player data is sold to or shared with outside companies, advertisers, or data brokers — not in anonymised form, not in aggregated form. Two: no location or behavioral tracking on minor players — the platform does not log GPS coordinates, movement patterns, or in-app behavioral signals against a minor’s identity. Three: no secondary markets for player images or family contact data — no partner integration that gives a third party independent commercial access to your roster. Four: your data leaves with you — one-click export includes every record the platform holds about your players and families, available at any time. These commitments are in the onboarding agreement, not a footnote.

Book a conversation Full platform

How it works

The league season in four stages — consent first at every step

Youth League Software runs on a consent-first season rhythm: roster import and guardian opt-in before the first practice, photo day with gallery delivery to consented families mid-season, fundraisers and team books running through the season, and a clean season-close with data export and deletion handling. Every stage is described as it is built today.

Step 1 · Before the season — roster import and consent collection

The league director imports the season roster from a spreadsheet or an existing export. Every player gets a consent record from day one: depiction consent (may appear in team photos and products), communications opt-in (guardian receives team messages), and data retention period. The default state for every flag is no consent until the guardian opts in. Guardians receive a consent request before the first practice, not a permissions checkbox buried in a registration form. The consent ledger is populated before the season opens — so when photo day arrives, the platform already knows exactly which players may appear in which products.

Step 2 · Photo day — scheduling, capture, and consent-gated proofing

Team photo day is scheduled through the platform’s picture-day workflow. Photo slots are assigned by team and age group; the schedule is published to guardians whose players are on the consented-communications list. After capture, images are uploaded against the roster: the gallery-build step runs consent checks player by player. A player whose guardian has not consented to depiction does not appear in any output — gallery, team book, or product. Proof galleries go live for consented families via private, revocable share links. No image is publicly accessible before guardian review. The checkout that accepts payment for prints is honest-off until the charge rail is enabled.

Step 3 · Mid-season — fundraisers, team books, and print orders

The split engine runs mid-season fundraisers. A league director configures the split: fee off gross first, then the net split to the league fund, a team account, or a proportional allocation. Families preview the exact-cent distribution before the charge rail runs. Team books are assembled from the roster: only players with active depiction consent appear in the book. Individual print packages and additional gallery products are available in the storefront to consented families. A guardian who changes their consent mid-season triggers an immediate ledger update; downstream products are updated to reflect the change before any new order ships.

Step 4 · Season close — data export, deletion requests, and year-over-year handoff

At season close the league director receives a full roster export: consent status per player, products purchased, fundraiser splits, communication opt-in status. The organisation owns this data. A guardian who submits a deletion request at any point during or after the season receives a written confirmation when the deletion is complete. The one-click export is available in writing: if the league ever leaves the platform, every record leaves with it — roster, consent ledger, product orders, fundraiser splits, and communication consent status. The next season opens on a clean import with prior consent status carried forward unless the guardian has withdrawn consent.

The full platform

Five engines — honest about what is built and what is coming

Every feature is labelled honestly: Built means the underlying engine is production-ready. In development means the surface, wire-up, or carrier integration is in active build. We do not claim otherwise.

Private roster and consent ledger — every player’s permissions, auditable

The roster is never public or searchable. Every player in the import carries a consent flag, a depiction flag, and a delete-on-request log. Guardians opt in; the default state is no consent. A player whose guardian has not opted in does not appear in any shared gallery or team product — not by cropping, not by blurring, but by exclusion at the engine layer. The consent ledger records who consented, when, and for what purpose. A guardian can withdraw consent at any time; the ledger records the withdrawal and downstream systems are notified. A deletion request is logged at intake and processed within a stated window; completion is confirmed back to the guardian in writing. The private roster import and consent/depiction ledger are built and production-ready.

Roster + consent ledger built · production-ready

Team photos, team books, and print fulfillment — professional-grade, privacy-first

Youth League Software is built by a company that operates the photography business. That is not a marketing claim; it is the reason the software and the photo service share a consent ledger rather than living in separate databases with a PDF export between them. Team photo day, team books, individual prints, and package orders are all consent-aware from the first shutter click. A team book is assembled only from players whose guardians have consented to the product; an unconsented player does not appear as a blank page or a silhouette, their record is simply not in the book. The branded parent storefront and order management layer are built and production-ready. The checkout interface that accepts payment from a family is honest-off: present in the platform, not enabled for live transactions today.

Storefront + order management built · checkout honest-off

League and club fundraising — the no-skim split engine, exact cent

The fundraising split engine divides gross proceeds with exact-cent precision. The fee is deducted from gross proceeds first, before any split is calculated, and splits are applied to the net remainder. Every party sums to exactly 10,000 basis points. A largest-remainder reconciliation pass ensures the total always equals exactly what came in, minus the fee, with no penny coerced into a platform margin. A league director sees the exact projected distribution before the charge rail runs — there is no platform skim between what a supporter contributes and what the program receives. A split can be configured to go to the league, to a specific team, or proportionally across teams. The split engine is built and production-ready. The charge rail that moves money is honest-off: present in the platform, not enabled for live fundraiser transactions today.

Split engine built · charge rail honest-off

Team and league communications — roster-based, guardian-approved

Messaging in a youth league runs through the guardian, not directly to the player. The platform’s communication layer routes team and league messages to the guardian on record for each player. No message reaches a guardian who has not opted in to communications from the organisation. Opt-in is consent-positive: the default is no message. A guardian can opt out of communications at any time. The communication channel infrastructure and templates are built on the platform. Carrier delivery — the SMS and email gateway integration that delivers messages — is early-access: the configuration layer is present, carrier delivery is not yet enabled for live use. Team and league subscription checkout is also early-access.

Channel infrastructure built · carrier delivery + subscription early-access

Who uses it

Built for league directors, club directors, coaches, and privacy-conscious parents

League and club directors

The league director owns the roster, the consent ledger, and the season schedule. They configure the consent flags at season open, run the picture-day scheduling, and manage the fundraiser split configuration. They are the data owner in the onboarding agreement: every record belongs to the league, not to the platform. At year-end they export the full season record and hand it to the incoming director, or carry it forward on the platform with prior consent status intact.

Head coaches

A coach accesses the team roster, the practice schedule, and the consent status of every player on their squad. They see which players have active depiction consent, so they know before a team photo day which players will appear in the team book. A coach does not have access to the full league roster or to family contact data beyond what the league director grants. Communications to families run through the platform’s guardian-routed channel, not through a personal phone number.

Privacy-conscious parents

A guardian sees their player’s consent record, the photos their player appears in, and the products available to their family. They do not see the roster as a whole or another family’s gallery. If they want their player’s images removed, they submit a deletion request: it is logged at intake, processed within a stated window, and confirmed in writing when complete. The platform does not ask them to accept that deletion may take an unspecified time or may be partial.

Why the photography business matters to the software

The consent ledger and the shutter click run on the same record — not two databases with an export between them

A software company that has never managed a picture day can describe consent workflows in general terms. A company that has run them encounters specific edge cases: the divorced household with two guardian records that conflict, the foster placement that changes three weeks into the season, the restraining order that means one guardian cannot see attendance records. The platform’s consent ledger was designed around those cases because they were encountered in the field running an actual photography operation, not derived from a design document.

The operational consequence is a single consent record shared between the software and the photo service. An image captured on picture day is tagged against the player’s roster record at capture. The consent ledger is checked at gallery build, at team book assembly, at every product step. An unconsented player does not appear in any output. A guardian who withdraws consent after picture day triggers an update across every downstream product that has not yet shipped. That is only possible when the software and the photo service share a ledger rather than exchanging consent data via a periodic CSV export.

Consent, deletion, and data ownership

Guardian-controlled. Delete-on-request. Confirmed in writing. Your data leaves with you.

Consent in this platform is not a checkbox in a registration form. It is a record with a guardian identity, a timestamp, a scope (depiction, communications, data retention), and a withdrawal history. A guardian can withdraw consent at any time. Withdrawal triggers an immediate update to the consent ledger and a notification to downstream systems. Products that have not yet shipped are updated before they go. Products that have shipped are noted in the deletion record.

A deletion request is logged at intake, not queued for a weekly batch job. Processing completes within a stated window. The guardian receives a written confirmation when deletion is complete. The platform does not accept a request and then provide no further communication. The league owns the consent ledger and can export it at any time. If the league leaves the platform, the full consent record leaves with it — including withdrawal history and deletion confirmations.

What is built and what is coming — plainly stated

The platform is built. The charge rail is not live yet.

Built and production-ready today: the private roster import and consent/depiction ledger per player; consent-gated private galleries mapped to the roster (unconsented player excluded at build time); the branded parent storefront substrate and order management layer; the no-skim fundraiser split engine (exact-cent, fee-off-gross-first, largest-remainder reconciliation); picture-day scheduling and workflow; delete-on-request logging and processing; and one-click data export.

Not yet enabled for live use: the payment rail (the part that moves money), the checkout interface that accepts payment from families for prints, team books, and packages, the charge rail for live fundraiser transactions, team and league subscription checkout, and SMS carrier delivery for communications. These are honest-off — present in the platform, not yet enabled for live transactions. There is no live checkout here. No billing. No subscription today. We say so directly because league directors deserve to know what is production-ready and what is still being wired.

Connected to the school platform

The league runs the season. Assembly captures the moment. Seen puts every player on the page.

Youth League Software manages the roster, the consent ledger, and the season. Assembly is the moment layer: live school and youth events captured, archived, and made accessible to consented families — the championship game, the tournament final, the closing ceremony. A league season event and an Assembly event are the same night; the consent record is shared. Seen is the recognition layer: the programme that ensures every student athlete appears on a real page in the yearbook, the sports programme, or the season record — adviser-approved and consent-verified. For school photography and year-round school photo operations, k12.photos is the professional school photography platform that runs on the same consent-ledger substrate.

assembly.school seen.school k12.photos homeroom.software

Early access · League directors, club directors, head coaches

Book a conversation to see the current state honestly

Youth League Software is in active development. We do conversations that show the current state honestly: how the consent ledger is structured and what a guardian sees when they opt in or withdraw, how the consent-gated gallery works and why an unconsented player is excluded not blurred, how the no-skim split engine models a fundraiser split to the league treasury, and what delete-on-request looks like at the guardian end. There is no pricing commitment and no signup. If it looks right for your league, we discuss what early access looks like.

To book: email [email protected].

FAQ

Common questions

What does “your team’s photos stay with your team” mean, exactly?

It means that no team photo, player image, or roster record is ever shared with another team, published to a public site, made searchable, or sold to a third party. A gallery is accessible only to families whose players have active depiction consent on record. The share link is private and revocable. An unconsented player does not appear in any gallery, product, or team book — not cropped, not blurred, excluded. A guardian can request deletion at any time; the platform logs the request and processes it within a stated window, confirming completion in writing. That is the whole promise in operational terms.

Is the photo storefront live? Can families order prints and team books yet?

Not yet. The consent-gated gallery, the branded parent storefront substrate, and the order management layer are built and production-ready. The checkout interface that accepts payment from a family is honest-off: present in the platform, not enabled for live transactions today. When the charge rail is enabled — a founder-gated decision — leagues and families will be notified. There is no live checkout, no billing, and no subscription right now. The CTA here is “book a conversation,” not “sign up and pay.”

How does the deletion request process work?

A guardian submits a deletion request through the platform. The request is logged at intake with a timestamp and the requesting guardian’s identity. The platform processes the deletion — removing the player’s images from galleries, removing the record from team products, and flagging the consent ledger entry as deleted — within a stated window. The guardian receives a written confirmation when deletion is complete. The window and the scope of deletion are published in plain language in the trust materials, not buried in a terms document. Deletion is not conditional on whether a product has already shipped; the platform tracks what has been sent and what has not.

What is the data pledge? What does “no secondary markets” mean?

The data pledge has four parts. One: no minor player data is sold to or shared with outside companies, advertisers, or data brokers — not in anonymised form, not in aggregated form, not as part of a platform sale. Two: no location or behavioral tracking on minors — the platform does not log GPS data, activity patterns, or in-app behavioral signals against a minor player’s identity. Three: no secondary markets — the platform does not pass player images, roster data, or family contact information to any marketplace, partner, or affiliated service for independent commercial use. Four: the league owns its data. If the league leaves, every record leaves with it via one-click export. These commitments are part of the onboarding agreement, not a footnote in a privacy policy.

Who can see the team roster?

The roster is private by default. It is accessible only to the league director, the head coach, and any administrator the league explicitly grants access. No roster is publicly accessible, indexable by search engines, or shared with other teams or leagues on the platform. A parent can see their own player’s record and consent status, not the roster as a whole. A minor player’s name, image, or record is never visible to another family — a family can query only their own player, never another’s.

Is the platform live? Can our league use it today?

The platform is in active development. The private roster import and consent ledger, the consent-gated gallery, the branded parent storefront substrate, the order management layer, the no-skim split engine, and the picture-day scheduling workflows are built and production-ready. The payment rail — the part that moves money — is honest-off: not enabled for live transactions today. Carrier delivery for communications and subscription checkout are early-access. A conversation is the honest next step: we show what is built, what the charge-rail timeline looks like, and what early access means for your league.

Why is the company that builds this software also in the photography business?

Because running a photography operation for youth programs is the fastest way to understand where the consent and privacy gaps actually are. A software company that has never managed a picture day can describe consent workflows in general terms; a company that has run hundreds of them has encountered every edge case — the divorced household with conflicting guardian records, the foster placement that changes mid-season, the restraining order that means one guardian cannot see which school events the player attends. The platform’s consent ledger reflects those operational realities because they were encountered in the field, not derived from a design document. There is no conflict of interest: the software and the photo service share a consent ledger rather than living in separate databases. The league and the family are served by the same consent record.

How does the no-skim fundraising engine work?

The split engine applies three rules in order: fee off gross first (the platform fee is deducted from gross proceeds before any split is calculated, so no party’s share is inflated at the expense of another); splits calculated on the net remainder (never on the gross, which would silently enlarge the platform’s share); and a largest-remainder reconciliation pass (any residual penny is assigned to the party with the largest fractional remainder, so the total always equals exactly what came in, minus the fee, with nothing coerced into a platform margin). A league director sees the exact projected distribution before the charge rail runs. The split engine is built and production-ready. The charge rail that moves money is honest-off.

What team books and print products are available?

The platform supports team photo books (every consented player on the roster, formatted as a printed team record), individual player prints in standard package sizes, and additional gallery products available to consented families through the branded parent storefront. A team book is assembled only from players whose guardians have consented to the product; an unconsented player does not appear as a placeholder or a blank page. Team books and print products are configured at the league or team level by the director. The order management and fulfillment layer is built. The checkout interface that accepts payment is honest-off until the charge rail is enabled.

How is this different from a general youth team management app?

A general team management app is built around the coach’s schedule and the parent communication board. Youth League Software is built around the consent ledger and the minor player’s data. The difference shows up in a specific operational scenario: when a season ends and a parent asks for their child’s photos to be deleted, a general app has no mechanism for that request and no record that it was made. The platform here logs the deletion request, processes it within a stated window, confirms completion in writing, and updates the consent ledger. That is the operational difference. The scheduling, communication, and photo-commerce features that a general app also has are present here — but they are built on top of the consent layer, not the other way around.

When is the payment rail enabled?

The payment rail — the part that enables live checkout for print orders, team books, and fundraiser transactions — is honest-off: present in the platform, not yet enabled for live use. There is no published date. The decision to enable the charge rail is founder-gated; leagues that have a conversation with us now are the ones who hear first when it opens. A conversation today shows the current state honestly and discusses what early access looks like for your league. The CTA is “book a conversation,” not a signup form.