ChatGPT Health launched 23 July 2026. It connects Apple Health and medical records from Epic, Oracle, One Medical so ChatGPT can answer questions about your health data. AppleInsider, TechCrunch, and The Verge all covered the privacy implication: your heart rate, sleep stages, blood oxygen, and medical records now live on OpenAI's servers.
This is not unusual for a cloud AI product. The question is whether you want your resting heart rate and sleep architecture on a third party's servers.
How ChatGPT Health works (and where your data goes)
ChatGPT Health is a cloud service. Your Apple Health data and your question go to OpenAI. GPT processes them and returns an answer. Your HRV, sleep, and medical records now sit on OpenAI's infrastructure.
How on-device health AI works (and what stays on your iPhone)
On-device health AI apps process everything on your iPhone. No account, no sign-in. The open-source MCP server makes zero runtime network calls. For Health Export AI, the Meta advertising SDK cannot access HealthKit data: enforced in code with a CI test that fails the build.
Same question, two architectures
Consider: "How did my HRV trend this week compared to last week?"
ChatGPT Health: your question and Apple Health data go to OpenAI's servers. GPT processes the comparison. Your HRV data now lives on OpenAI's infrastructure.
On-device + MCP: the model runs on your phone. Same answer. Nothing leaves.
The trade-off that disappeared
On-device health AI apps are private by design, but most are walled gardens. You ask questions in the app, you get answers there. Your data never leaves, but you also cannot feed it to the AI agents you already use.
If you use an on-device health AI that also ships an MCP bridge, you get both: the privacy of on-device processing and the ability to query your health data from Claude, Cursor, ChatGPT Desktop, or any MCP-aware agent.
The trade-off used to be privacy or portability. An on-device app with an MCP bridge gives you both.
Install:
npx -y health-export-mcp
Originally published on healthexport.dev.
Top comments (0)