Home › Legal › Security & Trust
Legal — Draft
Security & Trust
A trust summary for clinic reviewers: the safeguards that exist today, and the gates that must pass before real patient data — stated without badges or claims.
This page summarizes, for clinic reviewers, the safeguards built into Carezeve and the gates that remain before real patient data. It is the trust companion to the product’s Security & Privacy page.
Safeguards implemented in the current build
- Clinic isolation — each clinic’s records are separated at the database level; staff of one clinic cannot open another clinic’s patients, and platform administrators have no path to patient records.
- Invitation-only, role-based access — staff join by invitation; roles separate clinical, billing, and administrative access, and final care-plan approval is reserved for authorized clinical roles.
- Tamper-evident audit log — significant actions are written to a hash-chained log whose integrity can be verified on screen.
- Encryption — data is encrypted in transit and at rest through the hosting platform the product runs on.
- Session and password discipline — idle sessions sign out automatically; new accounts must meet stronger password rules.
- Controlled export and backups — a clinic’s data can be exported by its authorized administrators only, exports are audit-logged, and backups are restore-tested.
Development discipline
Development and testing use synthetic (fictional) data only. No real patient information exists in the development environment, and draft assistance features run locally on recorded data inside the product — no patient information is sent to an external AI service in the current build.
What is not claimed
Carezeve does not claim HIPAA compliance or any security certification today. No badge, audit result, or certification is asserted on this page or anywhere on this site, because the pre-launch gates below have not yet been completed.
Gates before real patient data
- A signed Business Associate Agreement chain covering Carezeve and every provider that stores or processes patient data — see BAA Information.
- HIPAA-eligible production hosting, configured for healthcare workloads.
- An independent security and HIPAA review by reviewers outside the development team, with findings addressed.
- A staged rehearsal and a small, controlled first-clinic pilot before wider availability.
Subprocessors and questions
Service-provider categories are described in Subprocessor Information. Security questions, and reports of suspected vulnerabilities, can be sent through [CONFIGURATION: Security incident notification route — to be completed once contact channels are operational]. Details on this page describe the current build and may change as the production architecture is finalized before launch.
Legal Drafts
All legal documents
Every document below is a draft for legal review — none of them is in effect yet.