SECURITY & PRIVACY

Patient data moves only under a signed BAA.

Your records are encrypted in transit and at rest, processed in an isolated tenant for your facility, and handled only by subprocessors bound by a BAA. A language model reads the documentation and reports what it says. Fixed rules make every decision.

We would rather describe this precisely than generously. Everything below is what is true today, including the parts we do not have yet.

AI MODEL

Reads the record. Fixed rules decide.

Access

Requested, time-limited, and logged

 
SUBPROCESSORS

AWS and Anthropic.

HOSTING
HIPAA-eligible AWS, encrypted at rest and in transit.
BUSINESS ASSOCIATE AGREEMENT

Signed before any patient data moves

 

SOC 2

Not yet

DATA USE
Never sold, never used to train external models.
AUDIT TRAIL
Every finding traceable to a rule and a citation.

Last updated 29 October 2026 

DATA USE

What your data is never used for.

Never sold.

To anyone, for any purpose, ever.

Never used to train external models.

Your clinical documentation does not improve a vendor’s model. It generates findings for your facility and nothing else.

Never pooled across facilities.

Your data is not combined with another operator’s to build benchmarks, datasets, or products.

Never retained beyond your agreement.

On termination, your data is deleted on the schedule your BAA specifies.

What happens to your data

Four steps, in this order

From upload to finding, in order.

01

Your data arrives under a BAA

Encrypted in transit, into an isolated tenant that belongs to your facility alone. Protected health information is expected here. That is what the BAA is for.

02

The model reads the record

A language model, run by Anthropic under a BAA, reads the clinical documentation and reports what each note says.

03

Fixed rules decide

The model does not score, decide, or select codes. Fixed rules make those decisions from what the model reports.

04

Findings stay inside your tenant

Your staff review findings inside your facility’s tenant. Every finding names the manual and section it came from.

FOR YOUR COMPLIANCE OFFICER

The questions you may have

Will you sign a BAA?
Yes, before onboarding. It is a precondition, not a negotiation.
Not yet. We are early and we will not claim otherwise. We can walk your team through our controls in detail, and we will pursue formal audit as we grow.

HIPAA-eligible AWS services in a single US region. Our subprocessors are AWS (hosting) and Anthropic (AI model), each under a BAA.

No. The model sees only the record being reviewed for your facility and has no access to other facilities’ data. Anthropic, which runs the model under a BAA, holds the record in a short-term cache while it is being read; that cache expires five minutes after last use. Anthropic also retains API inputs and outputs for up to 30 days under its standard retention. We do not have a zero-data-retention arrangement, and we won’t tell you nothing is retained.

Your data is deleted from our systems on the schedule specified in the BAA. Our model provider, Anthropic, may retain API inputs and outputs for up to 30 days under its standard retention, as described above.

No one by default. Support access is requested, time-limited, and logged.
NEXT STEP

Send this page to your compliance officer.

If it does not answer their questions, we will get on a call and go through the architecture in detail.