Privacy policy
Placeholder. Not drafted or reviewed by counsel. A product collecting data from minors has specific obligations (COPPA in the US, and state student-privacy laws) that need real legal review before launch.
What the product actually collects today
- Account: email, name, role, and password (hashed by the auth provider).
- Athlete profile: positions, class year, ZIP code, travel organization and team, and any optional fields you fill in — including height, weight, GPA, test scores, and measured fastpitch metrics.
- Activity: camps you save, follow, mark interested, and registration links you click.
- Analytics: anonymous interaction events. Role is the only user attribute sent — never name, email, school, or location.
What is never public
The email address used to sign in, date of birth, exact address and ZIP code, and precise location. Contact details entered specifically for coaches are the exception and are optional, for the athlete or a guardian or both. There is no public athlete profile at all: a profile is visible only to the athlete and a confirmed linked parent until she sends a connection request to a specific college coach and that coach approves it. Following a coach exposes nothing. Either side can end an approved connection at any time. Accounts are not available under the age of 13. A camp organizer cannot see who saved their camp as individuals — only counts. See Trust & safety for the full list of what is visible and to whom.
Sections that must be written before launch
- Legal basis for processing, and parental consent for users under 13.
- Retention periods and deletion procedure.
- Subprocessor list (hosting, database, email, analytics, maps).
- Data subject rights and how to exercise them.
- Breach notification commitments.