Privacy policy

Last updated 14 November 2026

The short version

Pacefire keeps your journal on your iPhone. Your plans can sync through your own iCloud. An account is optional. Without one, Pacefire sends nothing to Borrowed Fire or anyone else. With one, Pacefire's server keeps your name, the email Apple shares, your Apple sign-in, a profile photo if you add one and, unless you turn it off, a backup of your journal. Nothing from Apple Health goes there, except the parts of a run you choose to post to a crew or your coach and, if you join a coach and turn on Sessions done and missed, the distance and time of each planned run you did; only the people you chose see them. If you connect a Garmin account, which is optional, Pacefire's server also keeps that connection, the runs Garmin sends for you, with each run's average and highest heart rate, and your iPhone's push address so it can tell Pacefire a run came in (see Garmin below). Your health information is never used for advertising, never sold, and never stored in iCloud.

What Pacefire reads

• Run routes, read only. The first time you tap Show the route on a run, Pacefire asks Apple Health for access to your runs' GPS routes. Once you allow it, Pacefire reads a run's route to draw it on that run's screen and as a small picture in History, and, on your iPhone, to find the reps of an interval session in it and grade them. When a run has no route (a treadmill run, or you haven't allowed routes), Pacefire reads that run's distance samples from Apple Health, under the runs and distance access you already gave, for the same purpose; it never asks for new access to do this. Routes and distance samples stay on your iPhone.
• Apple Health, read only. With your permission, Pacefire reads your workouts and their walking and running distance from the last year, or from the start of your current season if that is earlier: your runs, and your other workouts (such as rides, strength training, yoga and walks) with their type, time and length. It uses them to show your history, to check each run against your plan, and to mark cross-training, strength and mobility days done. It also keeps the time it last read Apple Health, to show when your runs were last updated. Pacefire never writes to Apple Health.
• Heart rate, calories and running form, read only, each only if you allow it. You › Settings › Apple Health lists each kind of data, what it's for and whether it's on. Pacefire explains a kind before Apple Health asks for it, and asks nothing when the app opens. With your permission it reads, for each run: heart rate (average, max, each rep's average and time in each heart rate zone, measured from your resting heart rate, or an estimate of 60 bpm, up to your highest heart rate in Apple Health over the last six months), active calories, step count (for cadence), stride length, vertical oscillation, ground contact time, running power, and the workout's effort score (the 1 to 10 your Apple Watch estimates, or the one you rate on it). With heart rate, it also works out each mile's average heart rate from the run's route and readings, to grade the run; that stays on your iPhone. It reads them when you open a run, to show them on that run's screen, and when a run you've finished shows on Today, on its session's screen or in the summary after the run, to grade it there; for the zones it also reads your resting heart rate over the last 30 days, if you allow it. When you open You › Settings › Apple Health, or the first run you open after starting Pacefire, it also checks for one recent reading of each kind (and one recent run and route), to show whether that kind is on; it doesn't keep or show that reading. If heart rate is allowed and You › Settings › Your Watch › Heart-rate alert on easy runs is on (it is unless you turn it off), Pacefire also reads your highest heart rate over the last six months and, if you allow it, your resting heart rate over the last 30 days, each time it updates your Watch workouts. It puts one number from them, the top of zone 2 (your resting heart rate plus 70 % of the gap up to that highest heart rate), or the number you set yourself, into your easy and long run workouts on your paired Apple Watch, so the Watch can buzz above it. Apart from that number on your Watch, they stay on your iPhone, are never stored in iCloud, and are never sent anywhere.
• What your Watch saves with a run. Elevation gain and the weather during the run (temperature and humidity) come with the running workouts you already allowed. Pacefire shows them on the run's screen and keeps them on your iPhone.
• What you paste in. If you import check-offs from the old web tracker, Pacefire keeps only the dates you marked done. It ignores everything else in the pasted text.

What Pacefire stores, and where

• Your training plans, the ones you import, build or add as a sample, and the changes you make to them. They are files on your iPhone.
• Your journal. Days you mark done, effort, notes, pain areas, days off with their reason (sick, tired, busy, travel or just not today), the reason you give for a run cut short or a missed run (sick, tired, busy or travel), and what you set on a run after it (its name in Pacefire, which planned session it counts as, and runs you removed from Pacefire; those stay in Apple Health, and stay on this iPhone: the account backup holds only the days). It is a file on your iPhone, protected by iOS file encryption and excluded from iCloud backup. Because it isn't in iCloud backup, it doesn't move to a new iPhone on its own, unless you're signed in to a Pacefire account with journal backup on (below). You › Settings › Journal Backup › Back up now saves a backup file where you choose (for example in Files), and Import a backup restores it on a new iPhone. Pacefire remembers only the date of your last backup.
• Your first name, if you give one (on You), to show at the top of You. It is kept in the app's settings on your iPhone (included in your iPhone's backup, like other settings). Without an account it isn't sent to Borrowed Fire or anyone else; while you're signed in to a Pacefire account, the name you set on You is also saved to your account.
• Settings, such as your race pace and the quick workouts you sent to your Watch, in the app's settings on your iPhone. These are not health information and are included in your iPhone's backup like other app settings.
• iCloud, for plans only. When you're signed in to iCloud, your plans, the changes you make to them, your race paces and your race start times sync through your own iCloud account (Apple's iCloud key-value storage), so they follow you to another iPhone. Borrowed Fire never sees them. Your journal is never sent to iCloud: it's health information. It stays on this iPhone unless you back it up to your Pacefire account (below).
• Run notes. When Apple Health saves a new workout, iOS can wake Pacefire in the background to read it the same way and check it against your plan. A run that comes from your connected Garmin account is checked the same way when you open Pacefire, and, once Pacefire's server has your iPhone's push address (see Garmin below), also when Apple wakes Pacefire in the background for it. Pacefire then shows a notification with the run's distance, pace and the planned session it counted for (for a Garmin run while your iPhone is locked, only its distance, time and pace: see Garmin below). Until you turn them on fully from Today, notifications are quiet (Notification Center only); like any notification they can show on your lock screen and your paired Apple Watch, and you can turn them off in Settings › Notifications › Pacefire. To tell each run once, Pacefire keeps a short list of the runs it has told you about (their IDs in Apple Health, or Pacefire's own ID for a run from Garmin, their start and end times, whether each came from Garmin, and whether its notification was the short form, from around your latest run; the times let Pacefire recognise a Garmin run and its copy in Apple Health as one run) in a file on your iPhone that is kept out of iCloud backup, like the journal. Notifications are made on your iPhone; their text is never sent to Borrowed Fire or anyone else.
• Garmin runs, if you connect Garmin: a file on your iPhone, kept out of iCloud and out of your iPhone's backup, and a copy on Pacefire's server (see Garmin below).
• Widgets and the Live Activity. So Pacefire's widgets and Live Activity can show your plan and how today's run went, Pacefire keeps a small copy of today's and the coming week's planned sessions (with whether each is on your Watch or a day off), this week's planned and completed miles and runs (counted from your runs), which days this week are done, the words that say how today's run matched the plan (such as "Long Run Banked"), and, once today's planned run is done, that run's distance, time and pace and each rep's pace against the coach's target, in a file on your iPhone that only Pacefire and its widgets read. It never holds heart rate, calories, your route, notes or other Apple Health samples, and like the journal it is kept out of iCloud backup. Like any widget or Live Activity, these can show on your Lock Screen, in StandBy and in the Dynamic Island, and a Live Activity can also show on your paired Apple Watch. The run's numbers are marked as sensitive, so iOS can hide them while your iPhone is locked; your plan stays visible. You can remove the widgets, and turn off Live Activities in Settings › Pacefire. Nothing is sent to Borrowed Fire or anyone else.
• The Apple Watch app. If you install Pacefire on your paired Apple Watch, your iPhone sends it the small copy the widgets read (above), without a finished run's distance, time, pace or reps, each time that copy changes, through Apple's WatchConnectivity, directly between your iPhone and your Watch. Nothing else goes to the Watch, and nothing comes back from it. The Watch keeps the copy in a file of its own, out of backup, for its app screen, its Smart Stack widget and its complications, which show your plan, this week's miles and runs, which days are done and the words that say how today's run matched the plan, never a run's own numbers or heart rate. The Watch app never reads Apple Health. Delete all Pacefire data on your iPhone also empties the Watch's copy, the next time your Watch is in reach; removing Pacefire from your Watch deletes it too. Nothing is sent to Borrowed Fire or anyone else.
• Watch workouts. With your permission, Pacefire schedules your plan's runs in the Workout app on your Apple Watch through Apple's WorkoutKit. Apple's Workout app records the run and saves it to Apple Health under Apple's privacy terms.

