Garmin, Oura, Apple Health — 4 sync gaps siloing your data

Running three fitness platforms at once sounds excessive. It isn't. Garmin owns GPS and structured training load. Oura owns passive recovery and sleep temperature. Apple Health owns the aggregation layer — in theory. The gap between "in theory" and "in practice" is where your data goes to die. I've spent the last few months testing sync reliability across Garmin Connect (version 4.88, May 2026), Oura app (version 3.57, April 2026), and Apple Health on iOS 18.4, and found four specific failure points that most setup guides quietly ignore.

Why Multi-Wearable Data Silos Keep Getting Worse

Each platform has a commercial incentive to keep you inside its own ecosystem. Garmin wants you opening Garmin Connect. Oura wants you checking the Oura app. Apple Health is theoretically neutral — a data aggregation layer, not a product in itself. But even Apple's neutral posture breaks down when duplicate entries inflate your step count, or two different resting heart rate readings make trend analysis meaningless.

The deeper technical issue: HealthKit, Apple's underlying data store, does not automatically deduplicate. If both Garmin and Oura write HRV data for the same overnight window, you get two entries. Some third-party apps handle this gracefully. Most don't bother.

Multi-wearable ownership has become normal enough that Apple, Garmin, and Oura all publish integration guides now — but none of them tell you what actually happens when all three run simultaneously. That's the gap this piece fills.

Garmin → Apple Health: What Syncs and What Doesn't

Native Garmin-to-Apple Health sync has existed since around 2018, but the permission model is granular in ways that consistently catch people off guard.

Enabling the connection

1. Open Garmin Connect on iPhone.
2. Tap the profile icon (top left) → Settings → Connected Apps.
3. Scroll to Apple Health and tap it.
4. Toggle on the categories you want: Workouts, Heart Rate, Sleep, Steps, Active Energy.
5. Switch to the Health app → Settings → Privacy → Apps → find Garmin Connect and confirm all categories are toggled On.

That last verification step is where most guides stop. It's also where the most common problem hides. Garmin Connect requests both read and write permissions for some categories but only actually uses write. If your Apple Health step count ever looked roughly double what Garmin shows, this is usually why — the iPhone's built-in accelerometer and Garmin are both writing steps to the same bucket, no deduplication logic applied.

Fix: in Health → Steps → Data Sources & Access, drag Garmin Connect above iPhone in the priority list if you trust your Garmin watch over your phone's accelerometer. Or keep iPhone on top for indoor days when you leave the watch behind. Either choice is valid — just make it deliberately.

What Garmin does NOT push to Apple Health natively (Garmin Connect 4.88, May 2026):

• Body Battery score (Garmin proprietary, no export path)
• Training Status and Training Load
• Respiration rate during sleep (some HR data writes, but not the dedicated respiration metric)
• Hydration tracking

If you want Body Battery or Training Load available outside Garmin's app, you're looking at either the Garmin Developer API or an intermediary like Health Auto Export (iOS, $3.99 for the full feature tier). Neither is zero-effort.

Oura Ring → Apple Health: Partial Sync and the Export Workaround

Oura's Apple Health integration improved noticeably with app v3.5 in late 2024, but it remains asymmetric. Oura pushes certain categories into Apple Health; others stay walled inside Oura's own platform indefinitely.

What Oura sends to Apple Health (v3.57, April 2026)

The Readiness score is the number people most want in Apple Health. It doesn't go there. Full stop.

The practical workaround is Oura's CSV data export: go to Oura app → Profile → Data Export, choose your date range, and request the file. It arrives in your inbox within a few minutes and includes daily granularity on every metric — Readiness, HRV balance, temperature trend, the lot. I've used this CSV alongside Garmin Connect's own activity export to spot a clear correlation between high-load training weeks and Oura's 3-day lagged temperature response, a pattern that's invisible inside either app's native dashboard.

Preventing HRV duplicates when Oura and Garmin both write

