Apple Health data privacy with AI agents: local-first vs cloud

ChatGPT Health launched in July 2026. Ask it about your resting heart rate, and your HRV, sleep stages, and workout history leave your phone for OpenAI servers you do not control. The answer comes back in a chat, so most people assume the data stayed local. It did not.

AI Health Export (Gemini) works the same way. Your metrics transit a server you cannot audit, get processed by a model you cannot inspect, and the result gets stored by a company you do not own.

The local-first path is the opposite. An MCP agent reads Apple Health on your own hardware and sends nothing over the network. No upload, no remote model, no stored copy. The data your AI agent reasons over never leaves your machine.

What this means in practice:

• Your resting heart rate, HRV, sleep stages and workouts stay on device.
• The agent queries Apple Health read-only through a local MCP server.
• Zero network calls during a query. Nothing transmits.
• You can read 190 metrics this way without handing them to a cloud model.

Privacy here is not a toggle in a settings screen. It is a property of the architecture. If the tool cannot transmit, your data cannot leak. That is a stronger guarantee than any privacy policy.

Install:

npx -y health-export-mcp

Canonical: https://www.healthexport.dev/blog/apple-health-data-privacy-with-ai-agents?utm_source=devto&utm_medium=social&utm_campaign=exp-20260818-hea44-privacy