The third parties that touch the service, and on what terms.

Data in scope. Hosts application compute (Azure Container Apps), application data (Azure PostgreSQL Flexible Server), binary clinical media (Azure Blob Storage), secrets (Azure Key Vault), and service-to-service messaging. This is where clinical data — including PHI — is processed and stored.

Terms. Contracted under Microsoft’s HIPAA Business Associate Agreement. Data is encrypted at rest (AES-256) and in transit (TLS 1.3); network isolation via private endpoints and VNet. Region selection is set per institutional deployment.

Data in scope. Captures first-party performance signals (page-load timing, request errors, JS exceptions) and explicit instrumentation events designed so no PHI flows into the telemetry. No behavioral analytics or session-replay tooling runs on the clinical surfaces.

Terms. A Microsoft service, covered under the same Microsoft HIPAA Business Associate Agreement as the rest of the Azure substrate.

Data in scope. Processes clinical queries routed to the frontier reasoning slots. The specific provider(s) are abstracted here; the identities and full contract terms are available to institutional customers under NDA. Where a customer or jurisdiction prohibits a specific provider, that frontier slot can be swapped out without rebuilding the agent.

Terms. Accessed under enterprise contract with data-processing terms appropriate to regulated workloads. No frontier vendor trains on, or retains, customer data or Protected Health Information.

Data in scope. Runs on the www.chirongrid.ai marketing site exclusively. It is not installed on the clinical surfaces (cds.chirongrid.ai, om.chirongrid.ai), which render PHI. The marketing site does not collect, process, or store PHI.

Terms. Consent-gated behind a CCPA / GDPR banner: Clarity does not load until the visitor affirmatively grants analytics consent, and declining keeps the site fully functional with no behavioral signal collected.