Both Garmin and Oura write HRV values to Apple Health's Heart Rate Variability field. Because they measure from different sensor positions — wrist versus finger — overnight averages often differ by 10–20ms, and both end up in your Apple Health record.

To control which one dominates your trend chart: Health → Heart Rate Variability → Data Sources & Access → drag your preferred source to the top. Most users should prefer Oura here. Finger-based PPG sensors tend to produce lower measurement noise than wrist-based sensors for overnight HRV, though neither is clinical-grade. For the full configuration of Apple Health source priority across three wearables, the Garmin, Oura, and Whoop sync gaps guide has the exact source-ordering setup that prevents conflicting data from muddying your trends.

Whoop vs Oura Recovery Score — Not the Same Metric

This comparison comes up every time someone owns both devices, and most write-ups treat the two scores as interchangeable. They're not. The structural difference matters when you're running both and trying to decide which one to act on in the morning.

Whoop Recovery is calculated primarily from HRV, resting heart rate, sleep performance, and respiratory rate. It outputs a percentage (0–100%) calibrated against your personal 90-day baseline. Sleep performance weighs heavily — a 5-hour night against a 7-hour target drags the score down regardless of how strong your HRV looks.

Oura Readiness uses similar inputs — HRV balance, resting HR, body temperature deviation, sleep, activity balance — but the temperature deviation component is unique. It's a rolling comparison of skin temperature against your personal baseline, measured via infrared sensors in the ring. This makes Oura particularly sensitive to illness onset and, for people who track it, menstrual cycle phases — in a way that Whoop simply isn't equipped to detect.

Here's the contrarian take: for most non-elite athletes, Oura Readiness is more actionable than Whoop Recovery — not because the algorithm is superior, but because the free tier gives you the complete picture. Whoop locks historical trends and full data access behind a mandatory membership. Pause your subscription for even a month, and you lose the context window. Oura's free tier delivers full Readiness scores with no paywall. Given that the membership gap between the two runs to roughly $120–$140 per year, that difference compounds fast. The 3 free apps that replace Whoop's $239/yr plan comparison is worth reading before you renew — especially if you're primarily tracking recovery rather than live heart rate coaching.

Strava and Apple Health — Closing the Workout Loop

Strava's Apple Health integration is cleaner than Garmin's, but carries its own wrinkle. By default, Strava writes workouts to Apple Health. If you record a run on Garmin and Garmin auto-uploads to Strava, you end up with a duplicate workout entry in Apple Health — same activity, two records, inflated weekly calorie totals.

Preventing duplicate workout entries

1. In Strava → Settings → Health & Privacy → Apple Health, note which data Strava is actively writing.
2. In Apple Health → Browse → Activity → Workouts → Data Sources & Access, confirm both Garmin Connect and Strava appear as sources.
3. If both are active: disable Garmin Connect's workout write permission (keep Garmin active for HR, HRV, and other biometrics) and let Strava be the sole workout source. Strava pulls from Garmin anyway, so the activity data is identical — you're just eliminating the redundancy.

The same fix resolves VO2 Max duplication. Garmin estimates VO2 Max from GPS workouts and pushes it to Apple Health's Cardio Fitness field. Strava calculates its own estimate from pace and HR data. If both are writing simultaneously, your trend chart becomes noise. Go to Health → Cardio Fitness → Data Sources and leave only one source active.

For a detailed source-priority map across multiple wearables, the 3 wearables, 1 Apple Health view — fixing HRV duplicates guide walks through the exact ordering that keeps Cardio Fitness, HRV, and step counts clean.

Fitness Data Privacy — What These Platforms Actually Share

Most fitness sync guides skip this section entirely. Given that the data involved includes overnight heart rate, sleep patterns, location history, and temperature baselines, that's a notable omission.

Garmin states in its privacy policy that health data is not sold to third parties. That commitment was tested in July 2020 when a ransomware attack (attributed to the Evil Corp group) took Garmin Connect offline for nearly five days, disrupting sync for millions of users. The incident didn't result in confirmed data exfiltration, but it demonstrated the practical risk of centralizing dense biometric data in a single cloud platform — one that, unlike Apple, does not apply end-to-end encryption at rest.

