> For the complete documentation index, see [llms.txt](https://saviorofhealth.gitbook.io/saviorofhealth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saviorofhealth.gitbook.io/saviorofhealth-docs/readme.md).

# Savior of Health

**Consented health-data infrastructure: a Data API and Partner Portal fed by a live consumer health app.**

{% hint style="info" %}
This site reproduces Whitepaper v0.3 (first issued September 2026; figures as of 19 October 2026) together with the product and API reference. Sections marked **\[TBD]**, **\[Design]** or **\[Counsel]** are still being finalised. Read the [Important Notice](/saviorofhealth-docs/legal/notice.md) first. Nothing here is an offer, advice, or a commitment.
{% endhint %}

Savior of Health is consented health-data infrastructure: organisations (clinics, researchers and brands) commission surveys and receive threshold-suppressed statistical outputs through a Partner Portal and a metered Data API. The supply side is a live consumer health application at [saviorofhealth.app](https://saviorofhealth.app), where members keep a daily health journal, talk to four AI health agents that read the member's own record before answering, and answer short health surveys.

Members earn [**Heal Points (HP)**](/saviorofhealth-docs/heal-points/heal-points.md) for activity. HP have no monetary value, cannot be redeemed, withdrawn, cashed out, or transferred, and confer no right to any other asset.

## How this site is organised

| Part                                                                                                                                                                      | What it covers                                                               | Source                                            |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------- |
| [Overview](/saviorofhealth-docs/overview/summary.md)                                                                                                                      | Summary, the problem                                                         | Whitepaper §1–2                                   |
| [Partners & Data API](/saviorofhealth-docs/partners-and-data-api/partners.md)                                                                                             | Partner Portal, business model, API reference (12 endpoints)                 | Whitepaper §3 + product reference + `/developers` |
| [Data & Privacy](/saviorofhealth-docs/data-and-privacy/data-privacy.md)                                                                                                   | What is stored, where it is processed, clinical boundary                     | Whitepaper §4                                     |
| [Product](/saviorofhealth-docs/product/product.md)                                                                                                                        | Journal, AI agents, earn deck, missions, goal commitment, referrals, sign-in | Whitepaper §5 + product reference                 |
| [Platform Integrity](/saviorofhealth-docs/platform-integrity/integrity.md)                                                                                                | Automated-account classification and controls                                | Whitepaper §6                                     |
| [Heal Points](/saviorofhealth-docs/heal-points/heal-points.md)                                                                                                            | What HP are and are not                                                      | Whitepaper §7                                     |
| [Legal](/saviorofhealth-docs/legal/notice.md)                                                                                                                             | Notice, amendment, team, investors, risk factors                             | Whitepaper §8–10                                  |
| [Roadmap](/saviorofhealth-docs/reference/roadmap.md) · [Glossary](/saviorofhealth-docs/reference/glossary.md) · [Appendices](/saviorofhealth-docs/reference/key-facts.md) | Milestones, terms, evidence, open items, prior statements                    | Whitepaper §11, App. A, C, D                      |

## Figures

All figures are dated snapshots of a live production system and change continuously. Quote any figure with its date. The reference snapshot for this draft is **19 October 2026, 09:01 UTC** unless a page states otherwise.

## Materials

Shareable collateral hosted on the Platform: [product one-pager (PDF)](https://saviorofhealth.app/materials/health-saviors-onepager-en.pdf) · [demo walkthrough (PDF)](https://saviorofhealth.app/materials/health-saviors-demo-en.pdf) · [product demo video](https://saviorofhealth.app/materials/health-saviors-demo.mp4).

Contact: <official@saviorofhealth.app>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://saviorofhealth.gitbook.io/saviorofhealth-docs/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.