Privacy and data
How LineupSnap handles the information needed to run the coaching service and launch waitlist.
Last updated August 14, 2026
Waitlist and account information: email address; bounded acquisition-attribution details associated with a waitlist reservation or confirmed account; coach display name; authentication records; profile details; invitation status; and the messages needed to confirm or support an account.
Team and player information: team and season details; player names, jersey numbers, skill and position preferences, participation and attendance; games, lineups, fairness history, practices, notes, and files or exports a coach chooses to create.
AI-assisted content: files submitted to Magic Import, Coach Ted conversations, generated practice plans, and relevant team, season, or player context used to answer a coach's request. LineupSnap may store conversations and permit limited review by authorized people for safety, support, evaluation, and product-quality improvement. LineupSnap also keeps pseudonymous usage and cost telemetry to enforce allowances, detect abuse, evaluate reliability, and operate the service. Pseudonymous identifier fields do not make message content anonymous; chat content can still identify coaches, teams, or players.
Technical and usage information: browser and device details, IP-derived rate-limit information, page and feature usage, diagnostics, errors, and security events. Billing information may also be handled if paid checkout is enabled.
General and lineup Coach Ted conversations are private to the coach who created them under the product's access controls. Practice-planning conversations are part of the team's practice workspace and may be visible to other authorized team members.
LineupSnap does not currently use Coach Ted conversations to train or fine-tune a model. A future training program would require a separate decision, updated disclosure, retention and access controls, consent design, and an opt-out.
On public landing and sign-up pages, LineupSnap can keep one session-only first-touch record containing standard bounded UTM campaign values, the LineupSnap landing path, the referring site's origin, and the optional analytics-consent state. The record does not include an ad click identifier, email address, IP address, user-agent string, or a separate visit or session identifier.
If you create and confirm an account, those bounded fields are attached to a service-only account-attribution record. Referring-page paths, queries, fragments, and credentials are discarded. Duplicate confirmations do not overwrite the original acquisition record.
LineupSnap uses this information to authenticate coaches, manage teams and permissions, build rosters and lineups, calculate and display playing-time information, support practice planning and imports, send requested service or launch messages, prevent abuse, diagnose failures, support coaches, and improve product reliability.
Accounts are intended to be operated by adult coaches and other adult team organizers, not by children. Coaches decide which player information to enter and should use only what is needed for team operations. Do not enter player health or medical information, dates of birth, parent or guardian contact details, or unrelated sensitive information.
LineupSnap does not intentionally send player names, roster information, lineup data, or information about children to Meta for advertising measurement. AI-assisted features are different: when a coach chooses those features, relevant uploads, messages, and team context may be sent to a configured AI processor as described below. Coach Ted may include player names and team or season statistics automatically when that context is relevant to the request.
LineupSnap uses Supabase for authentication and application data, Vercel for hosting and aggregate web analytics, PostHog for consent-gated product analytics, and Resend for account, invitation, and waitlist email. Configured AI processors handle Magic Import and Coach Ted requests. These requests may include coach messages and relevant team, player, season, lineup, practice, or file context needed to produce the requested result.
Sentry may receive diagnostic and error information when error reporting is enabled. Upstash may process technical identifiers for rate limiting when that service is configured. Stripe may process account and payment information if paid checkout is enabled. Meta receives public-page measurement events only after the visitor grants the optional consent described below.
PostHog receives privacy-protected page views, a stable account identifier, and selected product milestones only after the visitor grants analytics consent. Milestones can include account confirmation, team or game creation, roster readiness, lineup generation, saving or export, and practice-plan generation or finalization. Event properties use opaque record keys and broad roster-size ranges; they do not include names, email addresses, team names, roster contents, or coaching notes. LineupSnap disables PostHog session recording, automatic interaction capture, heatmaps, performance capture, and browser error capture. Dynamic route identifiers, query strings, fragments, page text, and element attributes are not included in page-view events.
LineupSnap may show a consent-gated product survey after selected milestones. Survey responses are optional and are stored with the consenting account's product analytics. Do not include player information or other sensitive team details in an open-text response.
When you submit the public waitlist form, LineupSnap stores standard, bounded UTM campaign values, the LineupSnap landing path, the referring site's origin, and whether optional analytics consent was granted at that time. Referring-page paths, queries, fragments, ad click identifiers, IP addresses, and user-agent strings are not added to the waitlist attribution record.
This information is attached to the waitlist reservation only after you submit it. LineupSnap does not create a separate public-visit identifier or add attribution storage in your browser for this reporting path. Launch reports are available only through a service-only aggregate query that excludes email addresses, signup IDs, and exact signup times.
With your permission, LineupSnap uses Meta Pixel on public marketing, privacy, sign-in, and registration pages. Meta may use cookies or similar technologies to record page views and selected actions, such as joining the launch waitlist, starting registration, or confirming a new account. A sign-up email request is labeled StartRegistration; it is not counted as CompleteRegistration. This helps us measure advertising results and improve campaign targeting.
Meta Pixel is suspended on authenticated team-management pages. We do not intentionally send player names, roster information, lineup data, or information about children to Meta.
You can allow or decline PostHog and Meta Pixel from the analytics notice. Meta Pixel remains limited to public pages; PostHog can record privacy-protected page views, selected product milestones, and optional survey responses throughout the product after consent. After choosing, use the Privacy choices control in the lower left corner to change your selection. You can also manage interest-based advertising through Meta ad preferences and the Digital Advertising Alliance opt-out tool.
Coaches can correct much of their profile and team information in the product. LineupSnap does not currently offer one-click account deletion. Contact us to request access, correction, or deletion, and we will review the request and explain the available action. Team roles and other obligations may affect what can be changed or removed.
Waitlist emails include a private Email Preferences link. Use it to stop future promotional launch updates associated with that waitlist signup. Essential service or account messages are handled separately, and submitting the same waitlist email again does not silently restart promotional updates.
Account and team information remains stored while the account or team exists. Waitlist email addresses remain stored while the launch reservation and related updates are managed. A minimal suppression record may remain so a promotional opt-out continues to be honored. A coach can delete visible general or lineup Coach Ted chat history, which removes that conversation and its messages. Separate pseudonymous usage, cost, and transcript telemetry is not automatically deleted with the visible history and may remain for allowance enforcement, quality evaluation, product review, security, and support. Practice-planning chats remain part of the team's practice records. Technical logs, security records, and backups may also remain for product operation, review, security, and recovery. LineupSnap has not yet published fixed retention periods for these categories. Contact us to request review of retained data.
LineupSnap uses authentication, permission checks, access controls, and other safeguards represented in the product to protect information. No online service can guarantee complete security.
Questions or data requests can be sent to info@lineupsnap.com. See the Beta Terms of Use for the responsibilities that apply during beta.