Trust and security
What Lumagen does today to protect clinic and patient data, and what it does not do yet. Everything on this page describes something already in place.
This page states current practice, not plans. Where something is not in place, it is listed under What is not in place rather than described as underway.
Tenant isolation
Every table carrying clinic data is row-level-secured and scoped to a single clinic. There is no application query that can reach across clinics without the service role, and the places that use it are enumerated and reviewed.
Enforced by database policy, not by application code.
Isolation is asserted against a live database rather than reviewed in a diff: every table carries a clinic id, row-level security is on, and no client role holds a privilege that ignores it.
A standing check run after every schema change.
Documents are stored under a path prefixed by the clinic that owns them, with a storage policy that reads that prefix.
Covered by an automated test.
Access and accountability
Multi-factor authentication is enforced on every account with access to patient data.
Required at sign-in; not optional per user.
Every clinical decision and every state change is recorded in an append-only audit log naming the person, the action and the time. The log holds references, never patient details.
Written in the same transaction as the change it records.
Where Lumagen staff act on a clinic's data, the action requires a stated reason and is written to the clinic's own audit log as well as ours.
The clinic sees the same entry we do.
Data handling
Data is encrypted in transit and at rest.
Standard transport encryption and provider-managed encryption at rest.
Patient data is never used to train machine-learning models, on any plan.
A contractual position with our model vendor, not a setting.
A clinic can export everything it has built, at any time, in a machine-readable format. That right survives non-payment, downgrade and termination.
A term of the master services agreement, not a courtesy.
Deletion is real deletion, and produces a receipt stating what was removed. What survives is an audit record that the deletion happened.
Available on request from the clinic's own settings.
Vendors
Every vendor that can access patient data is published, with what it can see and where it runs. The list is incorporated into our business associate agreement by reference, and changes carry notice.
Published at lumagen.ai/subprocessors.
A business associate agreement is available and is executed before any clinic sends patient data.
Signed as part of activating a paid plan.
What is not in place
Stated plainly rather than described as underway, because a security review deserves the gaps as clearly as the controls.
- SOC 2. No audit has started, and no report exists. We will say so until one does.
- Independent penetration testing. None has been performed.
- Continuous security monitoring. Lumagen does not operate a monitoring service, and our agreements say so rather than implying one.
- A published uptime commitment. We do not offer a service level agreement today.
Questions
Security questionnaires and requests for our agreements go to legal@helix-reserve.com.