Team visibility has levels
Coaches need enough to run a team: completion, availability, general training status, whether you answered an assignment and who is ready to go. Your private history, injury details, routes and health signals are a different matter.
CorrCoach does not send athlete fitness data to OpenAI or Anthropic for model training. Team privacy is a separate question: which people on a licensed team can see which parts of your training.
Approval and licensing protect athletes
A coach portal checks the person's role, the team license and admin approval before it shows anything sensitive. Anyone can fill in the public signup form. That doesn't give them coach tools.
New coaches join a waitlist first, get portal access once approved, and only staff on a real license can manage a team.
Your history before the team stays yours
A coach may need your current training, recent completion, whether an injury rules you out and your upcoming assignments. Anything from before you joined the team stays out of the default coach view.
That limit is enforced on the server as well as in the app, so a coach can't reach your old history by changing a date range.
Coaches get what they need
A good team view is short: assignments, who's doing them, who's available and any summaries that matter for safety.
You decide whether injury details, routes and deeper health data get shared. Coaches get enough to help you, and the rest stays private unless you say otherwise.
Questions athletes ask
Can a coach see athlete data from before the athlete joined a team?
Not by default. Personal history from before you joined stays out of the coach view, and coach access covers only the time you're on the team.
Can athlete privacy and coach tools coexist?
Yes. Role checks, licenses, consent, time windows and per-field sharing give coaches what they need to run the team while your routes, health data and injury notes stay private.