What should I know about Syncky Health?

Who owns and controls the data I share?

You select the Apple Health data to send to software you run. Your local agent and direct server receive plaintext and control their own stored copies. Removing Relay data does not erase those copies. Protect your receiving machine and review any workflow destinations. Syncky requires no account. See Privacy and agent setup.

Can Syncky or an AI provider read my health values?

Syncky Relay sees delivery metadata such as device ids, IP address, time and size, but sees no health values. Client health-data envelopes are sealed end to end. Relay-generated hub notices are plaintext. A chosen model sees what the agent supplies; encryption in transit does not prevent your selected model from receiving tool output. The local MCP server does not itself call an AI provider. A direct webhook sends straight to your server without Relay.

What can an agent or server write into Health?

Writes apply at the next sync for the types the owner allowed for writing in the app, with iOS Health permission. Only supported writable types can be used. The app's device-wide write allowance starts empty; add writable types in Choose Health data, then choose the agent's write scope or enable the server's Accept writes to Health toggle. HealthKit sync metadata identifies the requesting agent or server and command; Syncky Health is the writing app. Check command results to distinguish a queued write from an applied one. See writing to Apple Health for source metadata, refusal reasons and removal. n8n and custom servers can return commands; the Home Assistant recipe returns an empty reply and cannot write back.

Is there an Apple Health API for my server?

There is no Apple Health web API; HealthKit runs on the device. Use an XML export, Shortcuts or an iPhone app that sends data to your endpoint or agent. See Apple Health API options for the routes and MCP projects compared for their architectures, write support and dated prices.

How do I export Apple Health data or send it to a webhook?

See exporting Apple Health data for Health app XML, Shortcuts and Syncky's JSON/CSV file export. For ongoing delivery to your own server, see Apple Health webhooks for formats, authentication, signing, deduplication and reply writes.

Which assistants can I connect to Apple Health?

See Claude and Apple Health, ChatGPT and Apple Health or Gemini and Apple Health for dated checks of built-in options, supported Syncky clients and links to setup guides.

Does it sync in the background or deliver in real time?

iOS decides when to wake the app, and Health reads require an unlocked iPhone. Samples can be hours old. Writes wait for a sync; webhook commands also wait for a data delivery to reply to. Use Sync now for a manual attempt, and the Reliability screen for recent wakeups. There is no real-time guarantee.

What happens while my agent is offline?

Relay queues sealed client envelopes until acknowledgment or retention expiry, at most 7 days. After expiry a message is deleted. The agent can request history again from the iPhone; that is not a guarantee of recovering every expired sample. The agent keeps what it received in its inbox for 30 days.

Is launch access free, and is the app available yet?

Version 0.1.0 is free during launch, including Relay; plans are coming later. The pricing page is the source of truth. The home page shows App Store availability. No account is needed.

Which installation should I use for MCP or a direct server?

After pairing, the canonical local MCP command is npx -y @syncky/agent mcp, requiring Node.js 22.15 or newer and npm. A compatible client can import the release's checksum-verified syncky-health.mcpb instead; it also needs Node.js. See the Claude Code, OpenClaw, Claude Desktop, VS Code Copilot in agent mode and Windsurf Cascade guides for configuration files, startup checks and permission limits, or the four approaches compared. Home Assistant, n8n, Node-RED and InfluxDB 2 and Grafana use direct webhooks without MCP or agent pairing; the server contract keeps the canonical Node-RED and InfluxDB recipes.

Can I use ChatGPT desktop, web or mobile?

ChatGPT desktop works locally on Mac and Windows through the stdio MCP server. Follow the shared ChatGPT desktop and Codex CLI/IDE read-only setup, which disables syncky_send and syncky_ack in the client before use. ChatGPT web and mobile cannot reach a local agent.

Detailed steps are in the ChatGPT desktop and Codex CLI/IDE guides. Cursor has its own install link/manual JSON and approval rules; that registration does not disable syncky_send or syncky_ack.

Is the whole service open source or self-hosted?

The protocol, reference agents, example servers and test vectors are Apache-2.0. The iPhone app and hosted Syncky Relay are separate. You run your agent or direct server; the relay route also uses Syncky's hosted service. Syncky Health transfers data and gives no medical advice.

Can my agent ask for additional Health permissions?

Yes, after explicit approval the agent sends an access request with syncky_send. Every write to Apple Health, every diagnostics request and every request for more Health types is a message the agent sends to the iPhone. Writes apply only to the types the owner allowed for writing in the app; a diagnostics report or more Health types need the owner's tap on the phone. Review and confirm individual read/write choices on the phone; the reply arrives in the agent's inbox and the next ordinary sync delivers scope. A queued request grants nothing, Health read authorization is unobservable, and approval to request access is separate from permission to write Health values. Read-only setups disable syncky_send and syncky_ack. See access request guidance.