How Health Connect works: the complete guide for Android

You have a Galaxy Watch, a Pixel Watch, or any Android wearable, and at some point you've found yourself looking at the Health Connect app wondering what it's for. It's not a fitness dashboard, has no fancy charts, and doesn't record any data on its own. Yet it's the component that holds together the entire Android health ecosystem. Understanding how it works helps you fix sync problems, take control of your permissions, and understand where your data actually goes.

What Health Connect is (and what it isn't)

Health Connect is an Android API and system app distributed by Google. Its main function is one thing: letting health apps exchange data between each other in a controlled way, with your explicit consent for each data type. It's not Google Fit version two (even though technically it replaced that project). It's not a cloud backup. It's not a dashboard.

The most accurate comparison is an electrical panel: it doesn't produce energy, doesn't consume it, but decides which circuits are connected to each other and with what protections. An app can't read your steps from Health Connect without your explicit permission — and you can revoke it at any time, type by type.

The data flow: where data comes from and where it goes

The actual data flow in a typical Galaxy Watch setup works like this:

1. Watch sensors (accelerometer, photoplethysmograph, gyroscope) capture raw data.
2. Samsung Health receives data via Bluetooth and processes it: calculates steps, heart rate, sleep phases, SpO2.
3. Samsung Health writes a copy of the data to Health Connect, for the data types you've authorized.
4. Health Connect holds this copy in a local database on the phone.
5. Any app that has been granted permission (FitMesh Sync, Strava, a doctor's app, etc.) reads from Health Connect — not directly from Samsung Health.

On Pixel Watch the flow is similar, with Fitbit (or Google Fit, for older devices) replacing Samsung Health as the companion app. On Garmin the path is different: Garmin doesn't write to Health Connect natively, but uses a separate OAuth API — each app must integrate with Garmin Connect directly.

The data types Health Connect manages

Health Connect manages dozens of data types, organized by category. The most relevant for everyday wearable users:

Each data type has its own separate permission. You can grant an app permission to read steps without giving it access to sleep data. This granularity is one of the substantial differences from Google Fit, which had much coarser permissions.

How to activate Health Connect and configure permissions

On Android 14 and later, Health Connect is preinstalled as a system app. On Android 12 and 13, it's available on the Play Store as a separate app. The basic setup process is:

1. Open Health Connect (you can find it in Android settings, under 'Privacy', or by searching in the app drawer).
2. Go to 'App permissions': you'll see all installed apps that have requested access to health data.
3. For each app, you can expand and see exactly which data types it can read and which it can write.
4. Enable or disable permissions individually.
5. If an app like Samsung Health doesn't appear yet, open Samsung Health → Settings → Data management → Health Connect and follow the authorization flow.

What Health Connect doesn't do (important limits to know)

Knowing the limits is as important as understanding the features. Here are things Health Connect doesn't do, which often surprise first-time users:

• •Doesn't sync retroactively: Health Connect can only read data written after permission was granted. If you authorize an app today, it won't see your steps from three years ago — those remain only in the Samsung Health (or Fitbit, etc.) database.
• •Is not a cloud backup: if you lose your phone or do a factory reset, data in Health Connect is lost. Backup depends on the app that wrote that data (e.g. Samsung Health has its own separate cloud backup).
• •Doesn't do visualizations: no charts, no trends, no weekly reviews. To visualize data you need third-party apps that read from HC.
• •Doesn't support all brands equally: Garmin, Polar (via app), Suunto and some others don't write natively to Health Connect. Their access point is a separate OAuth API that each app must integrate individually.
• •Doesn't replace the companion app: you can't use only Health Connect to keep Watch sync alive. Samsung Health (or Fitbit, or Galaxy Wearable) must remain installed and active.

Health Connect and privacy: what actually happens to your data

The privacy model of Health Connect is genuinely stronger compared to traditional cloud APIs, for two structural reasons. First: data stays on the device — Google doesn't have automatic access to Health Connect contents. Second: every access is logged with timestamp and app name, and you can see it in 'Data access history'.

The privacy risk, when it exists, comes from apps that read from Health Connect and then send that data to their servers. A fitness coaching app might read your HRV and archive it in its cloud — but this is app behavior, not Health Connect behavior. The 'Data access history' feature helps you understand who is accessing what and when, allowing informed decisions about which permissions to keep.

Solving the most common problems

Most Health Connect problems fall into three categories. Before looking for complex solutions, check in this order:

1. Permission not granted: open Health Connect → App permissions → find the app not receiving data → verify that the relevant types are enabled for both read and write.
2. Samsung Health not writing to HC: in Samsung Health → Settings → Data management → Health Connect, verify that sync is enabled and the data types you need are checked.
3. Missing historical data: by design, HC doesn't sync retroactively. If you just installed an app and historical data is missing, consider manually exporting it from the original companion app.