Bide Health — Privacy Policy
Last updated: 2026-07-12
Bide Health is built on one rule: your health data never leaves your device. This document explains exactly what that means.
The short version
- Bide Health has no servers, no accounts, and no analytics or crash-reporting SDKs.
- Bide Health never makes a network request. There is nothing in the app capable of sending data anywhere.
- Everything the app reads from Health, computes, and caches stays in local storage on your device (and, for widgets, in an App Group container shared only between Bide Health and its own widget extension — still on your device, never off it).
- If you delete Bide Health, its cached data is deleted with it. Nothing persists anywhere else because nothing was ever sent anywhere else.
What Bide Health reads from Health
With your permission, Bide Health reads the following from the Health app, only to display it back to you and compute the on-device estimates described in the app (training load, sleep quality, readiness, critical power, etc.):
- Heart: resting heart rate, heart rate, heart rate recovery, heart rate variability (SDNN), VO₂ max
- Activity: steps, walking/running distance, active energy, exercise minutes, flights climbed, workouts (including routes, for elevation data on hikes)
- Sleep: sleep analysis (stages, if your source records them), respiratory rate, blood oxygen, wrist temperature
- Body: body mass, biological sex, date of birth — biological sex and date of birth are used only to seed default training-load and heart-rate-zone calculations (Banister TRIMP coefficients, age-predicted max heart rate); you can override both in Settings at any time
- Mindfulness: mindful session data
Bide Health never writes anything back to Health — it only reads. You control every one of these individually in the Health app under Sharing → Apps → Bide Health. If you revoke access to something, the corresponding card or feature simply stops updating; nothing about revoking access is visible to Bide Health (this is an iOS privacy protection for read access, not a Bide Health choice).
What Bide Health stores, and where
| What | Where | Why |
|---|---|---|
| Cached metric values, computed year-over-year history | On-device database (SwiftData) | So the dashboard loads instantly instead of re-querying Health on every launch |
| Latest readings, training-load state, your preferences | On-device UserDefaults |
Instant launch, and to remember your settings |
| Workout summaries, per-workout training load, time-in-zone breakdowns | On-device file storage, excluded from iCloud/device backups | Same as above, and health-derived data is deliberately kept out of backups |
| Widget snapshot (VO₂ max, resting heart rate, training load) | An App Group container shared only with Bide Health's own widget | So the widget can display current numbers without launching the app |
None of this is a server, a database you don't control, or anything reachable from outside your device.
Third parties
There are none. Bide Health has no third-party dependencies of any kind — no SDKs, no analytics, no advertising, no crash reporters. The only frameworks it uses are Apple's own (HealthKit, SwiftUI, SwiftData, Swift Charts, WidgetKit, WorkoutKit).
Children's privacy
Bide Health collects no data from anyone, of any age, in the sense that matters here: it never transmits anything anywhere. It is not directed at children and has no age-specific handling because there is no data collection to handle.
Changes to this policy
If Bide Health's data practices ever change, this document will be updated and the in-app version number will reflect the change. Given the app's design — no network stack exists in the codebase — a change of this kind would be a deliberate, visible rewrite, not a quiet update.
Contact
Questions about this policy or the app can be sent to: health@bideapps.com