Terms of use · summary

Terms of use, pilled honestly.

This page is a usage summary, not the binding legal Terms of Service — the full ToS for the production product will be published prior to general availability. Two blocks below: Today covers what you can and can't do with the public prototype and source code; Designed previews the shape of the production ToS so a procurement reviewer can plan their review.

⚕️ Not for clinical use. The prototype is a demonstration only. Nothing here is medical advice. Do not enter real PHI. If you have menopause-related symptoms, please consult an MSCP-credentialed practitioner directly.

Today — prototype usage terms

In force on this site

What you can and can't do with the public prototype and the open-source codebase right now. These apply to every visitor of the public site.

Shipped

Not for clinical use

The prototype is a demonstration of architecture and workflow only. Nothing you read, submit, or generate here is medical advice, a clinical decision, or a substitute for evaluation by a qualified clinician. If you are experiencing menopause-related symptoms, please consult an MSCP-credentialed practitioner via the directory at the menopause society — directly, not through this prototype.

Shipped

No PHI

Do NOT enter real protected health information into any surface on this site, including the embedded Agentforce chat. The demo personas are synthetic; the prototype is not under BAA. See /hipaa and /privacy for the full posture.

Shipped

Acceptable use

You may browse, share, and reference the public site, the demo flow, and the open-source code. You may not (a) attempt to extract PHI (there is none to extract; this is a safeguard), (b) attempt to deceive the embedded Agentforce agent into clinical advice that would harm a real person, or (c) impersonate Pause-Health.ai or its founder in materials derived from the brand assets.

Shipped

No SLA, no warranty

The prototype is provided as-is, with no uptime SLA and no warranty (express or implied) of fitness, merchantability, or accuracy. Vercel + Salesforce dependency outages may take parts of the demo offline; we'll fix them when we notice.

Shipped

Source code · Apache License 2.0

The codebase is published at github.com/hucmaggie/pause-health.ai under the Apache License, Version 2.0. You may use, modify, and redistribute the code for any purpose — including commercial — provided you preserve the copyright notice and the NOTICE file. The Apache 2.0 license also includes an explicit patent grant from contributors, which matters for downstream healthcare-AI use. Third-party software referenced by the project (JupyterHealth, DBDP, FLIRT, Salesforce platform components, Anthropic API) is governed by its own license terms — see the NOTICE file in the repo root for the full attribution list.

Shipped

Trademark + brand

The Pause-Health.ai wordmark and icon are trademarks of Pause-Health.ai and are NOT licensed under Apache 2.0 (the source-code license, above). Per Apache 2.0 Section 6, the license grants no permission to use Pause-Health.ai's trade names or marks except as required for describing the origin of the Work. The press kit at /press provides assets for editorial use; please don't recompose the wordmark or imply endorsement / partnership without prior written agreement.

Shipped

Changes to these terms

We may update this page as the prototype evolves. Material changes will be called out in commit history (the page source is in github.com/hucmaggie/pause-health.ai under frontend/app/terms/page.tsx) and in the changelog when the full ToS publishes.

Designed — production Terms of Service

Pre-GA · not yet binding

The shape of the production ToS once Pause-Health.ai is generally available to design-partner provider organizations. This is a preview, not a legal contract — the binding ToS will be published before any production deployment goes live. See also /hipaa · /security · /privacy.

Planned

Production Master Services Agreement

Standard SaaS MSA executed with each provider organization, separate from the HIPAA BAA. Covers service description, fees, mutual confidentiality, IP ownership of customer data, and service-credit SLAs.

Planned

BAA (HIPAA Business Associate Agreement)

Executed with every Covered Entity before any PHI access. See /hipaa for the BA posture and standard terms.

Planned

SLA + service credits

Production uptime SLA scoped to the integration surface (typically 99.9% for the customer-facing Care Router API). Service credits for missed SLA per the MSA schedule.

Designed

Data processing addendum

For customers requiring CCPA / CPRA / GDPR-equivalent data-processing terms in addition to the BAA.

Designed

Indemnity + liability

Mutual indemnity for IP claims, limited liability per industry norms; carve-outs for confidentiality breach, gross negligence, and HIPAA breach attributable to either party.

Designed

Acceptable-use policy (production)

Covers the production product: customer responsibility for clinical decisions made with Pause-Health.ai outputs, prohibitions on using the platform outside the menopause-care scope contracted for, audit-log access for the customer's Compliance team.

Planned

Termination + data return

Customer can terminate for material breach or convenience per MSA. Upon termination, customer data is returned (or destroyed at customer's instruction) per the BAA schedule.

Legal contact

For early-access program agreements, NDAs, licensing inquiries about the source code, or any other legal questions, email legal@pause-health.ai. Procurement reviews from prospective design partners are welcome — flag the inquiry as such and we'll route to a faster path.

Back to HomePrivacyHIPAA notice