Tracko
Privacy policy
Tracko is run by Ben Fowler in Victoria, Australia ("we", "us"). This policy explains what information Tracko holds about you, why, where it goes, and what you can do about it. Some of it is health information, which Australian privacy law treats as sensitive, so we've tried to be specific.
The short version
- We hold your training and recovery data so we can show it back to you. That's the point of Tracko.
- We don't sell it, share it for advertising, or use it to train AI. Other members don't see your training. They can see your name and photo in Friends, as you choose (below), and the people you run with see the run you do together.
- It's stored with Cloudflare, and parts of it go to the services that make Tracko work (listed below), some of them outside Australia.
- The AI coach is off unless you turn it on, and you can turn it off in Settings → Profile at any time (AI transparency statement, below).
- You can ask for a copy of your data, and delete your account and everything stored for it from Settings, whenever you like.
What we hold
| What | Where it comes from |
|---|---|
| Your email address, the invite you joined with, when you joined, which version of the terms you agreed to, and whether you chose to be Findable or Private in Friends | You, when you sign in and join |
| Your name, and if you choose to add them: a photo, your date of birth, your sex, and an emergency contact's name and phone number. The photo is cut to a small square on your device before it's sent, which also drops any location or camera details in it | You, in Settings → Profile |
| Friends: a copy of your name, for Friends to show; your friend code, which Tracko makes for every member; whether you're Findable or Private; and, as you use it, your friends and since when, the friend requests you've sent and been sent and how they were answered, the people you've blocked, with their name as it was then, and who you've looked up by name or code, and how many lookups and requests you've made, for the limits on them | Tracko (your code), and you: when you join, and on the Friends page |
| If you run with friends: the runs you agree to (the day, the distance and pace together, who's in, and the asker's line about when and where to meet), and the sessions Tracko moved or added in your plan for them. For a run request, your usual easy pace (from your runs, or as you type it; for a workout together, the pace of your hard sessions too) and a summary of your last six weeks of running, sent from your device, used only to work out the run and deleted when the request ends | You and your friends, when you ask or answer |
| Activities: date and time, sport, distance, duration, pace, heart rate, power, cadence, elevation, laps, and the GPS route | intervals.icu, once you connect it |
| Wellness and recovery: resting heart rate, HRV, sleep, weight and anything else you or your watch record in intervals.icu | intervals.icu |
| If you import your Garmin history: each run's summary (date and time, name, distance, duration, heart rate, climb and cadence), and your daily resting heart rate, HRV and Garmin's normal range for it, overnight breathing rate and running VO₂max from your Garmin data export. Nothing else in the export is read or kept, nor the download link | Garmin, from the export link you paste in Settings |
| Your intervals.icu athlete id, and the access key intervals.icu gives Tracko when you approve it (or the API key you paste instead). Tracko uses it to read your activities, wellness and settings, and, if you switch it on, to add your planned runs to your intervals.icu calendar for your watch | intervals.icu, or you, when you connect. The key is stored encrypted. |
| If you connect Garmin: your Garmin user id and the access tokens Garmin issues; which kinds of data you've let Tracko have; your activities (date and time, sport, distance, duration, pace, heart rate, power, cadence, elevation, laps and the GPS route); from your daily, sleep, HRV and fitness summaries, your resting heart rate, sleep, HRV, breathing rate and VO₂max; and, if you have Tracko send your planned sessions to your watch, the ids of the workouts it put in Garmin Connect. Tracko asks only for the kinds of data it uses, and keeps only these parts of them | Garmin, once you connect it. The tokens are stored encrypted. |
| What you enter in Tracko: training plans, races and goals, gym sessions, weights and reps, how your runs and sessions felt (including feeling unwell or in pain), your heart-rate threshold, shoes, notes, fuelling plans | You |
| If the club's admins make the AI coach available to you: that they have; whether you've turned it on, and when and under which version of the terms you last turned it on or off; what you've told your coach about yourself; and the morning briefs and run debriefs it writes for you | The admins, you (in Settings → Profile, or on the screen that asks you to agree again), and the coach |
| If you have your physio's email read into your exercises: the email or letter, only while it's read. Tracko keeps the exercises you save, and when you last had one read (for the limit of one a week), not the email | You, in Physio exercises |
| Bug reports and feature suggestions you send from Settings, with any screenshots you add, and with a bug report the page you were on, your device, browser and screen size, and any recent errors on the page | You |
| If you connect Strava: your Strava athlete id and the access tokens Strava issues; for 3 days, the ids of your new runs and gym sessions there, so each is handled only once; and, for 7 days, the ids of the activities Tracko wrote to, with what it wrote (and, until it's written, a new activity's day, start time and distance) | Strava. The tokens are stored encrypted. |
| If you turn on notifications: a notification address for your device | Your browser |
| Technical logs, such as IP address, browser and the time of each request; and Tracko's own log of its background jobs (your account's id, the kind of job and how it went, with the id of the Strava activity a description was for, never names or health values) | Cloudflare, automatically, for security and keeping the site running |
Tracko also keeps a copy of your data on your own device so it opens quickly and works offline. Signing out or deleting your account clears it from that device.
Why we hold it
- To show you your training: dashboards, records, trends, maps and recovery.
- To build your training plan and send sessions to your watch through intervals.icu or Garmin Connect, when you ask it to.
- If you connect Strava, to write each run's and gym session's summary into its Strava description.
- If the coach is available to you and you've turned it on, to write your morning briefs and run debriefs with AI (AI transparency statement, below); and to read a physio's email into your exercises when you ask.
- For Friends: to let members find you as you've chosen, to send and answer friend requests, and to fit runs together into both plans.
- To read bug reports and suggestions, to help fix and build Tracko.
- To send the notifications you've turned on.
- To count members' runs and kilometres for the club's admins, in Club stats (Who can see it, below).
- To keep Tracko secure and working, and to fix problems.
- To contact you about your account or about Tracko changing or ending.
If you connect Garmin, what Tracko gets from it is used for the same things as what it gets from intervals.icu, and nothing else: to show you your training, to build and adjust your plan, for your Strava descriptions if you connect Strava, for the coach if you turn it on, for the notifications you've turned on, for the paces Friends works out for a run together, and for the counts of runs and kilometres in Club stats (Who can see it, below).
We don't use your information for advertising or sell it, and we never use it, or anything worked out from it, to train, evaluate or improve AI models. When you join you consent to us handling your health information for these purposes, apart from the coach: that has a consent of its own, which you give by turning the coach on and take back by turning it off (AI transparency statement, below).
Who it goes to
We don't sell your information or share it for advertising. It goes only to these services, and only for what each row says:
| Service | What for | Where |
|---|---|---|
| Cloudflare | Hosts Tracko, handles sign-in (the emailed code), stores your data and sends Tracko's emails: your invite, the confirmation when your account is deleted, and the one when you remove Tracko in Strava's settings | Cloudflare's global network, which includes data centres outside Australia |
| intervals.icu | Where Tracko reads your training from, and sends planned sessions to | Outside Australia. You have your own account with them. |
| Garmin, only if you connect it | Garmin sends Tracko what you've let it have (What we hold, above) as your watch syncs, and tells Tracko if you remove it in Garmin Connect or change what it may have. If you switch it on, Tracko sends your planned sessions to Garmin Connect so they're on your watch: each one's day, name and steps, with their paces or heart rates. When you disconnect Garmin or delete your account, Tracko asks Garmin to end the connection. What's in Garmin Connect is under Garmin's own privacy policy and your settings there. | Outside Australia. You have your own account with them. |
| Anthropic (Claude) | Writes coaching notes from your recent training, plan and recovery data, and what you've told your coach about yourself, if the coach is available to you and you've turned it on; and reads a physio's email or letter into exercises when you ask it to. Nothing from Strava is ever sent to the coach, or to any other AI. Under Anthropic's commercial terms, data sent to its API isn't used to train its models. Ben also uses Claude Code, Anthropic's coding assistant, to fix and build Tracko. It reads the bug reports and suggestions members send, with their screenshots, and while it tests or fixes something it can see what Ben can as administrator, including the data stored for the accounts involved, but it never reads anything from Strava. For a member who has connected Garmin, it reads none of their training or recovery data, nothing Tracko builds from it, and none of their screenshots. Ben's Claude Code account is set so that what it reads isn't used to train Anthropic's models. The AI transparency statement, below, says more. | United States |
| Open-Meteo | The weather for your coach's notes, if you've turned the coach on, and the forecast on today's and tomorrow's runs in your plan. It's sent a rough location (the middle of your latest run's route) and a date, and nothing that says who you are. And the forecast on race day: it's sent the name of the town your race is in, then its date, from your device. | Europe |
| Strava, only if you connect it | Strava tells Tracko each time you add an activity, and Tracko reads it from Strava to see whether it's a run or gym session, using only its sport, day, start time and distance. Once a run or gym session reaches your Strava, Tracko writes the session's summary into its description, after anything already there: for a run, its distance, pace, heart rate and how it went against your plan; for a gym session, the exercises, sets and weights you ticked off. If you connect Garmin, or import your Garmin history, a run's numbers in it can come from Garmin. When you send one from Share, Tracko finds the matching activity by reading your Strava activities around that day, private ones included, and writes it the same way. It can rename the activity after your planned session too. What Tracko writes is then on Strava, under Strava's own privacy policy and your settings there. | United States |
| Esri | The maps under your routes. Your device fetches the map of the area a route is in from Esri, which sees your IP address and that area, not the route itself or anything else about you. | United States |
| Amazon Web Services | The height of the ground along your runs, to measure their climb. For each run, Tracko's servers fetch from Amazon the squares of a public map of the ground that the run passes through, each a few kilometres across, with nothing that says who you are. Most are saved from earlier runs and aren't fetched again. | United States |
| Google Fonts | The app's lettering. Your device downloads it from Google, which sees your IP address and browser, nothing else. | United States |
| The calendar app you add your calendar link to (Apple, Google, Microsoft or another), only if you make one | It fetches your planned runs and gym sessions, with their steps, paces and notes, from the link, and keeps them up to date. What's in it is then under that company's privacy policy and your settings there. | Mostly United States |
| Apple, Google, Microsoft or Mozilla push services, only if you turn on notifications | Delivering the notifications you've turned on to your device, the coach's notes among them. The notification text passes through them, and a friends notification names the person asking you, saying yes or withdrawing a run request, or the friend you asked when a run didn't go ahead. | Mostly United States |
| Zoho | Tracko's mailbox, [email protected]: what you email us and our replies, such as a copy of your data when you ask for one | Australia |
What Tracko gets from Garmin, and what it works out from it, goes only to:
- Cloudflare, which hosts and stores it;
- Anthropic, only if you've turned the coach on;
- Strava, as a run's numbers in its description, only if you connect Strava;
- Open-Meteo, as a rough location from your latest run;
- Esri, as the area a route is in, from your device;
- Amazon Web Services, as the map squares a run passes through;
- intervals.icu and the calendar app you add your calendar link to, as your planned sessions, which Tracko sizes partly from your runs, only if you send them there;
- the push services, in the coach's notes and the other notifications you've turned on;
- Zoho, if you email us for a copy of your data;
- and people only as Who can see it, below, describes: Ben, as administrator; your friends, in Friends; and the club's admins, as your runs, kilometres and last run's day in Club stats (and, added up with everyone's, in the club's totals they can post), and in a screenshot you send with a bug report.
It's never sold, or shared for advertising.
Because these services are overseas, your information is handled outside Australia, and the law where it's held may not protect it in the same way. We choose established services with their own privacy and security commitments. We'd also disclose information if the law required it.
Strava may monitor, collect and use data about how Tracko uses Strava's API, for any business purpose (for example, to support developers and to check Tracko keeps to Strava's rules). Strava's own privacy policy covers your data on Strava, and where it and this policy differ about Strava data, Strava's applies.
AI transparency statement
Tracko uses AI in two places, the coach and the physio reader, both Anthropic's Claude through its API. Neither is used unless you choose it. Nothing else in Tracko is written or worked out by AI: your plan, readiness and paces come from ordinary software.
The coach writes you a short brief each morning and a debrief after each run.
- It's off until you turn it on. The club's admins decide who it's available to, because each note costs money. If it's available to you, you turn it on yourself: with a box of its own, not ticked unless you tick it, on the screen that asks you to agree again when the terms change, or with the switch in Settings → Profile, under Your coach. Agreeing to the terms doesn't turn it on. If your coach was on before this version of the policy, it's paused until you turn it on.
- What it's sent, and why: what a note needs to fit your day and your training. Each is sent your plan around that day, your races, heart-rate zones and shoes, six weeks of weekly distance, and what you've told your coach about yourself. A morning brief also gets your runs and rides from the last week or so, with their names, distance, pace, heart rate and training load; your gym log for the last two weeks; about a week of nights' recovery (resting heart rate, HRV, sleep, fitness and fatigue), with your longer averages for HRV and resting heart rate; and the day's weather. A debrief also gets the run itself, with its splits and weather; your runs and rides in the ten days before it, and your recovery on the nights before; and how you said it felt, your note on it and what you took. If you connect Garmin, all this includes what Tracko gets from Garmin. It isn't sent your routes, your email address or your Profile details (name, photo, date of birth, sex and emergency contact). Nothing from Strava is ever sent to the coach, or to any other AI.
- What comes back: Claude writes the note, and Tracko shows it to you as it is, on Today and with the run, and sends it to your devices if you've turned those notifications on. Nobody at Tracko reads or checks it first. It's written by software, can be wrong, including in ways that sound sure, and isn't medical advice (terms of use, section 2).
- Turning it off: in Settings → Profile, under Your coach, at any time. It stops within a minute or so: nothing more is sent to Anthropic for it, and no new notes are written or sent to your devices, though the notes it's writing at that moment may still be finished. The notes already written stay where they are. You can turn it on again whenever you like. If the club's admins make the coach unavailable to you, it stops the same way, and if they make it available again, your earlier choice stands.
The physio reader reads a physio's email or letter into exercises, only when you ask it to in Physio exercises, so each read is your choice. It's sent that email or letter and nothing else (never your training, nor anything from Garmin or Strava), and Tracko doesn't keep it.
Training AI. Tracko never uses your data, from Garmin or anywhere else, or anything worked out from it, to train, evaluate or improve AI models. Under Anthropic's commercial terms, what Tracko sends to its API isn't used to train its models; Anthropic may keep it for a limited time, and may review it if it's flagged for misuse.
Claude Code. Ben also uses Claude Code, Anthropic's coding assistant, to fix and build Tracko (Anthropic's row in Who it goes to, above, says what it reads). It never reads anything from Strava. For a member who has connected Garmin, it reads none of their training or recovery data, nothing Tracko builds from it, and none of their screenshots. Ben's Claude Code account is set so that what it reads isn't used to train Anthropic's models.
Who can see it
Other members can't see your training, plan, routes, heart rate or recovery. Tracko is run by one person, Ben, who has administrator access to where it's stored, through Cloudflare. He'll only look at your data when it's needed to help you or fix a problem, or if the law requires it. While a friends notification waits to be sent, Cloudflare's dashboard can show who it's for and the name in it.
In Friends, which every member has, with a friend code and the choice of Findable or Private made when they join:
- Your name and photo are seen by your friends, by people you ask to be friends, by anyone with your friend code, QR code or link (even if you're Private), and, if you're Findable, by members searching by name. A new code stops the old one, and its link, working.
- If you answer a friend request with Not now or Block, the person who asked isn't told.
- The people in a run together see that run: the day, the distance and pace together, who's in, and the asker's line about when and where to meet. In a group, that can include your friend's other friends, who see your name and photo. The pace together can be the slower runner's usual easy pace, and the distance together can be all of the shorter runner's run. If one of you says Not sure about your pace, the pace together is the other's usual easy pace, and you're both told so. If you ask for a run and run further than the run together, the friends you asked see how much ("Ben runs 2 km first"), which shows your planned distance for the day. If a friend you asked runs further, you aren't told how much. If you have no plan that week, Tracko adds the run to your week, sized from your longest run in the last six weeks (at least 5 km), or less if your physio limits say so, so the distance together can show either. Because you then never run any of it first, a friend may be able to tell you have no plan that week. In a workout together they also see the kind of session and the pace of its hard parts. If you run only part of it, they see how much, not why. In a group, friends who've been asked but haven't joined yet see the day, the pace together and how far those in are running, without names, which can be your own easy pace and distance.
- A friend who asks you for a run has the changes to their own plan chosen to suit yours too, before you answer, so they may be able to guess something about your week. When you ask a friend for a run, they see when the request ends: the evening before your plan would first change for it, so they can tell which day that is. If a run doesn't go ahead when it's accepted, because one person's plan has changed since the request, the other is told that much, not what changed. Nobody sees anyone else's plan.
- A friends notification shows the name of whoever asks you to be friends or to run, says yes to your run, or withdraws a run request they sent you, on your lock screen or watch. So does one saying a run you asked for didn't go ahead when your friend accepted it: it names that friend.
- Strava may show on its own that you ran together, from your activities there.
- Apart from the friends notification, Tracko doesn't send friends' names anywhere outside Tracko: not to Strava, Garmin, your calendar feed, intervals.icu or the workouts sent to your watch, the coach, or Tracko's other notifications.
A few club organisers may be made admins in Tracko, to invite people and help run the club. Admins see members' email addresses and what they've added in Settings → Profile (name, photo, date of birth, sex and emergency contact), whether they've connected intervals.icu, and how many runs and kilometres they've done since joining. In Club stats, that's each member's runs and kilometres, and the day of their last run, from Garmin too if they've connected it, and the club's totals, everyone's added up, which admins can post. They don't see anyone's training, routes, heart rate or recovery, whether anyone has connected Strava or anything from it, or anyone's friends, friend requests, blocks or runs together, and they can't reach Tracko's database. Nor do they see whether anyone has connected Garmin, or anything else from it. They see whether the coach is available to each member, as they decide that, but not whether the member has turned it on. They also see what the coach has cost that month, for everyone together. Admins do see the bug reports and suggestions members send, with any screenshots, which show whatever was on the screen at the time (that can include your training, your friends' names and photos, or whether you've connected Strava).
Keeping it secure
Everything travels over encrypted connections, sign-in uses Cloudflare Access, each member's data is kept separately, and keys for connected services are stored encrypted. No system is perfectly secure. If a breach were likely to cause you serious harm, we'd tell you and the Office of the Australian Information Commissioner.
How long we keep it
For as long as you have an account, with a few things kept for less. From Strava, Tracko keeps your athlete id and tokens only while you're connected, and the ids of the activities it wrote to, with what it wrote, for 7 days. If you remove Tracko in Strava's settings, it deletes them once Strava confirms it, or, if Strava doesn't answer, after trying again for 7 days. The ids of your new runs and gym sessions there, kept for 3 days, and those in Tracko's log of its background jobs, kept for 7, aren't deleted with the rest when you disconnect Strava or delete your account: they go by themselves. From your Garmin connection, Tracko keeps what it gets, with your Garmin user id and tokens, only while you're connected. When you disconnect Garmin, remove Tracko in Garmin Connect or delete your account, Tracko deletes straight away everything it got through the connection for you and what it built from those activities and readings: their maps, splits and records, and the coach's notes written from them. Your plan, and runs together already agreed, stay, though your runs from Garmin may have shaped them. Garmin history you imported from an export stays until you remove it under Garmin history in Settings, or delete your account. What's already on Strava or in your Garmin Connect stays there. A few copies go by themselves instead: Tracko's copy of what it wrote on Strava, and its log of its background jobs, within 7 days, and anything deleted from Tracko's database, which its restore history holds for 30 days more. In Friends, a friend request lapses 30 days after it was sent, who you've looked up is used for an hour, and the counts for the limits for a day; each is deleted after that. A run request ends when it's answered or withdrawn, when either of you removes or blocks the other, or at its deadline. The paces, summary and changes worked out for it are deleted when it ends (for one that reaches its deadline, or whose friend's account is deleted, the next time anyone opens Tracko), and the request itself 30 days after that. A run together is kept until 112 days after its day, with who's in it and what Tracko moved or added in each plan for it, then deleted; its line about when and where to meet goes with its request, 30 days after the run was agreed. Friends and blocks stay until you remove them. Screenshots sent with a bug report are deleted once it's fixed, or after 30 days.
When you delete your account, everything stored for it is deleted straight away from Tracko's storage, including your intervals.icu key and everything Tracko held from Strava, Tracko asks Strava to revoke its access, it asks Garmin to end the connection if you've connected Garmin, and you're taken out of your friends' lists and out of any runs together still to come. The one exception is what's kept in Tracko's database: your training plan, and what Friends keeps (your name as Friends shows it, your friend code and choices, friends, requests, blocks and runs together). Its restore history, kept only so we can recover from a serious fault, holds them for 30 days more before they're gone for good. If we ever had to use it, we'd delete again what's kept for accounts deleted since. Your data stays in your own intervals.icu, Garmin Connect and Strava accounts, which you manage there. Cloudflare's technical logs are kept for a short time under Cloudflare's own policies, and Tracko's own log of its background jobs for 7 days. Once your account is deleted, we email you at its address to confirm what's been deleted. The page says when that email has gone; if it doesn't, email [email protected] and we'll confirm it in writing.
Your choices and rights
Wherever you live, you can:
- See or correct what we hold: most of it is shown in Tracko, and you can ask us for the rest. Your name, photo and the rest of your details can be changed or removed in Settings → Profile. To correct what came from intervals.icu or Garmin, change it there, or ask us.
- Get a copy of your data: email [email protected] from the address you sign in with, and we'll send you what we hold for you within 30 days.
- Delete your account and data: Settings → Profile → Delete my account. We email you to confirm it, and if that email can't be sent, we confirm it when you ask.
- Disconnect intervals.icu or Strava from Settings, or from those services' own settings. When you disconnect Strava in Settings, Tracko deletes everything it holds from Strava for you, asks Strava to revoke its access and says so there. When you remove Tracko in Strava's settings, Tracko deletes it all once Strava confirms it, or, if Strava doesn't answer, after trying again for 7 days; either way, it emails you to say so, and if that email can't be sent, we confirm it when you ask. Only the activity ids that go by themselves within 7 days (How long we keep it, above) are left.
- Disconnect Garmin, if you've connected it, in Settings, or remove Tracko in Garmin Connect. Either way, Tracko deletes straight away everything it got through the connection for you and what it built from it (How long we keep it, above). When you disconnect in Settings, it also asks Garmin to end the connection.
- Turn the coach on or off in Settings → Profile, under Your coach, if the club has made it available to you (AI transparency statement, above).
- Withdraw your consent at any time: turn the coach off, disconnect a service, or delete your account. That doesn't change what was done before.
- Choose who can find you (Findable or Private), make a new friend code, remove a friend or block someone, on the Friends page.
- Turn off notifications, or just the Friends one, from Settings.
To ask a question or make a complaint, email [email protected]. We'll reply within 30 days. If you're not happy with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
If you're in the EU or the UK
If you're in the European Union or the United Kingdom, the GDPR or the UK GDPR applies to your information, as well as the rest of this policy:
- Who's responsible: the controller is Ben Fowler, in Victoria, Australia, at [email protected].
- Why we're allowed to: to provide Tracko to you under its terms of use, our contract with you; with your consent, for your health information, each service you connect and the coach, once you turn it on; and for our legitimate interests in keeping Tracko secure and fixing problems. You can withdraw your consent at any time, by turning the coach off in Settings → Profile, disconnecting a service or deleting your account. That doesn't change what was done before.
- Your rights: to access what we hold about you, to correct it, to have it deleted, to restrict how we use it, to object to our using it, to have what you gave us in a form you can take elsewhere, and to withdraw your consent. You can do much of this yourself in Tracko (above); for anything else, email [email protected], and we'll reply within a month.
- Objecting: you can object at any time to what we do for our legitimate interests (keeping Tracko secure and fixing problems). Email [email protected], and we'll stop, unless we have compelling reasons to carry on that outweigh your interests and rights.
- Complaints: you can also complain to the data protection authority where you live or work (in the UK, the Information Commissioner's Office).
- Transfers: Tracko is run from Australia, and the services in Who it goes to handle your information outside the EEA and the UK too, much of it in the United States. The European Commission hasn't made an adequacy decision for Australia. For Cloudflare and Anthropic, which store and handle your information for us, we rely on the safeguards in their data processing terms, such as the European Commission's standard contractual clauses; you can ask us at [email protected] for a copy. What you email us is kept in Tracko's mailbox, which Zoho holds for us in Australia. intervals.icu, Garmin, Strava and the calendar app you add your calendar link to are services you have your own account with, under their own terms; Esri, Amazon Web Services and Google are sent only what's needed to fetch a map or the app's lettering, under theirs; and the push services only carry a notification to your device, under theirs.
- How long: as in How long we keep it, above.
Changes
If we change this policy, we'll update the version and date above and tell you in Tracko. If a change affects how your health information is used, we'll ask you to agree again. A change never turns the coach on for you.