SECURITY & PRIVACY

The model never sees a patient's name.

Names, dates of birth, and record numbers are removed before anything is analyzed. What the model reads is clinical text with the identifying details already taken out. It cannot leak a name because it was never given one.

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

DE-IDENTIFICATION
Before any model call, not after.
Access

Signed before any patient data moves

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

Signed before any patient data moves

 

SOC 2

Not yet — see below

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

Last updated 31 July 2026 · 

What happens to your data

Four steps, in this order

The order matters. Identifiers come out first, not last.

THE COMMON APPROACH
Identified text reaches the model. Identifiers are removed from the output afterward. The model has seen the patient.
PREDISIGHT
Identifiers are removed before the model is called. The model has never seen the patient.
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 WE DO NOT HAVE YET

The gaps, named

No SOC 2

We have not been through a SOC 2 audit. The controls are built the way an audit would expect, but that is our word, not an auditor’s.

 

No third-party penetration test

[CONFIRM: keep or cut] Not yet commissioned. When one is, the report will be available under NDA.

 
No customers yet

You would be among the first facilities to send us a chart. There is no reference customer to call.

 

What happens to your data

Four steps, in this order

The order matters. Identifiers come out first, not last.

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

Identifiers are separated before analysis

Names, dates of birth, and record numbers are removed from the clinical text and held in a separate encrypted store. The text that continues carries a pseudonym, not a person.

03

The model reads. It does not decide

A language model reads the de-identified text and reports what the note says. It does not score, decide, or select codes — fixed rules do that, the same way every time.

04

The finding is re-linked to the resident, inside your tenant

Your staff see a name because the re-link happens on your side of the boundary. The model never did. Every finding also names the manual and section it came from.

During a design-partner review, before any BAA is in place, we ask for a de-identified record instead — nothing identifying leaves your building at all.

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. AWS is our only subprocessor.
It has none to reveal. Identifiers are removed before any model call, and the identity mapping is held in a store the model has no path to.
Your data is deleted on the schedule specified in the BAA. We do not retain a copy.
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.