In This Article
The short answer: "Apple Health integration" means an app uses Apple's HealthKit framework to ask for permission to read specific categories of data already stored on your iPhone, to write its own data back into that same store, or both. It does not mean the app automatically receives your whole health history or shares data with every other app you use. Each permission is granted per data type and per direction, read or write, one at a time, and you can see and revoke exactly what you approved at any point in Settings, under Health, then Data Access and Devices. So when a wellness app advertises Apple Health integration, the useful question is not whether it integrates, almost any health app can claim that, but which specific data types it reads, which it writes, and whether that actually matches what you want shared.
- What Is HealthKit?
- Does It Share Everything?
- What Can It See vs. Add
- iPad and Apple Watch
- What Happens to Your Data
- The Misconception
- FAQ
- Key Takeaways
- References
Read key takeaways →
What Is HealthKit, and What Does "Integration" Actually Mean?
HealthKit is the framework Apple built into iOS that stores structured health and fitness data in a private, on-device database. It is not an app itself. The Health app is Apple's own window into that database, and every third-party app that says it "integrates with Apple Health" is really saying it uses HealthKit's programming interface to request access to that same underlying store, the same one the Health app reads from and writes to.
What HealthKit actually stores data as
Quantity types
Numeric, time-stamped data such as step count, heart rate, active energy, or body weight. Each sample carries a value, a unit, and a source app.
Category types
Data that falls into discrete states rather than a number, such as sleep analysis (in bed, asleep, awake) or menstrual flow.
Correlation and workout types
Grouped records like a full workout session, or a blood pressure reading that bundles a systolic and diastolic value together.
Clinical records
A separate, more tightly controlled category covering data pulled from a connected healthcare provider, such as lab results or medications, gated by its own authorization step.
Because every app is talking to the same store rather than to each other directly, HealthKit is closer to a shared filing cabinet than a messaging system. An app that writes your sleep data is not sending it to your other apps. It is filing it in a cabinet that other apps can later ask to look into, if you have separately told each of them they are allowed to.
Does Connecting an App to Apple Health Automatically Share Everything With Every Other App?
No. Each app has to request access to each data type separately, in a specific direction, read or write, and Apple shows you a checklist the first time an app asks so you can approve some categories and deny others individually rather than accepting or rejecting the whole request at once.
Example: a running app
Might request write access to workouts and distance, so its runs show up in the Health app, while requesting read access to heart rate so it can show your pace against effort. It has no access to sleep, nutrition, or any category it never asked for.
Example: a sleep tracking app
Might request write access to sleep analysis and read access to heart rate and respiratory rate, so it can annotate your night with physiology, while having no ability to see or write your workout history at all.
This is also why two apps that both say they integrate with Apple Health are not necessarily seeing each other's data. If your wearable's own app writes sleep data to HealthKit but a nutrition app never requested read access to sleep, that nutrition app still cannot see it, integration or not.
What Can an App Actually See vs. What Can It Add?
Read access and write access are granted separately, and they behave differently once approved. If an app is granted write access to a data type, it can also read back the specific data it wrote itself. If it is granted read access, it can see every sample of that type already in the store, written by any source, not just its own.
An app has write-only access to a data type
It can add new entries and read back its own entries, but it cannot see what any other app or device has recorded for that same type.
An app has read access to a data type
It can see every existing sample of that type in your Health store, going back as far as data exists, from whichever source originally wrote it, not only new data going forward.
You deny an app read access to something
The app is not told it was denied. It cannot distinguish between you saying no and there simply being no data of that type yet, which is a deliberate privacy design, not a bug in the app.
That last point matters for judging any app's marketing. An app cannot prove to you which permissions it holds beyond what you remember granting, so if you want the ground truth of what an app can see or add right now, the authoritative source is Settings, then Health, then Data Access and Devices, not the app's own onboarding screen.
Does Apple Health Integration Work the Same Way on iPad and Apple Watch?
Mostly, but with one hardware limit worth knowing: an Apple Watch can only ever be paired with an iPhone, so any workout or heart rate data your watch collects reaches HealthKit through that iPhone first, not directly through an iPad.
How data actually travels across your Apple devices
1. Apple Watch collects a sample
Heart rate, a workout, or a sleep stage is recorded on the watch and stored in its own local HealthKit store.
2. It syncs to the paired iPhone
The watch can only pair with one iPhone. That sync is how the sample reaches the iPhone's Health store in the first place.
3. It shares to iPad or Mac over iCloud
iPadOS 17 brought the Health app and HealthKit access to iPad, but the iPad only displays and shares data already synced from a paired iPhone signed into the same Apple ID. It does not pair with a watch on its own.
For a third-party app, this means "integrates with Apple Health" on iPhone does not automatically mean the same app has full HealthKit access on iPad. Some apps request and support both; others are iPhone-only even if the same data eventually appears in the iPad Health app through Apple's own sync.
What Happens to Your Data Once It Is Inside Apple Health?
Health data stored on your iPhone is encrypted on-device and locked behind your passcode, Face ID, or Touch ID. If you have iCloud sync for Health turned on with two-factor authentication enabled, that data is also end-to-end encrypted while it moves between your own devices, meaning Apple itself cannot read it.
On-device encryption and end-to-end iCloud sync apply to Apple's own Health store. They describe how your data sits and moves between your devices, not what a third-party app does with a copy after it reads that data out through HealthKit.
The gap worth knowing
Once you grant an app read access and it pulls a data type out of HealthKit, what that app does with its own copy, how long it keeps it, whether it uses it for anything beyond the feature you wanted, is governed by that app's privacy policy, not by HealthKit's encryption. Apple's App Store review guidelines restrict some uses of health data, such as selling it to advertisers, but the honest way to judge an integration claim is to read what the specific app says it does with the data once it has read it, not to assume HealthKit's own security automatically extends into every app that connects to it.
The Biggest Misconception
Common misconception
"If an app says it integrates with Apple Health, it must be pulling in my entire health history."
In practice, integration is scoped down to whichever specific data types the app requested and you approved, nothing more. An app can genuinely and accurately say it "integrates with Apple Health" while only ever touching one or two categories, say, workouts and steps, with no access to sleep, nutrition, cycle tracking, or clinical records at all. The phrase describes a connection method, HealthKit, not a guaranteed scope of access. If you want to know how deep any specific app's integration actually goes, check the app's own permission request screen and your Health app's Data Access and Devices list rather than taking the word "integration" on its own. This is the same reason two apps can both pass a feature checklist for Apple Health support and still behave completely differently in daily use.
Frequently Asked Questions
When an app asks for Apple Health permission, do I have to approve every data type it lists?
No. Apple's permission screen lists each requested data type individually with its own toggle, so you can approve some and deny others in the same request. Denying one category does not block the rest.
Can an app tell if I denied it access to something?
No, by design. An app cannot reliably distinguish between you denying read access and there simply being no data of that type yet in your Health store. This keeps your permission choices private from the app itself.
If I delete an app, does the data it wrote to Apple Health get deleted too?
No. Data an app has written stays in your HealthKit store after you delete the app. If you want it gone, you have to find that data source under Health, then Data Access and Devices, and delete it there.
What happens if two different apps both write data for the same day, like two step counts?
HealthKit keeps both entries rather than merging them into one number. The Health app lets you see which sources contributed and choose a preferred data source per category so your own charts do not double count or conflict.
Does Apple Health integration mean the app also works on Android?
No. HealthKit is an Apple framework built into iOS and iPadOS. An app that integrates with Apple Health on iPhone needs a separate integration, typically with Health Connect, to read or write equivalent data on Android.
Do I need an Apple Watch for an app to integrate with Apple Health?
No. HealthKit stores data from iPhone sensors, manual entry, and any connected third-party wearable whose own app writes into it, not only Apple Watch data. A watch is one possible data source among several, not a requirement for integration to work.
What to Remember
- →Apple Health integration means an app uses the HealthKit framework to request read or write access to specific data types, not automatic access to your whole health history.
- →Read and write permissions are granted separately per data type. Write-only access lets an app read back its own entries; read access exposes every existing sample of that type from any source.
- →Apps cannot tell whether you denied them access to a data type, so the only reliable record of what any app can currently see or add is Settings, then Health, then Data Access and Devices.
- →An Apple Watch can only pair with an iPhone, so watch data reaches HealthKit through that iPhone first. iPad gained its own Health app and HealthKit access in iPadOS 17, but only for data already synced from a paired iPhone.
- →On-device encryption and end-to-end iCloud sync protect data inside Apple's own Health store. Once an app reads data out through HealthKit, what happens to that copy depends on that app's own privacy practices, not HealthKit's security.
- →It genuinely depends on the app. Two apps can both accurately claim Apple Health integration while accessing completely different, non-overlapping sets of data types.
Related on Protocol
How Do You Choose a Health Tracking App That Actually Fits Your Life?
A decision framework for matching an app to the signals you would actually check, useful before you judge any app's integration claims.
Can You Combine Data From Multiple Wearables Without It Becoming a Mess?
Why two devices that both sync into the same Health store can still disagree, and how to pick a primary source per signal.
What Does It Actually Mean for an App to Personalize Your Health Recommendations?
What real personalization requires beyond reading your Apple Health data, and how to tell it apart from generic tips.
Protocol
Want to see what your granted permissions actually add up to?
Protocol reads the HealthKit data types you specifically approve, sleep, HRV, workouts, and more, and brings them into one daily view instead of leaving each reading scattered across separate apps.
Get started freeReferences
Guidelines
- Apple Developer Documentation About the HealthKit framework: how the on-device store, data types, and read/write authorization model work.
- Apple Support Protecting access to a user's health data: documents the per-type, per-direction permission model and why apps cannot detect a denied request.
- Apple Support Manage Health data on your iPhone, iPad, or Apple Watch: how data syncs across a user's own paired devices, including the iPad Health app added in iPadOS 17.
Key Studies
- Perez, Mahaffey, Hedlin, and colleagues (2019) New England Journal of Medicine, volume 381, issue 20, pages 1909 to 1917. The Apple Heart Study enrolled 419,297 participants entirely through an iPhone app to test whether a smartwatch could identify atrial fibrillation, an example of HealthKit-adjacent infrastructure supporting research at a scale not possible with clinic-based recruitment alone.
