Brick Privacy Policy
Effective date: November 9, 2026
Brick is a triathlon training app for iPhone, iPad and Apple Watch, published by Fireside WiFi LLC ("we", "us"). This policy explains what Brick does with your information. The short version: Brick has no account, no server and no analytics. What you put into Brick is stored on your own devices, and we never receive any of it. It leaves them only in the ways this policy names: the sessions you choose to book go into your calendar, which syncs through your calendar account (see Your calendar); your iPhone sends your upcoming sessions to your own Apple Watch (see Apple Watch); and backups, exports and plan copies go wherever you send or save them (see Backups and exports). For forecasts and imports, Brick asks outside services directly from your phone, and we aren't part of those requests: a saved place's coordinates go to Apple Weather for its forecast, and the place searches you type go to Apple Maps, with nothing that identifies you (see Weather and places); and, only if you connect Intervals.icu, Brick requests your own activities from Intervals.icu with your Intervals.icu sign-in (see Activity files and Intervals.icu).
Everything stays on your phone
- Brick has no sign-in and no account, and we run no server. Your training plan, your logs, your test results, your race results, your settings and your notes are stored on your iPhone, in Brick's own storage, shared with Brick's widgets on the same phone. Copies leave the phone only in the ways the short version above names.
- We don't collect, receive, sell or share any of your information. We can't see your plan, your training or anything else you enter in Brick.
- Your iPhone's own backup (iCloud Backup or a backup to your computer) includes Brick's data, as it does for other apps, under Apple's terms and your settings. Brick itself writes nothing to CloudKit, and puts nothing in iCloud except the calendar events you choose to book (see Your calendar).
- For forecasts, Brick asks Apple's services directly from your phone: a saved place's coordinates go to Apple Weather, and the place searches you type go to Apple Maps. We aren't part of those requests and receive nothing from them; Weather and places says exactly what is sent.
- Activity files you import are read on your phone, and Intervals.icu is used only if you connect it; Activity files and Intervals.icu says what Brick asks Intervals.icu for and what it never sends.
- Brick makes a random identifier for this iPhone and keeps it in the iPhone's Keychain, so it can tell which of your devices books your sessions. It isn't tied to you, your Apple Account or any identifier from Apple. It's stored with your plan, so your Brick backups carry it, and it's never sent anywhere else.
- iPad and Apple Watch. On an iPad, everything above is true of the iPad: it keeps its own Brick data, separate from your iPhone's, and nothing syncs between them through us or iCloud; you can send it a copy of your plan as a file (see Backups and exports). Your Apple Watch shows what your iPhone sends it, straight from your iPhone (see Apple Watch). Weekly coach notes are written on your device (see Coach notes).
Your calendar
Booking is off until you turn it on. When you turn it on, Brick asks for access to your calendars and then:
- reads your calendars on the phone to find busy times, so it can place sessions around them. It doesn't copy or keep your other events;
- adds your sessions to the calendar you choose: a "Brick Training" calendar it creates, or one you pick.
Booked events sync through the calendar account the calendar belongs to, such as iCloud or Google, under that provider's terms, like any event you add yourself. Each event carries only the sport, the kind of session, the planned time, the session's workout text (if you leave "Workout text in events" on) and a check mark once you've done it. Skip reasons, test results, notes and anything read from Apple Health never go into an event. You can turn booking off at any time, and Brick asks whether to remove its future events.
Apple Health
If you turn on Apple Health, Brick asks to read your finished workouts so it can suggest which planned session each one matches. Brick:
- only reads from Apple Health and never writes to it;
- keeps only the ID of each workout you confirm or decline, or link to a race result, so it can find it again. Workout values such as time, distance and heart rate are read from Apple Health when you look at them and are never copied into Brick's storage. The one exception is gear: a matched run's or ride's distance counts toward its shoe or bike in a cache file on your phone, kept outside Brick's storage and outside backups (see Gear and plan changes);
- never sends Health data anywhere. Health data is never used for advertising or sold, and it is never stored in iCloud.
- asks each device for its own permission: on an iPad, Brick reads the iPad's own Apple Health data, if you turn it on there. Your Apple Watch's Brick app doesn't read Apple Health.
Apple Watch
- Watch workouts. If you turn on Apple Watch workouts, Brick sends your planned swims, rides and runs to the Workout app on your Apple Watch through Apple's WorkoutKit. They go from your iPhone to your own Watch; we receive nothing.
- Brick on Apple Watch. Brick's Watch app comes with the iPhone app. Your iPhone sends it, through Apple's Watch Connectivity, straight to your own paired Watch: the next 14 days of sessions (each one's sport, title, time, workout and done, partial or skipped mark, when it was marked, and a skipped session's reason), your race's name and dates, the week's progress, forecasts for your outdoor sessions, your fixed commitments, and whether your subscription lets you log. When you tap Done, Skip (with its reason) or Start on the Watch, the Watch sends your iPhone that session, what you tapped and when, and your iPhone logs it.
- What the Watch keeps. The Watch keeps the latest update from your iPhone, and any taps it hasn't delivered yet, in its own storage, shared only with Brick's complications on the Watch. Each new update replaces the last. Deleting Brick from the Watch removes it.
- Its own subscription check. Brick's Watch app asks Apple's StoreKit on the Watch whether your subscription is active, and keeps that status on the Watch. Buying or restoring a subscription there goes to Apple, as on the iPhone.
- Nothing through us. None of this passes through us, a server or iCloud.
Coach notes
- Written on your device. Each week, Brick writes a coach note on your iPhone or iPad from your plan and your logs: what got done, what slipped and one suggestion. Rules in the app pick every fact and the suggestion.
- Apple Intelligence, on the device only. Where Apple Intelligence is turned on, Brick asks Apple's on-device model to put those facts into words, and the note says "Written on-device by Apple Intelligence". Brick never uses Private Cloud Compute, so nothing goes to Apple's servers or to us. Otherwise, and always for illness, pain or overtraining, Brick uses fixed wording.
- Your notes stay out of it. The notes you write on logs never go into the model's prompt. Brick only checks them on your device for words about pain, so that it can suggest easing off.
- Stored with your plan. Coach notes, and whether you marked one Helpful or Not helpful, are stored on your device with your plan, go in your Brick backups and plan copies, and are shown by the Coach note widget. Delete all my data erases them. When a subscription ends, your notes stay, and Brick writes no new ones.
Weather and places
Brick shows forecasts for outdoor sessions that have a place, and can suggest moving a session indoors the evening before.
- Places are stored on your phone. You add each place yourself, by typing it or with Current Location. A place is a name, a latitude and longitude, and a time zone, stored on your iPhone with your plan.
- Coordinates go to Apple Weather. To fetch a forecast, Brick sends a saved place's coordinates to Apple's WeatherKit service (Apple Weather), with no name, account or identifier of yours. It does this a few times a day at most for each place (no more than three), and only for places your upcoming outdoor sessions use. Apple sends back the forecast.
- Forecasts are kept briefly. A forecast is kept on your phone only in a temporary cache, shared with Brick's widgets, and deleted when it expires. Brick keeps no forecast history.
- Place search uses Apple Maps. While you search for a place, the text you type goes to Apple Maps to find matches; a typed address goes to Apple Maps to find where it is; and when you use Current Location, its coordinates go to Apple Maps once to name the place.
- Current Location is one-time. Tapping Current Location grants Brick your location for that one use, through the system's own button. Brick reads your location only then, to save that place. It never tracks your location, never reads it in the background and never asks for "Always" access.
- Water temperatures stay on your phone. A swim's posted water temperature that you type is stored with your plan on your iPhone. Brick doesn't check water conditions.
- Apple's privacy policy governs Apple. Apple handles these weather and map requests under its own privacy policy (apple.com/legal/privacy). We receive none of them, so Brick's privacy label still says Data Not Collected.
Activity files and Intervals.icu
Brick can bring in workouts that Apple Health gets poorly or not at all: FIT and GPX files you import, and, if you connect it, your activities on Intervals.icu.
- Imported files are read on your iPhone. When you import a FIT or GPX file from the Files app, the share sheet or another app, Brick reads it on your phone and keeps what it needs to match it to your plan: the sport, start time, duration, distance, heart rate, laps and the recording device's name. These stay on your iPhone, in your Brick backups and in your iPhone's own backups. When you open a file in Brick from another app or the share sheet, the copy iOS gives Brick is deleted once Brick has read it; a file you pick in the Files app stays where it is. Nothing is uploaded, and Brick never writes imports into Apple Health.
- Intervals.icu is optional. It's off until you connect it in Settings > Imports, and it appears only in versions of Brick that Intervals.icu has approved.
- You sign in on Intervals.icu's own page. Connecting opens Intervals.icu's sign-in page in a private browser session, so Brick never sees your password. It's standard OAuth with PKCE, with no secret built into the app, and Brick asks only to read your activities.
- The token stays in your iPhone's Keychain. Intervals.icu gives Brick a sign-in token, with your Intervals.icu athlete ID and name. Brick keeps them in your iPhone's Keychain, on this iPhone only: they're never synced, never put in a Brick backup and never restored to another device.
- What Brick asks for, and when. The list of your activities for the past week or so (each one's start time, type, duration, distance, heart rate, device name and source) and, only for activities Brick doesn't have yet, the FIT file. Brick asks right after you connect, when you open Brick (at most once every 15 minutes), during background refresh and when you tap Sync now.
- What Brick sends. Only those requests and your token. Never the plan, your logs, notes or test results, your places, or anything from Apple Health.
- Strava and Garmin. Activities Intervals.icu got from Strava are skipped, since Intervals.icu can't share their data. Activities that came from Garmin show Garmin as their source. Brick doesn't promise that any source stays available through Intervals.icu.
- Intervals.icu's terms govern your account there. Intervals.icu's privacy policy and terms govern your Intervals.icu account and what it holds. We receive nothing from these requests, so Brick's privacy label still says Data Not Collected.
Gear and plan changes
- Gear is stored on your phone. The shoes and bikes you add (each one's name, kind, starting and retirement distance) are stored on your iPhone with your plan, and go in your Brick backups.
- Gear totals are a cache. Each one's total distance is worked out on your phone from your logs, your imports and, if you turned it on, Apple Health. Totals live in a cache file on your phone, outside Brick backups and your iPhone's backups, and Brick rebuilds the file when it's missing.
- Plan changes stay on your phone. Travel weeks, swaps, moved and repeated weeks, a new long day and skipped weeks change your plan on your iPhone. Each plan edit, and what undo needs to reverse it, is stored on your phone with the plan and goes in your Brick backups.
Race results
- Race results are stored on your phone. A race result you save (the race's name and day, its distance, the finish and split times you type, and your note) is stored on your iPhone with your training history. It goes in your Brick backups, in the plan copies you send to your own devices and in the log export, and nowhere else.
- Only a workout's ID from Apple Health. If you link a race-day Apple Health workout to a result, Brick keeps only that workout's ID. Its times are read from Apple Health when you look at them and are never copied into Brick's storage; the times in a result are the ones you type.
- Nothing is sent. Comparisons with your earlier races and the training totals are worked out on your phone. Delete all my data erases your race results.
Notifications, widgets, Siri and Live Activities
Reminders are local notifications that Brick schedules on your phone; nothing is sent from a server. That includes the evening-before weather suggestion to move a session indoors, which Brick works out on your phone from the cached forecast. Widgets, Siri and Shortcuts run on your phone and read the same data as the app; Brick's complications on Apple Watch read what the Watch app keeps. Live Activities show your current step and its timer on your Lock Screen, in the Dynamic Island and in your Apple Watch's Smart Stack; Brick starts and updates them from your phone, with no server and no push notifications.
Backups and exports
When you back up Brick or export your logs as a CSV file, Brick creates the file and hands it to the share sheet. The file goes wherever you choose to save or send it (for example Files, iCloud Drive, AirDrop or Mail), under the terms of that service. Brick keeps no copy elsewhere and never uploads it. Backups and plan copies hold your coach notes too. A plan copy for another device works the same way: it's a file holding what a backup holds, which Brick hands to the share sheet, for example to AirDrop it to your iPad. Brick never sends it through iCloud or a server. Importing a backup or a plan copy reads the file you pick, on the phone.
Purchases
Subscriptions are sold by Apple through the App Store. Apple handles payment, and Brick never sees your payment details, name, email address or Apple Account. On your phone, Brick asks Apple's StoreKit whether your subscription is active, and keeps that status (with its renewal date and whether it renews) on the phone so its widgets and notification buttons know what you can do. On an iPad, and in Brick's Apple Watch app, Brick asks StoreKit on that device in the same way; one subscription covers all of them.
No analytics, advertising or tracking
Brick contains no analytics, no advertising, no tracking and no third-party SDKs. It doesn't track you across apps or websites, and it has no account to link anything to. On the App Store, Brick's privacy label says Data Not Collected.
Apple may give us aggregated, anonymous App Store figures (such as downloads and sales) and, only if you've chosen to share analytics with app developers in your iPhone's settings, crash reports. Apple provides these under its own privacy policy; they don't identify you.
Not medical advice
Brick's plans are general training guidance, not medical advice. Check with a doctor before starting a training plan, especially if you have a health condition. Brick doesn't diagnose, treat or monitor any condition.
Children
Brick isn't directed to children under 13. Brick collects no personal information from anyone, including children.
Deleting your data
- Delete all my data. Settings > Your data > Delete all my data erases everything Brick has stored on your phone: your plan, logs and settings, your race results, your imported activities, your gear and the gear cache file, your saved places and any cached forecast, and the Intervals.icu token in the Keychain. It also replaces this iPhone's random identifier with a new one.
- Disconnecting Intervals.icu. Disconnect in Settings > Imports deletes the Intervals.icu token from your iPhone at once. Your account on Intervals.icu is yours to manage there.
- Coach notes, the iPad and the Watch. Delete all my data erases your coach notes too. It works on the device you use it on: an iPad's data is erased on the iPad, and deleting Brick from your Apple Watch removes what the Watch keeps.
- Deleting the app. Deleting Brick removes its data from your iPhone, except for its Keychain items, which iOS keeps after the app is deleted: the Intervals.icu token, if you connected, and the random identifier for this iPhone. If you install Brick again, its first launch deletes the old token, so you connect again, and it goes on using the identifier. To remove the token before you delete the app, disconnect Intervals.icu or use Delete all my data first.
- Your iPhone's backups. Backups of your iPhone that you've already made (in iCloud Backup or on your computer) still hold the Brick data they were made with, under your backup settings.
- Apple Health and subscriptions. Apple Health holds nothing of Brick's to erase, since Brick only reads from it and never writes imports there. To cancel a subscription, use your Apple Account's subscription settings.
Changes to this policy
If a future version of Brick handles information differently, we'll update this policy and its effective date before that version is released, and describe the change in the App Store release notes.
Contact
Questions about this policy: contact@examready.io
Fireside WiFi LLC, 785 Buckingham Dr, North Salt Lake, UT 84054-6099, United States