Your Pacefire account (optional)

Pacefire works without an account. You can sign in with Apple on You or at the end of the welcome.

• What the account keeps. An account ID, your name (Apple shares your name the first time you sign in, and you can leave it out; a name you set on You while signed in replaces it), the email address Apple shares (it can be an Apple private relay address; Pacefire never emails you), your role (runner, or coach if Borrowed Fire makes you one) and when you signed in. Pacefire's server checks Apple's sign-in once and doesn't keep Apple's tokens.
• Your journal, backed up. While you're signed in, your journal backs up to your account unless you turn it off in You › Settings › Account and Backup: for each day, when you marked it done and how, effort, your note, pain areas, a day off and its reason (sick, tired, busy, travel or just not today) and a workout logged on a rest day. It's there so your journal is safe if you lose your iPhone; signing in on a new iPhone brings it back, without changing days that iPhone already has. In Pacefire only you can see it: coaches can't. It isn't end-to-end encrypted; it's stored like the rest of your account (see Where). Turning backup off deletes it from the server; your journal stays on this iPhone.
• Your profile photo, if you add one. Adding a photo arrives in a coming build; this is what happens once you add one. Pacefire keeps the one photo you choose, on Pacefire's server with your account (see Where). Before it leaves your iPhone, Pacefire makes it a small JPEG (at most 512 pixels across) and removes the details a camera adds, such as where the photo was taken. You see it, and so do the people in your crews and households and, once they've approved you, your coach. If you're a coach, the runners you've approved see yours. Nobody else does: it isn't public, and people you've blocked, or who blocked you, don't see it. When someone stops being able to see it (they leave your crew, you or your coach end the coaching, or one of you blocks the other), Pacefire stops showing it to them: a link Pacefire's server gave their app works for one minute. Pacefire on their iPhone drops a copy it already showed the next time it checks; Pacefire can't take back a copy someone saved. Pacefire doesn't analyze the photo. Borrowed Fire may look at it when it reviews a report about you. Changing your photo replaces it. Removing it in Pacefire deletes it from the server, and Delete all Pacefire data and Delete account delete it too. If someone has reported your photo, a copy of it stays with the report, even after you remove the photo or delete your account (see Report under Crew).
• What it doesn't keep. Nothing from Apple Health, except a run you choose to post and, with a coach's Sessions done and missed switch on, the distance and time of your planned runs (see Crew below): no other runs, no full routes, and never heart rate, calories or running form. Your plans aren't sent to the account in this build (if you connect Garmin, your planned runs pass through the server on their way to Garmin: see Garmin below); with that coach switch on, each day's session kind and whether you swapped, rested, edited or did something else are sent, for your coach only. If you connect Garmin, the server also keeps what the Garmin section below lists, which includes each Garmin run's average and highest heart rate.
• Where. Pacefire's server runs on Supabase (Supabase, Inc.) in the United States (AWS us-east-1), which stores and processes it for Borrowed Fire. Row-level security lets each account read its own data and, with Crew, only what other people chose to share with it (see Crew below).
• Signing out (You › Settings › Account and Backup) removes the account from this iPhone and, if Garmin had saved this iPhone's push address, deletes it from the server when your iPhone can reach Pacefire's server (see Garmin below). The account stays, and so does everything on this iPhone.
• Delete account (You › Settings › Account and Backup) deletes your account and everything the server keeps for it, journal backup, profile photo and Garmin connection included, right away, except reports you made and reports about you, which stay as described under Report (Crew). Apple asks you to confirm once more, so Pacefire can ask Apple to revoke Pacefire's Sign in with Apple access, as Apple requires. What's on this iPhone stays, except Garmin runs, which are deleted with the connection.

