Security and data handling

Updated September 25, 2026

Status: Practice demos are open. CHAI runs daily on its founder’s record, and we’re preparing our first practice deployments.

Our approach: CHAI uses a dedicated server for each practice, private-network access, encryption and a record of changes. Patient data is never sold or used to train AI models. The sections below distinguish current controls from work planned before practice launch.

Where CHAI runs

Its own server per practice. We deploy each practice on its own server with its own database. Practices don't share one.
A private network. CHAI is reached over an encrypted private network (Tailscale), not the open internet. Clinicians and patients join that network on their devices during setup.
Encrypted. Traffic is encrypted in transit (HTTPS), and the server's disks are encrypted at rest.

Who can see what

Each clinician and patient has their own login. Passwords are stored as salted hashes, and sessions use a secure, HTTP-only cookie.
Every change to a patient's record is written to an append-only log: what changed, and when.
Proactive messages go only to the patient, inside CHAI.

Services that process patient data

Anthropic (Claude) writes CHAI's explanations and answers from the record it is given. Patient data is not used to train a model.
Patient messaging runs inside CHAI on the practice's CHAI environment; no messaging vendor handles it.
Apple Health, on the patient's own iPhone, is where wearable data comes from. The patient chooses what to share.
Email carries account invitations, the practice's weekly report, and a generic alert when a message is waiting ("You have a new message in CHAI. Sign in to read it."), with no names or excerpts.

How CHAI makes answers reviewable

Rules and calculations come first. The requisition, dose changes, statistics and verdicts are computed from the record. The model is handed those figures and told to quote them, not recompute them.
Every answer shows the draws and values it used, so a clinician can check it.
Hard safety rules for critical values, such as systolic blood pressure of 180 or higher, override everything else CHAI says. CHAI isn't an emergency service: urgent findings follow your practice's own process.

Approvals

CHAI proposes dose and protocol changes, with the calculation behind each one. Only a clinician or practice-admin account can accept one; nothing is applied until they do, and the acceptance is recorded with who accepted it and when. Patient accounts cannot accept dose or protocol changes. Checkpoint rules flag a result; they don't change a dose on their own. A signed clinician review record, with dual-review badges and document upload, is in development.

HIPAA

CHAI is built to the HIPAA Security Rule. We don't call it "HIPAA compliant" until the pieces below are in place for your practice.

In progress before launch

Business associate agreements with each vendor that handles patient data.
A documented risk assessment, and an independent security review.
The signed clinician review record.
A wider review of access controls for each role in a practice.

Questions

Security and procurement questions go to sales@centurionhealth.ai. We can walk through current controls, deployment plans and outstanding requirements for your practice. For how this website handles your information, see the privacy policy.