Security & compliance

A short summary of how ELH Health handles customer and member data. We share extended materials (DPA, architecture diagram, SBOM) under a mutual NDA on request.

Data classification

ClassExamplesStorage
PHIHealth profile, biometrics, mealsEncrypted at rest, RLS-locked, audit-chained reads
PIIName, email, employee IDEncrypted at rest, RLS-locked
OperationalIPs, user agentsHashed before storage; raw IP never persisted

Authentication

Authorization

Audit chain

Every read of member PHI inserts a row into audit_log with a SHA-256 digest of the previous row + the current canonical event. Tampering with any historic row breaks verification at that point. Logs are retained for 7 years (HIPAA) and exportable on request.

Network

Subprocessors

The complete sub-processor list — provider names, purpose, region, and BAA coverage — is shared with every customer under the Data Processing Addendum (DPA) at contract signing. Customers are notified 30 days before any new sub-processor is added.

Reporting

Quarterly security reviews are included in every Enterprise contract. We will (a) walk through the audit chain for your tenant, (b) review access patterns and flag anomalies, (c) hand you a written summary for your security committee.

Vulnerability reports

Coordinated disclosure to security@elhhealth.app. We respond within one business day and credit reporters in our public security log.