Garmin (optional)

Connecting a Garmin account is optional, and it arrives in a coming build: this section says what happens once you connect. It needs your Pacefire account. Garmin Connect is Garmin's service; what Garmin itself keeps is covered by Garmin's privacy policy.

• Connecting. You › Settings › Your Watch › Garmin opens Garmin's own sign-in page, where Garmin asks what you allow: sending workouts to your Garmin, and sharing your activities with Pacefire. Pacefire never sees your Garmin password. Garmin gives Pacefire's server access keys for your Garmin account (one to act for you and one to renew it, each with its expiry time), and your Garmin user ID. The keys stay on the server, are never sent to your iPhone, and are used only for what this section lists. The server also keeps which of those two things you allowed, when you connected, when your latest Garmin run started, and when Pacefire last sent workouts or checked the connection. While you sign in, it keeps a one-time code for up to 10 minutes.
• What Pacefire sends to Garmin. Your planned runs, as workouts on your Garmin Connect calendar: each workout's name, its date, its steps (warm-up, runs, recoveries, cool-down), each step's time or distance, and pace targets where your plan or your coach sets them. Your iPhone sends each workout to Pacefire's server, which passes it to Garmin; the server keeps only the workout's date, a key for the planned session, a fingerprint of what was sent and the IDs Garmin gives it, so Pacefire can change or remove that workout later, and doesn't keep the workout itself. Garmin Connect then puts the workouts on your watch. Before you connect, Pacefire tells you this and asks you to agree to it; nothing is sent until you do. Garmin handles what it receives under the Garmin Connect privacy notice. Don't connect Garmin if you aren't allowed to put your plan in your Garmin Connect account, for example because whoever wrote the plan doesn't allow it. Nothing else goes to Garmin: not your journal, notes, effort, pain areas or days off, and nothing from Apple Health.
• What Pacefire gets from Garmin. After you connect, Garmin sends Pacefire's server each run you record; Pacefire doesn't ask Garmin for your earlier runs. Pacefire keeps when it started (with your watch's time offset), how long it took, its distance, its type (such as a treadmill run), your watch's model name, its average and highest heart rate, and whether it was entered by hand, and discards the rest of Garmin's message. If Garmin also sends the run's detailed record, the server reads it once to work out each lap's start, time and distance, keeps only those, and discards the rest, including the heart-rate and position readings in it: Pacefire keeps no heart-rate trace and no GPS route from Garmin. The server also keeps Garmin's own ID for the run, so it recognises the run if Garmin sends it again; that ID is never sent to your iPhone or shown to anyone. Pacefire's server doesn't write Garmin's messages to its logs.
• How Pacefire uses it. To show the run in Pacefire, check it against your plan and grade it (average heart rate included), the same as a run from Apple Health, and for nothing else. Heart rate from Garmin is never shared with a crew or a coach. A coach or a crew sees a Garmin run only the way they see any run: if you post it, or through the coach switches you turned on (see Crew below). A Garmin run you post carries an ID Pacefire makes for it in place of the Apple Health workout ID, never Garmin's own activity ID.
• Waking Pacefire for a new run. So a Garmin run's notification can come while Pacefire is closed, Pacefire's server keeps your iPhone's push address (the token Apple gives Pacefire on that iPhone), with which of Apple's two push services it belongs to and when it was last saved, with your account, for each iPhone where you use Pacefire while Garmin is connected (up to five). When Garmin sends a run, the server asks Apple to wake Pacefire on those iPhones, at most once every few minutes. That signal carries no run, no health data and no text: it only wakes Pacefire, which then fetches the run from Pacefire's server with your own sign-in, as when you open it, and makes the notification on your iPhone. While your iPhone is locked, Pacefire can't read your journal (it stays fully protected until you unlock), so it doesn't yet know how the run matched your plan: that notification is the short form, with only the run's distance, time and pace (never heart rate), and how it went is in Pacefire when you open it. Apple delivers the signal under its privacy terms and may delay or skip it; then the notification comes the next time you open Pacefire. Pacefire doesn't need notification permission for this and asks for none. The push address is deleted from the server when you disconnect Garmin (or remove Pacefire in Garmin Connect), delete your Pacefire data while signed in, or delete your account, and when Apple says the address no longer works. Signing out on that iPhone deletes it too when your iPhone can reach Pacefire's server; if it can't, the address stays until one of those happens, or until someone with Garmin connected signs in on that iPhone, which moves the address to their account. If you never connect Garmin, Pacefire doesn't send it.
• Who receives or processes it. Borrowed Fire, and Supabase (Supabase, Inc.), which hosts Pacefire's server on Amazon Web Services in the United States (AWS us-east-1) and stores and processes the data for Borrowed Fire. No other company receives or processes it: no analytics, advertising, integration, AI or data-processing service.
• Not sold, not shared. Borrowed Fire doesn't sell your Garmin data, and doesn't share it with any third party apart from the hosting above and the people you choose to share a run with.
• No AI. No AI system processes your Garmin data. Pacefire never passes Garmin data, or anything worked out from it, to Apple Intelligence or any other AI model, never uses it to train, test, evaluate, benchmark or improve one, and doesn't let anyone else do so.
• Where it's kept, and for how long. On Pacefire's server, with your account, and on your iPhone in a file that is kept out of iCloud and out of your iPhone's backup. It stays in both places until you disconnect Garmin, delete your Pacefire data or delete your account. Each of those deletes it from your iPhone, and from the server too; Delete all Pacefire data reaches the server only while you're signed in (see Your control). What happens to copies you shared is under Disconnecting below.
• Seeing, correcting and exporting it. Your Garmin runs are in Runs, and each run's screen shows what Pacefire keeps about it, apart from Garmin's own ID for the run. On a run you can change its name in Pacefire, choose which planned session it counts as, or remove it from Pacefire. Those choices are kept on your iPhone and change only what Pacefire shows you and the people you share with; a run you remove is hidden in Pacefire, and the server's copy stays until you disconnect. Pacefire never changes your activities in Garmin Connect: the only things it changes or removes at Garmin are the workouts it put on your calendar. To change the recording itself, edit the activity in Garmin Connect. You › Settings › Your Watch › Garmin › Export my Garmin runs gives you a file of every Garmin run Pacefire keeps, with everything it keeps about each apart from that ID.
• Disconnecting and withdrawing consent. You › Settings › Your Watch › Garmin › Disconnect deletes the access keys, your Garmin user ID, your Garmin runs, the list of workouts Pacefire sent (their dates and Garmin's IDs) and your iPhones' push addresses from Pacefire's server right away, deletes the Garmin runs on your iPhone, and tells Garmin to stop sending. It also unshares the Garmin runs you posted to a crew or your coach, and takes the distance and time of Garmin runs, and the words for how those runs went, out of the days you share with a coach; the words for how your runs went on your household's week are cleared until Pacefire next shares your week. One copy stays: if someone reported a run you posted, the text kept with that report (see Crew). Removing Pacefire from your connected apps in Garmin Connect does the same: Garmin tells Pacefire, the server deletes them, and your iPhone deletes its copy the next time you open Pacefire. Delete all Pacefire data (while you're signed in) and Delete account also disconnect Garmin and delete this data, on the server and on your iPhone. Workouts Pacefire already put on your Garmin Connect calendar stay in your Garmin account until you delete them there. Garmin may keep and use what Pacefire sent it, under its own privacy notice, and Pacefire can't make Garmin remove it. Your activities in Garmin Connect are Garmin's to keep: Pacefire can't delete them.
• Your other rights. You can also object to how Borrowed Fire uses your Garmin data, or ask it to limit that use, and you can ask for anything the controls above don't cover: to see, correct, delete or get a copy of your Garmin data. Email [email protected].

What leaves your iPhone

Nothing leaves unless you act:

• Signing in. Sign in with Apple sends Apple's sign-in token to Pacefire's server, which checks it with Apple and creates or opens your account. Your name, if Apple shares it, is saved to the account. After that the app changes only your own account, and reads only your own data and what others chose to share with you. With journal backup on, each change to your journal goes to your account a few seconds after you make it.

• Sharing a run. A run's Share button shows what it would show and lets you change it: the map, pace and time, the plan and how it went, effort and note. Heart rate is never shared. Before anything is drawn or sent, Pacefire trims the route on your iPhone: it removes every point within at least 400 m (or the distance you choose in You › Settings › Coach and Sharing) of where the run, or each recording in it, started and ended (in a circle moved off that spot by an amount kept secret on your iPhone, so the start can't be found from many shared routes), plus a little more along the route at each end (a random amount, the same each time you share that run), and every point inside a circle around each hidden place you add there. That circle is moved a random distance from the place and is wide enough to keep the place at least 400 m inside, so routes can't be lined up to find it. A shared run doesn't say how much was hidden. You can also leave the map out of every share. If you set Hide start and end to Off and add no hidden places, the whole route can be shared. Share as an image makes a picture on your iPhone and hands it to the share sheet; it goes only where you send it, and nothing goes to Borrowed Fire. Your sharing choices and hidden places are kept in Pacefire's settings on your iPhone.

• Posting to Crew or your coach. See Crew below.

• Connecting Garmin. See Garmin above.

• Export. You › Settings › Export (and the export rows in You › Settings › Journal Backup) create a file of your plans or your completions, which includes run distances and times from Apple Health. The journal backup also holds effort, pain, sick days and notes. Each file goes only where you save or send it.

• Copy findings report (Step 0 findings, in test builds only; not in the App Store app). It puts run dates, the names of the devices that recorded them, Watch workout IDs and the names of Health metadata fields on the clipboard. The clipboard can sync to your other Apple devices through Universal Clipboard. It contains no distances, times or heart rate.

• Apple Maps. To draw a route, the map loads map images for that area from Apple, as any map on iPhone does, under Apple's privacy terms. Your route line is drawn on your iPhone and isn't sent.

• Apple Intelligence. This build doesn't use it. Change this session offers only the options your plan's rules allow, worked out on your iPhone.

• Best time to run (Apple Weather). Off until you turn it on. Then Pacefire asks Apple Weather (WeatherKit) for the hourly forecast where you run, and scores each hour on your iPhone. The request carries only a location: your location while Pacefire is open, if you choose Use my location (iOS asks you first), or a place you picked by name instead. Picking a place sends what you type to Apple Maps to find it. Apple handles these requests under its privacy terms; Pacefire sends nothing about you or your runs with them. Your usual run times, which set the hours it looks at, are worked out on your iPhone from your runs and never sent. The place you chose is kept in Pacefire's settings on your iPhone; Turn off on the card, or Delete all Pacefire data, removes it.

• Route planning. When you plan a route, Pacefire uses your location once (only if you tap Use my location) and asks Apple Maps for walking directions between the start and a few turn points, which sends those points to Apple. Saved routes stay on your iPhone.

• Add to Calendar. This opens Apple's event editor. The event is saved only if you tap Add, and then it follows your calendar's own sync settings. Pacefire can't read your calendar.

Pacefire has no analytics, no crash-reporting service, no ads and no third-party code that collects data. The one third-party package, Supabase's Swift client, talks only to Pacefire's server, and only for the account. TestFlight builds may send crash reports to Apple if you allow it in TestFlight.

Crew

Crew is in test builds (TestFlight) only; the App Store app doesn't show it yet. It needs your account.

What's shared. When you post a run, Pacefire's server gets what the share sheet showed with your switches. These always go: its title, the day and part of day (or the clock time, if you turn Time of day on), the distance, and the run's Apple Health workout ID (see below; for a Garmin run, an ID Pacefire makes instead). These go only if you leave them on: the trimmed route, pace and moving time, the plan session (its name and kind) and how the run went, and effort and your note. With the plan off, a title that is the session's name is sent as "Run". A run from Garmin shows your watch's model name under its title, such as "Garmin Forerunner 265", as Garmin requires; so do Garmin runs you share with your coach. Heart rate, calories and running form are never shared. The post also carries the run's Apple Health workout ID, so sharing the same run again replaces its post instead of adding one; people who can see the post can see that ID, which means nothing outside Pacefire. The server also notes when the post was made and last changed; people you share with can't see those times, and the feed's order comes from a number instead. They can see when each person joined the crew and when each fire was given.

Who sees it.

• Crew: the people in the crew you post to, at the time they look. Crews are invite-only: the person who starts a crew makes invite links, each works once, for 14 days, and the server keeps only a scrambled copy of the link. People in a crew see each other's account name and profile photo (if they added one), the runs each posted to it, and who gave each run a fire. They don't see your email, anything else from your account, your journal or your other runs.
• Your coach: you ask to join a coach with their link, and they approve or decline you. A coach's link works for up to 50 runners for 14 days, and the server keeps only a scrambled copy of it. Before a coach approves you, they see only your account name and that you asked. After, you and your coach see each other's profile photo (if added), and they see the runs you share with Coach and, for each switch you turn on in You › Your Coach (all start off): Sessions done and missed: for the last two weeks and the rest of this one, each day's planned session kind, whether you did it, missed it, rested or took a day off, for a session you did the few words for how it matched your plan (for example "Cut Short" or "Long Run Banked"), and the day off's reason (sick, tired, busy, travel or just not today), the reason you give for a run cut short or a missed run (sick, tired, busy or travel), the distance and time of a run you did (and whether that run came from Garmin), and whether you swapped, rested, edited or did something else on that day; Effort and notes: the effort and note you gave each day. Pain areas are never sent to a coach. Turning a switch off deletes what it shared from every day on the server. A coach can set your race pace and your easy-run heart-rate ceiling; Pacefire puts them on this iPhone, and they drive your Watch alerts until your coach changes them. Leaving or being removed deletes everything you shared with the coach and the targets on our server. The race pace and heart-rate limit they set stay on your iPhone as your own settings until you change them. If your coach clears a target, the last one stays on your iPhone the same way.
• Your household (Our week): a household is a crew for the people you live with. As in a crew, its members see your profile photo if you added one. Nothing else is shared there until you turn on Share my week; then its members see, for this week only, each day's session kind and its status (done, missed, rest or a day off, without its reason), for a session you did the few words for how it matched your plan (for example "Cut Short"), and nothing else: no distances, times, effort, notes or pain. Turning it off, leaving, or being removed by the person who started the household deletes those days from the server.
• Borrowed Fire can see posts and reports when it reviews a report, and keeps the service running. It doesn't use them for anything else.

How long it's kept. Days shared with a coach are the last two weeks and the rest of this one, sent when you open Pacefire; they stay until you turn sharing off, leave the coach, or delete your account. A post stays until you unshare it (from the run's Share sheet), leave the crew, the crew is deleted, or you delete your account. Fires stay until you take them back, leave the crew, block or are blocked by the run's author, or delete your account. Moving a post to another crew deletes its fires. If you're signed in, Delete all Pacefire data unshares all your posts, leaves any coach (deleting what you shared with them) and turns off Our week sharing (deleting your days there) first (if it can't reach the server, it deletes nothing).

Leaving and deleting. Leaving a crew deletes the runs you posted to it and your fires on its runs. The person who started a crew can remove you from it, which does the same. Deleting a crew you started deletes it for everyone, with its runs and invites. Deleting your account deletes your posts (a reported run's text stays with the report, as described below), fires, crew memberships, the crews you started (for everyone in them), your invites, mutes, blocks and rules agreement, and your coaching: what you shared with a coach, and, if you're a coach, your links and your runners' shared days.

The Crew rules. Before you post, give a fire or add a profile photo, you agree to the Crew rules (in the terms). The server keeps which version you agreed to and when.

Muting, blocking and reporting.

• Mute hides someone's runs from you. They aren't told. The server keeps only that you muted them.
• Block works both ways: neither of you sees the other's runs or fires in any crew, or the other's profile photo (a coach included), your fires on each other's runs are deleted, and they aren't told.
• You can unmute and unblock in You › Settings › Coach and Sharing › Muted and blocked.
• Report sends Borrowed Fire the run, person or profile photo you reported, the reason you picked and your note, if you add one. The person isn't told who reported them. Borrowed Fire reviews every report within 24 hours and may remove the run, the photo or the person. Every report keeps who reported it and who it was about (their account IDs), the reason, when, and what Borrowed Fire did about it. A report of a run keeps a copy of the run's text as it was (its title, day and part of day, distance, pace and time, plan and how it went, effort and note), without its route or times. A report of a profile photo keeps a copy of the photo as it was, and where in Pacefire the reporter saw it (in which crew or household, or through coaching). If you report something, your account ID is kept with the report. Apart from the reporter seeing their own report, only Borrowed Fire can see reports, and only Borrowed Fire their copies. They're kept so Borrowed Fire can act on the report and answer a challenge to what it did, so they stay after the run or photo is removed and after the reporter or the reported person deletes their account. They're kept until the report is resolved and then for one year, or longer only if they're needed for a legal claim. After that only a note that a report was deleted, and when, is kept, with nothing about the people in it.

Your control

• Change Health access in Settings › Health › Data Access & Devices › Pacefire.
• Remove a check-off, note or sick day in the session's screen.
• Disconnect Garmin in You › Settings › Your Watch › Garmin, or remove Pacefire from your connected apps in Garmin Connect.
• Unshare a posted run from its Share sheet; leave or delete a crew from Crew's ··· menu; unmute and unblock in You › Settings › Coach and Sharing.
• Delete all Pacefire data (in You › Settings › Account and Backup) deletes your plans and their changes (here, in iCloud, and so on your other iPhones signed in to the same iCloud), your journal and its backups, the list of runs Pacefire has told you about, the Garmin runs on this iPhone, Pacefire's workouts on your Apple Watch, the copy of your plan that Pacefire's widgets read (and its copy on your Apple Watch), and Pacefire's settings, after offering to export your journal first. Your runs in Apple Health stay there: they belong to Health, not to Pacefire. If you're signed in, it also deletes your journal's backup on your account and your profile photo (reports you made or about you stay, as described under Report), disconnects Garmin if you connected it (deleting your Garmin runs, access keys, Garmin user ID, the list of workouts sent and your iPhones' push addresses from the server), and signs you out on this iPhone; if you're signed out, your Garmin connection and its runs stay on the server until you sign in and disconnect Garmin or delete your account; the account itself stays until you delete it in You › Settings › Account and Backup.
• Deleting the Pacefire app also deletes its plans, journal and settings from your iPhone. Workouts already in Apple Health stay there.

Children

Pacefire is not meant for children under 13.

Changes and contact

A changed policy will show a new date at the top. Contact: [email protected].