Robert Bartel runs debrief; write to him at legal@debrief.fit. Using debrief means agreeing to this page. It is short enough to read.
What we store
Your GPS tracks. A run usually starts and ends at your door, so a track shows where you live, where you go, and when you’re out. We use tracks to compute grade, distance, routes, and weather. We use them for nothing else.
Your body’s data: heart rate, cadence, and power. If you fill in the profile, we also store your birth year, sex, body mass, and thresholds. Training data is health data. We treat it that way.
A connected watch account. If you link a Suunto or Garmin account, we store the account id it knows you by, the tokens that let us fetch your workouts — encrypted at rest — and a per-workout log of what we synced, used for syncing and nothing else. Disconnecting deletes all of it; runs already synced stay in your account like any upload.
The rest: your email, name, and password hash; the metrics and debriefs we compute from your runs; the coaching notebook we keep from those debriefs, so each new one remembers what the last ones said; weather for where you ran; counts of page visits, without cookies; and the IP address you connect from, kept to rate-limit abuse and secure the account. The only cookies keep you signed in, carry your invite code while you sign up, or secure the admin console. The waitlist holds only the address you gave us. We use it to send an invite, then nothing.
What we do with it, and what we never do
We read your runs and write your debriefs, always against your own history. That is the whole use. There is no public feed; only you can see your runs. We don’t sell your data or share it with anyone beyond the companies listed below that run debrief for us, we show nothing to advertisers, and we never use your data, or anything derived from it, to train, evaluate, or improve AI models. Our weather and air-quality providers get coordinates rounded to about eleven kilometers. When we can’t read elevation from our own map data, an elevation service receives points along your route to look up the ground height — the one case where precise coordinates leave our servers, and we store nothing alongside them.
Companies run debrief’s machinery on our instructions: Vercel (hosting, file storage, and page-visit counts), Neon (database), Anthropic (the writing model), Resend (email delivery), Axiom (service logs), Open-Meteo (weather, air quality, and elevation), and Amazon Web Services (the public elevation map we read). All of them are in the United States except Open-Meteo, which is in Switzerland. If you live in the EU or UK, they process your data outside your region under their data-protection terms.
AI transparency statement
What the writing model receives. Your debriefs are written by Claude, a model made by Anthropic. We send it what a coach would look at, and never your coordinates. From your profile: the name on it, your age, sex, and body mass, your thresholds (threshold heart rate and pace, max and resting heart rate), and your heart-rate zones. From the run: date and start time, the session type and any intent you set, distance, time, climb, pace and grade-adjusted pace, average and peak heart rate and the time spent in each zone, cadence and running dynamics, each lap, a timeline in 30-second steps of pace, heart rate, grade, and cadence, whether it was daylight, and notes on where the recording was unreliable. Around the run: the weather and air quality where you ran, your training load, your last four weeks of training, how this run compares with similar runs of yours, whether you have run the route before, and what we already told you: the priorities from your recent debriefs and the coaching notebook. A second, smaller Anthropic model updates that notebook after each debrief. It sees the notebook, the new priorities, your load, your recent pattern, and your zones, not your name, age, sex, or mass.
Anthropic processes this under its standard API data-retention terms. We have no zero-retention agreement with them, so deleting your account here cannot reach what has already been sent. We attach no account id or email to what we send.
You consent to this AI processing explicitly, with the checkbox at sign-up. You can withdraw that consent at any time: disconnecting a watch account stops its runs from reaching the model, and deleting the account ends all of it.
Consent, and taking it back
Creating an account means you agree to all of this, health data included — the sign-up checkbox is where you say so, and we record which version of this page you agreed to. debrief cannot work without it. Withdrawing is built in, not an email thread: Profile → Delete the account removes your runs, files, metrics, debriefs, coaching notebook, and profile. We keep your account data until you delete it; there is no undo. Short-lived logs and the IP records behind rate-limiting age out within about a month, and backups expire on their own — the one exception is a minimal record of administrative actions, such as an invite issued or an account suspended, kept by email for security. For a copy of your data, email data-export@debrief.fit; for questions or corrections, write to legal@debrief.fit. EU and UK athletes can also reach out to their data-protection authority.
What debrief is, and what it is not
A reading of your own training data, in beta, with no promises: features may change, pause, or break. It is not medical advice and no substitute for one qualified human. The debrief sees what a watch records, not injury or illness. Decisions about your training and health stay yours; anything that feels medically wrong deserves a professional, not an app.
Your runs remain yours. We take only the permission we need to run debrief, and it ends when you delete the account. Upload only data that is yours, don’t attack the service or other accounts, and be 16 or older. We may suspend accounts that break these rules. If the beta ends, we will tell you and give you time to take your data. Where the law allows it, we exclude liability for damages; we cannot and do not exclude it for intent or gross negligence. If this page changes in a way that matters, the date above changes and you will hear about it by email first.