Oura holds a relatively strong privacy posture for a consumer wearable. They commit to not selling personal data and have published documentation on on-device processing for some metrics. The caveat worth tracking: Oura raised substantial investment tied to healthcare partnerships in 2021–2022, which creates a long-term commercial incentive to eventually monetize aggregated, anonymized population-level data. Their privacy policy permits this under anonymized conditions — worth reading before assuming strict non-use.

Apple Health is the strongest option here. HealthKit data never leaves your device without explicit per-app permission. Apple cannot read your Health data — it is encrypted on-device and in iCloud with end-to-end encryption. Third-party apps reading from HealthKit must disclose their access and cannot share the data with advertisers under App Store rules. For privacy-conscious users, Apple Health as the aggregation layer is the right call.

Strava's privacy history is mixed. The January 2018 global heatmap incident — where aggregate route data inadvertently exposed the locations of military bases and covert facilities worldwide — is the most cited example. Strava has tightened defaults significantly since then, but accounts created before mid-2020 may still have legacy settings active. Check Strava → Settings → Privacy Controls: Flyby should be off, route visibility should be set to Followers Only, and segment leaderboards set to Only You if you run recurring routes you'd rather not map publicly.

For a framework-level view of personal health data security, NIST SP 800-63B offers rigorous baseline thinking around authentication and data access controls — not fitness-specific, but directly applicable to how you authorize third-party apps to read your Apple Health data.

Quick Checklist — What to Do Now

1. Audit Apple Health write permissions first. Go to Health → Settings → Privacy → Apps and revoke access for any app you no longer actively use.
2. Fix step deduplication. In Health → Steps → Data Sources & Access, drag Garmin Connect above iPhone — or make a conscious choice, but pick exactly one primary.
3. Remove Garmin's workout write permission. Let Strava be the sole workout source in Apple Health — it pulls from Garmin anyway.
4. Enable Oura → Apple Health sync for HRV and resting HR, then immediately check for duplicates via Health → Heart Rate Variability → Show All Data.
5. Set HRV source priority. In Health → Heart Rate Variability → Data Sources & Access, move Oura above Garmin if you want ring-based readings to dominate (lower noise for most users).
6. Export Oura CSV monthly for Readiness score trends outside the app: Oura app → Profile → Data Export.
7. Pick one recovery metric as your daily decision signal. Oura Readiness if you want temperature-sensitive illness and cycle tracking; Whoop Recovery if you're already subscribed and use strain coaching.
8. Clean up Strava privacy controls. Flyby → Off. Route visibility → Followers Only. Segment leaderboards → Only You.
9. Audit Cardio Fitness sources. In Health → Cardio Fitness → Data Sources, only one app should be writing — disable the duplicate.
10. Re-audit every quarter. App updates silently reset permission states. Garmin Connect 4.80 (February 2026) re-enabled duplicate sleep data writes for users who had previously disabled them — with no in-app notification.

Sources & Further Reading

• Apple Support — Health app sources and data access — Official documentation for managing HealthKit permissions, setting source priority order, and reviewing what each connected app can read and write.
• Garmin Support — Apple Health integration guide — Step-by-step permission setup for Garmin Connect on iPhone, including the category-level toggle documentation for Garmin Connect v4.x.
• Oura — Help Center: Data Export and Privacy — Oura's official documentation covering the CSV export process, which metrics are included, and their privacy policy commitments around health data.
• Electronic Frontier Foundation — Mobile Health App Privacy — EFF's analysis of what consumer wearable and health platforms do with biometric data, including data broker relationships and third-party sharing risks under current US regulations.
• NIST National Cybersecurity Center of Excellence — Health IT Security — Framework-level guidance on protecting personal health data, relevant for users who grant third-party iOS apps access to Apple Health's sensitive biometric records.