Privacy Policy
Effective date: [PLACEHOLDER — set on publication] · Last updated: [PLACEHOLDER]
DRAFT SCAFFOLD — this page is a structural placeholder. The final policy text will replace
every [PLACEHOLDER] and must resolve every blue/red NOTE before app-store submission.
Remove this banner when the real text lands.
Who we are
2Seam Labs LLC ("2Seam Labs", "we", "us") operates GameStat, a mobile application for
live-scoring amateur baseball games. Privacy questions:
privacy@2seamlabs.com
[PLACEHOLDER — confirm this address exists and is monitored; confirm LLC legal name and state of formation].
What information we collect
[PLACEHOLDER — to be provided]
NOTE for drafting — describe accurately, do not copy boilerplate:
Account data from OAuth sign-in via Google, Facebook, and Apple (name, email address,
profile photo URL — enumerate exactly what each provider sends us and what we store).
Team and game data entered by coaches/scorekeepers: team names, rosters, player names,
jersey numbers, positions, play-by-play events, statistics. Team logos/avatars (URL or
uploaded image). Optional livestream links (YouTube URLs we embed — we do not capture video).
Payment status via Stripe (see Payments note below). Crash and performance data via Sentry.
How we collect it
[PLACEHOLDER — to be provided]
NOTE: Three channels to cover: (1) directly from the user at sign-in
(OAuth) and in-app forms; (2) entered about other people by coaches, scorekeepers,
and team staff — player profiles are typically created by an adult, not by the player;
(3) automatically — crash reports, device/OS info, request logs (IP addresses in server logs).
State whether any analytics SDK beyond crash reporting is present (as of scaffolding: Sentry
only, no ad/analytics SDK — verify before publishing).
How we use it
[PLACEHOLDER — to be provided]
How we share it
[PLACEHOLDER — to be provided]
NOTE — third parties actually in use (verify list at publication):
Amazon Web Services (hosting, US region), Stripe (payments), Sentry (crash reporting),
Google / Facebook / Apple (sign-in only). Also state the visibility model plainly: game
scores, rosters, and player stats are visible to other users of the app (e.g. fans following
a team) — define who can see what, since player names/stats of minors may be visible.
No sale of personal data / no ad networks (confirm and state).
NOTE — Payments (Stripe): we use Stripe-hosted checkout; card numbers are
entered with and stored by Stripe, not us. State exactly what we retain (e.g. subscription
tier, Stripe customer ID) and link Stripe's privacy policy. If subscriptions end up billed
through Apple/Google in-app purchase instead of Stripe, this section must change to match.
Data retention
[PLACEHOLDER — to be provided]
NOTE: the product keeps play-by-play history as an audit trail (soft
deletes — play data is never hard-deleted once logged). The policy must reconcile that
design with deletion rights: what happens when a user asks for account deletion, and what
happens to player records of minors on request of a parent/guardian. Apple also requires
an account-deletion path for apps with accounts — coordinate this section with that flow.
Security
[PLACEHOLDER — to be provided]
Your rights and choices
[PLACEHOLDER — to be provided; cover access, correction, deletion, and how to exercise them; state-law rights (e.g. Texas, California) as applicable]
Children's privacy
[PLACEHOLDER — to be provided]
CRITICAL NOTE — youth data / COPPA. Highest-risk section; get legal review.
GameStat is a youth-baseball app: player profiles routinely represent children under 13
(names, jersey numbers, positions, statistics, and potentially photos in team imagery).
The policy MUST accurately address: (1) accounts are held by adults (coaches, scorekeepers,
parents, fans) and the app is not directed at children as users — verify this claim against
the actual product and app-store age rating before asserting it; (2) child data is entered
by coaches/team staff, and what consent model applies (who is responsible for
parental consent — us or the team/league entering the data); (3) COPPA obligations for
under-13 data and any verifiable-parental-consent requirements; (4) how a parent/guardian
can review or request deletion of their child's data; (5) visibility of minors' names and
stats to other app users. Do not publish generic "we do not collect data from children
under 13" boilerplate — it would be inaccurate here, because child data is collected about
players even if children are not the account holders.
Analytics and crash reporting
[PLACEHOLDER — to be provided]
NOTE: Sentry is integrated (server and mobile) for crash/error reporting —
device model, OS version, app version, and error context. Confirm whether any other
analytics SDK exists at publication time and enumerate exactly what is collected; this list
must also match the App Store "privacy nutrition label" and Google Play Data Safety form.
User-generated content
[PLACEHOLDER — to be provided]
NOTE: covers team logos/avatars, player photos if added later, team and
player names, and game data. If the livestream feature links video (YouTube embeds), state
that we link/embed third-party streams and do not host or record video ourselves — verify
against the shipped feature before publishing.
Changes to this policy
[PLACEHOLDER — to be provided; how users are notified of changes]
Contact
[PLACEHOLDER — postal address if required]
Email: privacy@2seamlabs.com
[PLACEHOLDER — confirm address]