Privacy policy
Jesuit Cross Country training app, run by Jesuit High School. Effective November 1, 2026.
This app lets our cross country athletes share their running data with their coaches so we can plan training and reduce injuries. This policy explains what we collect, including data from Garmin, how we use it, who else handles it, and how athletes and parents can see, fix, download or delete it. Questions or requests: keegan.smith@jesuithighschool.org.
Who uses the app
Athletes on the team, who are high school students and usually under 18; their coaches; and the athletic trainer. Athletes use a private personal link; staff sign in with their own accounts. A parent or guardian must approve before an athlete connects Garmin and, separately, before any AI analysis. The app is not meant for children under 13.
What we collect
From Garmin, only after the athlete connects their Garmin account: activity summaries (date and time, type of activity, duration, distance, average and maximum heart rate, and the device model) and activity files and activity details (laps, timing, distance and heart rate during the activity, and the VO2 max estimate the watch records after a run), and, if the athlete shares health data, each day’s resting heart rate from Garmin’s daily summary. We keep only the resting heart rate from that summary and ignore everything else in it, such as steps, sleep and stress. When an athlete connects, we also ask Garmin for their activities from the previous 90 days, so training load is accurate from the start; coaches can repeat this request for up to a year. We also keep the athlete’s Garmin user ID, the permissions they granted, and the access tokens Garmin issues, which are encrypted.
What we never collect or keep from Garmin: we never use or store GPS positions or routes. Garmin’s activity details can include positions; the app discards them as the data arrives. We do not keep the original activity files: heart rate during the activity is used once, to work out each rep and how fast heart rate recovers, and only those per-lap results are kept, along with the watch’s VO2 max estimate for that run.
From athletes: whether they want reminder emails; their resting heart rate in the morning, if they choose to enter it; whether they will be at upcoming meets and, if not, why; how hard each run felt (0 to 10), how their legs felt, pain reports (where, how much, and whether they’ve seen the athletic trainer), days they didn’t run and why, including injury details they choose to describe, and short notes to coaches. Athletes without Garmin can upload activity files themselves; those are handled the same way.
From coaches and the athletic trainer: the roster (name, grade, boys or girls team, group, an optional email address used only to contact the athlete about the team, and optional maximum and resting heart rate), each athlete’s roster photo (the team photo from the school’s athletics website, used with the school’s approval and shown only to staff and on the athlete’s own page; it is never sent to the AI), race and time-trial results, goals, planned workouts, training groups, and injuries. Athletic trainer notes on injuries are visible only to the athletic trainer and administrators.
Worked out by the app: weekly mileage, load ratio (this week’s miles against the previous four weeks), reps, pace against target and heart-rate recovery, VDOT (an estimate of fitness from race results; the watch’s VO2 max is shown beside it for interest but does not set groups), training group and targets, a watch list for coaches, charts, and, only for athletes who agree, the AI briefing described below.
How we use Garmin data
Only to coach the team:
- to show each athlete their own runs, charts, targets and training group, and to show coaches the same for the athletes they coach;
- to total weekly mileage and spot sudden jumps in training load, which are linked to injury risk;
- to find the reps in a workout, compare pace with the target, and measure heart-rate recovery between reps;
- to show each athlete their daily resting heart rate, and to let coaches know when an athlete’s average for the week is several beats above their usual, which can be an early sign of illness, fatigue or poor sleep;
- to show the watch’s VO2 max estimate on each run, and the latest one beside the athlete’s VDOT;
- to match runs to the day’s planned workout and put athletes on the coaches’ watch list when something needs a check-in;
- for athletes who explicitly agree, to include their training numbers in the AI briefing (see the AI transparency statement).
We do not use Garmin data, or anything derived from it, for advertising, marketing, recruiting, or any purpose outside coaching this team. Garmin data and anything derived from it is never used to train, evaluate or improve any AI model.
Who else receives or processes Garmin data
| Who | What they receive | Why |
|---|---|---|
| Cloudflare, Inc. (runs the app) and Supabase, Inc. (stores the database) (hosting) | Everything the app stores, including Garmin data, kept on their servers and in backups | Run the app and its database for us. They do not use the data for anything else. |
| Anthropic PBC (Claude, AI processing) | Only for athletes who agreed to AI analysis: training numbers under a code instead of a name, as listed in the AI transparency statement | Writes the nightly coaching briefing and answers coaches’ questions. Under Anthropic’s commercial terms it may not train models on this data. See the AI transparency statement. |
| Resend, Inc. (email delivery) | Only for athletes who turn on reminder emails: their first name, email address, link to their page, and the reminder (such as how many runs need an effort rating) | Delivers the reminder emails. It does not use the data for anything else. |
| Open-Meteo (weather) | Only a map location (a course or the practice field) and a date and time. Nothing about any athlete. | Returns forecasts for upcoming meets and practices, and the weather at past races. |
| Garmin | Requests to send data, and notice when an athlete disconnects | Garmin is the source of the data. The athlete’s Garmin account is governed by Garmin’s own privacy policy. |
The app’s software libraries and fonts run inside the app itself and send nothing to their makers. We have no other integration partners and use no analytics, advertising, social media, data broker or recruiting services. The app does not connect to Strava.
We do not sell or share Garmin data
We do not sell Garmin data or any personal data, and we do not share it with any third party for that party’s own use. The services listed above handle data only on our behalf, for the purposes described. We would disclose information only if required by law, or to protect someone’s health or safety, and we would tell the athlete and their parent or guardian unless the law prevents it.
The team calendar
Practice times, meets and team events are on a calendar that athletes and families open with a private link, and can add to their phone’s calendar so it updates on its own. It contains no information about any athlete. Coaches can replace the link at any time, which stops the old link and subscriptions.
The team newsletter
Coaches send a weekly newsletter, for now only to the coaching staff. It is written from team data: the schedule, race results, personal records, team totals and milestones. An athlete’s name, race times or photo appear only when a coach has recorded consent for that athlete (such as under the school’s media release), and a numeric VDOT only when that is ticked too. Team totals count everyone but name no one, and nobody is ranked by miles or points. Photos have their location and camera details removed. Team captains can send short notes for the newsletter from their page; a coach reads each one before it is used. Consent changes apply from the next issue; issues already sent can’t be recalled. Nothing about body weight or dieting is ever included.
AI transparency statement
What the AI does. Each night, and when a coach asks a question, the app sends training numbers to Claude, an AI model made by Anthropic, through Anthropic’s API. Claude writes a short briefing for coaches: athletes whose training jumped, who are recovering slowly between reps, who reported pain or missed runs, and who is improving. Coaches read it as a second set of eyes. It makes no decisions: coaches and the athletic trainer decide all training, team and medical matters, and the AI is never used to diagnose injuries.
Only with explicit consent. AI analysis is off for every athlete until they turn it on. To turn it on, the athlete opens their personal page and ticks two boxes: that they agree, and that a parent or guardian agrees. We record the date. Athletes who have not agreed are left out completely: none of their data is sent, and the team-wide numbers sent to the AI are worked out only from athletes who agreed. If a coach’s question names an athlete who hasn’t agreed, the name is removed before the question is sent.
What is sent, for athletes who agree: a code (such as R07) instead of a name; their group and grade; weekly miles, load ratio and injured weeks for the last six weeks; effort ratings and how their legs felt; recent workouts (pace, target, heart rate and recovery); pain reports (where and how much); days missed and the reason, with the structured injury answers (where, which side, pain level, when it started, who has seen it, and whether they expect to miss more days); the type of any logged injury and how long ago it started; benchmark times and goals; and race results from about the last two seasons: the meet, level and distance, about how many weeks ago it was, and the athlete’s time adjusted for the course and weather, with their team scoring points.
About race results. Race results are published, so someone who saw what was sent and compared it carefully with published results could work out which athlete a code belongs to. To make that harder, the exact race date, the course, the athlete’s finishing place and their actual race time are not sent.
What is never sent: names, gender, maximum or resting heart rate, the watch’s VO2 max estimate, anything an athlete or staff member writes (notes and injury descriptions), athletic trainer notes, Garmin user IDs or tokens, and location data, which the app never collects.
No AI training. Garmin data and anything derived from it is never used to train, evaluate or improve AI models, by us or by Anthropic. Anthropic’s commercial terms, which cover our use of its API, prohibit it from training models on the content we send.
How long the AI provider keeps it. Under Anthropic’s standard commercial retention policy, what we send and the replies are deleted within 30 days, unless a longer period is required by law or to enforce Anthropic’s usage policy. In the app, each new briefing replaces the previous one.
Withdrawing consent. Tap Turn off AI analysis on the personal page at any time, or ask a coach or email keegan.smith@jesuithighschool.org. It takes effect immediately: the athlete’s data is left out of every AI request from then on. The previous briefing is replaced by the next nightly one; to have earlier AI answers about an athlete removed sooner, contact us.
Seeing, fixing, downloading and deleting your data
- See it: the personal page shows the athlete’s runs, charts, results, targets and training group.
- Download it: Download my data on the personal page gives a file of everything the app holds about the athlete. Athletic trainer notes are kept separately and are available on request.
- Fix it: athletes can change their effort, pain, missed-day reports and each run’s type and workout from My runs. For anything else, such as a result or roster detail, ask a coach or email keegan.smith@jesuithighschool.org.
- Delete Garmin data: Delete my Garmin data on the personal page disconnects Garmin and deletes every run that came from Garmin, immediately.
- Delete everything: Ask to delete everything on the personal page, or an email to keegan.smith@jesuithighschool.org. We delete all of the athlete’s data within 30 days and confirm.
- Withdraw consent: Disconnect Garmin on the personal page, or removing the app in Garmin Connect, stops new data at once and deletes the stored access tokens. Turn off AI analysis withdraws AI consent. Data already shared stays with the team unless you also ask us to delete it.
Parents and guardians can make any of these requests for their athlete by contacting us. Families may also have rights over student records under federal and state law; ask the school for details.
How long we keep data
We keep an athlete’s data while they are on the team. When athletes graduate, their records (races, results and training) are kept as the team’s history; their personal link and Garmin connection end, and nothing new is collected. If an athlete leaves the program before graduating, we delete their data within 90 days. Any athlete, graduate or parent can ask us to delete their data at any time, and we will. When an athlete leaves, their personal link stops working and their Garmin connection is ended straight away. Garmin access tokens are deleted as soon as an athlete disconnects. Backup copies are kept for no more than 30 days.
How we protect it
Every connection is encrypted (HTTPS). Garmin access tokens are encrypted, staff passwords are stored only in hashed form, and each staff role sees only what it needs. Athlete links are private and can be replaced at any time. Our Garmin API credentials are issued only to Jesuit High School and are never shared with, transferred to or used by anyone else; any request for them is reported to Garmin at connect-support@developer.garmin.com.
Changes
If we change this policy we will update the date above and tell athletes and parents before any change in how Garmin data is used or who receives it takes effect. A new use of AI, or a new company receiving data, would need fresh consent.
Contact
Jesuit High School, Jesuit Cross Country: keegan.smith@jesuithighschool.org.