Effective date: 29 October 2026
Adapt & Triumph (“the app”) is made by Adapt & Triumph LLC, an Oklahoma limited liability company (D-U-N-S 149990473) (“we,” “us”). The app is built to respect your privacy. This policy explains what the app does and does not do with your information.
The rest of this policy gives every detail. It covers, in order: the feature status; the short version; the checks every phone makes; teams and coaching (what a team keeps, your weekly summary, the team games, sport, Numbers, clubs, Training now, Team vs Team, seasons, the crest, training tournaments, organisations, food, leaving a team, and each part of coaching); reporting a concern about a child; what the app stores on your phone; health data; backups; purchases; links; your phone’s voice; deleting your data; sponsored access; help build better products; more features, described before they are on; analytics; the companies that help us run this; children; security; changes and new features; and contact.
Every feature this policy describes, and every one we plan, is listed here as On or Off.
| Feature | Status | Described in |
|---|---|---|
| Checks every phone makes: anything waiting, app updates, purchases, recipe pictures, the holiday calendar | On | Checks every phone makes |
| Sponsor and organisation codes | On | The short version; If your access was sponsored |
| The sponsor’s “still using it” count, if you switch it on | On | If your access was sponsored |
| Gym check-in codes | On | If your access was sponsored |
| Teams: boards, posts, games, sport and training tournaments | On | Teams and coaching |
| Coaching | On | Teams and coaching |
| Organisation vs Organisation, and organisation challenges | On | Organisations: Organisation vs Organisation; Organisations: challenges |
| Game tournaments | On | Coaching: game tournaments |
| Several teams per coach, and an organisation’s teams | On | Coaching: several teams, and an organisation’s teams |
| A code for each of a coach’s teams, and asks to join a team | On | Teams and coaching |
| Reporting a concern about a child | On | Reporting a concern about a child |
| The feature count in Settings, kept on your phone and never sent | On | The short version |
| Files you share yourself: a Backup, your appointment summary, the Athlete Sheet, your journal | On | Backups you control |
| Your avatar mark | On | Artists and your avatar |
| Reminders your phone sets for itself | On | Push notifications |
| Spoken cues and voice “next” | On | Your phone’s voice and microphone |
| Purchases | On | Purchases |
| Coach subscription | On | Purchases; What changed since the 30 July 2026 version |
| Client seats | On | Purchases; What changed since the 30 July 2026 version |
| Messages with your coach | Off | Coaching: messages with your coach |
| Help build better products: Count me | Off | Help build better products |
| Help build better products: Build better products | Off | Help build better products |
| Help build better products: Show it’s working | Off | Help build better products |
| Totals for organisations, funders and clinics | Off | Organisations and clinics: totals only |
| Accounts and sign-in | On | Optional accounts and sign-in |
| Organisation invites by email | On | Organisations: invites by email |
| The organisation portal on the web | On | Organisations: the portal |
| Organisation members by email | Off | Organisations: members by email |
| Sign in with Google | Off | Optional accounts and sign-in |
| Settings sync across your phones | Off | Optional accounts and sign-in |
| Push notifications for events and safety notices | Off | Push notifications |
| Features for children under 13, their parents, and schools | Off | Children’s privacy |
| Event tickets and donations | Off | Event tickets and donations |
| Artists’ credits and the 3D avatar | Off | Artists and your avatar |
| The robot avatar, and your robot’s look sent to your teams | Off | Artists and your avatar |
| Food photos | Off | Food photos |
| Find a coach | On | Find a coach |
Turning a feature on changes only its word in this table, with a dated line in What changed (see Changes and new features).
Everything you keep in Adapt & Triumph — your workouts, your food, your weight, your Health Hub — stays on your device. We never require an account to use the app for yourself, we do not build a profile of you (apart from Help build better products, below, which sends only what you choose, and only while it is on), we do not follow you across other apps or websites, and we never sell or share your personal data. We cannot see what is in your workouts (apart from what Help build better products sends, if you switch it on), your food log, your body weight or anything in your Health Hub. If you join a team or link a coach, they and our server get the counts listed below.
Some requests happen on every phone. When the app opens, it asks our server whether a team, a coach, a plan or a message from a coach is waiting for you, and it asks again when you open Home, Triumph or the menu. It also downloads our list of holidays and special days. It asks Expo, the service that sends app updates, whether there is a newer version, and RevenueCat checks whether you have bought the app. Recipe pictures come from our server when you look at recipes. None of these carries anything you entered, except, if you signed in, the sign-in token, which contains your email address. They are described under Checks every phone makes, below.
More reaches our server only when you use it: a sponsor code, a team or a coach, a tournament, a gym check-in scan, the sponsor’s “still using it” count if you switch it on, Help build better products if you switch a level on, a report you choose to send us about a child’s safety, and the other features Feature status lists as On. Each is described below with exactly what it sends.
Sponsor codes. If you were given a sponsor code — by a gym, a clinic, an employer or anyone else — the app has to check that code is real, and that check happens on a server. What we send is the code itself and a random number the app made up to identify this installation, with the random number for your profile and the private keys described under Teams and coaching, below, and, while you are signed in, the sign-in token described under Optional accounts and sign-in, which contains your email address. Nothing else leaves your device for that check: not your name, not a workout, not a weight, not a health note, not an advertising or device identifier, and no email unless you are signed in. For each try, our server also keeps this installation’s random number, the time and a scrambled token for the network it came from (never the address itself), to slow down people guessing codes. These are deleted automatically after about two days. Unless you signed in, we do not know your real name or email. The code check records the random number for your profile, which also labels your seat in a team or your link to a coach if you use them, so we could connect those records to your first name. The code is checked when you enter it; a retry sends it again, and a phone that already has access can check it once before claiming it. After that, whenever you open Triumph, the app sends your card’s two-letter batch label (and the label of any other organisation’s card you hold) and the two random numbers to our server, to show your organisation’s name and, once it can be shown, its count of people who logged something today (see If your access was sponsored). The code check, and Triumph’s check of your cards, also tell your phone the kind of organisation each card belongs to, which the app uses only to decide the order of your organisations’ names (on Home, and in Triumph’s Organisation row when no card there names one) and, when more than one organisation’s card is waiting to cover you, which one starts first. It is never shown. Your phone keeps it with the card, and the app never sends it anywhere, except in a Backup you export yourself. If a coach handed you the code, checking it also puts you on that coach’s list without a second approval, and the app names the coach when it happens.
Teams and coaches. If you start or join a team, or enter a coach’s code, the app shares what those people need to see — counts of what you did, which of a team’s clubs you are in, that you are mid-workout if you share your workouts with a team, and, only in a Numbers team where you switch them on yourself, your weekly training numbers and your monthly Meet entries; never your Health Hub. If your team plays another team in Team vs Team, an organisation whose gym team you are in plays another in Organisation vs Organisation, or your coach plays another coach in Coach vs Coach, the other side sees one number a week for your whole team, your organisation or your coach’s clients, the teams in your team’s season league see its season points, place and division, and in a training tournament the teams it plays and the tournament’s directors see your team’s score each round; never your name, though when only a few people are counted a number can say something about them. If your coach enters their team in a game tournament, its directors see the first names and numbers of the team’s players who said OK to being shown, for check-in, and anyone with its spectator code sees its schedule and scores, never a player’s name. Once its schedule is out, the team’s games show on its coach’s, staff’s and players’ Calendars. Teams and coaching, below, lists exactly what.
Messages with your coach are listed in Feature status. When they are on, a member 18 or over and their coach, also 18 or over, can type messages to each other. Our server keeps them for 90 days, nobody under 18 can send or get one, and either of you can report a message or block the other. See Coaching: messages with your coach.
Help build better products is listed in Feature status. When it is on, people 18 and over can choose to send us a summary of each week’s training, the reasons they tap for skipping or swapping a move, an email address for study invites, and, under Show it’s working, what they choose to tell us about themselves, check-in answers and self-test results, to help us show the app is used and that it helps, and build what does not exist yet. See Help build better products.
An optional extra, off unless you switch it on. In Settings there is a switch called “Help us see which features get used.” It is off by default. If you turn it on, the app counts, on your phone, how often screens such as Workouts and Recipes are opened. This version of the app does not send those counts anywhere. They stay on your phone.
The count is meant for one thing: working out which parts of the app are worth improving and which nobody opens.
Even if you never join a team, enter a coach’s code or use a sponsor code, the app makes these requests:
Everything else in this policy that reaches our server is sent only when you use the feature it describes. A feature in More features that would add a request like these says so in its own section.
Like any web service, the company that hosts our server (Supabase) keeps short-lived logs of the requests that reach it, which include your network address and the time. This is true of every request to our server described in this policy.
Triumph is the part of the app for training alongside other people. None of it is switched on for you. Apart from the questions every phone asks (see Checks every phone makes), nothing in it is sent until you start or join a team, or enter a coach’s code. From then on the app shares what those people need to see, and nothing else. Its requests carry the random numbers the app made up for this installation and for your profile — never a phone number. If you are signed in, they also carry your sign-in token, which contains your email address (see Optional accounts and sign-in). Your phone also keeps private keys, one for each profile and one for the phone, that prove those requests come from it. Our server keeps only a scrambled form of each, with the random number it belongs to and the date it was first seen. It keeps them after you delete a profile, so that nobody can later use that number as you, and each network can register only a limited number of keys an hour. Email us to have them removed. To enforce that limit our server also keeps a scrambled token for the network (never its address) and the time of each registration, with no random number for you. These are deleted automatically after about two days.
Entering a code (a team’s invite code, a coach’s code, a challenge code or a tournament code) and each team write you make, such as a post, a welcome, setting or clearing the Close, or a call in Call It, leaves a short record so the number of tries an hour can be limited: this installation’s random number, a scrambled token for the network (never its address) and the time, one row each, kept for about two days. It is not shown to anyone.
In a team — up to 14 people who shared a code with each other, or up to 25 in a team that had more than 14 when 14 became the limit — our server keeps:
It never receives your body weight, your measurements, your food log, or anything from your Health Hub. Leaving a team deletes your name and your counts from it, once our server confirms you are out, apart from what Leaving a team, below, says stays. Posts you wrote are not removed when you leave, so delete them first if you want them gone. Feed posts that name you also stay, such as a session you put up (announced in the feed with your first name), a welcome another member posted to you (it keeps your first name in its sentence, because it is their post), a line saying you got into a club, or a line saying you were made the team captain. If you report a problem in a team, the report and any note you add are sent to us so we can act on it. We keep a team report while it is open and for 12 months after we close it, and then it is deleted automatically; email us if you want one removed sooner.
If you block someone in a team, our server keeps the team and the two random numbers (yours and theirs) so their posts stop reaching you. They are not told. It stays until you unblock them or delete your profile, and leaving the team does not remove it. A block someone else placed on you also stays if you delete your profile. Your phone keeps their first name so you can unblock them.
If your team plays another team, our server also keeps one number a week for the whole team, described under Teams: Team vs Team below, and a weekly score for the team during a season, described under Teams: Seasons. In a training tournament it keeps a score for your team each round, described under Teams: training tournaments.
After a week or more with no workout, food or water logged, a team can offer a “Tell the team I’m back” button. It posts only if you tap it, and the post is always the same fixed words, “back in”, under your first name. It carries no number: not how long you were away and not what you missed. Other members may see it as an alert inside the app the next time they open that team in Triumph. The one-tap logs near the top of a team’s Today pill are ordinary logs on your phone and send nothing beyond the counts above.
What someone holding your invite code sees before joining. When you start a team you can add an optional founder line, for example “Tuesday and Thursday mornings, nobody cares how slow”. It is built only from preset choices (days, time of day, pace); you cannot type your own words into it. Anyone who enters the team’s invite code sees the team’s name, whether its board is on, whether it counts Numbers, the founder line if there is one, and how many of its 14 seats are taken (for example “3 of 14”), before they decide to join. For a full team, the answer to that code includes its name and, on a current version of the app, how many people are in it. They are not shown who is in the team, anyone’s name, or any activity. If a code is refused because the team is not open to that person, the answer to that code includes only the team’s name. The founder line is stored with the team on our server and is shown to the team’s members. It stays with the team if you leave. A team is not deleted when its members leave: its name, invite code, founder line and crest stay on our server. Email us to have a team removed.
Your own week label on the board (“best week since June”, “a typical week for you”) is worked out on your phone from your own logs. That history is never sent to our server or to other members. Only the weekly count the board already shows is shared.
With a coach, your coach sees the sessions you complete against what they assign, your first name, your age group, and — only when you tap it — that you are training right now. Only if you turn on “Let my coach see my food” for that coach, they also see how many days this week you logged a recipe (see Teams and coaches: your food, below). Only if you turn on “Show my coach when I’m on rehab” for that coach, they also see whether you are on rehab for a sport (see Coaching: your coach’s sports team, below). Only if you turn on “Send my drill numbers to my coach” for that coach, they also see the numbers of the drills you log each week (see Coaching: your drill numbers, below). Only if you turn on “Send my cleared tick to my coach” for that coach, they also see the day you ticked that your doctor or athletic trainer cleared you after a concussion (see Coaching: your coach’s sports team, below). Your phone sends your coach that summary when you save a workout (or edit or restore workouts) and when you open Triumph, so your coach’s count can change soon after you save a workout. If nothing has arrived from your phone for two weeks, your coach’s screen says they have not heard from you: that is about your phone, not about whether you trained. Your coach’s app also receives the day your link with them was made and the week your phone last sent a summary. Everything your coach sees about you is what your phone sends them, as described here, and what they note on their own phone, such as who came to a practice, which stays on their phone (see Coaching: your coach’s sports team), except a short note they can type on your page about what you are working on together, which our server keeps (see Coaching: what your coach picks for you), and, once messages are switched on, the messages you send them (see Coaching: messages with your coach). Your coach can also give you a mark once a month, from a fixed list (see Coaching: your coach’s mark, below). If your coach turns on a leaderboard, the other people they coach can see your sessions done on it, and you can take yourself off it. Your coach can also set you Coach’s Rules and a weekly challenge from fixed lists, and run a group you are in as a block; your phone then also sends your coach how many of their rules are at their full run and whether you did the week’s challenge, and while the leaderboard is on the people they coach can see more (see Coaching: your coach’s team, blocks, rules and challenges, below). Your phone’s summary also carries how many sessions you saved since Monday and in the whole of the week before, which your coach’s screen does not show: if your coach plays another coach in Coach vs Coach and you are marked as 18 or over, those sessions also count toward one weekly number the other coach sees, never with your name (see Coaching: Coach vs Coach, below). Never your Health Hub, your weight, your measurements or your food log. You can stop sharing with a coach at any time, in one tap, while your phone is online (see Stopping sharing with a coach, below). A coach approves each new client who joins with their coach code or one of their teams’ codes first, and what they see before that is under Coaching: approval and your age group, below. If a coach handed you a sponsor code, checking it puts you on that coach’s list without a second approval, and the app names the coach when it happens. If your coach runs a sports team and marks you as a player (or approves a request or an ask you made with a team’s code), more is shared with their assistant coaches, their helpers and your teammates, only as described under Coaching: your coach’s sports team, below.
Your coach’s card, and yours if you coach. From your coach shows a card about each coach you share with: their first name; a crest each phone works out from the coach’s random number (nothing about it is stored or sent); the name of the organisation their coach card came through, unless they turn that off; whether their team has a sport set; and what they saved under Your profile for clients: up to four specialties and when they are usually around, both from fixed lists, what they coach, and a bio of up to 200 characters that they type, with links, emails, @handles and phone numbers we can spot taken out. Their bio, their team’s name and its sport, level and squad, and a nutrition specialty are sent only to people marked as 18 or over, unless the coach also chooses to show their bio and specialties on a Find a coach listing, which anyone can see (see Find a coach). If you coach, our server keeps what you save there, and when you saved it, until you change it or delete that profile in the app, and sends your card, as described above, to each person you coach.
If you are in a team, your phone sends our server a short summary of your workouts each time it syncs with the team. This summary is sent whether or not “Share my workouts with this team” is on. That switch only decides two things: whether the app offers to post a finished workout to the team, and whether the team sees your first name under Training now while you are mid-workout (see Teams: Training now, shouts and Iron Hour).
Logging food or water can also start a sync. That sync sends the same counts any sync sends, which your team’s phones already receive beside your name. Your days trained and days in a row count only days you saved a workout, and no food, water or recipe count is among them, except how many meals you logged, which goes only to a team you turned on “Share my food with this team” for. The sync can also update your last active day, the date of your phone’s latest sync with the team, which your team’s phones receive too. It adds nothing about food or water to the workout summary. Our server also keeps the time of your phone’s latest sync with each team. It is never sent to a phone; it is used only to leave out stale weight totals, and it is deleted with your summary.
What the summary holds:
The summary never includes food, water or recipes. It never includes your weight, measurements or pain, or anything from your Health Hub. Every phone builds its summary the same way, from saved workouts alone, and it never includes your health conditions.
No other phone ever receives your summary itself, including the phones of people in your team, though Draw Week sends your rival one number from it (described below). From summaries the server works out only the three things below, and the floor, the weekly titles, the Draw, Team Bingo, Draw Week, Call It, The Seven, Move the Bus, Team vs Team, Seasons, Organisation vs Organisation, organisation challenges, Ball Every Day and Make It Rain described in the sections after this one:
How long it is kept:
Posting the team’s line or a welcome
Since you last looked
The PR Wall
The floor
The Close
Weekly titles
In a team of three or more, our server can hold a Draw for a week, using the workout summaries phones in the team have already sent. It happens once, the first time a phone in the team sends its weekly summary during the following week. If no phone in the team does that during the following week, that week is never drawn.
Everyone still in the team who was in it before that week began (midnight UTC on its Monday), and whose summary shows a saved workout that week, has one ticket, however many workouts that was. Whoever came out the week before does not get one. Taking yourself off your team’s board does not take you out of the Draw, and you can be the name that comes out. There is no Draw unless at least three people still in the team were in it before that week began, and none if fewer than two tickets are left; those weeks are recorded as having had no draw, with no name on them.
The server picks one ticket and stores the result: the week, how many tickets went in, which seat came out, and when it was settled. Nothing else about anybody’s week is stored with it.
Unlike the trained-today count, Spot the Week and this week’s team totals, and like the weekly titles, the Draw’s result carries a name: the winning seat is shown to the team, because that is what the Draw is for. The server never sends anyone a list of who had a ticket, a count of how often anyone else has come out, or a run of weeks anybody has not. Your own winning weeks are sent back only to you. The team does see how many tickets went in, and in a small team that number, the winner’s name, or a week with no Draw at all can still show whether other people in the team saved a workout that week.
If you leave a team and our server confirms it, are removed from it, or delete your profile and that request reaches our server, your name is taken off any Draw you won there. The week itself stays, with no winner, so it can never be drawn again.
A weekly job deletes each Draw result about twelve weeks after the start of the week it describes.
Team Bingo. In a team of two or more, our server deals the team a card of squares each week, from the team and the week: nine squares for a team of two to six, sixteen for seven to twelve, and twenty-five for thirteen or more. On a team where somebody has logged sport the card is dealt from more squares, some of them sport ones, so it is dealt again when sport first shows on the team, or stops, and a square someone holds can leave it. From the Bingo part of each member’s workout summary it works out who holds each square: the earliest day wins, one person per square and at most three each, and a tie on the same day is settled the same way every time. Each time your phone syncs with the team, once your phone has sent this week’s summary from a version of the app that has Team Bingo, the server sends it the card and which member holds each square, and your phone shows each holder by first name. So your teammates see your first name on any square you hold, which shows that you did that act this week, and who holds what can hint at which days people did things. In a small team, a square left open, or someone holding none, can also show that a person has not done that act this week, that their phone has not synced since doing it, or that their phone has a version of the app without Team Bingo. Taking yourself off your team’s board does not take you off the card. For Bingo, the server never sends anyone’s days, and it stores nothing about the card: it works the card out again on each sync from the summaries it already keeps, and someone who has left the team is never on a card it sends.
Three Cards. Your three cards are dealt and ticked on your phone, from the team, your place in it, the week and your own saved workouts. Nothing about them is sent to our server or to your team. Your phone keeps the two you keep, and any week you sit out of Draw Week, with the app’s other data, so they are included in a Backup you export and stay with this profile when you switch.
Draw Week. Only in a team whose board is on. Our server pairs, at random, the members who were in the team before the week began (midnight UTC on its Monday) and are on the board, using the team’s member list. Anyone who has taken themselves off the board is left out of the pairing, and someone leaving the team, or going off or back on the board, deals that week’s pairs again. Anyone who shows the team they are on rehab (see Teams: sport) is left out of the pairing too, and turning that on or off also deals that week’s pairs again. In a small team the same two people can be paired week after week. Each time your phone syncs with the team, the server tells it who your rival is and, once your rival’s phone has sent this week’s summary from a version of the app that has Draw Week, how many days this team week they saved a workout; your rival’s phone, if it is on a version of the app that has Draw Week, is told the same about you. Draw Week sends neither number to anyone else in the team, but after a re-deal your new rival’s phone is told the same, so in that week more than one person in the team can be told your number. Nothing about the pairs is stored. If you sit a week out, nothing about that is sent, so your rival’s phone is still told how many days you saved a workout. To leave Draw Week, take yourself off the board.
Call It. In a team of two or more, each person can make one call each week, on Monday by their phone’s date: how many workouts the team will save by Sunday. A call is a whole number, picked with buttons. Our server keeps it with your place in the team, the week and when you made it, and it is never changed after it is made. Until Sunday our server sends your call only to you; on Sunday, by the date of the phone asking, it sends every call that week to each phone in the team that has sent this week’s summary, and your phone shows them by first name. Taking yourself off your team’s board does not hide your call. Each sync also sends those phones the team’s number so far: the workouts in the summaries phones in the team have sent this week, added together. In a small team, the team’s number less your own can show what the others saved, and in a team of two it is the other person’s workouts this week.
If anyone in the team called last week, then once Sunday is over everywhere (12:00 UTC on Monday), the first time a phone in the team sends its weekly summary, our server locks last week’s number: the workouts in the summaries of people still in the team then who had joined before that week ended (midnight UTC at the start of the following Monday), as they had reached our server by then. It stores that number, how far the closest call was from it and when it was locked, and nothing else about anybody’s week. If no phone in the team does that during the following week, that week is never locked and nobody takes it. The closest call takes it, and so does every call that ties with it. Our server sends each phone in the team who that was and their call, and sends your own past wins only to you. Within 10% of the team’s number without going over pays 90 coins, and closest otherwise pays 45 coins, added on that person’s phone the next time it opens that team while that week is still kept. A week the team saved no workouts has no winner. If you leave a team and our server confirms it, are removed from it, or delete your profile and our server accepts that request, your calls in that team are deleted, so they are never shown again or named as closest. If that happens after a week’s number is locked, nobody else is named in your place for that week; if it happens before, your call and your workouts are left out of that week’s number, and the closest of the calls left takes it, if the number left is above zero. A weekly job deletes calls and locked numbers about four weeks after the start of the week they are about. Your coins, and the weeks your phone has paid, are kept with the app’s other data, so they are included in a Backup you export and stay with this profile when you switch.
The Seven. In a team, The Seven has a slot for each of the app’s seven kinds of training. From the part of each member’s workout summary described above, our server works out which of the seven anyone in the team trained this week, and sends that one answer for the whole team to each phone in the team that has sent this week’s summary. It never sends which person trained which kind, and it stores nothing about the card: it works it out again on each sync from the summaries it already keeps. Training “Residual-limb strength” or “Seated / wheelchair” can say something about a body. Our server answers for those two slots only once this week’s summaries from phones on a version of the app with The Seven show at least three people in the team who each trained at least one of the seven, so never in a team of fewer than three; until then the card shows them as neither covered nor open. A slot that closes right after one teammate saves a workout can still show who trained it, and in a small team a closed slot can show it at any time. A teammate whose phone has a version of the app without The Seven closes no slots. Taking yourself off your team’s board does not take your training off the card.
Move the Bus. In a team of two or more, Move the Bus sets one target a week for the whole team. Each time your phone syncs with a team, it also sends our server the weight you lifted on working sets since Monday, by your phone’s date, as one number beside the seven-day total above. Our server keeps it with your place in the team, replaced at each sync and deleted with your other counts when you leave the team. The first time in a week that a phone in the team with Move the Bus syncs, our server sets that week’s target, and it stays the same all week: the median of how much of the team’s lifting counted in up to four weeks before it (each person’s part counts only up to the limit below), plus 15%, and never less than 5,000 lb. A team with weeks on record but no lifting in any of them, or yet that week, plays in saved workouts instead, with its target set the same way from its weeks in saved workouts and never fewer than 4. Working sets move it, and so do the mobility workouts and workout days in your weekly workout summary: each takes 250 lb off, up to half the target. In saved workouts, the saved workouts in your summary move it instead, and mobility workouts and workout days take nothing off. No one person’s part (their lifting, mobility workouts and workout days together, or their saved workouts) counts for more than 40% of the target, rounded up, or half if the team had two people when the target was set or has two now. Our server works this out from each person’s number and sends each phone in the team that has Move the Bus one answer for the whole team: the target, how much is still to go, and the most one person’s part can count for. It never sends anyone’s own number or part, and taking yourself off your team’s board does not take you out of it. How far it moves between two looks can still show what one person lifted or did, if only they synced in between, and in a small team the target and how far it moves can show what the others lifted, for example in a team of two by taking away your own. When nothing is left to go, our server records when, and writes at most one line in the team feed, naming nobody. For each team and week it stores the target, how many people were in the team when the target was set, the team’s total weight lifted and saved workouts that week, how much of that counted (to set the targets after it) and when it was moved, and nothing that says who lifted or trained. These stay when someone leaves, until a weekly job deletes them about six weeks after the start of the week they are about.
The Raid. Every other week the same target is shown as a Raid: a boss with a health bar, whose name and crest your phone picks from a fixed list using the team and the week, so every phone in the team on the same version of the app shows the same one. Nothing more is sent or stored for it.
Sport on a team. The parts below, except On rehab, show only on a team where somebody’s phone has said their saved workouts include a drill, practice, game or tryout. Your phone never sends your sports, levels or goals on its own: only that yes or no, counts of what you did and which days you did it, if you turn on “Show my teams I’m on rehab”, that you are on rehab, while you are shown as training now, the kind of drill your last set was, such as “shooting”, which can show a sport (see Teams: Training now, shouts and Iron Hour), and your Combine entry and which sport clubs your log has reached, as described under Teams: the Combine, sport clubs and callouts below. What you choose to post in the team’s feed or send as a callout can name a drill or a workout, and your cleared tick and “Show my coach when I’m on rehab” are described under On rehab below. Your skill reps, days with skill work and games reach your team’s phones beside your first name; the sport counts in your workout summary reach only our server. Every number in this section is something you did, such as an attempt, a day or a game, and never a make, a percentage, a distance or a time. Skill reps are attempts you log at a drill, made or not; warm-ups and cool-downs don’t count, a counted set, such as dribbles, adds at most 50, and a distance or time drill counts only once its distance or time is logged.
Goals. A team with sport can aim at skill reps, days with skill work or games this week, as a team total, the same way as any other goal.
Ball Every Day. Like who trained today, our server works out how many people in the team put in skill work today, counted from the members whose phones send skill days, and, for your phone only, whether you are one of them, with the same rules: at least three people counted, including you, or in a team of two only that everyone did. In a small team a count can still show that everyone, or nobody else, put in skill work today. It sends the count and stores nothing. When you put in skill work on seven days in a row, or fourteen and so on, and you share your workouts with that team, the team feed can say so under your first name, the same way it says a workout streak.
Make It Rain. In a team of two or more with sport, Make It Rain sets one target a week in shots, which are the skill reps described above. The first time in a week that a phone with it syncs, our server sets the target, which stays the same all week: the median of how many shots counted in up to four weeks before it, plus 15%, and never fewer than 500. Each stretch or mobility workout in your summary takes 25 shots off, up to half the target, and no one person’s part (their shots and those workouts together) counts for more than 40% of the target, rounded up, or half if the team had two people when the target was set or has two now. Our server works this out from each person’s summary and sends each phone one answer for the whole team: the target, how many shots are still to go, and the most one person’s part can count for. It never sends anyone’s own number or part, and taking yourself off your team’s board does not take you out of it. How far it moves between two looks can still show what one person did, if only they synced in between, and in a small team the target and how far it moves can show what the others did, for example in a team of two by taking away your own. When nothing is left to go it writes at most one line in the team feed, naming nobody. For each team and week it stores the target and when it was set, how many people were in the team then, the team’s shots, how many counted and when it was done, and nothing that says who did what. These stay when someone leaves, until a weekly job deletes them about six weeks after the start of the week they are about.
Team sessions. On a team with sport, the app offers names for a session from a fixed list: “Practice”, “Shootaround”, “Open gym” or “Game”. Our server writes those words, so anyone in the team can post one, at any age. A typed name still needs you to be 18 or over. Posting a game this way puts its day and time in the team’s sessions; logging a game does not. The team gets the count of games above, a Bingo square or a weekly title can name you for logging one this week, and that count going up after a sync can show which day.
On rehab. If you mark a sport injury on your sport goal, it stays on your phone, except as below. If you then turn on “Show my teams I’m on rehab”, each sync sends your teams that you are on rehab, and nothing else: not what happened or since when. This goes to every team you are in, with sport or not. Your teams see “on rehab” beside your name; their boards and the Meet list you without a place (the Numbers tab not at all), and Draw Week leaves you out of its pairs, until you say you are back or turn it off. This switch sends nothing to your coach, though a coach who is in one of your teams sees it there like anyone else in it. Separately, whether or not you show your teams you are on rehab, a coach you turn on “Show my coach when I’m on rehab” for is sent whether you are on rehab (see Your on rehab line), and a coach you turn on “Send my cleared tick to my coach” for is sent the day of a concussion’s cleared tick (see Your cleared tick).
The Combine. On a team where somebody has logged sport, the team has a monthly Combine on the same days as the Meet: the last 14 days of each month, by your phone’s date. A Combine test is a drill a sport’s Combine uses, scored by a time, a distance, a speed or a fixed number of shots; a match score, such as bowling’s, is never one. During those days, if you did a Combine test in them, each sync sends our server your entry: how many Combine tests you did, and how far above your own usual you are, as a whole percentage, worked out on your phone from your log, each test’s best in those days against the middle of your best in each of the three months before, timed the same way, with a lower time counting as better. The percentage is sent only when you are above your usual: level, below it, no usual yet, or on rehab for a sport all send none, so the team is not told which. In a team that counts Numbers, while your own numbers are on for it, the entry also carries each test’s best, with “h.t.” kept inside a hand time, which names the tests and so can show your sport or that you train seated or in a chair. Our server keeps one entry per person per month, replaced at each sync in those days, with when it was last replaced, and shows it to the people in your team while the team’s board is on and you are on it: those above their usual first, highest first with no place, then everyone else in the Combine in first-name order, each with how many tests they did, and “on rehab” for someone who shows their teams they are on rehab. Each test’s best is shown only under the same conditions as your numbers (see Your numbers). Entries are kept until the end of the month after the one they are about, and deleted within a week after that, or sooner if you leave; switching your numbers off, or the team switching to Consistency, deletes the tests’ bests and keeps the rest.
Sport clubs. In a team that counts Numbers where somebody has logged sport, the team also has three sport clubs: The 1,000-makes month (1,000 makes or more in one calendar month at drills you score by makes), The 80% club (100 shots) (80% or more of at least 100 shots at one drill in one session, with one hand for a drill you log by side) and Ten Straight (ten makes in a row at one drill, counted from the Drill Screen’s taps only), and the team can build more makes-in-a-month and makes-in-a-row clubs. Games, warm-ups and cool-downs never count toward them. They are results, so they work like lift and reps clubs: your phone asks to be put in one only while your own numbers are on for that team, they write no feed line, the team is shown that you are in one only under the same conditions as your numbers, and switching your numbers off, or the team switching to Consistency, deletes our server’s record of which of them you are in.
Callouts. On a team where somebody has logged sport, you can stamp a set you logged in the last day and send it to one teammate as a callout. Nobody types anything: it carries the drill, from the app’s own list and never one you made yourself, its spot if it has one, how many tries and, for “Beat it” or “Match it”, how many went in. “Beat it” and “Match it” carry a result, so they work only in a team that counts Numbers, between two people whose own numbers are on there, and while your own numbers are on there they are the only callouts you can send; anywhere else a callout is “Match me”, on how many tries at one drill that day. If either of you switches your numbers off for that team, or the team switches to Consistency, our server deletes your “Beat it” and “Match it” callouts there, whatever their state, and nothing more is sent for them. Only someone the team feed lets post (18 and over) can send one, and only to someone our server also holds as 18 or over. The person you call out can reply “On it” or “Not this week”, or not at all, and only you are shown their reply. Once they say “On it”, their phone checks their own log after each sync with that team, and their next log of that drill at the same number of tries (and the same spot, if yours named one) sends our server how many went in, or, for “Match me”, their most tries at it in a day once that reaches yours. If it does what yours asked (more for “Beat it”, at least as many for “Match it” and “Match me”), you are both shown “Callout won.” with their number. If not, it ends quietly: it leaves their list, and you are never told. Only the two of you are shown a callout, and it writes nothing in the team feed. Our server keeps each callout: who sent it to whom, its team week and when it was sent, the drill, spot, kind (“Beat it”, “Match it” or “Match me”) and numbers, the reply and when it was given, whether it was won or ended, and the winning number. It answers a callout only in its own team week, and keeps one from each person to each other person a week. A weekly job deletes it within a week after it is 14 days old, and leaving the team, being removed or deleting your profile deletes the ones you sent or were sent there. Someone you blocked in a team, or who blocked you there, cannot send you a callout or be sent yours, and neither of you is shown the other’s. Nothing reaches anybody’s phone until their app next syncs with the team. Your phone keeps, for each callout you said “On it” to, how many matching sets or tries you had already logged then, so only your next log counts.
What a team counts. Every team counts showing up, such as sessions and days trained. That is Consistency. A team can instead be started as a Numbers team. What a team counts is picked when it is started, stored with the team, and shown to anyone who enters its invite code. The team captain can switch a Numbers team to Consistency, and a Consistency team can never become a Numbers team. When a team switches, our server turns everyone’s Numbers switch off for it, deletes its copy of everyone’s numbers and the Meet entries it holds for that team, along with the team’s lift and reps clubs and everyone’s places in them, and writes one line in the team feed that names nobody, though only the team captain can switch a team.
Your numbers. In a Numbers team nothing more is sent about you until you switch your own numbers on for that team. Only you can, and only at 18 or over: our server checks the age your phone has told it, the same record the team feed uses. Then each time your phone syncs with that team it also sends our server, for the team week (Monday to Sunday, by your phone’s date): the weight you moved on working sets, your heaviest working set, your reps on working sets, your minutes of timed cardio and of timed mobility and stretching, your longest timed set outside cardio, and how many personal records you broke. The first of these is the same number Move the Bus counts. Our server keeps them with your place in the team, replaced at each sync, and stores them only while the team counts Numbers and your switch is on. It shows them to the people in your team, beside your first name and ranked, on the Numbers tab of the team’s board, while the board is on and you are on it, and only for the current week. While you show your teams you are on rehab (see Teams: sport), the Numbers tab leaves you off, though our server still sends your numbers to your team’s phones. So in that team, the lines above about no teammate being shown your share of the weight you lift no longer hold. Whether your switch is on is kept too: your team can tell it is on when your numbers appear and, if you trained that week, that it is off when they do not. Turning it off stops your phone sending them and deletes our server’s copy of them and the Meet entries it holds for you in that team. The weight you lift still goes to our server for Move the Bus, as in any team, and in a Numbers team, when everyone else’s numbers are on, Move the Bus’s “to go” can show what you lifted that week, even with yours off or you off the board. “Keep my numbers off every board” in Settings stops your phone sending them to any team, and each team’s copy is deleted the next time your phone reaches it. Leaving a team deletes them too. On a team where somebody has logged sport, the same switch also decides each Combine test’s best, the sport clubs and “Beat it” and “Match it” callouts (see Teams: the Combine, sport clubs and callouts).
The Meet. A Numbers team also has a monthly Meet on three lifts the team picks from a fixed list. Any member can change them, and the team feed says which lifts, naming nobody. During the last 14 days of each month, by your phone’s date, if your numbers are on for that team, each sync sends our server your entry: for each of the team’s lifts, your best estimated one-rep max from a working set in those days, worked out on your phone from your log (0 for a lift you did not do); how your total compares with your own usual, as a percentage, from your own log of the three months before; and how it compares, in pounds, with your own total for the last 14 days of the month before, from your log, whether or not you entered that meet (the table calls this “vs last meet”). Either comparison is left out when there is nothing to compare with. Because your total is shown beside them, your team can work out your usual and your total for the month before from them, including from before you switched your numbers on. Our server keeps one entry per person per month, replaced at each sync in those days, with when it was last replaced, and shows it to the people in your team, beside your first name and ranked (without a place while you show your teams you are on rehab; see Teams: sport), under the same conditions as your numbers, through the month after. If anyone changes the team’s lifts during those 14 days, by the date on their phone, our server deletes that month’s entries at once, and each person’s phone works its entry out again on the new lifts at its next sync in those days. Last month’s result keeps the lifts it ran on. Entries are kept until the end of the month after the one they are about, and deleted within a week after that, or sooner if you switch your numbers off, the team switches to Consistency, or you leave.
The clubs. Every team has The 100-sessions club and The 30-day club, and a team that counts Numbers also has The 225 club. A team that counts Numbers where somebody has logged sport also has the sport clubs under Teams: the Combine, sport clubs and callouts. Anyone in a team can build up to twelve more by picking what a club counts, a number and, for a lift or reps club, a movement from a fixed list, so no club has a name anybody typed. Our server keeps the clubs a team built and when each was built, and keeps nothing with a club about who built it. The team feed says when a club is built, naming nobody, though if whoever built it has already reached it, they are usually the first one shown getting in. Only the team captain can remove a club, and only one the team built; the team feed says so, naming nobody.
Getting in. After your phone syncs with a team, it checks your own workout log on your phone, and when you reach one of that team’s clubs, it asks our server to put you in. This counts your whole log, including workouts from before you joined the team. Nothing from your log is sent for this, only which club. Our server keeps which of the team’s clubs you are in, with your place in the team. A run of days in a row that starts again, or a workout you delete, does not take you out. The people in your team are shown the first names of the people in each club, never a list of who is not in one, though anyone can compare a club’s list with the team’s member list and see who is not on it. A sessions or days-in-a-row club lists you whether or not you are on the team’s board or share your workouts with the team. When you get into one, one line in the team feed says so with your first name and its time, which is often soon after you saved the workout that got you in. Our server writes that line, as it does the line saying a goal was set, so nobody can remove or report it in the app; email us to have one taken down. Like other team feed posts, it is deleted after twelve months.
Lift and reps clubs. These say what your body did: that you logged a working set of a barbell lift at a weight or more, or that many reps of a movement in one working set. They exist only in a team that counts Numbers. Your phone asks to be put in one only while your own numbers are on for that team, and our server refuses otherwise. They write no feed line, and the team is shown that you are in one only under the same conditions as your numbers: the team’s board is on and you are on it. Switching your numbers off for a team, including through “Keep my numbers off every board” in Settings, deletes our server’s record of which of its lift and reps clubs you are in. When a team switches to Consistency, our server deletes its lift and reps clubs and everyone’s places in them.
What your phone keeps. Your phone keeps its own list of the clubs you have been in, in each team. It uses it to ask our server to put you back in a club you were in, such as when you switch your numbers on again or rejoin a team, and to give you Shield, a symbol for your avatar mark. Leaving a team, being removed from it, or deleting your profile deletes your places in its clubs from our server, and when the team captain removes a club, everyone’s places in it go too.
Training now. If “Share my workouts with this team” is on for a team, then when you log the first set of a workout in the session player, the app tells our server, and the team sees your first name under Training now (their app also receives when your workout began, to put the names in order). It shows for up to 3 hours, or until you save or discard that workout. If the last set you logged in that workout was a sport drill, the team also sees beside your name what kind of drill it was, such as “shooting”, “striking” or “skill work”, and never a number; your next set changes it, and saving or discarding the workout takes it away. The kind is worked out on your phone from the drill’s movement, never from anything typed. Our server keeps one row for you in that team: when that workout began, by our server’s clock, whether it has ended, and that kind of drill, if there is one. Your next workout replaces it, so this row keeps no record of when or how often you trained. A job runs every hour and deletes rows that began more than 3 hours ago, so each one is deleted within 4 hours of when it began. A quick log never shows you as training. Turning sharing off for a team deletes your row there, at once or at your phone’s next sync with that team, and the hourly job deletes it anyway. Someone you blocked in a team, or who blocked you there, is not shown that you are training or the shouts sent to you, and cannot send you a shout, and you are not shown theirs.
Shouts. While someone is shown as training, a teammate can send them one of six fixed phrases, such as “Finish it”. Nobody types anything. Our server keeps which phrase, who sent it to whom and when, so the person can see it in their workout, and a second job, also every hour, deletes it once it is more than 3 hours old, so it is deleted within 4 hours of when it was sent. A shout also goes in the team feed as a line naming who sent it to whom, with its time, kept, reported and removed like any other post. So a shout you are sent stays in the team feed with its time, naming you, and shows that you were training then; the feed leaves that line out for anyone you blocked in the team, or who blocked you there. Only someone the team feed lets post (18 and over) can send a shout, whether or not they share their own workouts. Each person can send each teammate one shout per workout. On a team where somebody has logged sport the app offers five more fixed phrases: “Splash”, “Next play”, “Lock in”, “Big game” and “Wheels”.
Iron Hour. A team captain can pick one hour a week for the team. Our server keeps the day and the time with the team, and when it was set, and the team feed says when it is set or cleared. If a team has one, each time your phone syncs with that team it also sends how many of your workouts in the last seven days you started in the session player during the team’s Iron Hour since it was set, worked out on your phone from your log, whether or not you share your workouts with that team. Our server keeps that one number with your place in the team, replaced at each sync. When the team’s goal is a total of sessions this week, our server adds it once more to that goal, so those workouts count twice there; nothing else counts it. It is never shown beside your name, but the goal says how many sessions Iron Hour counted twice for the whole team, so in a small team a teammate can work out yours, for example in a team of two by taking their own from it. During the hour, each member’s team card shows the first names of the people whose Training now row began during that member’s own Iron Hour, by their phone’s clock, in the order they started, including anyone who has since finished. Any reminder for it is set on your phone, for up to six teams, and only if you switch it on. The reminder shows the team’s name, so anyone who glances at your lock screen can read it.
Team vs Team. A team captain can make a challenge code and read or send it to another team’s captain, who enters it on their own team’s Team vs Team card. A team can play up to three other teams at once, and any two teams only one rivalry at a time. Each week our server works out one number for each team from the weekly workout summaries its members’ phones already send (see Teams: your weekly workout summary, above) and, for weight moved, from the weight lifted since Monday that Move the Bus already uses. Nothing new is sent from your phone for it. The number is for the whole team, so a bigger team cannot win by having more people: sessions per person, the share of the team that trained, the days everyone on the team trained, or weight moved per person. Everybody still on the team who was on it when the week began (Monday, midnight UTC) counts, including anyone whose phone sent nothing that week, who counts as having done nothing, but not anyone whose version of the app sends no weekly summary; in the week a rivalry starts, everybody on the team when it was accepted counts; someone who joins later counts from the next week. So it is your team’s number, not yours, but in a small team the other team’s members can sometimes work out something about the few people in it, and in a team of one it is that person’s own.
What the other team sees. Your team’s number each week, how each week went, your record against them, your team’s crest, and a name of two words: one the team captain picks from two fixed lists, or until then one the app makes from the team. Never your team’s own name, and never anybody’s name, number or anything else about anyone in it. The team feed of each team says when a rivalry starts and, for each week both teams have a number, how it went, naming the other team by that two-word name. A week is settled the first time a phone in either team syncs after Monday has begun everywhere (12:00 UTC on Monday). Either team’s captain can end a rivalry at any time; no line says it ended, and the other team stops seeing it. The week under way then does not count, and before 12:00 UTC on Monday neither does last week.
Weight moved. Only between two teams that count Numbers, each with at least four people whose numbers are on for that team, and where our server holds everybody on both teams as 18 or over. Each team’s number is the weight lifted since Monday by the people whose numbers are on, divided among them. If somebody our server does not hold as 18 or over is on either team, that team has no number while they are. When a team has no number because of these rules, the other team is told that the rules for weight moved are why, never which one or who.
What our server keeps. Each rivalry: which team made the code and which accepted it, what it is played on, when it started and when it ended, and each team’s number and result for each week. These are about the teams, not about anybody in them, and they are kept with the teams, so the record continues if the two teams play again. A team is not deleted when its members leave, so they have no set end date; email us to have them removed. Leaving a team does not take you out of the numbers your team was already given. A challenge code is kept until it is used or the captain makes a new one, and stops working after seven days. The two words a captain picks are kept with the team, and the team feed says when they change, naming nobody.
Seasons. A team with a Team vs Team rivalry during a season is in a league with every team joined to it by rivalries that season. A season is six weeks, then a fallow week. Each week our server works out the team’s score, the share of its people who trained, from the weekly workout summaries its members’ phones already send; nothing new is sent from your phone for it. It is the team’s, never yours, though in a small team it can say something about the few people in it.
What is kept, and who sees it. Our server keeps each team’s score for each week and, once the season is settled, its place, points and division, whether it moved division, which league it was in and when it was settled. A season is settled the first time a phone in its league syncs in the fallow week, from 12:00 UTC on its Monday, or in the week after. These are kept with the team and are not deleted after the season, so the record of past seasons stays. Every team in the league sees each team’s two-word name, crest, points, place, division and whether it moved division, never anybody in it. Leaving a team does not take you out of its past scores.
The team crest. Every team has a crest: a symbol and a colour from two fixed lists of the app’s own pieces, which the team captain picks, or until then the pair the app gives the team. Nobody can type or upload anything into it. Our server keeps the team’s crest and a record of each week the team hit its weekly goal (never a meals goal) and each season it scored points in, with how many there are and when the last one was; the crest’s ring and finish change with that count and how recent the last one is. Apart from the symbol and colour a captain picks, nothing new is sent from your phone for it. These are about the team, not anybody in it, and they are kept with the team, which is not deleted when its members leave (email us to have a team removed). Everyone in the team sees the crest, and the team feed says when it changes, without saying who changed it. The teams it plays in Team vs Team and the teams in its season league see its symbol and colour, never how far it has come.
Season pieces. Once a season is settled, when your phone next syncs with a team our server tells it which seasons you earned with that team: each season of a league the team was in that was settled after you joined. Your phone keeps that list, and each season’s colour, ring and glow are yours to wear on your avatar mark. If you wear them, they are sent as your mark, like any other.
Training tournaments. Anyone in a team can start a training tournament from a team’s Competitions card, and is its head director. It has a name made of two words from fixed lists, a format (a league or a knockout) and match days. Its directors get one code: a team’s captain enters the team with it, and a director lets the team in. Anyone else handed the code can ask to help run it; their first name, as they gave it to the app, goes to the head director only, who lets up to five people help. Directors see each team’s two-word name and crest, how many of its people said they’re in, which teams sat it out, and the teams’ scores, never anybody’s name (apart from the first names of people who asked to help run it, to the head director), training, food or health.
What is sent from your phone. Before a tournament starts you can tap “I’m in”; our server keeps that you did, for which team, and when. You count for one team in a tournament, and only if you were still on that team when it started and had been on it for a week. Once it has started, and only if you were counted, each sync with that team sends which of the tournament’s match days, from today and the nine days before, you saved a workout on, by your phone’s own dates, and nothing else about them: not what kind of workout, how many, or anything about food. Any workout counts, including a stretch or a quick log. If you tap “Resting this round”, our server keeps which round you are resting; you get one in each tournament.
How a score is worked out. For each round our server works out one score for each team from those match days: the share of its counted people who trained on the match day, or the days trained each when a round is a whole week. People resting that round are left out, and so is anyone who has left the team and did not train in it. A round locks 24 hours after its last day has ended everywhere on Earth, which is 12:00 UTC two days after that day; until then a late workout still counts and the result is provisional, and after it the round’s scores are kept and do not change. The order of play, the byes and the coin that settles a knockout tie (after the share of each team that trained) come from a draw our server stores when the tournament starts, so every phone shows the same.
Who sees what. Your team sees its score each round, the score of the team it plays, the results, a league’s table and how many of its people are in; only you see your own row and whether you are resting. In a small team, though, its score and its count of people in can show that everyone, or nobody else, trained, that somebody is resting (a rest leaves that person out of the team’s score for the round), or who has not said they’re in. The team yours plays in a round sees your team’s score for that round, every team in a league sees the table (each team’s points, by two-word name and crest), and the directors see every team’s scores; none of them sees your team’s own name or anybody in it, though in a small team a score can say something about the few people in it. A league’s table is not shown if anybody counted in it is under 18 by our server’s record. Your team’s feed says when it is let in, when the tournament starts or it sits one out, when it is over, and when it is on again. Nobody gets a notification; results show when the app is opened. If your team’s captain pulls it out, a round whose day has already begun anywhere in the world is still decided on its scores, later rounds go to the other side, it leaves the league table, and nobody is told why.
What our server keeps, and for how long. The tournament, its directors and the first names of people who asked to help run it, its teams, who said they’re in for which team, the stored draw, and each round’s team scores and results. Which match days you trained on is deleted about four weeks after its last round locks; everything else about it about six months after its last round locks, or along with the match days if its results were never worked out; and a tournament that never starts about two months after it was made. If a director runs a finished tournament again, its directors, with the first names they gave, and its teams are carried into the new tournament and kept on that tournament’s dates instead. When you delete your profile and our server accepts that request, your “I’m in”, your match days and any director place are deleted from our server. Leaving a team does not take you out of rounds already played. Your phone keeps the tournament’s piece, and its trophy if your team won, on your own shelf, and the match days on your calendar while it runs.
Organisation vs Organisation. If a gym, clinic or other organisation covered your access with a member card, and you are in one of its gym teams (a team started as gym-only on its cards), its owner can play another organisation’s owner in Organisation vs Organisation. Each week our server works out one number for each organisation from the weekly workout summaries of the people in its gym teams, the summaries described above, counting each person once, and not anyone whose version of the app sends no weekly summary: sessions per person, or the share of them who trained. Nothing new is sent from your phone for it. Teams on a coach’s card, or on a card a coach hands out, never count, and the anonymous check-in count is never used for it. Someone who joined the gym team after the week began counts from the next week (in a rivalry’s first week, everyone in the team when it was made counts). A person whose phone has not sent anything yet counts as having done nothing. Each profile counts once, even in two of the organisation’s teams.
What is shown. Each organisation’s owner, and its members on their Organisation screen, see both organisations’ names and their weekly numbers, results and record; never a team or anybody’s name, though when only a few people are counted a number can say something about them. A number is shown only once at least five people are counted in it; below that there is no number.
What our server keeps. Each rivalry between two organisations, and each one’s weekly number and result, for as long as both organisations’ cards exist. An owner’s code is kept until it is used or the owner makes a new one, and stops working after seven days.
Organisation challenges. If a gym, clinic or other organisation covered your access with a member card, and you are in one of its gym teams, its owner can run one challenge at a time for its members: a number of sessions together, or everyone training a set number of times a week. Each week our server works out one number for the organisation from the same weekly workout summaries as Organisation vs Organisation, counting each person once, and not anyone whose version of the app sends no weekly summary: the sessions they saved, or the number of them who trained that many times. Nothing new is sent from your phone for it. Teams on a coach’s card, or on a card a coach hands out, never count, and the anonymous check-in count is never used for it. Someone who joined the gym team after the week began counts from the next week (in a challenge’s first week, everyone in the team when it was made counts). A person whose phone has not sent anything yet counts as having done nothing. Each profile counts once, even in two of the organisation’s teams.
What is shown. The organisation’s owner, and its members on their Organisation screen, see the challenge and its count; never a team or anybody’s name, though when only a few people are counted a number can say something about them. For a times-a-week challenge, that count is how many of the people counted trained that many times, out of how many were counted, so in a small organisation it can show that everyone, or nobody else, did. How far the count moves between two looks can show what one person did, if only they synced in between. A week has a number only once at least five people are counted in it; below that there is no number, and members are shown nothing that week. You also see how many of your own sessions count toward it this week, worked out from your weekly summary when you open the screen and shown only to you.
What our server keeps. The challenge, and each week’s number with how many people were counted in it, until the owner ends it or starts the next one, and for no longer than the organisation’s card exists. Your own part is not kept.
Your food is private. A team or a coach gets no count of your food unless you turn it on for that team or that coach, and it is off for everyone until they do.
A coach can open a private group space for one of their groups, or for all the clients they coach. A group space works like a team and shares the same things, as the Teams sections describe them. Everyone who has joined sees your first name, the counts a team shows (such as workouts done, days trained and streaks), your food count only if you switch it on there, and what you post, and so does the coach who runs the space, whose own first name and counts the space shows too. As in a team, your phone also sends our server the short workout summary with each sync, which no other phone receives itself (see Teams: your weekly workout summary), and the weight you lift, which is added into one total for the group: nobody is shown your share of it, though in a small group someone can sometimes work it out. You are in a space only after you tap “Join” yourself. Nobody can add you, and there is no invite code. Your Health Hub is never shared. Group spaces are for people 18 and over. Opening a space for a group shows it as a group: every adult client in the group sees its name under “From your coach”, whether or not they join, and everyone who joins sees who else did. Our server keeps who has joined each space, as it does for a team; the coach who runs a space sees the first names of the people who joined, and can remove a post or take someone out of the space. If a coach opens a group’s space inside an organisation they coach for, that organisation sees the group’s name and, once five or more have joined, its totals (how many joined, how many saved a workout this week and how many workouts they saved), never a member’s name. In a small group a total can still show that everyone, or nobody, trained. You are taken out of a space when you stop sharing with the coach, when the card that covers your coaching ends, when you leave the group, or when the coach stops coaching. Leaving a space yourself needs a connection, as leaving a team does, and you stay the coach’s client. Groups an organisation makes for its own members are built but switched off.
Leaving a team needs a connection. When you tap “Leave this team”, your phone asks our server to take you out of the team, and the app forgets the team on your phone only when the server answers that you are out. If your phone is offline, or that answer does not come, the team stays on your phone, the team screen says you are still in it, and your phone keeps syncing with that team as before. If the answer was lost after our server had already taken you out, the team comes off your phone the next time you open your teams online.
Leaving a team deletes your name and your counts from it, and your places in its clubs, though feed posts that name you, such as a session you put up, a welcome or a change of captain, stay. Your team’s Team vs Team numbers and its season scores stay with the team, because they are the team’s and not yours. The team’s crest, and how far it has come, stay with the team too. In a training tournament, the rounds already played keep their scores, and the match days you trained on count for the team in any round you trained in.
Stopping needs a connection. When you tap “Stop sharing with your coach”, your phone asks our server to end the link, and the app drops the coach only when the server answers that it is ended. If your phone is offline, or that answer does not come, the coach stays on your screen, the app says so, and your phone keeps sending that coach how many sessions you completed this week, how many sessions they assigned, how many days this week you logged a recipe if you turned on “Let my coach see my food” for them, your first name and your age group, as before. It also keeps sending the rest of the weekly summary described under Coaching: what your coach sees. If the answer was lost after our server had already ended the link, the coach comes off your screen the next time you open the app online. Your coach is not told either way.
When you stop sharing, or your coach removes you, our server keeps the ended link (your first name, age group, weekly target, the note your coach typed about what you are working on, and your board and food choices) and the earlier weekly records described in this policy (sessions done and assigned, recipe days if you had switched that on, rules at their full run, whether you did the challenge, and the Coach vs Coach counts) until you or your coach delete a profile in the app, or you ask us to remove them. Your coach’s app no longer shows you. An ask you made to join one of that coach’s teams is deleted when the link ends. The marks, season awards, picks, drill numbers and rules set on you alone that this policy says are deleted when a link ends are deleted as described. If you stop sharing yourself, you also stay in that coach’s groups on our server until the coach removes you or a profile is deleted.
Our server also keeps the last time you tapped “I’m training now”: one time for each coach, replaced each time you tap, which your coach is shown for only a few hours. It is not deleted when the link ends or when either of you deletes a profile; email us to have it removed.
Your coach can pick, for you alone, three lifts for your own monthly meet and up to three one-tap shortcuts, each a movement from the app’s library and an amount from a fixed list. Our server keeps those picks with your link to that coach, as ids and fixed keys, and sends them to your phone, which shows only movements from its own library, in the library’s own words, never words your coach typed. When the link ends, our server deletes them, and your phone drops them the next time it checks in. Your meet result is worked out on your phone from what you log and is not sent to your coach or anyone else. If you rename a shortcut or take it off Today, that stays on your phone and your coach is not told. One tap on a shortcut logs it like any quick log.
Your coach can also set you a weekly target: sessions, days with skill work, or tries or makes at one drill from the app’s library, as a number and fixed keys. Our server keeps it with your link to that coach and sends it to your phone, which counts it from your own log and shows it (“Free throws · 134 / 200 made · 3 days left”); nothing about that count is sent back, and nothing records whether a week’s target was met. Your coach sees how you are doing only from the weekly summary your phone already sends them (see Coaching: what your coach sees), and a drill’s numbers while you send them through “Send my drill numbers to my coach”. A target your coach sets for a group stays on their screen.
Your coach can also type a short note on your page about what you are working on together (up to 160 characters, for example “balance”), and can name and describe groups in their own words. Our server keeps the note with your link to that coach, and a group’s name and description with the group. The note and the description go only to your coach’s app, not to you or to anyone else; a group’s name also reaches assistant coaches and helpers as described under Coaching: your coach’s sports team, and, if your coach opens a group space for the group, every adult client in it and everyone who joins it, and the organisation the space is counted for, if there is one (see Coaches and organisations: group spaces). The note is kept as described under Stopping sharing with a coach.
A plan your coach sends as part of a block of weeks can carry the week it belongs to, how many weeks the block runs and a phase from a fixed list (such as Build or Deload). Your phone shows “Week 3 of 6 · Build” from those, and once the last session of the block’s final week has passed it files a win on your phone, the next time you open Home within two weeks. Nothing about it is sent back. For a sport drill, a plan can also carry how many sets, how many tries in each, and one aim your coach set (a percent made, a time, or a mark in the drill’s own unit, such as a distance, speed, score or level), as numbers from the app’s own ranges, never words. Your phone shows them beside the drill (“Free throws · 5 × 20 · Coach’s aim: 70%”), and “Count it” opens the drill with your coach’s aim, if they set one, under your count. Sending that plan sends nothing back about how you did.
Once a coach has sent you a drill in a plan, you can turn on “Send my drill numbers to my coach” for that coach, from the phone that joined with their code. Then, each time your phone sends that coach your weekly summary (when you save, edit or restore workouts, when you open Triumph, and right after you switch this on), it also sends this week’s and last week’s numbers (Monday to Sunday on your phone) for each drill from the app’s library you logged outside a game: which drill, and how many tries you took. If your phone says you are 18 or over, it also sends how many went in (only when every set that week counted makes), your best mark and your best time, and whether that time was hand-timed; our server keeps those only on a link it holds as 18 or over. For a drill you took at the five shooting spots, at the free-throw line or in the strike zone, it also sends how many tries you took at each spot and, if your phone says you are 18 or over, how many went in there; our server keeps those makes only on a link it holds as 18 or over. It never sends a drill you made yourself, the skin, socket and foot check, a game’s numbers, or anything you typed, except, if you are signed in, the sign-in token, which contains your email address (see Optional accounts and sign-in). Our server keeps each week with your link to that coach until its Monday is 91 days back, and deletes all of them when you turn the switch off or the link ends. That coach sees, on your page in their app, each drill’s tries and, where it was kept, its make percent and bests for your latest week, and how that make percent went over the last eight weeks; your tries at each spot and, where they were kept, the makes there, over this week and the three before it, drawn on a court or a strike zone; and, if they mark you as a player on their sports team (which they can do only for someone 18 or over), those spots added together with the other players’ who send theirs, with no names, on their team page; and, if you play for their sports team, each drill’s tries and make percent for the season on their History page; and, if you are in a group they put inside another of their groups (such as Guards inside Varsity), your tries this week beside the others in that group, on that group’s page in their app. Nobody they work with is sent them, and neither are your teammates.
Once a month, your coach can give one person they coach a mark: a short phrase from a fixed list (“Turned up when it was hard”, “Did the boring part”, “Came back” or “Held the line”; the app also offers a coach of a sport “Did the boring reps”, “Next-play mentality” or “Best teammate”), never words they type. A coach gives one mark a month, cannot change it once it is given, and cannot give another that month. The month is the one on your coach’s phone the day they give it. If they give it to you, our server keeps your coach’s random number, yours, the month, which phrase it is and when it was given. It sends the mark to your phone; while you are on their roster, your coach’s app receives the marks they gave you from last month on, counted by our server’s calendar (UTC), and shows this month’s. No other person they coach, no team and no board is sent it, and nobody is told who did not get one. When your link with that coach ends (you stop sharing, they remove you, or an organisation ends the link), our server deletes it within a day, and a mark your phone had not received by then never reaches it. If the sponsored time on the sponsor code that linked you to that coach runs out while the link stays, it is not deleted, and it still reaches your phone. It is also deleted when either of you deletes the profile in the app and our server accepts that request (a deletion made offline deletes nothing there). So that a month stays given after a link ends, our server also keeps which months each coach has given a mark in, without who it went to, and sends that coach’s app the ones from last month on; it is deleted when that coach deletes their profile in the app and our server accepts that request. Your phone keeps its own copy in your Trophy case, also after the link ends, and Home celebrates it once.
If your coach has picked the season their team is in (such as Fall 2026), they can give each of their players one season award for it, from a fixed list (“MVP”, “Most Improved”, “Best Teammate”, “Hardest Worker”, “Defensive Player” or “Coach’s Award”), never words they type. Any number of people can be given the same one, and once given it cannot be changed that season. If they give you one, our server keeps your coach’s random number, yours, the season, which award it is and when it was given, and sends it to your phone; while you are on their roster, your coach’s app receives the season awards they gave you. No other person they coach, no team and no board is sent it, and nobody is told who did not get one. When your link with that coach ends (you stop sharing, they remove you, or an organisation ends the link), our server deletes it within a day, and one your phone had not received by then never reaches it. It is also deleted when either of you deletes the profile in the app and our server accepts that request (a deletion made offline deletes nothing there).
If a coach marks you as a player on their team, our server also sends your phone the season the team is in, as the season and year only. From those, From your coach and your Trophy case show a Season Card for each season once its dates have started: the practices and games you saved and the shots you took (tries at drills scored by makes, outside a game) between the season’s dates, whether your last Combine that season beat your first at any test, and any season award that came with it. It is worked out on your phone from your own log, and nothing on it is sent anywhere. Your phone keeps the seasons and awards it was sent, and your Trophy case shows them, also after the link ends; a season whose dates have not started and that came with no award goes if our server stops sending it before then, as when your coach picks another. If you tap Share on a card, your phone’s share sheet opens with one line: the season, your practices, games and shots taken, and an award’s name, never a Combine result.
Your coach’s team. Everyone a coach coaches is one team, named for the coach (such as “Coach Dana’s team”), with a crest each phone works out from the coach’s random number; nothing about the crest is stored or sent. Your coach’s own screen shows this week’s sessions against the sum of each person’s weekly target, each person counted up to their own target, from what it already receives; only your coach sees that. If your coach’s leaderboard is on for clients, our server also sends each person they coach the coach’s first name, so their screen can show the team’s name. Nobody is sent anybody else’s target or a total for the team. Nothing new is stored for it. If your coach typed a team name or picked the team’s sport, level or who plays, a person they coach who is marked as 18 or over is sent those with the coach’s first name (see Coaching: your coach’s sports team).
A block. Your coach can run one of their groups as a block: a start Monday and 4 to 12 weeks, kept with the group. Our server sends each member’s phone the start and the length, so it can show which week it is. While your coach’s leaderboard is on for clients, it also sends everyone in the group except anyone under 13 a table of the first names of the members who are on the leaderboard and, while the block runs, each one’s session count from their phone’s weekly summary this week (the sessions in the seven days up to when it was sent), so the others in your group see that you are in it, and your count. If a group was made around something its members share, such as an injury, they can see who else shares it. Someone whose phone has sent no summary this week is shown with a dash. Nobody under 13 and nobody who took themselves off the leaderboard is in anyone’s table, and taking yourself off works the same way as for the leaderboard. When the block ends, your phone files the same finish everyone in the group gets, the next time you open From your coach within two weeks while the block is still set, and keeps it in your Trophy case; nothing about it is sent back.
Coach’s Rules. Your coach can set you, or a group you are in, up to three Coach’s Rules each from fixed lists (the same day each week, or a number of sessions a week, for a number of weeks running, with a name from a list), never words they type. Our server keeps each one with your coach’s random number, yours or the group’s, and when it was set, and sends it to your phone. Your phone checks it against the workouts you save and, with the weekly summary, sends your coach only how many of their rules are at their full run (such as 8 Tuesdays of 8): never which one, the days, or how long your run is. A rule set on you alone is deleted when your link with that coach ends, and when either of you deletes the profile in the app and our server accepts that request; one set on a group goes when the coach removes it or deletes the group.
The week’s challenge. Your coach can set one challenge a week for everyone they coach, and one for a group you are in, from a fixed list (sessions, days trained or mobility sessions, with a number from 1 to 7). Our server keeps each with your coach’s random number, the group if there is one, and the week, deletes it about six weeks after its week began, and sends your phone the one that applies to you (your group’s, or else the team’s). Your phone checks it against the workouts you save and, with the weekly summary, sends your coach only whether it is done and which week that is about. Your coach’s app shows how many have said it is done, and on your own page in it, once your phone has said so, that yours is done; it never shows anyone as not done. If your coach changes or clears a week’s challenge, what phones had said for that week is emptied (for the whole team’s, everyone’s), and each phone says it again on its next summary. While their leaderboard is on for clients, the people they coach (not anyone under 13) are also sent the first names of those on the leaderboard whose phones said they did their own challenge this week; nobody is listed as not having done it, but because the leaderboard lists everyone on it, anyone can see who is not on this list. Nobody under 13 and nobody who took themselves off the leaderboard is named.
How many rules are at their full run and whether you did the challenge are kept on the same weekly record as your session count, and go when it goes. How long that record stays is under Stopping sharing with a coach.
Coach vs Coach. A coach can make a challenge code and share it with another coach, who enters it on their own Coaching screen. A coach can play up to three other coaches at once, one rivalry with each. Each week our server works out one number for each coach’s clients: sessions per client, or the share of the clients counted who trained. It counts the sessions you saved that week, Monday to Sunday by your phone’s calendar, as your phone has sent them by 12:00 UTC on the Monday after, when that Sunday is over everywhere. Your phone sends that count, and the whole of the week before’s, with the weekly summary it already sends your coach; our server keeps them only on a link that holds you as 18 or over, on the same weekly records as your session count, and each goes when its record goes. Your coach’s screen does not show them. Coach vs Coach uses no other fact about your training or food: never your food count or your readiness. How long those weekly records stay is under Stopping sharing with a coach.
Who is counted. You are counted for your coach only if your link with them is approved and still on their roster, our server holds you as 18 or over for that link, and you have not taken yourself off your coach’s leaderboard. Someone whose link was made after a week began (Monday, midnight UTC) counts from the next week; in a rivalry’s first week, everyone whose link was made before it started counts. A client whose phone sent nothing for that week counts as having done nothing, but not one whose summary for that week, or for the week before when it sent none that week, has no such count, as when it comes from a version of the app that does not send it: they are not counted that week. Nobody under 18 by our server’s record, and nobody it does not hold as 18 or over, is ever counted.
What is shown. Each coach sees both sides’ weekly numbers, how each week went and their record. Each side is shown to the other as a crest and a two-word name the app makes up from the coach’s profile, never the coach’s name. A number is shown only once at least five clients are counted on that side; below that there is no number, and the other coach is shown only that too few are counted. The other coach is never shown any client’s name or own number, though when only a few clients are counted a number can say something about them. Your coach already sees each client’s sessions, so from their own number they may be able to work out who is not counted, including someone who took themselves off the leaderboard; they are not told. You see only your own part: whether you are counted, and your own sessions this week as your phone last sent them.
What our server keeps. Each rivalry (which coach made the code, which accepted it, what it plays on, and when it started and ended) and each coach’s weekly number and result, for as long as both coaches’ profiles exist. Apart from each client’s own weekly counts (above), nothing about any client is kept for it. A coach’s code is kept until it is used or the coach makes a new one, and stops working after seven days. When either coach deletes their profile in the app and our server accepts that request, their rivalries and code are deleted.
The team’s name and sport. A coach can type their team’s real name (up to 40 characters, with no links, emails, phone numbers or handles) and pick what the team does, its level and who plays, from fixed lists. Our server keeps these with the coach’s code and sends them to the coach’s assistant coaches and helpers, to their players, to anyone holding one of the coach’s assistant coach or helper codes before they join (with the coach’s first name and, for an assistant coach’s code, the group’s name), and, with the coach’s first name, to the people they coach who are marked as 18 or over when the coach’s leaderboard is on for clients. With nothing typed, each phone builds the name from those choices. A coach can also pick the season the team is in (one of four seasons and a year, such as Fall 2026); our server keeps it with the coach’s code and sends it to the coach’s app and, as the season and year only, to their players, as Coaching: season awards and your Season Card describes.
Players. A coach can mark people they coach as players, and give a player a number (0 to 99) and positions from the sport’s fixed list. Only someone our server holds as 18 or over can be marked a player; a link made with a card a coach handed out never is. Our server keeps these with your link to that coach, sends a player the team’s practices and games, and deletes them when the link ends. Your link to that coach also carries a random number for you on the team: after your OK, assistant coaches and helpers are sent it, and keep it on their phones, to name you. It is not the random number the app made up for your profile.
Your OK. Until you tap “Show me to my team” on your own phone, nobody but your coach is shown your name as a player. If you are picked for a game before then, your coach’s assistant coaches see a count, never your name. Once your coach shows the team, your helpers and teammates see a count too. In a small team a count can say who it is. After your OK, assistant coaches and helpers see your first name, number and position, and if your coach enters the team in a game tournament, its directors see your first name and number for check-in (see Coaching: game tournaments). Your coach is not sent whether you said OK. Turning it on needs your phone’s own proof for that link; “Hide me from my team” takes it back, and it is deleted when the link ends or your coach stops marking you as a player.
Practices and games. A coach can put their team’s practices and games on their schedule: a day, a time, a length, and which of the two it is. Our server sends them to the coach’s players (with the team’s sport, so each phone uses the right word, such as Meet or Rehearsal), assistant coaches and helpers. It keeps each one until about 90 days after its day, and deletes it, with everything below that belongs to it, when the coach cancels it. A coach can also book a run of them at once (which weekdays, a time, a length and how long it runs): their app shows every date, they untick any, and our server writes the ones left as practices or games like any other.
Whether you can make a game. On each game you can tap “Can make it” or “Can’t make it”, or take your answer back. Our server keeps your answer with the game, your coach’s random number and yours, and when you gave it, and deletes it two days after the game’s day (by our server’s calendar, UTC), or with the game. Your coach sees every answer. After your OK, an assistant coach for a group you are in sees whether you said you can make it. Nobody else is ever sent your answer, and nobody but your coach is ever sent “can’t make it”.
Who is playing. A coach, or an assistant coach for the players in their own group, picks who plays each game and, where the sport has a starting lineup, who starts. Our server keeps each pick with the game, your coach’s random number and yours, whether you start, and when it was last changed. Until the coach shows the team, only the coach and their assistant coaches see the picks. After that, the coach’s players and helpers see the first names of the picked players who said OK, how many others are picked, and who starts. Only the coach’s screen, and an assistant coach’s for the players in their own group who said OK, lists who is not playing, though assistant coaches and helpers, who also see the players who said OK, can tell which of them are not picked. Picks go with the game.
Pitch counts. On a baseball team, the coach, their assistant coaches after your OK, and their helpers after your OK once the coach shows that game’s team, can keep how many pitches you threw in a game. Our server keeps the number with the game, your coach’s random number and yours, and when it was last changed, not who kept it, and sends it to the same people and to you. If you are 7 to 22, the ages Pitch Smart covers, your phone shows what Pitch Smart says about the count, from the age you set; your age is never sent. It goes with the game.
Testing. A coach can record a player’s Combine test results in their app’s Testing mode: which test, the number, how a time was taken and the day, for a player on their team our server holds as 18 or over. Their app keeps each result until our server takes it. The next time the coach opens Coaching or Testing mode, their app takes off one our server refuses for good, for example because the player has left their roster or is not marked as a player 18 or over, or the result is more than 14 days old; and, even with no signal, one more than 15 days old. Our server keeps a result it takes with your link to that coach and sends it to your phone, which asks whether you want to keep it. Keep it, and your phone saves it in your own log as a Combine your coach recorded. Whether you keep it or not, our server then deletes it; it also deletes one nobody answered after 60 days, and every one waiting when the link ends. Nobody else is sent them.
Assistant coaches and helpers. A coach can give a one-time code, good for seven days, to an assistant coach, tied to one of the coach’s groups, or to a helper, such as a team manager or team parent. Only someone whose phone says they are 18 or over, with no child’s or teenager’s record on our server, can look one up or use one. Our server keeps a code with the coach’s random number, the role, the group and when it was made, until it is used, or for up to a day after its seven days end. Once it is used, our server keeps the coach’s random number and the person’s, a random number for the pair, the person’s first name, their role, for an assistant coach the group, and when they joined, until the coach removes them, they stop helping, the group is deleted, or either of them deletes their profile in the app and our server accepts that request, except that the random number for the pair stays on a call they last changed in a game the coach shared, and as that game’s book of record, until that game’s calls are deleted (see Your coach’s active play). The coach sees their first name and role, and the coach’s players see their first name and role. An assistant coach or a helper is sent the coach’s first name and, for an assistant coach, the group’s name and which of the players who said OK are in that group, and is never sent anyone’s health, food, sessions, weekly summary or “can’t make it”, or the random number the app made up for anyone’s profile. An assistant coach can also be given a side to log, and is sent the calls of a game the coach shares with them, as Your coach’s active play describes; a helper is sent neither.
Your cleared tick. You can turn on “Send my cleared tick to my coach” for a coach, on a link our server holds as 18 or over, from the phone that joined with their code. Then, if you mark a concussion on a sport goal and tick “Cleared by my doctor or athletic trainer”, your phone sends that coach the day you ticked it. It sends nothing in its place once there is no tick: after you tap “I’m back to playing”, or once you mark a new injury. Each change is sent at once if your phone is online, otherwise the next time you open Triumph, and it is sent again each time Triumph reads your coaches. Turning it off deletes the day from our server, and so does the link ending. Because that tick is only offered after a concussion, your coach can tell it was about one. Nothing else about it is sent: not the injury, your steps, or the day you were hurt. Only that coach is sent it, and nobody they work with.
Your on rehab line. You can turn on “Show my coach when I’m on rehab” for a coach, on a link our server holds as 18 or over, from the phone that joined with their code. Then your phone tells that coach whether you are on rehab for a sport: yes from when you tap “I’m hurt” on a sport goal until you tap “I’m back to playing”, and no after that. Each change is sent at once if your phone is online, otherwise the next time you open Triumph, and it is sent again each time Triumph reads your coaches. Our server keeps the switch and that yes or no with your link; turning the switch off, or the link ending, sets both back to off. While it says yes, that coach sees “on rehab” beside your name on their roster and on your page in their app, and when they rank their roster by sessions done it lists you after the people it ranks, without a place. Nothing else about it is sent: not what happened, since when, or your steps. Only that coach is sent it, and nobody they work with. It is separate from “Show my teams I’m on rehab”, which sends your coach nothing, though a coach who is in one of your teams sees it there.
Your coach’s History page. Your coach’s app has a History page for their team that only they see. It shows the team’s practices and games our server still keeps (about 90 days after each one’s day); for each game, which of the players on the team now were picked, and which were picked to start; and, for each player on the team now, their first name, number and positions, and the number of sessions their phone sent them each week in that time, the same weekly number their roster already shows; and, for a player who turned on “Send my drill numbers to my coach” for them, each drill’s tries and make percent in that time. It shows nothing about your food, your Health Hub or your body, and nothing new is sent from your phone for it. Assistant coaches, helpers and teammates are never shown it. What your coach types or taps about a game there, such as the opponent or whether it was won, and who they tick as having come to a practice, stays on their phone and is not sent to anyone, except a game’s home or away and its score: our server keeps those with the game, so the coach’s other phones show them on History, and deletes them with the game. Nobody else is sent them.
Your coach’s Playbook. Your coach’s app has a Playbook for their team: plays, lineups, a depth chart, pitch counts, a play card and practice plans. It is kept on your coach’s phone, and nothing in it is sent to our server, to you or to anyone else, except the name and random number of a play your coach calls in a game they share with their assistant coaches (see Your coach’s active play). It can hold your first name and number, from their roster with your random number, or typed by your coach; where you bat, play and sit in their lineups, and your place in their depth chart; and an age and a pitch count or innings pitched your coach keeps there themselves. It holds nothing about your food, your Health Hub or your body. Assistant coaches, helpers and teammates are never shown it. Your coach can share a play card, which holds only play numbers, play names made from preset words and numbers, and the day it was made, or a Backup, themselves, through their phone’s own share sheet.
Your coach’s active play. On a baseball, softball, basketball or football team, your coach’s app can log a game’s calls by tap: what the other team was in, the call (from the sport’s fixed list, or a play from their Playbook), and how it went, from fixed lists, with the yards in football. A call has no place for a player: no name, shirt number or random number. A Playbook play’s name is made of preset words and the numbers 1 to 99. It is kept on your coach’s phone for about 90 days after the game’s day. If your coach shares a booked game with their assistant coaches, our server keeps that game’s calls with the game and your coach’s random number: each call’s own random number, the sport, its side (offense, defense or special teams), the call, or a Playbook play’s random number and its name made of preset words and numbers, the other team’s formation, the results and yards, when it was called by the calling phone’s clock, a revision number, the random number of the assistant coach who last changed it (none for the head coach), whether it was deleted, and when it last changed; and, for the game, which assistant coach holds the book of record, if one does, for football whether it is tackle or flag, when the coach shared it, and when that last changed. Our server keeps no opponent’s name, no player and no text anyone typed: the only typed parts of a call are the yards and the numbers in a Playbook play’s name. It deletes them when the coach stops sharing the game or cancels it, when the coach deletes their profile in the app and our server accepts that request, and otherwise with the game, about 90 days after its day. The random number of an assistant coach on a call, or as the game’s book of record, stays until that game’s calls are deleted, even after they stop helping. Only the coach and their assistant coaches are sent them; helpers, players and teammates never are. The coach can give each assistant coach one side to log, which our server keeps with their staff row; an assistant coach is told whether a side is theirs, the head coach’s or another assistant coach’s, never another assistant coach’s name. A name your coach gives a formation stays on their phone.
Several teams. A coach can run more than one team. Each team has its own name, sport, level, who plays and season, its own players with their own numbers and positions, its own practices and games, assistant coaches and helpers, challenges, season awards and game tournament entries, each kept and shared as Coaching: your coach’s sports team describes. Someone can help on only one of a coach’s teams at a time: an assistant coach or helper code for another of that coach’s teams moves them to it, and the team they helped before loses them. Your OK is per team: “Show me to my team” on one team shows you to that team’s teammates, to its assistant coaches and helpers (on an organisation’s team, those added by a coach you are linked to), and to the directors of a game tournament that team is entered in (your first name and number), and to nobody on your coach’s other teams. The cleared tick you send a coach is still per coach: that coach sees it on each of their teams. If you play on more than one of a coach’s teams, your phone shows each one. Your answer for a game or your OK says which team it is for, by the random number our server gave that team.
On your coach’s phone. Your coach’s app keeps the list of teams they run (each team’s random number from our server, name, sport, level, who plays and season, and for an organisation’s team the organisation’s name and two-character label), and keeps each team’s Playbook, practice plans and clock, History copy, game notes, who came to each practice and Active play games apart from the other teams’. When your coach archives one of their own teams, or stops running an organisation’s team (its admin takes them off it, or their coaching through that organisation ends), that team’s copies leave their phone: at once for an archive made on that phone, and otherwise the next time Coaching reads their teams. The copies of their own teams stay on their phone while those teams are theirs, even while they are not coaching, as their first team’s always have.
An organisation’s teams. An organisation can have teams of its own, made by its admin or by one of its coaches. Our server keeps which of its coaches run each team, since when, and, for a coach who stopped, until when; that record is kept until that coach deletes their profile in the app. A team can have more than one coach. Its practices, games and results, and each player’s number, positions and place on it, are then the team’s: our server lets each of its coaches see and change them, and its players and helpers see them as Coaching: your coach’s sports team describes. Each coach’s app lists the team’s upcoming practices and games, whichever of its coaches, now or before, booked them, and its History shows the team’s by their day. Who is picked for a game is the team’s too: before the team is shown, each of its coaches and their assistant coaches see who is picked of the players linked to that coach. Its season awards are the team’s too: each of its coaches sees them and can give one, one per player per season, and an award is not changed once given. A coach sees only the players linked to them. Each coach sets their own weekly challenge for the team, and it reaches only the players on it who are linked to that coach. Each coach sees and manages only the assistant coaches and helpers they added, and those helpers see only that coach’s players who said OK; every player on the team sees the first name and role of all of its helpers.
When a coach stops running a team (the admin takes them off it, or their coaching through the organisation ends), the team stays with the organisation, with its practices, games, results and season awards. That coach’s weekly challenges for it are deleted. Its players who are not also coached by another of its coaches come off it, with their number, positions and OK for it, and the assistant coaches and helpers that coach added for it lose it; the next coach adds those players and helpers again. If that coach entered the team in a game tournament, their entry stays, but from then on it carries none of the team’s players: no player’s first name is sent under it, no player can be added to it, and nobody is stored on it when rosters lock. If rosters had already locked, the players stored on it come off it too, unless the tournament has ended or was called off: then they stay on it until the time limits delete them (for one that was played, counted for its directors and shown to that coach by number only). When a team is archived (by the organisation’s admin, or by a coach, of one of their own teams), every coach, player and helper comes off it.
The organisation’s admin sees each team’s name, sport, level, who plays and season, which of its coaches run it and, once a team has 5 players or more, how many it has; never a player’s name, number, position, answers, health, food or training. A count can still show that somebody joined or left, or, when the admin takes a coach off a team, how many players came off with them.
How long. A coach’s own teams are deleted when they delete their profile in the app. An organisation’s teams stay with the organisation. Your place on a team is deleted when you no longer have a live link with any coach who runs it, when the team is archived, or when you delete your profile in the app.
Game tournaments. Anyone 18 or over can start a game tournament (real games at a venue, for coaches’ teams) under Triumph → Working with a coach → Game tournaments, and is its head director. Its name is two words from fixed lists. Our server keeps what its directors set: the sport, the venue’s time zone (the app fills it in from the phone’s time zone, and a director can change it from a list), the days, the fields and their hours, the rules (each from a fixed list), the divisions, the schedule and the check-in checklist, and which profiles direct it. Up to five more people 18 or over can help run it once the head director lets them; the first name each gave when they asked is kept and shown to its directors.
Your coach’s team in one. A coach enters their own team with the tournament’s code, and a director lets it in to a division. Our server keeps the entry and its division, when the team checked in, and which checklist items were ticked; ticks stand in for the papers themselves, and no documents, birth dates or health details are kept for a game tournament. Its directors, the other teams’ coaches and staff, and anyone with its spectator code see the team’s name as the coach typed it (or as built from its sport, level and who plays), with two words the app deals for it when another team’s name is typed the same or built from the same parts, its division, its games, scores and results, and, in a division whose standings are on, its pool table; its officials see the same for the games they are put on, without the tables. Only its directors and the team’s own coach and staff see the coach’s first name. Its directors see every division’s tables, even where standings are off; youth divisions start with standings off. Besides the team’s own coach and staff, only its directors see the team’s check-in and ticks. When a division is full, or teams that asked first are waiting for it, a team a director lets in goes on that division’s waitlist instead: our server keeps that it is waiting, its directors see it there in the order the teams asked, and the team’s own coach and staff see its place in line; until the schedule is out, directors let teams in from it in that order.
Players. Directors see the first names and numbers of a team’s players who said OK to being shown, and how many other players it has, for check-in. A player is someone your coach marked as a player and our server holds as 18 or over (see Coaching: your coach’s sports team). At the time the directors set (at or before the first game, or at the start of a day they pick, if that is sooner), our server stores which players are on each team then: the random number for each player’s profile and for their coach, and the player’s number. It stores no first names: each time a roster is read, a player is named only while they still have their OK on and are still on the team, so “Hide me from my team” takes the name back at once. A player on two teams in the tournament is stored on the team let in first; before the rosters lock, the other team’s coach is told that player is also on another team in the tournament, never which. The team’s coach sees by first name every one of their own players still on the team; its staff see those who said OK and a count of the rest. After rosters lock, a team’s coach can ask to add one of their own players: our server keeps the request (the random numbers for the coach’s and the player’s profiles, when it was asked and when it was answered, and the answer, from a fixed list: the head director’s, or ours when the player is already on another team in it or no longer a player on the coach’s team) and shows it to the tournament’s directors, naming the player and their number only if they said OK to being shown (unless the director is that team’s coach), and to that coach, who sees the names of their own players as before. If the head director adds them, the player is stored on the team like the others. A player already stored on another team in it can’t be added, and the coach is told so, never which team. Nobody in a game tournament is sent anything from anyone’s Health Hub, food or training.
On your Calendar. Once a tournament’s schedule is out, the games of your own team in it show on your Calendar if you are the team’s coach, one of its assistant coaches or helpers, or one of its players: each game’s day, start time and field at the venue, how long it is, home or away, the tournament and stage, the other team’s name, a move a director made and the notices posted that day, and, when you tap it, the venue’s details. When you open the Calendar, your phone asks our server for them, carrying this installation’s and this profile’s random numbers as every coaching request does, and only if this profile has a coach, holds a coach’s card, helps with a coach’s team (as Working with a coach last read it), has a team listed under Game tournaments, or already holds games. A person sees one team’s games in a tournament: the team they coach, else a team they help with, else the team they play for (for a player, the team they are stored on once rosters lock, or, if they joined after, their coach’s team), never another player’s name. Your phone keeps the answer and replaces it with each later one, so a moved game shows its new time and a tournament called off leaves your Calendar; a player’s games also show on Home’s athlete card and the Sports tab, and a coach’s in the block they lay around the team’s games; there, a game today or later shows only once the Calendar has read it that day. Our server keeps nothing new for this.
The venue. Its directors can type the venue’s details: the address, where the fields are, parking, the check-in point, rest rooms, accessible entrances and seating, and the nearest medical point, each up to 200 characters. Each is checked against the same word list as a team post, and kept with links, emails, phone numbers and other long runs of digits taken out. Its directors, its teams’ coaches, staff and players, its officials and anyone with its spectator code whose phone says they are 18 or over see them. Anyone who sees them can report them: our server keeps the report with the details as they stood when reported, the reporting profile’s random number and when, and a person at Adapt & Triumph reads it and can hide the details from everyone but its directors. Its directors are not told who reported them.
Scores. A team’s coach or staff, the game’s official or a director enters a game’s score. Our server keeps the score, which side entered it (the home team, the away team, the official or a director, never a person’s name), a revision number and when. When two phones send different scores, the book of record’s stands: the home team’s, or the official’s when its directors chose that and the game has one; a director’s correction always stands. A score that did not stand is kept with the game for the directors only, until another score or a forfeit lands. A director can set a forfeit from a fixed list of reasons: everyone sees “Forfeit”, and only its directors and the two teams in the game see the reason.
On the day. Directors can post notices from a fixed list, such as “Games delayed 30 minutes”; everyone in the tournament sees each one for a day. Heat and lightning notices show a line from public guidance (the National Weather Service; the NFHS); the app reads no weather. Nobody gets a notification; notices and scores show when the app is opened. An official joins with a one-use code a director made, which works for seven days; our server keeps which profile they are, their first name and a random number for them, shows the first name to its directors, and shows the official only the games they are put on and the teams in those games. An official can flag an incident on their own game from a fixed list, such as “Player dismissed”; only its directors see it.
Spectators. Anyone with a tournament’s spectator code sees its times, fields, brackets, scores and notices, its venue details if their phone says they are 18 or over, and tables where standings are on, never a player’s name, a coach’s name, a roster, a check-in or a forfeit’s reason. Our server keeps no record of who watches a tournament, apart from a report you make about its venue details (above); looking up any code leaves only a record that a code was tried, with this installation’s random number and a scrambled token for the network, never its address, deleted after about two days, and, the first time this phone or profile uses teams, coaching or a code, the private keys described under Teams and coaching, which say nothing about which tournament you looked up. A new spectator code stops the old one, and phones that used it stop seeing the tournament.
Called off. Its head director can call a tournament off. Nothing is deleted then: its directors, its teams’ coaches and staff, its officials and its spectators see “Called off” when they open it (an app from an earlier version says it is over); its games leave every Calendar, its players’ included, the next time the Calendar is opened with signal; from then on our server sends nobody its rosters, its directors included, and rosters not yet locked never lock (players already stored stay stored as they were until they are deleted as below); nothing in it can change after; and the time limits below still apply.
What our server keeps, and for how long. The stored players, and any late add asked for, are deleted about two weeks after its last day; everything else about a tournament, about six months after its last day; and a tournament never published, about two months after its first day. The venue’s details, and any report about them, are deleted with the tournament. When you delete your profile and our server accepts that request, your places as a director or an official, your team’s entries as a coach, the stored player rows you are on as a coach or a player, any late add asked for by you as a coach or for you as a player, and any report you made about a venue’s details are deleted from our server; a tournament you head passes to another of its directors, if it has one, or else stays with no director until the time limits above delete it; and your team stays in games already drawn as a team with no name.
When you type a coach's code, the app shows you that coach's name before you say yes (for a team's code, the team too). When you enter a coach's code or a team's code and say yes, your phone sends our server your first name and an age group worked out from the age you gave the app: 18 or over, under 18, or not set. It never sends your age or a birth date. (That is about this coach request. A team is told something different: see Teams: what our server keeps about you.) When you join by entering their coach code or one of their teams' codes, your coach approves you before anything else is shared. Until they do, they see only your first name and that age group. A request your coach has not answered stays on our server until you cancel it, they answer it, or one of you deletes their profile in the app. It may also be deleted when an organisation ends that coach's coaching through it (see Coaching: organisations and coach cards, below). You can cancel a request that is still waiting, while your phone is online.
If they decline, the app tells you the link was not approved, and that coach's codes from before the decline stop working for you. For that, our server keeps the declined request: the random number the app made up for your profile, your first name, your age group, which team it was for if it was for one, a random number your phone made up for that request, and when it was made and declined. It stays until you ask that coach again with a code they made after the decline, until you or the coach delete a profile in the app, or until you ask us to remove it.
A coach can give each of their sports teams a code of its own (see Coaching: your coach's sports team). When you enter one, the app shows you the coach's name and the team before you say yes, and the request you send also remembers which team it was for. Your coach sees which team you asked for on their Waiting for you list. For an organisation's team, your coach is the coach whose code you used: each coach of the team has a code of their own. If your coach approves the request and your app has told our server you are 18 or over, our server puts you on that team as a player, if the team is still theirs; if you are under 18, or your age is not set, you join the coach only. What being a player shares, and when, is under Coaching: your coach's sports team, and your coach is not sent whether you have said OK there. A request names one team: entering the code of another of that coach's teams while it waits moves it to that team. The team stays with the request for as long as our server keeps the request, as described above. If the team has been archived, or is no longer your coach's, by the time they approve, it is left off and you join the coach only. Our server keeps each team code with the random numbers for the team and for the coach until the coach deletes their profile in the app. A new code for the team replaces the old one, which stops working at once, and a code also stops working when the team is archived or your coach stops running it.
If you already work with a coach, and your app has told our server you are 18 or over, and you enter the code of one of their teams that you are not on, the app sends an ask instead of a request. Our server keeps that you asked, which team, and when, with the random numbers the app made up for your profile and your coach's, until your coach answers it (puts you on the team, whether from the ask or from the team's Players tab, or says "Not now"), the team is archived or your coach stops coaching it, you stop working with that coach, or you or the coach delete a profile in the app. If your age group stops saying 18 or over, your coach stops seeing the ask, but our server keeps it until one of those happens. Your coach sees your first name beside the team on their Waiting for you list; nobody else sees the ask. "Not now" tells you nothing and keeps nothing.
A sponsor code handed out by a coach can add you to that coach's roster without an approval step. The under-18 rules below (preset lines only, no calorie figures) apply to that link too, and on a link made this way our server may never record that you are 18 or over, so they can apply whatever your age. The under-13 limit below covers a coach's code or a team's code only.
While you are linked or waiting, your phone sends your age group each time it syncs with your coach, so a change to your age follows. Your coach's app receives it.
If you are under 18, or our server does not have your app's word for that link that you are 18 or over, your coach can only send you lines from a preset list: no typed line and no note. Messages are not for you either (see Coaching: messages with your coach). Plans they send you arrive without calorie figures, a movement they named themselves shows as "A movement your coach added", and the current version of their app does not show them calorie numbers for you. If you are under 13, you cannot link with a coach by entering a coach's code or a team's code.
Their status is in Feature status. While they are Off, the app sends none and our server stores none. When they are on, the app shows Messages on From your coach, under your coach on Triumph → Working with a coach, on Home while a message from your coach is new, and, for a coach, on a client’s Lines page.
Who can send them. Only a member and their coach, on a coaching link that is still live, and only when both are 18 or over: the link is marked 18 or over (see Coaching: approval and your age group), and the coach’s app has told our server they are 18 or over (the record described under Teams: what our server keeps about you). Anyone under 18, or anyone whose age our server does not hold, gets no messages; preset lines still work.
What our server keeps. For each message: the words typed (up to 500 characters), whether the member or the coach sent it, the random numbers for both profiles and when it was sent. A message with a link, an email address or a phone number in it, or a word on our list, is refused and not stored, and the app says nothing was sent. That filter is a list of rules, not AI, and no message is sent to an AI company or anyone else. Each person can send only so many messages an hour and a day.
Who reads them. Only the two of you. We read a message only if one of you reports it. There are no notifications: when the app opens, and when you open Home or one of those pages, the app asks our server whether a new message is waiting (when each was sent, never the words). Your phone keeps only, for each conversation, the time of the newest message you have seen in it and the other person’s random profile number, so it can show what is new; the other person is never told when you read a message. The messages themselves are not saved on your phone (the app holds the ones you opened only while it stays open).
Report and block. Every message from the other person has Report, and the conversation has Block at the top. A report tells us a message needs a look: our server keeps which message, the random number for your profile and when, and you stop seeing its words. We are emailed that a report is waiting; that email holds only counts, the report’s id and when it was filed, never the words. We read reports every day, and we can hide a message for both of you or end the coaching link. Block ends your coaching link from your side (as Stop sharing does, or Remove for a coach), deletes the conversation, and means the same code cannot link you again. Our server keeps a record of the block: the two random numbers and when. The other person is not told.
How long. A message is deleted 90 days after it was sent, and sooner when the link ends (either of you stops sharing, removes, blocks, or an organisation ends it) or when either of you deletes your profile. While either of you is not held as 18 or over, neither of you can read or send them, but that alone deletes nothing: they come back if it changes within their 90 days. A message someone reported is kept past those times until we close the report. A report is kept for 12 months after we close it. A block you placed is deleted when you delete your profile; a block someone placed on you stays.
A coach card is the code we issue that switches on the coaching tools. It is not the coach code a coach gives clients. For each coach card, our server records which organisation, if any, it was issued through and the date it was issued. For a coach card registered before 7 October 2026, both were filled in from the set of cards it came in: the date that set was first made, and the organisation that set named when we started recording this. That stays with our record of the card.
If an organisation issued your coach card, it sees, under Your members, the name the card was made under and whether you still coach through it (and which of its cards it is: the start of the card’s code). It is never told who your clients are, or how many of your client links it ended. If it paid for the cards you hand to clients, it sees how many of them have been claimed, as it does for any seats it pays for (see If your access was sponsored).
That organisation can end your coaching through it. When it does:
Our server keeps which organisation ended it, and when, with its record that your card was used. That record has no set end date. It also keeps how many client links ended until you delete your profile in the app. Email us to have either removed.
If you are a client and an organisation ends your coach's coaching through it, your link with that coach may end. The app tells you only that the link ended, not who ended it or why, and nothing more from coaching is shared with that coach. A request still waiting for that coach may be deleted too, and the app does not say so. So may an ask to join one of that coach's teams. Our server keeps the ended link, with the date and which organisation ended it, until you ask that coach again, until you or the coach delete a profile in the app, or until you ask us to remove it. You can ask that coach again with their code if they still coach, and they approve you as before.
Which roles your profile holds. A phone whose profile holds a coach card or an organisation owner’s card, has client seats it bought as a coach, or already holds a private key (see Teams and coaching), asks our server what that profile holds: when the app opens, after you enter a code or Coach is switched on or refused, and each time you switch to Coaching or Organisation (from the menu, or by opening one of their screens from search, the help hub, an alert on the Notifications page (the bell) or a button in Triumph). The request carries the random numbers for this phone and profile with the private keys, as every coaching request does, and nothing you entered, except, if you are signed in, the sign-in token, which contains your email address (see Optional accounts and sign-in). Our server answers with the roles the profile holds (such as coach or organisation owner), the organisations they come through, and whether it has client seats it bought as a coach; where no coach card makes the profile a coach and our server has a Coach subscription on record for it, it may also ask RevenueCat whether Coach is still active. Our server writes nothing for this question, apart from registering a private key it has not seen yet, as Teams and coaching describes. Your phone keeps the answer to decide which menus to show; every coaching action still asks our server again. A phone that holds none of these and no key does not ask. When you hold more than one organisation and pick one on the Coaching or Organisation home, your phone also names that organisation (the two-character label our server gave it, or “your own clients”) on the requests that fill the Coaching home’s roster, analytics and codes left, and the Organisation home’s sites, challenge, rivalry, coaches, teams and group totals, so each of those answers is about that one alone. Your groups, your sessions and the Seats screen are not split by organisation, and the app keeps your pick on this phone.
Adapt & Triumph does not run background checks on coaches, and does not check what an organisation tells us about them.
Nothing in teams or coaching is used for advertising, sold, or shared with anyone outside the team or coaching relationship it belongs to, except a team’s Team vs Team number, results, record, crest and two-word name, which the team it plays sees, a team’s season scores, place, division, crest and two-word name, which the teams in its league see, a team’s training tournament scores, results, crest and two-word name, which the other teams in that tournament and its directors see, how many of its people said they’re in, which that tournament’s directors see, the first name of anyone who asks to help run a tournament, which its head director sees, a coach’s team’s name and its games, scores and results in a game tournament, which that tournament’s directors, other teams, officials and anyone with its spectator code see, the coach’s first name and the first names and numbers of its players who said OK, which that tournament’s directors see, the first names of a game tournament’s directors and officials, which its directors see, an organisation’s Organisation vs Organisation number, results, record and name, which the organisation it plays sees, a coach’s Coach vs Coach number, results, record, crest and two-word name, which the coach they play sees, an organisation challenge’s count, which that organisation’s owner and members see, the name a coach card was made under and whether the coach still coaches through that organisation, which the organisation that issued it sees, the name typed for each coach or admin an organisation invited by email, that address (in full to the admin who sent the invite, and otherwise as its first letter and its domain) and where each invite stands, which that organisation’s admins see, an organisation team’s name, sport, level, who plays and season, which of the organisation’s coaches run it and, from 5 players, how many it has, which that organisation’s admin sees, and, before they join, the coach’s first name (and, for a team’s join code or an assistant coach’s or helper’s code, the team’s name, sport, level and who plays, and the group’s name), which the person holding that code sees. A coach’s assistant coaches and helpers are part of that coach’s sports team, and see only what is described under Coaching: your coach’s sports team. Find a coach is separate (see Find a coach): once it is On, a listed coach’s listing can be seen by anyone, including people who do not use the app, and a request’s first name and choices by the coach it is sent to.
If you are worried that a child is being hurt or neglected, the app’s “Worried about a child?” screen (open Send feedback, or open any team’s Settings pill and go to the bottom) shows who to call first: 911 if a child is in danger right now, and, to report abuse or neglect, your state’s reporting line (in Oklahoma, Oklahoma Human Services; the Childhelp National Child Abuse Hotline can help you find yours). Calling one opens your phone’s own dialer, and the app sends nothing for it. Telling us does not replace telling them.
If you also choose to tell us, our server receives and keeps:
A profile, a phone and a network can each send only a few reports a day. To count a network’s, our server keeps a scrambled token for it, never its address, for two days.
Only Adapt & Triumph reads it. It is not shown to the team, a coach, or anyone else in the app. We are emailed within minutes that a report is waiting. That email holds only counts, the id of the oldest open report (the reference number the app showed you is its first eight characters) and when that report was filed: never your words, a team’s name, or anything about who you are. We can’t reply in the app. The app shows you a reference number you can give us if you email us.
We keep a report while it is open and for 12 months after we close it. Deleting your profile does not delete a report you sent, because it is about a child’s safety. Where the law requires it, a report may be passed on to the authorities, or kept longer.
To work, the app saves the things you create directly on your phone, including the list below. Everything in this list is kept in a Backup you export and stays with the profile when you switch, unless a line says otherwise.
This information is stored locally using your device’s standard app storage. It is not uploaded to us or to any third party, except for what is described under Teams and coaching when you use those features, and the requests described under Checks every phone makes.
Your phone’s own backup is separate from this app. On Android, Google’s automatic backup and phone-to-phone transfer can copy the app’s saved data (including health entries, your journal and the private keys) to your Google account or a new phone, unless you turn your phone’s backup off. On iPhone, an iCloud or computer backup of your phone can include the photos in your Personal journal. We do not receive these copies.
Some of what the app stores is health data — the conditions you select, your answers to “Today I’m training…”, limb and skin check notes, your answer to “Hot today?”, pain entries, the days you mark as a flare or bad day, your answers to “How’s it feeling today?”, medications, body measurements, an injury or concussion you mark on a sport goal, and anything you write on your Emergency Card. Your answers about a burn, skin grafts or scars are health data too. So are your heart, diabetes, pregnancy, smoking and other health answers, the readiness questions, your allergies, and the photos you take for your Personal journal.
We want to be precise about something that is easy to get wrong, including by us: keeping data only on your phone still counts as collecting and processing it under laws such as the Washington My Health My Data Act and the UK and EU GDPR. “Processing” covers storing, organising and using information, wherever it physically sits. So even though almost none of it leaves your device, we are still the party that decided what gets stored and why, and the duties that come with that still apply to us.
The checks every phone makes, the sponsor-code check, the team and coaching features, a gym check-in, the sponsor’s “still using it” count if you switch it on, Help build better products if you switch a level on, a child-safety report you choose to send, and the features in More features once they are On, are the times anything reaches our server (see Checks every phone makes and the sections after it). None of them sends anything from that list by itself — your conditions, your answers to “Today I’m training…”, limb and skin checks, your answer to “Hot today?”, pain entries, bad-day marks, answers to “How’s it feeling today?”, medications, measurements, Emergency Card or an injury you mark on a sport goal; a report holds only what you type into it. Nor do they send your answers about a burn, skin grafts or scars. The exceptions you can choose: that you are on rehab for a sport, sent to your teams only while “Show my teams I’m on rehab” is on (see Teams: sport) and to a coach only if you turn on “Show my coach when I’m on rehab” for them; and the day you ticked that you were cleared after a concussion, which is sent only to a coach you turn that on for (see Coaching: your coach’s sports team). A team does receive a count of your workouts that used adaptive exercises (“Residual-limb strength” or “Seated / wheelchair”), which can point to a limb difference or wheelchair use (see Teams: what our server keeps about you). Help build better products, if you switch its levels on, sends us a summary of each week’s training, and the reasons you tap for skipping or swapping a move, such as “Hurt”, “Balance” or “Didn’t fit my body”, which can say something about your body or health, with which move it was, which for an adaptive move, such as a residual-limb or seated one, can point to a limb difference or wheelchair use; laws such as the Washington My Health My Data Act can treat both as health data (see Help build better products). Its third level, Show it’s working, if you switch it on, sends what you choose to tell us about yourself, such as condition groups you pick (never a condition from your profile) and whether you are a veteran, your check-in answers, including a pain score and your mood (its own questions, never your pain entries), and your self-test results, including whether you stopped one because it hurt; that is health information you choose to give, and the same laws can treat it as consumer health data (see Help build better products). For the sponsor-code check we are the controller. We keep the code, that random installation number, the random number for your profile, and a scrambled form of the private keys described under Teams and coaching. For each try we also keep the time and a scrambled token for the network it came from (never its address); those are deleted automatically after about two days. The check exists for one purpose: to stop a single code being copied and used by thousands of people, which would end the programme that gave you free access in the first place.
What that means in practice:
If you are in a jurisdiction with specific health-data rights — Washington, Nevada, Connecticut, the UK, or the EU among others — those rights apply to this data, and the practical way to exercise most of them is directly in the app, because, apart from what Help build better products sends us if you switch it on, and a Find a coach listing you choose to make (with a report’s copy of it), we hold no copy to act on. If you need something we can only do at our end, the contact address below reaches us.
The app’s Backup & Restore feature lets you export your data so you can save or move it. Any exported file goes wherever you choose to send it. We are not involved in and have no access to those exports.
Worth saying plainly: an exported backup is a plain, unencrypted file containing your health information. That is what makes it restorable on a new phone, and it also means anyone who opens the file can read it. Treat it the way you would a letter from your doctor — email it to yourself, put it in storage only you can reach, and delete copies you no longer need. The file also holds the installation number, the private keys that prove to our server that this phone and profile are yours, and your unlock. Anyone who gets the file could restore it on another phone and use them, so keep it as private as a password.
When you tap Share, Copy or Print on your shopping list, what is left to buy goes to your phone’s share sheet, clipboard or print dialog, and from there wherever you choose. The app itself sends it nowhere.
When you tap Share as PDF or Share as text on the Athlete Sheet (Training goals, on a sport goal), your phone makes one page for that sport from its own log and opens your phone’s share sheet, and from there it goes wherever you choose. It holds the sport, the version you play, your positions and level, and, over the last 12 months, the practices you saved and their minutes, the games you saved, the tries you took at that sport’s drills, the Combines you ran, and the days you did any of these. If your profile says you are 18 or over, it also holds your name as you set it in the app, your best at each test in your Combine that you have a result at, with its date (marked when your coach recorded it and you kept it), and your stats from the games you saved in your latest season: averages, totals and bests. It never holds your weight, height or any other body measurement, or anything about food. The app itself sends it nowhere; a PDF copy stays in the app’s cache on your phone until your phone clears it.
When you tap Share on your Health Hub’s appointment summary, your phone makes a page from your own entries (conditions, weight and measurements, training counts, limb checks, pain, appointments and medicines) and opens your phone’s share sheet, and from there it goes wherever you choose. The app itself sends it nowhere; a PDF copy stays in the app’s cache on your phone until your phone clears it. Sharing one entry from your Personal journal, or exporting the whole journal, works the same way: your phone makes the file (for the whole journal, one file holding its entries and photos) and opens the share sheet.
The app offers a subscription and a one-time lifetime unlock, purchased through the app store you installed from — Google Play on Android, or the Apple App Store on iOS. Payments are processed entirely by Google or Apple under their own privacy terms. We never receive, see, or store your payment details. Coaches can also buy the coaching tools as an in-app subscription, Coach Monthly or Coach Yearly, and client seat packs, one-time purchases that unlock nothing on their own phone. When a coach buys or restores Coach or seat packs, our server checks that purchase with RevenueCat, using the anonymous number RevenueCat made for this installation: no name, email or card details (see What changed since the 30 July 2026 version).
To confirm whether you have an active purchase, we use RevenueCat, a purchase-management service. RevenueCat’s software starts every time the app opens, whether or not you ever bought anything. It makes an anonymous number for this installation and asks the store whether a purchase exists. While the app is on its free trial or locked, it asks again when you come back to the app, so a code redeemed in the store can unlock it without a restart. On iPhone, after you apply an App Store code in the app, it also asks every few seconds for about a minute. RevenueCat sees that number, purchase receipts when there are any, your network address, and the device and app details its software sends with each request: your phone’s model and system version, the app’s version, your language settings, your app store’s country, whether it is a test purchase and, on iPhone, the device number Apple gives each app maker for that phone. It processes only the anonymous purchase information needed to unlock the app or add a coach’s seats — never your health, workout, or nutrition data.
Some screens link out to YouTube for exercise, stretch, recipe and motivation videos, and to your email app if you choose to send us feedback. Opening those hands you over to that service, which has its own privacy policy.
The words in a YouTube search can come from your profile: your limb level (for example “below knee amputee”), seated or wheelchair use, one-handed use, or limited range of motion, when your profile says so, and “seated” or “adaptive” on a motivation video. The line under the button says what kind of search it is before you tap. A recipe video searches for the recipe’s name. YouTube and Google see that search and your network address; the app sends them nothing else. An email only contains what you can see before you send it.
Links also open websites for organisations, source articles, your app store’s subscription page and our own policy pages. The iWALK link includes a code that tells iWALK you came from this app. Opening any link hands you to that site, which has its own privacy policy.
Spoken cues. If Spoken cues is on in Settings (it starts on for low vision), the workout player and Cook mode say each move, rest or step aloud. They use your phone’s own built-in voice, or your screen reader when one is on. The app sends nothing to us or to anyone else to do this.
Voice “next”. In the workout player and in Cook mode you can turn on voice “next” and say “next” instead of tapping. It is off until you turn it on, and it is off again each time you open the player or Cook mode. The first time you turn it on, your device asks whether the app may use speech recognition and the microphone (on Android, only the microphone). While voice “next” is on and the app is on screen, the app listens for the word “next” using your device’s own speech recognition, on the device only: it only turns on where the device can recognise speech without the internet, and it tells the device to keep the sound on the device. No sound and no words are saved, and nothing you say is sent to us or to anyone else. When voice “next” is off, the app does not use the microphone at all.
You can delete what is on your device yourself at any time. Uninstalling the app removes what the app holds on your phone, except that on an iPhone a sign-in kept in the Keychain stays until you sign out or delete your account (see Optional accounts and sign-in). Deleting a profile inside the app (open the menu and tap your profile’s name at the top, or go to Settings → Switch person (called Switch profile in older versions), when you have more than one profile) removes that profile’s saved data at once. It does not remove photos in your Personal journal (delete each entry first, or uninstall), PDFs you made to share (they stay in the app’s cache until your phone clears it), or the numbers and keys that belong to the phone (the installation number, its key and your purchase unlock).
Deleting a profile also removes its team seats and counts from our server when our server accepts that request. A deletion that never reaches it, because your phone is offline or the request fails, deletes nothing there, and uninstalling cannot reach the server at all — so leave your teams first, while your phone has service, if you want those gone. A deletion from a profile whose key our server refuses (the app’s Help on the Triumph screen says when) deletes nothing there either; email us and we will remove it. Deleting a profile does not delete a report it sent about a child’s safety (see Reporting a concern about a child). It also deletes that profile’s messages with a coach or a client from our server, except a message someone reported, which is kept until we close the report. And it deletes from our server everything Help build better products sent for that profile; its card in Settings → Privacy also has Delete my data, which does that while you keep the profile (see Help build better products). If you coach, deleting a profile also removes from our server that profile’s Coach subscription record, its client seats and their seat codes, its profile for clients, and the join codes it made for its teams. Deleting a profile also removes any ask to join a team that it made or that was made to it. A purchase record for a seat pack is kept, but without anything that identifies you: just the store’s and RevenueCat’s numbers for it, the pack, whether it was a test purchase and when it was added. If the profile was signed in on this phone (see Optional accounts and sign-in), deleting it also asks our server to delete the account it was signed in with, your email and its link, and our server does that when it receives the request, unless that account is linked to a different profile. In that case, or if the profile was not signed in on this phone, the account stays until you sign in and tap Delete account, or email us. If the profile is linked to a different account from the one it was signed in with, that other account is not deleted; it stays until you sign in with it and tap Delete account, or email us.
Some things stay on our server after you delete a profile: posts you wrote in a team’s feed (until the twelve-month clear-out, so delete them first), a problem you reported in a team (until 12 months after we close it), your sponsor-code seat (it stays claimed), the private keys, your 18-or-over record for teams, a block someone else placed on you, a message someone reported (until we close the report), a report you made about a message (until 12 months after we close it), the last time you tapped “I’m training now” for a coach, your sponsor’s “still using it” date if one was ever sent (until that day is more than 90 days ago), and anything else this policy says stays. To have any of these, your purchase record, or anything stored for a team or a coach removed, email us at support@adaptntriumph.com and tell us what helps us find it, such as a team’s name, a coach’s name, your sponsor code or the reference number the app showed you. We will remove what we can find within 30 days and tell you by email what we removed.
Several of these (the private keys, your 18-or-over record, a block placed on you, the “I’m training now” time and the “still using it” date) are filed only under the random numbers the app made up, and hold no name, email or anything you entered. The app does not show you those numbers, and once a profile is deleted your phone no longer has its number. We can find them from a sponsor code you used, or from a team or a coach link that still names you; without one of those, after a profile is deleted, we usually cannot tell which of them are yours. Full instructions are on our delete your data page.
The “still using it” count is off unless you switch it on. If you do, whoever paid for your access — a gym, a clinic, an employer — is told how many of their members are still using the app, and you are counted among them. If you never switch it on, the app sends nothing for it. Earlier versions of the app sent it unless you switched it off. If yours did, or you switch it off later, nothing new is sent, and the last day already sent stays in their counts for up to 90 days. The row that holds it (this installation’s random number, your card’s batch label and that day) is not deleted when you delete a profile or the app, but our server deletes it automatically once that day is more than 90 days ago; email us with your sponsor code to have it removed sooner. Whether or not you switch it on, they are never told who, and never told anything about what you do, except that an organisation that issued you a coach card sees it by the name it was made under, and whether you still coach through it (see Coaching: organisations and coach cards).
With it switched on, when you log a workout or a meal, the app sends the two-letter label of the batch your code came from, the random installation number and the random number for your profile, with the private keys described under Teams and coaching (and, if you are signed in, the sign-in token; see Optional accounts and sign-in), at most once a day. The server keeps one date per installation, replaced each time. There is no history, so nobody can look at a gap in your training, or see what you did, or how often, or when you stopped and started again. Once five of their seats have been claimed, members with that organisation’s card also see how many people there logged something today, counted the same way, never who. That floor counts claimed seats, not the members who switched this on, so when only a few people there share it, that count can point at you. Apart from a coach card, your sponsor only ever sees counts. If you are in one of their gym teams and they play another organisation in Organisation vs Organisation, your weekly workout summary (all the workouts you saved that week) counts toward one weekly number for their whole organisation, which the other organisation’s owner and members also see, shown only once at least five people are counted (see Organisations: Organisation vs Organisation). If they run a challenge for their members and you are in one of their gym teams, your weekly workout summary counts toward its one shared count too, which their owner and members see, again only once at least five people are counted (see Organisations: challenges). Leaving the organisation in the app, or turning off the switch below, does not stop either; leaving their gym teams does.
Apart from a coach card, your sponsor also never sees anything below a floor: nothing at all until five of their seats have been claimed, and no day-by-day or hour-by-hour breakdown until ten have. In a small group a count can point at the people missing from it, so we do not show one. The one exception is how many of their seats have been claimed: they always see that number, never by whom, so in a small group it can show how many people have not claimed theirs. The app also shows them neither “still using it” count until at least five members who share it have used the app in the last 90 days; an owner’s app from an earlier version shows both counts however small, until it is updated.
It is off unless you switch it on, when you enter your code or later in Settings → “Let your sponsor see that you are still using it”. You can turn this off again at any time, and leaving the organisation in the app turns it off. A card from a different sponsor starts with it off. Your access is not affected in any way, now or ever.
If they put up a check-in code where you train, scanning it sends the same two-letter label and random numbers, and our server adds one to a count for that place and hour. No row says who scanned. Once ten of their seats have been claimed, the person who scanned is shown how many check-ins there were there since the start of the hour before (the sheet gives the time), and nothing when there are fewer than three. A second scan from the same profile in the same hour is not sent. The switch above does not change check-ins: one is sent only when you scan a code.
Home shows the name of the organisation your card is from. If you hold cards from more than one, it shows two names at most, in one row. A name comes off when you leave that organisation, when the organisation ends your card (the app learns that the next time you open Triumph), or when the time it gave you runs out, if the app knows that date. The code check, and Triumph’s check of your cards, also tell your phone the kind of organisation each card belongs to, which the app uses only to decide the order of your organisations’ names (on Home, and in Triumph’s Organisation row when no card there names one) and, when more than one organisation’s card is waiting to cover you, which one starts first. It is never shown. Your phone keeps it with the card, and the app never sends it anywhere, except in a Backup you export yourself.
If you bought the app yourself, none of this applies and nothing is sent — there is nobody to report to.
Its status is in Feature status. In Settings → Privacy, the app has a card called Help build better products, with three optional levels. While it is Off, the app does not show that card or send anything for it, and our server stores nothing for it. When it is on, each level is off unless you switch it on, and only people 18 and over are offered them: not anyone under 18, and not a profile with no age. You can switch any of them off, or delete what they sent, at any time.
Count me, so the groups that gave you the app can show it’s used and keep it free. While it is on, after each week ends (Monday to Sunday) the app sends a summary of that week the next time it opens, counted from the day you switched it on: how many of that week’s days are counted (fewer in your first week), how many days you trained, your active minutes, how many workouts, sport sessions and stretches you logged, and how many programmes you started and finished. Active minutes are the minutes of the sessions you logged: a practice or game’s own minutes, or the time from your first set to Done in the workout player (to your last edit, if you edit the session later); no sensor is read. A time over 5 hours, or a practice or game over 10 hours, counts as 0. The summary also carries the two-letter label of a card you entered, if you have one (never a hardship grant), your phone type (iPhone or Android) and the app version. It never includes your name, a note, what you ate, your Health Hub or your conditions.
Build better products, to build the gear and tools that don’t exist yet. While it is on, when you skip or swap a move in a workout, the app offers seven reasons to tap: Hurt, Couldn’t grip, Balance, No equipment, Too hard, Too easy and Didn’t fit my body. Tapping one is optional, and there is no space to type. A reason you tap is sent with whether you skipped or swapped the move, which move it was (only a move from the app’s own library, never one you typed), which for an adaptive move, such as a residual-limb or seated one, can point to a limb difference or wheelchair use, and the week. For a swap, the move is the one you swapped away. Your coach and your teams never see these reasons. You can also add an email address so we can invite you to a study. It is stored apart from everything else here and never appears in a report. We never run a study in the app: if we write to invite you, the study asks for your OK itself.
What goes with them. Everything any level sends goes with the random number for your profile, which our server keeps with it, and with this installation’s random number and the private keys described under Teams and coaching (and, if you are signed in, the sign-in token; see Optional accounts and sign-in), which our server uses to check that the request came from your phone. Our server also notes when each summary and each reason reached it; a reason usually arrives just after the workout it is about. A check-in or self-test carries the day you did it; our server does not note when it arrived, and Who you are carries no date.
Show it’s working, to prove to funders and clinics that this helps people like you. It has three parts, and you can use any of them, or none.
What it sends, while it is on: your Who you are answers when you save a change to them, and again if the age in your profile moves you to a new age group, and each check-in and self-test when you finish it, with the day you did it. A self-test is sent as which test it was (so a 2-minute push says you used a wheelchair, and a 30-second arm curl, which the app offers only to people who use a wheelchair, train seated or have limb loss in both legs, can say that too) and its number, or only that you stopped. Check-ins and results you make while it is off stay on your phone and are never sent, even if you switch it on later. Show it’s working is health information you choose to give.
What we do with it. We use it to see how the app is used and what to build next. Laws such as the Washington My Health My Data Act can treat a summary of your training, or a reason such as “Hurt”, as health data, and Consumer health data, above, applies to them too. Those laws can treat everything Show it’s working sends as consumer health data. If we share anything from it, with an organisation that gave people the app, a funder or a clinic, it is a total for a group of 10 or more people, such as “40 members trained 3 days a week”: never a smaller group, and never anything that names you. That holds for totals split by an answer under Who you are, such as a ZIP-3 area, the condition groups someone picked, or being a veteran: a split that would show a group under 10 is not shown. Nothing from it goes to an AI company, an advertiser or a data broker, and none of it is sold. No data from Apple Health or Health Connect is sent.
How it differs from the sponsor’s switch. “Let your sponsor see that you are still using it” (see If your access was sponsored), at most once a day, lets whoever paid for your access count you among members still using the app. Help build better products sends us a weekly summary and, if you choose, the reasons you tap and what Show it’s working asks. Your sponsor sees nothing from it except totals for groups of 10 or more people.
How long. Each weekly summary is deleted 24 months after its week, and each reason 24 months after we receive it. Each check-in and self-test result is deleted 24 months after the day you did it. Your Who you are answers are kept until you switch off Show it’s working, or delete. Which levels you have on is kept while any of them is on. The email is kept until you remove it, switch off Build better products, or delete. Uninstalling the app deletes none of it from our server (see Deleting your data): use Delete my data first, or email us.
Stopping and deleting. Switching a level off stops it sending at once, even with no signal; our server is told the next time the app is online. If a profile’s age is changed to under 18, or removed, every level switches off the same way and our server is told; nothing else is sent from that profile, except Delete my data. Delete my data, on the same card, switches every level off, deletes from our server the summaries, reasons, email, Who you are answers, check-ins and self-test results they sent and which levels you had on, and says when it is done; the private keys stay (see Deleting your data), and your own copy of your check-ins and results stays on your phone. Switching Show it’s working off also deletes your Who you are answers from our server in the same request; the check-ins and results it sent stay until you delete them or 24 months pass. Deleting the profile deletes it too, when our server receives that request (see Deleting your data).
These features are described here before they are turned on, so that turning one on changes only its word in Feature status. While a feature is Off, the app sends nothing for it and our server keeps nothing for it. Messages with your coach and Help build better products have their own sections, above. Accounts and sign-in is On; Sign in with Google and Settings sync across your phones are still Off, described in the same section.
If you coach, or run an organisation, you are asked to sign in, so you can bring your coaching to a new phone or an iPad. You sign in with an emailed 6-digit code or with Apple; there is no password. Nobody else is asked to, and everything that works without signing in keeps working without it. It is not offered on a profile for a child under 13. Once Organisation members by email is On, a member whose organisation pays for their access also signs in, to use that access (see Organisations: members by email).
Sign in with Google is built but switched off: it is Off in Feature status, and nothing is sent for it until it is On. Copying your settings to our server while you are signed in is not part of what is On. While Settings sync across your phones is Off, the app copies none of your settings. Your answer to “What do you coach?” is not one of them: if you coach and are signed in, it is kept with your coaching (see What the app stores).
If you run an organisation on the app, you can invite your coaches and other admins by email, on the Coaches card of the Organisation side; we invite an organisation’s first admin the same way. Nobody else can send one, and nobody types a code.
If you run an organisation on the app, you can also open it on the web, at portal.adaptntriumph.com. You sign in there with an emailed 6-digit code, as in the app (see Optional accounts and sign-in); Apple and Google sign-in are not offered there. It works once your sign-in is linked to your profile in the app, and only for an organisation you run.
An organisation that pays us for its members’ full access, outside the app, can list those members’ email addresses. A member who signs in to the app with one of those addresses has the app’s full access until the date the organisation set, and nobody types a code. It is Off in Feature status, and nothing here is collected until it is On. It is for people 18 and over.
Once Help build better products is on, we may share what it collects with an organisation that gave people the app, a funder or a clinic, only as totals for groups of 10 or more people, such as “40 members trained 3 days a week” (see Help build better products).
No clinic or organisation receives anything from it that names you, or anything from your Health Hub. A clinic gets your own information only when you send it yourself, such as your Health Hub’s appointment summary through your phone’s share sheet (see Backups you control), and we never see that.
Reminders your phone sets for itself are on now. A reminder such as a team’s Close reminder is set by your phone from what is already on it, and nothing is sent to set it.
Push notifications for events and safety notices are notices about a game or event you are part of: a delay, a schedule or field change, a weather or lightning hold, or a notice from its organisers. They use fixed wording and are never about your training, streaks or scores. Your phone asks your permission the first time one would be sent, and you can say no.
A school or league could sell tickets to its games and events, bought ahead or at the gate, where its gate staff scan them on a phone or tablet. It could also take donations.
Your avatar mark is on now: its symbol, colour, ring and finish are kept on your phone, and are sent to a team only as your mark beside your first name on its board (see Teams: what our server keeps about you). The robot avatar is listed in Feature status. When it is on and you use the robot, your robot’s look (shape, colours, antenna) is sent to your teams only, beside your first name, just like the mark. How fast it moves and its floor shadow stay on your phone. Your phone sends the look, or takes it off when you switch back to the mark, the next time you open each team while online. Our server keeps the look with your place in each team, and it goes when that place does. When a team reaches its weekly goal, its members’ phones can show the whole team’s robots together; anyone who has not picked the robot is shown as the app’s default robot. Nothing more is sent for this.
Artists’ credits. Pieces for your avatar made by artists we work with. The app downloads the list of artists and pieces, and the pieces themselves, from our server; those requests carry no profile number. A piece shows “Created by” with its artist’s name on your avatar screen, and “Wearing a piece by” with that name when someone taps your mark. When you share a card from the app, it names the organisation your card is from and the artist of any piece you wear, unless you switch that off on the share screen. A clinic is named like any other organisation, so a shared card can show where you are treated. Nobody under 13 is shown an artist’s social links.
The 3D avatar. A figure you build, as a person or a character. As a person it can show a limb difference, a prosthetic, a wheelchair or another mobility aid, a body type and a skin tone. How it looks stays on your phone; a team sees only your mark, or your robot’s look if you use the robot.
A photo of your meal, added to a food log entry. Photos here are of food only.
Today the camera in the food log only reads barcodes, matched on your phone, and nothing about a scan leaves it.
Find a coach is a list of coaches that people can search, and a way to ask one for coaching. It is for people 18 and over. Every request the app makes for it, except the search, carries the random numbers for your phone and your profile and the private keys described under Teams and coaching (and, if you are signed in, the sign-in token; see Optional accounts and sign-in). Your phone makes no new key to read your own listing or to ask how requests stand; it can for the others. Any of these requests, those two included, can register a key your phone already holds if our server has none yet for that profile or phone (see Teams and coaching).
The app does not include third-party advertising or tracking SDKs, and does not track you across other apps or websites. There are no adverts in the app. Nothing described here is shared with anyone but the people it is for — your team, your coach, the sponsor who paid for your access, or, in Team vs Team, Seasons, training tournaments, Organisation vs Organisation, Coach vs Coach and organisation challenges, the other teams, organisations, coaches, organisation members and tournament directors those sections name, or, in game tournaments, the directors, other teams, officials and spectators that section names — and it is never sold.
From Help build better products we share only totals for groups of 10 or more people. The sections under More features say who gets what from each of them, once it is On.
Apart from Help build better products (only while it is On, and then only the levels you switch on), the only counting the app does for us is the optional feature count (Settings, off by default), which carries no identifier and which this version keeps on your phone and never sends.
Companies that help us run this, below, lists the companies that run parts of the service for us.
These companies run parts of the service for us and handle only what that part needs. A new company means a new line here and a dated line in What changed.
The app is not directed to children under 13, and we do not knowingly collect information from children. Apart from the features and checks described above, no data leaves the device. Nobody under 18 can send or get typed messages with a coach; they keep the preset lines. Help build better products is never offered to anyone under 18, or to a profile with no age. Features for children under 13, their parents, and the schools and leagues they play for are Off. Before any of them is turned on, a lawyer must approve it, and this section will become a full notice for parents, with what US children’s privacy law (COPPA) requires. We will not take on a school’s student records without a written agreement with that school.
Your data is protected by your device’s own security (passcode, Face ID / Touch ID, and system encryption). Keeping your device and its software up to date is the best way to keep your information safe.
Adapt & Triumph provides general health, fitness, and nutrition information for educational purposes only. This app is not a medical device and does not diagnose, treat, or prevent any condition. It is not medical advice and is not a substitute for professional diagnosis or treatment. Always consult your care team before starting any exercise or nutrition programme.
Before a feature that is Off starts collecting anything, we will update this page: change its word in Feature status to On, change the effective date above, and add a dated line to What changed. We will also tell you in the app. Nothing new about you is collected unless you choose to turn it on.
Any other change to this policy is posted at this same address, with a new effective date and a dated line in What changed. If a change would collect more about you, or share it more widely, than this policy says, we will also tell you in the app before it takes effect.
This app is operated by Adapt & Triumph LLC (Oklahoma, D-U-N-S 149990473). Questions about this policy? Email support@adaptntriumph.com.