What Orbit keeps, and who can see it

Orbit is a private, invite-only training app run by one person. This page says plainly what it stores about you and why.

What is collected

• Your login: an email address, and a password you set or a Google sign-in. Passwords are never seen by Orbit; Supabase Auth holds them.
• Training data from your watch, through your own intervals.icu account: runs and other activities, heart rate, pace, splits, climb and descent, running dynamics such as cadence when the watch records them, training load and the name of the watch that recorded each one, and wellness readings: sleep, HRV, resting heart rate and daily steps. When you open an activity, Orbit keeps a copy of its heart-rate trace with the point where it started, and, for a surf or a run that recorded one, its GPS track, with a run's altitude and the watch's power when the watch kept them. You connect that account either by authorising Orbit on intervals.icu or by pasting an API key; either way the credential is held encrypted on the server and no screen can read it back. The connection is two-way: Orbit reads your activities and wellness, writes the sessions on your plan to your intervals.icu calendar, which is how they reach your watch, and takes off the ones it removes. Beyond the calendar, it asks only to read. An earlier authorisation also allowed changing your activities, wellness entries and sport settings there, which Orbit never did; authorising again asks only for what Orbit uses.
• What you log in the app: sets and loads in the gym, fuel, effort and notes for runs, a run's distance, time and heart rate when you log it by hand, other sports you log by hand, your shoes and their miles, your supplements and the days you take them, symptom scores, and the daily journal (drinks, travel, late meals, caffeine, supplements) if you use it.
• Your plan and preferences: your race, your rules, the block and each week; what you told Orbit at setup, such as your running so far, your goal and any injury or sore spot to plan around; trips you add, with their dates, place, timezone and what gym you will have; and your settings, such as Orbit's voice and the look you chose.
• Your Google Calendar, if you connect one: the events in the weeks Orbit is planning — their titles, times, locations and whether you are busy. Orbit also writes the training it schedules, and creates a calendar of its own to put it on. It asks for that narrow set and not the full calendar permission, so it cannot change who your calendars are shared with, and it changes only the events it wrote itself. Your Google email address and account id are stored with the connection. To suggest a trip, Orbit also looks through your main calendar from two weeks back to about six weeks ahead for flights and hotel stays; that is worked out on the server without the AI, nothing from it is stored, and a trip is saved only if you confirm it.
• Anything you upload: a photo of a plan, an old training document, a physio PDF. Orbit keeps the file, and a summary and extract of what it read from it.
• Orbit keeps short notes on patterns in your own training, each with the runs or check-ins it rests on; you can see, edit and delete every one in More › What Orbit has learned about you, and a note you delete is not written again. Coaches do not see these notes.
• Reports you send with Report a problem: what you write, the name of the screen you were on, the app version and your browser, and a screenshot only if you add one.
• Notifications, if you turn them on for a phone: that phone's push address, its browser, and which of the three alerts (week ready, run read, evening check-in) it wants. All three are off until you turn them on.
• Workouts you share: a run or a lift you send to another athlete, as it stood when you sent it, with your note.
• If you coach on Orbit: your login, the athletes linked to you and with what access, the notes and plan changes you write for them, and the usage below.
• Usage: when the app was opened and for how long (a mark for each minute it is on screen, kept for 400 days), and the size and cost of each request to the AI, or for a voice clip the seconds billed, so the person running Orbit can see what it costs. None of it holds what was asked, written or said.
• On your device: the app keeps your sign-in, and anything you typed but have not saved yet, in your browser's own storage, so a dropped connection loses nothing. It sets no cookies.

Where it lives

In a Supabase database in the United States (us-east-2), under row-level rules that tie every row to the athlete it belongs to. Uploaded files, and a screenshot sent with a report, are kept in private storage in the same project. The app is served by Netlify. Like any website, Netlify and Supabase see your address and browser when the app talks to them.

A copy of the whole database is made every night and kept for 90 days, and another before each release of the app, kept for 30 days. Both are private files in the GitHub account that holds Orbit's code.

