How claims data is protected.
The controls in place, stated specifically enough for a hospital security review to check each one.
Controls
Tenant isolation
Every tenant-scoped resource is enforced server-side and covered by automated tests, including the partner hierarchy, which grants portfolio totals and nothing at row level.
Multi-factor authentication
TOTP with single-use codes and hashed recovery codes. An organization can require it of everyone.
Encryption
TLS in transit. Stored claim payloads, contracts, attachments and sent packages are encrypted at rest with AES-256-GCM.
Role-based access
Explicit permission sets per role, with every permission stating in plain language what it allows.
Audit trail
Authentication, privileged actions, data export and every financial decision are recorded with the actor and the reason.
Identity minimization
The platform holds a deliberately minimal patient reference, and discloses only a last name and first initial outside it.
AI governance
Every AI touchpoint is logged with the model, prompt version and the records it could see. No model determines a dollar amount.
Secrets handling
Credentials are referenced by environment variable name, never stored in the database. The credential field accepts only a value shaped like a variable name — upper-case letters, digits and underscores — and refuses anything else.
Login protection
Per-account and per-address failure budgets enforced before any password work, so the endpoint cannot be used as a CPU lever.
Responsible disclosure
If you have found a vulnerability, tell us and we will work with you. We will not pursue legal action against good-faith research that avoids privacy violations, service degradation and data destruction.
What to expect
Acknowledgment within three business days, an assessment of severity, and updates until it is closed.