SummitMetrics is built and operated by Carnagey IO ("we", "us"). This policy explains what data the app handles, where it goes, and what we don't do with it. We've kept it short on purpose. If anything is unclear, email us at the address at the bottom of this page.
SummitMetrics is a HealthKit app. With your permission, the app reads the following Apple Health data so it can show you your training:
With your permission, SummitMetrics also writes data to Apple Health: workouts you record on the watch, including heart rate, distance, route, and calorie samples.
All HealthKit data stays on your device and in Apple Health. SummitMetrics does not transmit HealthKit data to its own servers (we don't operate any), to advertisers, or to other third parties, with two exceptions that are both yours to start: an explicit Strava upload, and the workout summaries you choose to show the people you add in Friends (both described below).
During GPS-tracked workouts (walk, run, hike, cycle, kayak, ski, open-water swim), SummitMetrics uses your location to draw your route. Location samples are stored in Apple Health alongside the workout. If you've enabled iCloud sync, the route is mirrored privately to your iCloud account so the Mac app can display it.
We never share your location data with any third party. The one way
another person can see where you've been is if you turn on Friends
and then turn on Route Maps inside it; that is off by
default, and is described under Friends below.
Workout templates, planned routes, settings, and (optionally) your workout history mirror sync between your devices via your private iCloud database. Apple encrypts this data in transit and at rest. We never see it. Other users never see it; the only thing anyone else can be shown is what you share through Friends, which is kept apart from all of this.
The workout-history iCloud mirror is opt-in and toggled in
Settings → Workout History Mirror. Turn it off and the
history stops mirroring; existing iCloud copies can be deleted from
the same screen.
Friends lets people you invite see the workouts you finish, and lets
you see theirs. Nothing is shared until you turn it on in
Workouts → Friends, and nobody can see anything of
yours until you send them an invitation and they accept it. There
are no public profiles and no way to be found by search.
While it is on, each workout you finish from then on is shown to your friends as a summary:
Each workout also shares its mile splits, its
climb as an elevation profile, and the
weather it was done in (temperature, humidity and
wind). The profile is the height above the workout's own lowest
point, not an altitude, and none of this includes a location. These
are shared unless you switch them off under
Workouts → Friends.
Two more things are shared only if you switch each one on: heart rate (your average, a chart of it across the workout, and the average for each mile), and a route map. A shared route leaves out every point within about 200 meters (650 feet) of where the workout started and of where it finished, so it doesn't lead to your door. Workouts from before you turned Friends on are not shared. You can hide any single workout from the workout's share menu, and workouts drop out of what friends can see after 60 days.
Your friends also see your badges on your profile:
which ones you have earned (a run below freezing, a first marathon),
the date you first earned each, and how many times. Unlike the
workout summaries, badges are worked out from your whole workout
history, including workouts from before you turned Friends on. A
workout you have hidden is left out of them. Badges are shared
unless you switch them off under
Workouts → Friends, which removes the list.
When two people's workouts start and finish at the same time and cover the same distance, SummitMetrics shows them as done together. That is worked out on each phone from the summaries above; nothing extra is shared to make it possible, and no location is used unless both people already share route maps.
Friends runs on Apple's iCloud, not on a server of ours. What you share sits in your own iCloud account, in an area set aside for it and shared only with the friends you have accepted; we can't read it. To do their part your friends can add to that area as well as read it — a kudos they give you is stored there — so your friends can see each other's names on the kudos you receive, and iCloud shows the people sharing with you each other's iCloud names.
Removing a friend ends the sharing in both directions. Turning Friends off deletes everything you shared from iCloud and removes all of your friends.
If you connect a Strava account, SummitMetrics uploads completed workouts you choose to share. Strava's privacy policy then governs what they do with that data. Disconnecting Strava in Settings stops all future uploads. We never share data with Strava unless you've explicitly connected an account.
SummitMetrics counts your reps by reading the motion sensors in your Apple Watch. That happens on your wrist and needs nothing from us. Separately, you can choose to share those recordings so we can make the rep counter better. The setting is Settings → Motion Data → Improve Motion Detection, and it is off unless you turn it on.
While it is on, a gym or pool-swim session sends us the motion-sensor readings from your watch, the activity type, the start and end times, the set boundaries, and the reps, weight and exercise name you confirmed. Along with that goes your watch model, its watchOS version, the app version, and a random identifier the app generates on first launch so one device's recordings can be told apart from another's. That identifier is not your Apple ID, not a hardware serial number, and not Apple's advertising or vendor identifier, and it does not survive a reinstall.
We use these recordings for one purpose: training and testing the model that counts reps and swim strokes. We don't sell them, we don't share them with anyone, and we don't use them for advertising or to build a profile of you. Turning the setting off stops future uploads and immediately deletes anything still queued on your phone.
Because a recording carries only that random identifier and nothing that names you, we can't connect one back to you. That cuts both ways: it is why the data is anonymous, and it is also why we can't pick your past recordings out to delete on request. If you would rather not contribute, leave the setting off.
SummitMetrics captures a small weather snapshot (temperature, conditions, wind) for outdoor workouts using Apple's WeatherKit. The lookup uses your workout's location, sent to Apple's servers governed by Apple's privacy policy. The snapshot is stored locally with the workout. We don't transmit it elsewhere.
Subscription purchases and entitlement checks happen through Apple's StoreKit. We see only what Apple gives us — whether you have an active subscription, which plan it is, and the original transaction. We do not see your Apple ID, payment method, or billing address.
SummitMetrics isn't directed at children under 13. If you believe a child has used the app and you have a concern about their data, contact us at the address below.
Apple may automatically send anonymous crash logs from your device to us through App Store Connect if you've opted into "Share With App Developers" on your Apple device. These logs are anonymous and governed by Apple's policy.
With one exception, SummitMetrics doesn't store your data anywhere
except your own devices, Apple Health, and your iCloud account, so
there's nothing on our end to retrieve, modify, or delete. Manage
Health data in the Apple Health app; manage iCloud data in
Settings → iCloud. What you've shared through Friends is in your
iCloud account too, and Turn Off Friends deletes it.
The exception is the optional motion-data sharing described above. Those recordings do sit on a server we run. They carry no name, email, or account, so we can't tie them to you or pick yours out. Turning the setting off stops any further uploads and deletes whatever is still queued on your phone.
We'll update this page if anything material changes. The "Last updated" line at the top reflects the current version.
Questions or concerns: adam@carnagey.io