Email is sent through Resend from orbitathletics.com, so Resend handles more than an address: the weekly email and its calendar attachment contain that week's sessions, with their times and distances. Resend also carries sign-in links and invitations, setup and reminder emails (a reminder can list the sessions that went unlogged and the next ones on your plan), product notices, and a report or an invite request on its way to the person running Orbit.

Moment emails go through Resend too. When something stands out in your own training, Orbit may write to you, at most once a day: that email carries the run or the week it is about, with its distance, pace and heart rate, or the sessions that went unlogged, and the next days of your plan. You can switch them off in More › Emails, or with the link in any of them.

Connection credentials are kept apart from the data. Your intervals.icu credential is held encrypted on the server, in Supabase's vault (or, for an older pasted key, as an encrypted server secret), named but never readable by the app. Your Google tokens are in a table no browser and no other athlete can reach, and they are deleted when you disconnect.

Notifications, if you turn them on, go through your browser's own push service (Apple's on an iPhone, Google's in Chrome), encrypted so that service cannot read them.

Who can see it

• You.
• A coach you link, and only what you allow: read-only or editing, with the journal shared or withheld. A coach sees your plan, runs and numbers, the reads Orbit writes and what the Planner proposes, which can quote the weekly mileage and longest run you gave at setup. With editing, a coach can also change your plan and your running guidance (and so what reaches your watch and calendar), log sessions for you and email you your week; when they ask the Planner about your week, it reads that week's calendar events as it would for you, so its answer to them can mention them. A coach never sees your uploads. You can end it in one tap and the access ends immediately.
• Other athletes on Orbit, for sharing workouts and nothing else. While Workouts from friends is on (it is until you turn it off in More › What Orbit shows you), your name is on the list another athlete picks from to send a run or a lift. A workout you send carries its name, day, place and start time, the distance, steps and warm-up, and your note, with your heart-rate figures taken out; if they join it, the copy on their plan keeps your name.
• The administrator, Ryan, who runs Orbit. The console shows him the athlete list (name, email, race, goal, the coaching brief written for your account and how much is on file), when each person last opened the app, usage and costs, and, for the reminder emails, which planned sessions went unlogged. A daily check of everyone's data emails him when one of its rules breaks, naming the athlete and the session. Because he runs the database he can reach any row, and so can the Claude coding sessions (Anthropic's AI) he uses to build and check Orbit, which read it when they look into a problem or check a change.

The AI

The Planner, Ask Orbit, the read on each run and lift, setup, the Sunday build and moment emails send your training data to Anthropic's API to produce a plan, an answer or a note. Under Anthropic's API terms that data is not used to train their models. Orbit only sends what the request needs, and records the size and cost of each request, not its content. What you type to Ask Orbit or the Planner is not stored by Orbit; the changes the Planner proposes, with its reasons, are kept with your plan.

The notes Orbit keeps on your training go with the questions you ask Ask Orbit yourself. The Planner on your own login, the read on each run and lift, and moment emails get only the notes Orbit drew from your runs and sessions, never one you wrote or edited and never one from the journal. A coach's requests get none.

Three things are worth naming because "training data" would not cover them:

• Your calendar, if you connect one. When the planner works out where a session fits, it is shown the events in that week — including their titles and locations. That means those titles reach Anthropic's API.
• The Sunday build does this with nobody at the keyboard. If you leave it switched on, it acts as you early on Sunday morning in your timezone, and again that night if the morning did not work, to write next week from the week you just ran. When that week gives it no reason to change course, it carries it forward without the AI; otherwise it reads your calendar and sends the same things a Planner request you typed would. It then puts the week on your plan and your watch and emails it to you, or, with Let me review it first, leaves it on Now until you say so.
• Files you upload are sent to Anthropic as well, as the document or image itself, so the model can read it.

One more: when Orbit looks up a race course, at setup or when you tap Look it up again, it searches the web through Anthropic's API using the race name and date. That leaves Anthropic for a search provider, so it is worth saying even though the query is about a race and not about you.

When you use the mic, your voice clip is sent to Groq to turn it into text. Orbit does not keep the recording. Nor does it keep the words: they go into the box for you to read and send, and the only record is how many seconds of audio Groq billed.

