TempoLife › Features › Integrations › google-health-connect

Google Health Connect

The only automatic sync TempoLife has. Everything else on Android arrives through it.

LiveAndroid health platformSource label: com.google.android.apps.healthdataChecked 2026-09-02

This integration is built and running in the released Android app.

The honest status

Health Connect is the Android system store that health apps read from and write to. TempoLife reads it; it does not write to it. Every other Android device on this list reaches TempoLife the same way — through Health Connect, not through a connection to the vendor.

Concretely: the Android app bundles a Health Connect plugin, declares the Android health permissions in its manifest, and posts what it reads to per-metric endpoints that accept exactly three source tags — manual entry, the retired Fitbit tag, and health_connect. That whitelist is the reason nothing else can quietly inject data: there is no fourth source.

Data types, one by one

Setting it up

1. Install the TempoLife Android app. Health Connect is not readable from a browser, so the installed app is the requirement, not a preference. Get the app.
2. Open the app and tap Connect Google Health. Android shows its own permission sheet listing each data type. You choose which to grant, and you can revoke any of them later in Health Connect settings without uninstalling anything.
3. Grant steps, sleep and weight for the core experience. These are the three types TempoLife asks for by default.
4. Switch the heart module on if you also want heart rate, resting heart rate, HRV and workout sessions. It is a separate per-account setting and it is off unless you turn it on — a deliberate choice, because heart data is the most sensitive of the set.
5. Make sure something is writing. Health Connect is a store, not a sensor. If no app on the phone writes steps into it, TempoLife will correctly read nothing.

How the sync behaves

The foreground app reads on open: steps including the hourly buckets that draw the last-24-hours curve, sleep sessions with awake, light, deep and REM stages, separate naps, weigh-ins, and — with the heart module on — heart-rate samples, resting heart rate, HRV as RMSSD and workout sessions. A background worker additionally refreshes today's step total only; everything else waits for you to open the app. That split is why the step ring can be current while last night's sleep is not yet in.

The link is read-only in this direction. TempoLife never writes food, water, weight or anything else back into Health Connect, so nothing it stores can pollute another app's view of your data. If you revoke a permission, the previously imported records stay in TempoLife until you delete them there — revocation stops future reads, it does not reach back.

What TempoLife does with the data once it has it

Steps land on the daily total and the hourly curve, and feed the activity-energy estimate that sits beside the day's food. Sleep becomes a length, a stage breakdown and a wake time — and note that TempoLife dates a sleep record by the wake date, so a night that starts on Friday appears on Saturday. Weight becomes a point on the trend line and, where a goal is set, the input to the projection. Heart rate, resting heart rate and HRV are stored as their own series and are only ever shown, never interpreted — there is no diagnosis anywhere in the product.

None of these numbers are medical measurements and nothing here is a diagnosis. Consumer wearables estimate; they do not measure the way clinical equipment does. Talk to a clinician about anything that concerns you.

Privacy of the connection

Every permission is granted by you on the device and can be withdrawn on the device. TempoLife holds no credential for Google Health Connect — no OAuth token, no password, no account link — because it never talks to Google Health Connect at all. Deleting your TempoLife account deletes the imported records with it, and leaves whatever is in Health Connect and in the vendor's own app untouched.

Frequently asked questions

Source: TempoLife application source — assets/js/health-connect.js, api/health_connect.php, api/sync.php, api/fitbit.php, apple/ios/App/App/TempoLifeHealthPlugin.swift · checked 2026-09-02

Other integrations

All integrations · Developer API