Privacy

Signing in and completing onboarding records:

• Your account. The email address, name and Google account identifier Google gives us when you sign in. Sign-in is Google only, so we never see or store a password.
• Your training profile. Division, sex, date of birth, timezone, session length, available equipment, goal, any injuries you flag, and optionally bodyweight and height. Sex and date of birth are used because the scoring standards for this sport are banded by both.
• Your performance data. The benchmarks you enter or skip, whether each is a real result or your estimate, race results and splits you record, and what you log against each session.
• Your programming. Each generated week, the reasoning behind it, which framework versions and model produced it, and when it was delivered.

We do not use analytics or advertising trackers, and there is no third-party tracking script on the site.

• Supabase hosts the database and handles sign-in.
• Vercel hosts and serves the application.
• Google authenticates you. We receive your email, name and account identifier; Google does not receive your training data.
• Anthropic and OpenAI generate your weekly programming. See below, because this is the one that deserves detail.
• Resend delivers email to you.

Writing your week means sending a model enough about you to write it. That request contains your division, sex, session length, current phase and how many weeks you are from your race, whether you are returning from weeks without programming, your benchmark figures and which of them are limiters, equipment substitutions, and any movements to avoid because of an injury you flagged.

It does not contain your name, your email address, or your date of birth. You appear to the model as a set of training numbers, not as a person with an identity.

Two vendors are configured so that one being unavailable does not stop your programming. Whichever produced a given week is recorded against it.

You can read your own. The gym's coaching staff can read athlete data through an admin area, because that is what coaching this programming requires.

Every athlete-scoped table enforces this in the database itself rather than only in the application, so one athlete cannot read another's data even if the application had a bug. That isolation is covered by automated tests that run before any change ships.

We email you three things: your weekly programming, a reminder to log a benchmark before the week is written, and a nudge to record a result the day after you race. That is the entire list. There is no marketing email, no newsletter, and no list to be sold to anyone. Sign-in is handled by Google, so there is no password email either.

Your data is kept while your account exists, because training history is the point: the engine reads your past weeks to decide your next one. Ask us and we will delete your account and everything attached to it. Deletion cascades through the database, so your profile, benchmarks, races, programming and logs go together.

• Ask for a copy of what we hold about you.
• Ask us to correct anything, or edit most of it yourself from your account page.
• Ask us to delete your account and its data.
• Skip any benchmark you would rather not record. The engine schedules a session to establish it instead.

Questions about any of this, or a request about your data, go to info@8thdaygym.com.