Privacy Policy

1. Overview

Health Bridge helps users make selected Apple Health data available to their own local or self-managed tools, such as a personal receiver, database, command-line tool, or AI agent workflow.

Health Bridge does not operate as a hosted health data platform. By default, the app sends data only to the receiver URL configured by the user.

Health Bridge is not a medical device and is not intended for diagnosis, treatment, emergency use, or clinical decision-making.

2. Apple Health data the app may access

With the user's permission through Apple Health, Health Bridge may read selected HealthKit data types supported by the app, such as activity, workouts, sleep, or other health records the user allows.

The exact HealthKit data available to the app depends on:

• which HealthKit permissions the user grants in Apple Health;
• which sync features are implemented in the app;
• which receiver or sync configuration the user sets up;
• which records exist on the user's device.

Health Bridge requests HealthKit access through Apple's system permission interface. Users can allow or deny categories through Apple Health.

3. Read-only HealthKit access

Health Bridge is designed to use HealthKit in a read-only manner.

• The app does not write records to Apple Health.
• The app does not modify Apple Health records.
• The app does not delete Apple Health records.
• The app does not use HealthKit data for advertising, tracking, or data brokerage.

4. How Health data is used

Health data accessed by Health Bridge is used only to provide the app's core functionality:

• reading selected Apple Health records with user permission;
• preparing sync batches for the receiver configured by the user;
• showing sync status, connection status, and error messages;
• supporting local-first personal data workflows.

Health Bridge does not automatically send Apple Health data to the app developer, advertising networks, analytics providers, data brokers, or third-party AI services.

If a user chooses to connect Health Bridge to a receiver, the data is sent to the receiver URL configured by that user. The user is responsible for choosing and managing that receiver.

5. Where data is stored

Health Bridge may store limited app configuration on the user's device, such as:

• receiver URL;
• authentication or pairing token;
• sync status;
• pending sync data waiting to be retried;
• local app settings.

Sensitive pairing or token material should be stored using platform-provided secure storage where available, such as the iOS Keychain.

The user's receiver may store synced data in a database or file system controlled by the user. That storage is outside the Health Bridge app itself and should be managed by the user.

6. Data sent to the developer

Health Bridge does not collect Apple Health data on a developer-operated central server as part of its normal operation.

The developer may receive information only if the user intentionally provides it, for example by:

• sending an email to support;
• sharing logs or screenshots for troubleshooting;
• using a developer-provided demo receiver during testing or app review.

Any demo receiver provided for review should use synthetic or reviewer-provided test data whenever possible, should be revocable, and should be deleted or disabled after review. Users should not send real personal HealthKit data to a demo receiver unless they understand and choose that test setup.

Users should not send real HealthKit values, pairing tokens, receiver credentials, or private receiver URLs in public support channels.

7. Support communications

If you contact support, we may receive the information you include in your message, such as your email address, device or app details, screenshots, logs, or troubleshooting descriptions.

Support information is used only to respond to the request, debug reported issues, and improve the app. Do not include sensitive health values or credentials unless specifically requested through a private support channel.

8. Tracking, advertising, and sale of data

Health Bridge does not use Apple Health data for advertising or tracking.

• Health Bridge does not sell personal data.
• Health Bridge does not include third-party advertising SDKs.
• Health Bridge does not share HealthKit data with data brokers.
• Health Bridge does not include hidden analytics or telemetry in the app by default.

9. Third-party services

Health Bridge may interact with services chosen by the user, such as a self-hosted receiver, local server, private database, or agent tooling.

Public project pages may be hosted on GitHub Pages. GitHub may process basic web request information when visitors access the website. Website hosting does not provide GitHub with Apple Health data from the app.

If users contact support by email, the email provider may process the message according to its own policies.

10. User controls

Users can control Health Bridge data access and storage in several ways:

• revoke HealthKit permissions in the Apple Health app;
• disconnect the configured receiver in Health Bridge;
• clear pending sync data if the app provides that option;
• delete the app from the device;
• delete data stored on their own receiver or database;
• contact support to request deletion of support communications they previously sent.

Revoking HealthKit permission prevents future reads of the affected HealthKit categories, but it does not automatically delete data that was already synced to a user-controlled receiver. Users should delete receiver-side data directly from their receiver or database.

11. Security

Health Bridge is designed around a local-first, user-controlled data flow. Users should protect their receiver URL, pairing token, device, and local database.

When configuring a receiver, users should prefer secure transport such as HTTPS whenever possible and avoid exposing private receivers publicly without authentication.

No system can guarantee perfect security. Users should avoid sharing pairing links, bearer tokens, setup pages, logs, screenshots, or databases that contain private health information.

12. Children

Health Bridge is not intended for use by children. The app is intended for users who can manage their own Apple Health permissions and receiver configuration.

13. Changes to this policy

This Privacy Policy may be updated as Health Bridge changes. The updated version will be posted on this page with a new “Last updated” date.

14. Contact

For privacy or support questions, contact: