Google Health / Fitbit Data Notice

Effective 27 August 2026

This notice supplements the Unbroken Protocol Privacy Policy. It applies only when you choose to connect Google Health / Fitbit in the Unbroken Protocol app.

Read-only and optional. We ask for your permission before connecting. The connection reads data; it does not write, edit or delete data in Google Health or Fitbit. You can use the rest of Unbroken Protocol without connecting it.

What we read and why

Activity and fitness: recorded workouts and training details, so they can appear in your training history and provide training context.
Health metrics and measurements: resting heart rate, heart-rate variability (HRV), oxygen saturation and workout heart-rate values, so the app can show biometric and recovery trends.
Sleep: sleep sessions and stages, so the app can show sleep context alongside recovery and training information.

We do not request Google account email, contacts, Drive, Gmail, location, or permission to modify Google Health data. We do not sell this data, use it for advertising, or use it for insurance, employment, credit, diagnosis or treatment decisions.

How the connection works

When you tap Connect Google Health, Google shows its consent screen and tells you which permissions are requested. If you approve, Google sends Unbroken Protocol a limited access grant. The app shows the connection status and lets you tap Sync now to import recent data for the feature. It then shows imported workout, resting heart rate, HRV, oxygen saturation and sleep results.

Google Health / Fitbit data is used only to provide the user-facing training-history, biometric-trend, sleep-context, recovery and coaching-context features that you request. Our use of Google user data complies with the Google API Services User Data Policy, including its Limited Use requirements.

How we protect it

Data moves between the app, Unbroken Protocol and Google over encrypted HTTPS connections.
Google access and refresh tokens are kept on the Unbroken Protocol backend, not in the iPhone app. They are encrypted using AES-GCM before storage and separated by your Unbroken account.
Only an authenticated Unbroken account can request its own connection status, sync or disconnect action. Backend credentials are held separately from the app.
We minimise collection to the three read-only permissions above, use a bounded recent-data import, and do not put Google access tokens, authorisation codes or health-data values in application logs.

Your choices and deletion

You can disconnect at any time from Connected Apps → Google Health / Fitbit → Disconnect. Disconnecting revokes the Google grant and deletes the encrypted Google connection record from the Unbroken Protocol backend. It does not delete original data held by Google, Fitbit or your device. You can also request account deletion or ask a privacy question at welcome@unbrokenclub.com.

Changes to this notice

We will update this notice before materially changing how Google Health / Fitbit data is collected, used, stored or shared.