Direct
The iPhone sends permitted data over the route you configured to the receiver. Direct is the default.
Where your records go.
Your iPhone sends permitted Apple Health records to storage you control. Your assistant reads that copy through local tools. If it uses a cloud model, the provider may receive the query results your client sends.
Two different documents: This page explains the product architecture in plain language. The Privacy Policy remains the legal statement about data handling.
Data flow
- Apple Health permissionThe companion requests read access through Apple's authorization sheet. The user chooses which supported categories to allow.
- iPhone companionThe app reads permitted observations and can retain limited connection, sync, and pending-delivery state on the device.
- User-configured routePermitted data crosses the network route that the user prepared for the physical iPhone to reach the receiver.
- Receiver and AI clientThe receiver stores the delivered copy and provides read-only MCP and CLI queries on that machine. The client may send query results to its chosen model provider.
Choose how data reaches the receiver
Encrypted iCloud Mailbox (Beta)
On Mac, you can choose to move encrypted sync files through your own iCloud account. Your Mac decrypts them after delivery. Apple Health AI Bridge never switches methods automatically, and the developer cannot access either destination.
Trust boundaries
Apple and the device
HealthKit and iOS enforce authorization and background-execution behavior. Apple Health AI Bridge cannot bypass denied categories or promise a specific delivery schedule.
The network route
The receiver URL is supplied by the user, not by Apple Health AI Bridge. The operator is responsible for reachability, transport security, authentication, and exposure.
The receiver and storage
The receiver process and database run on infrastructure the user chooses. Apple Health AI Bridge does not operate a central health-data store for this path.
The AI client
Adding a client lets another local process query the stored records. If it uses a cloud model, the provider may receive the query results it sends, under that client's settings and the provider's policies. A local MCP connection does not by itself keep the conversation local.
What read-only means
- The iPhone companion requests HealthKit read access; it does not add, edit, or delete Apple Health records.
- The MCP server and direct CLI expose bounded query operations rather than write tools or raw SQL.
- An AI client's own behavior is outside the bridge boundary. Review the client and model configuration before sharing context with it.
Read-only does not mean risk-free. Any process that can read private data must be chosen, configured, and protected deliberately.
Receiver and storage ownership
Pairing tells the companion where to send permitted data. The destination, receiver process, credentials, database, backups, and retention practices belong to the user's environment. A local computer, private network route, or user-managed host can still be misconfigured or compromised.
The operational install guide requires the receiver to be supervised and checked from both the receiver host and physical iPhone before pairing. It also warns against exposing the receiver port or pairing page publicly.
Revocation and deletion
- Stop future HealthKit reads: change or revoke the app's permissions in Apple Health or iOS Settings.
- Stop future delivery: disconnect the receiver or remove the app, following the controls described in support.
- Remove pending device data: use the available clear-pending-data control, then remove the app if the entire local container should be deleted.
- Delete the receiver copy: purge or delete data on the receiver and any backups you operate. Revoking HealthKit access does not remove data already delivered.
Non-medical scope
Apple Health AI Bridge is a data plane. It does not diagnose, treat, coach, provide emergency guidance, or turn an AI agent into a medical service. Its interfaces return source-grounded data and provenance for the user-chosen client to handle.
Sources and related pages
- Apple Developer: HealthKit authorization
- Model Context Protocol specification and consent principles
- Apple Health AI Bridge source and architecture documentation
- Privacy Policy, support and deletion pointers, and Terms of Service
Review the operational path only after the trust boundaries match the environment you intend to run.