Planned, Not Released

Health Data / HealthKit Notice

Apple Health integration is a planned, optional feature for Ghostlight Premium, not something that exists in any shipped product today. This page describes exactly how it's designed to work, and what it will never be allowed to do, if and when it ships.

Status

Nothing to turn on, today

There is no Apple Health or HealthKit integration in any Ghostlight product right now. No current Ghostlight source kit contains HealthKit code, no iOS Companion App has been released, and no deployment — Basic, Plus+, or a commissioned Premium build — has a health-permission prompt for you to see or grant. Everything below describes design intent for a planned capability, not a shipped feature and not a committed release date. If and when Apple Health integration ships, it is intended to work exactly as described here. Until then, there is nothing to connect.

What Ghostlight deploys as today

Ghostlight ships today as a self-hosted Discord or Telegram companion (Ghostlight Basic and Plus+) or as a commissioned Premium build, deployed on your own Railway account or your own infrastructure. None of that requires, reads, or depends on Apple Health data in any way. This notice exists to describe a possible future addition, not a current dependency of anything you can buy right now.

Why we're publishing design intent before the feature exists

We're writing this notice before Apple Health integration exists, not after, so that if it ships, the rules were public from day one rather than written retroactively to match whatever got built. Treat this page as a commitment about how the feature must behave if it is ever released — not as an announcement that it has been.

The Design Intent

How it's planned to work, if it ships

Optional, with no exceptions

If Apple Health integration ships, connecting it is planned to be entirely optional, never required to use Ghostlight. The design intent is for Ghostlight to keep working fully, with nothing gated or degraded, for anyone who doesn't connect it.

Chosen one data type at a time

The design intent is per-metric permission: if this ships, you would choose exactly which Apple Health data types, if any, to share, the same category-by-category way iOS already asks for Health access, app by app. There's no planned all-or-nothing switch — sharing one metric wouldn't imply sharing any other.

Revocable at any time

If it ships, access is planned to be revocable at any time, the normal way iOS handles Health permissions — from iOS Settings, effective immediately, with no separate process on our end required to honor it.

Read access only

Nothing in the current design plan involves Ghostlight writing data back into Apple Health. The plan, if this ships, is read-only. A future write capability would be its own separate, explicitly announced feature, not something folded quietly into this notice.

Self-Hosted, By Design

Scoped to your deployment, not a Sirenwave server

Stays inside your own infrastructure

Ghostlight is self-hosted by design — see Security & Responsible Disclosure for the full model. If Apple Health integration ships, any signal you chose to share is planned to flow to your own self-hosted Ghostlight deployment — your own Railway account or your own infrastructure — the same place your conversation history and memory already live by default. It is not planned to be uploaded to any Sirenwave-run server.

No standing Sirenwave access

Sirenwave Studios does not operate, host, or have standing access to your running companion, its memory, or your API keys today. Health data is designed to follow the identical rule if it ships: it isn't planned to pass through anything Sirenwave operates in the first place. See the Self-Hosted Deployment Notice for exactly where our responsibility ends and yours begins.

Read This Part Carefully

What health signal is not, and will not be allowed to do

  • Not a diagnosis. If Apple Health integration ships, any health signal Ghostlight can see is not planned to function as a diagnosis of any physical or mental health condition, and never will.
  • Not a claim about your inner state. It's not designed to be treated as a claim of psychological truth about you. A companion that can see a health metric would not thereby know what's actually going on with you.
  • Not an automatic trigger. Ghostlight already includes proactive systems today, like the Pulse scheduler in Plus+ and Premium builds, running completely independent of Apple Health. Health signal is not planned to unilaterally plug into proactive companion behavior on its own. If health data is ever wired into a proactive trigger at all, that would need its own separate, explicit configuration and consent from you — never a default, and never silently bundled into an existing feature.
  • Not a medical device. Ghostlight is not, and does not claim to be, a medical device. That's true today, and it will still be true if Apple Health integration ships.
  • Not a substitute for care. Everything a companion says is LLM-generated conversational text — true today, and it will still be true with Apple Health connected. It is never a substitute for professional medical, psychiatric, or emergency care.

If you're in crisis or need medical attention, please contact a qualified professional or emergency services directly — that's true regardless of anything a companion says, and it will stay true no matter what Ghostlight can eventually see.

Delivery

Why this waits on the iOS Companion App

HealthKit only exists on iOS

Apple only exposes Health data to apps running on iOS or iPadOS with the right entitlements, not to a Discord bot, a Telegram bot, or a server backend on its own. That's part of why Apple Health integration is tied to a planned iOS Companion App, which is itself still in development and has not been released. Anywhere this site refers to "the iOS Companion App," it means a planned product you cannot currently download, not a released one.

Which metrics, exactly

Precisely which Apple Health data types would be available to share isn't decided yet — it depends on what Apple Health and your connected devices actually expose through HealthKit at the time this ships. Specific supported metrics will be documented here when this ships, rather than promised in advance.

Related