Keel processes Protected Health Information on behalf of brokers, employers, and health plans. We hold ourselves to the posture every benadmin and carrier requires before integrating — and we publish the details here.
A snapshot of the frameworks Keel is audited against, plus the ones we’re actively pursuing. Reports and letters are available under NDA — ask security.
The day-to-day posture behind the certifications — what’s on, what’s logged, what’s encrypted, what’s reviewed.
The third parties Keel uses to operate the platform. Each is governed by a BAA where PHI is involved and a DPA where applicable. See the privacy policy for the canonical list.
| Subprocessor | Purpose | Data category |
|---|---|---|
| Anthropic | Amanda’s language model (Claude) | PHI under BAA, with PHI redaction at boundary |
| Cloud infrastructure (primary) | Compute, storage, networking | All platform data under BAA |
| Database & managed services | Tenant database, queues, object storage | All platform data under BAA |
| Authentication | Identity, SSO, MFA | Identity metadata, no PHI |
| Observability | Error tracking, performance monitoring | Scrubbed telemetry, no PHI in payloads |
| Email & messaging | Transactional email, SMS, voice | Member contact data under BAA |