When a surf or a run with a GPS track is opened, the app can draw the track on a map from MapTiler. The browser of whoever opens it (you, or a coach you share with) asks MapTiler for the map of that area, so MapTiler sees which area is shown, with that browser's address, as any site something is loaded from does. Orbit sends MapTiler nothing else: not the track, not your name, not the session. The line is drawn on the screen, over the map.

When Orbit shows the weather for your runs, it asks the National Weather Service for a place in the United States, or MET Norway anywhere else, for the forecast. It sends them only a rounded location, about 1 km across: where you usually start your runs, or the city of a trip on that trip's days. Never a route, a track or a home address, and nothing that names you.

When Orbit looks at tomorrow's surf for you, it asks Scripps' Coastal Data Information Program (CDIP) for the swell forecast, the National Weather Service for the wind and the rip-current risk, and NOAA for the tide. It sends them only the fixed positions of the surf spots it knows (and NOAA's tide station) with the dates: nothing about you, where you run or where you have surfed.

A moment email's words are written through Anthropic's API from those same numbers, in the voice you chose and with the notes Orbit keeps on your training.

What Orbit does not do

• No advertising, no analytics trackers, and nothing is ever sold. The only services that receive anything are the ones named on this page: Supabase, Netlify, intervals.icu, Anthropic, Resend, GitHub (the database copies), Groq (only when you use the mic, to turn your voice clip into text), MapTiler (the map under a surf's or a run's track), the National Weather Service and MET Norway (a rounded location, for the weather on your runs), Scripps' CDIP, the National Weather Service and NOAA (fixed surf-spot positions and dates, for the surf outlook), Google (if you sign in with Google or connect a calendar) and, with notifications on, your browser's push service. The app and every page here load their typefaces from Google Fonts, which means Google sees the request — your address and browser — on any page you open, including this one.
• No medical use. Readiness, load and the reads are training observations, not diagnosis.

Your choices

• In More › What Orbit shows you, hide sleep, recovery, load or the morning journal. That changes what you see: Orbit still reads what your watch sends, and the Planner and Ask still use it. Turning off the nightly read stops the reads on your runs and lifts being written at all. Turn off Workouts from friends to leave the share list, and turn off the Sunday build, or have it wait for you with Let me review it first.
• Remove a coach, or change whether they can edit and whether they see the journal, in More › Coaches.
• Disconnect your watch in More › Watch, which deletes the credential Orbit holds (an older pasted key kept as a server secret is removed within a day). If you authorised Orbit on intervals.icu, it also withdraws that authorisation there, and tells you if it could not, so you can do it yourself. Workouts already on your intervals.icu calendar stay there.
• Disconnect Google Calendar in More › Google Calendar. That revokes Orbit's access at Google and deletes the stored tokens and the events it was tracking. Sessions it already put on your calendar stay until you delete them.
• Turn notifications off for a phone in More › Notifications.
• Stop the email. Moment emails have their own switch in More › Emails. Setup nudges, reminders and product notices each carry a link that ends them, and it takes effect immediately. The weekly plan email has no such link because you asked for it: it comes with the Sunday build and, if you turned it on, after every Apply, and it stops when you turn those off.
• Delete your account and everything in it: email the address below and it is done within a week. Your training goes with your login: runs, plan, journal, the notes Orbit keeps, the files you uploaded and what Orbit read from them, any screenshot sent with a report, calendar links, credentials, notification devices, reports, and the usage and cost rows. What is left behind: a one-line record that the account was deleted, with its name, email address and how many rows went; an invite request you sent through the front page, until you ask for it to go; a workout you sent that another athlete joined, which stays on their plan with your name; the database copies, until they age out after 30 or 90 days; workouts and events already on your intervals.icu and Google calendars, and Orbit's entry in those accounts' settings until you remove it there (Orbit no longer holds the keys); and the logs the services named here keep for their own periods.

If you ask for an invite

The form on the front page stores the name, email address and note you write in it, and emails them to the person running Orbit through Resend, with your address as the reply-to. It creates no account and no login, and nothing else happens with it. Ask at the address below and the request is deleted.

Contact

Orbit Athletics is run by Ryan Vizethann. Questions and deletion requests: ryan@orbitathletics.com.

Last updated 14 October 2026.