Privacy Policy

Health data access

On iPhone, HealthDrop requests read access to Apple Health data supported by the app. Categories include sleep and workouts; steps, activity energy, exercise and stand time, flights climbed and distances; heart rate, resting and walking heart rate, HRV SDNN, blood oxygen, VO2 max and respiratory rate; weight, BMI, body fat, lean mass and temperatures; and supported walking mobility metrics. Actual availability depends on your device, data sources and Health permissions. The app does not request permission to write these records to Apple Health.

On Android builds with Health Connect support, HealthDrop requests read access to steps, resting heart rate, HRV RMSSD, sleep and exercise sessions. The initial Android export is a fresh snapshot of the last 30 days. It does not request extended-history, background-health-read or health-record-write permission. You may manage or revoke health access in your platform's health settings.

Export destinations and automatic exports

On iPhone, exports can be written to your iCloud Drive, shared through the system share sheet, or posted to an HTTP endpoint you configure. iCloud export may also run when you open or resume the app if the launch-export setting is enabled, and through best-effort HealthKit/background refresh tasks. Turning off the launch-export setting controls launch/resume export; it does not currently disable the iOS background iCloud export path. Share-sheet and HTTP endpoint exports require a manual action in the current implementation.

On the initial Android Health Connect build, exports require an explicit foreground action and use the system share sheet only. No health snapshot is sent automatically, and Android does not support iCloud or HTTP endpoint export in that version. A new snapshot reflects currently readable records; HealthDrop cannot recall or modify copies previously shared with another app.

The destination you select receives the exported health data. For iCloud, Apple manages the cloud service under your Apple account. For a configured HTTP endpoint or a share recipient, that destination's handling of the file is outside HealthDrop's control. HealthDrop does not provide a hosted health export endpoint.

Crash diagnostics and app updates

Production builds use Sentry for crash and error diagnostics. Reports may include technical app, device, operating-system, stack and runtime context. The app does not intentionally attach health records, export files or webhook credentials to these diagnostic events. The Sentry configuration disables default personal-information collection and console/network-request/touch-event breadcrumbs. Performance tracing is not configured. These safeguards do not guarantee that every technical diagnostic is anonymous.

Expo's update service is used to check for and deliver compatible app updates. App/build/runtime information is used by that service. This is separate from health-file export. This release does not include an advertising or product-analytics SDK.

Local storage and copies

Export settings, including any configured HTTP endpoint and token, are stored locally by the app. Exported files may be retained in the destination you chose and, for share export, in the app's cache. Removing or revoking a health grant does not automatically remove earlier export copies from those destinations. Manage those copies through the destination's controls.

Contact

For support or privacy questions, use the contact links on the HealthDrop support page.