Deep Apple Health
A complete round-trip, both directions.
Runara talks to Apple Health both ways. It reads your resting and peak heart rate to anchor your training zones, and reads route geometry for past workouts so the History tab can map them.
When you finish a session it writes a complete HKWorkout back, the route polyline, heart-rate samples, distance, active energy, and per-segment events with distance metadata. Apple Health, Apple Fitness, and any third-party HealthKit reader then see exactly the workout your watch recorded.
Because your workouts live in Apple Health rather than a Runara database, they survive even if you delete the app, and nothing is ever copied to a server.
Grant Health read and write access once, on first launch, that is the whole setup.
Runara reads your resting heart rate and scans the last ninety days for your peak, so your five zones anchor on your real physiology, not a guess.
Every finished workout writes back complete: route polyline, heart-rate, distance, and energy samples, and each split as a segment event with real distance metadata. Step samples come along for foot sports, stroke counts for swims.
From there, Apple Health is the single source of truth: Apple Fitness, your rings, and any app you allow all read the identical workout. Runara stores only your configuration.
What happens to my workouts if I delete Runara?
Nothing. They live in Apple Health, not in a Runara database, so they stay exactly where they are. Only your screens, plans, and settings are Runara’s own, and those never left your devices either.
Can other apps read my Runara workouts?
Any app you grant Health access can read them, they are standard, complete HealthKit workouts with routes and samples. That is deliberate: your data should be portable, and permission should be yours to give per app.
What does Runara actually read from Health?
Resting and peak heart rate to anchor your zones, your workout history for the History tab and achievements, and route geometry for past workouts so they can be mapped. Reading happens on-device; nothing read is ever transmitted anywhere.