Cura
  • Workflow
  • Safety
  • About
Sign inGet startedGet started

Terms of service and platform governance

These terms govern your use of the Cura longitudinal health memory platform, setting out patient identity governance, proxy contributor boundaries, clinical liability, and data protection safeguards.

Emergency medical disclaimer: not for acute crises

Cura is strictly an asynchronous, between-visit health memory and tracking platform. Cura is NOT an emergency response system, real-time monitoring service, or diagnostic device. If you are experiencing a medical emergency, acute chest pain, severe shortness of breath, sudden weakness, or any life-threatening condition, immediately call 911 (US), 999 (UK), 112 (EU), or your local emergency services.

Article 1. Platform purpose & between-visit scope

Cura is designed to capture, organize, and synthesize asynchronous between-visit health observations reported by patients and authorized carers. The platform provides structured longitudinal timelines and pre-visit synthesis briefs to facilitate informed consultations between patients and their licensed healthcare professionals.

Cura does not provide live medical consultations, triage dispatch, or emergency medical monitoring. All information processed by Cura is intended exclusively for retrospective clinical review during scheduled healthcare encounters.

Article 2. Clinician-in-the-loop governance & medical responsibility

Cura does not practice medicine, formulate diagnoses, prescribe medications, or replace the clinical judgment of qualified practitioners. All clinical decisions, treatment plans, prescriptions, and symptom interpretations remain the sole professional responsibility of the treating clinician.

  • Zero autonomous prescribing: The software cannot alter, adjust, or initiate medication dosages autonomously.
  • Human-verified summaries: Pre-visit briefs and deterioration alerts serve as memory aids and require clinician verification prior to clinical action.
  • Medical duty of care: Clinical liability and care plan oversight remain strictly between the attending physician and the patient.

Article 3. User roles & access architecture

Cura enforces a strict tripartite role hierarchy with bounded cryptographic scopes:

  • Patients (Data Subjects): The primary account holders and subjects of care. Patients verify transcripts, view complete health timelines, and hold exclusive authority to grant or revoke carer proxy access.
  • Carer Proxies: Delegated observational contributors authorized by patient consent or clinical assignment. Carers submit symptom logs on the patient’s behalf with mandatory author provenance.
  • Licensed Clinicians: Attending physicians, GPs, and care team members bound by professional licensing and ethics. Clinicians establish clinical tenancy and maintain medical duty of care.

Article 4. Patient profile creation, clinical tenancy & proxy authorization safeguards

4.1 Lawful pathways for establishing patient profiles

To protect patient health sovereignty, prevent identity fabrication, and ensure clinical oversight, every patient medical profile within Cura must be established through one of two authorized pathways:

  • Pathway A: Clinician onboarding: A licensed healthcare practice provisions the patient profile, verifies the patient’s identity in a clinical setting, and assigns an accountable attending physician (primary_clinician_id) holding medical duty of care.
  • Pathway B: Direct patient self-registration: A competent adult patient directly registers their own account, verifies their identity, and provides explicit Special Category Health Data consent under GDPR Article 9.

4.2 Strict prohibition on unilateral carer profile creation

Carers, family members, guardians, and third parties are strictly prohibited from independently creating, registering, or self-provisioning a new patient profile on their own without prior clinical establishment or direct patient initiation. This rule is rooted in non-negotiable legal and clinical safeguards:

  • GDPR Article 9 (Special Category Health Data): Processing of sensitive medical data is prohibited under European Union law unless explicit, freely given consent is provided directly by the data subject (the patient) or an officially certified legal power of attorney. Third parties cannot lawfully consent to the creation of a digital medical dossier on behalf of another competent adult.
  • HIPAA 45 CFR § 164.502(g) (Personal Representatives): Under federal health privacy standards, proxy authority requires verified legal standing (such as court-appointed guardianship or a healthcare power of attorney). Unverified self-service creation of patient profiles by third parties violates privacy regulations and invites unauthorized medical profiling.
  • Clinical duty of care & malpractice prevention: Cura generates pre-visit synthesis briefs and early-warning deterioration alerts. If third parties could create unattached "orphan" patient records without an accountable attending physician, critical deterioration alerts would go unmonitored, creating lethal clinical risk and severe legal liability.
  • Anti-coercion & anti-surveillance safeguard: Restricting profile creation ensures vulnerable individuals, elderly family members, or domestic partners cannot be subjected to unauthorized surveillance, coercive digital tracking, or falsified proxy health histories without their explicit awareness and consent.

4.3 Lawful carer proxy delegation & consent hard gate

A carer may only be linked to a patient profile through: (1) an invitation initiated by the registered patient via their secure account settings, or (2) formal care team assignment by the attending clinician with the patient’s documented approval. Before any proxy logging occurs, the patient must execute the Carer Proxy Logging Consent gate (consent_type = "carer_proxy_logging"), establishing an active, time-bounded CarerPatientRelationship.

4.4 Immutable provenance & unalienable patient revocation rights

Every health observation entered by a carer is permanently marked with is_carer_entry = true and bound to the carer’s authenticated author ID. Carers can never overwrite or disguise entries as direct patient statements. In accordance with GDPR Article 7(3), the patient retains the absolute, unalienable right to view all proxy submissions and unilaterally revoke carer proxy access at any time with immediate effect. Carers cannot modify medication regimens, dismiss alerts, or delete historical records.

Article 5. Verbatim source-grounded AI extraction warranty

Cura enforces strict Pydantic v2 JSON schemas and verbatim string substring grounding validators on all AI model pipelines. Every extracted symptom, vital sign, or medication event is strictly verified against the raw patient or carer text to prevent unauthorized inference.

The system guarantees zero hallucination: AI models are prohibited from diagnosing conditions, guessing unmentioned symptoms, or speculating on prognosis. All extracted entities link directly to verbatim character offsets in the verified source text.

Article 6. Protected Health Information (PHI) security & cryptographic isolation

All Protected Health Information is encrypted at rest using AES-256-GCM envelope encryption and in transit via TLS 1.3 with forward secrecy. Medication names and search targets are indexed exclusively via salted HMAC-SHA256 blind indexing to ensure zero searchable plaintext in database indexes.

Multi-tenant isolation is enforced at the database layer via PostgreSQL Row-Level Security (RLS) operating in fail-closed mode. Patient data is strictly hosted within European Union data centers, is never used to train public foundation models, and is never sold or shared with commercial advertising brokers.

Article 7. Patient data rights & statutory archive retention (GDPR / AVG / WGBO)

Patients have the unalienable right under GDPR Articles 15–20 to access, export, rectify, and request erasure of their self-reported health narratives. Account exports are provided in open, structured formats.

Where health records form an integrated part of formal medical consultations, requests for deletion are balanced against mandatory statutory medical archive retention obligations (such as the 20-year retention rule under the Dutch Medical Treatment Contracts Act / WGBO). Non-clinical account information is erased upon request.

Article 8. Constitutional platform boundaries & prohibitions

Users, carers, and integrated healthcare systems agree to the following absolute boundaries:

  • No live consultation recording: Cura must never be used to ambiently record, scribe, or listen to live doctor-patient visits inside consultation rooms. Cura is strictly a between-visit asynchronous memory platform.
  • No billing or claims manipulation: The platform does not generate billing codes (ICD/CPT) or invoice calculation logic and must not be used for financial reimbursement disputes or commercial claims generation.
  • No unlawful proxy logging: Submitting proxy entries without documented patient consent or legal authority is strictly prohibited and subject to immediate account termination.

Legal & governance questions

Clear answers regarding patient identity, carer proxy boundaries, and data protection rules.

Can a family member or carer register or create a patient profile on their own?
No. Under GDPR Article 9 (Special Categories of Data) and HIPAA 45 CFR § 164.502(g), carers and family members are strictly prohibited from independently creating a patient medical record. A patient profile must originate either from an authorized healthcare provider (establishing medical duty of care) or directly from the competent adult patient. Carers operate solely as delegated proxy contributors linked to an existing profile with verified consent.
Why does Cura require an attending clinician or verified patient registration?
Cura tracks clinical deterioration trends and generates pre-visit synthesis briefs. Every medical profile must have an assigned attending clinician (primary_clinician_id) holding medical duty of care. Permitting third parties to create unattached or "orphan" patient records creates lethal clinical risk—red-flag deterioration alerts would have no accountable doctor to receive or act on them, creating severe clinical liability.
How does a patient delegate logging access to a family carer?
A patient or their attending clinician issues a secure, time-bounded invitation to the carer. Before any proxy logging occurs, the patient must review and sign the explicit Carer Proxy Logging Consent (GDPR Art. 9 consent_type = "carer_proxy_logging"). Once verified, the carer is linked through an active CarerPatientRelationship.
Can a patient see what a carer logs about them?
Yes. Full transparency is legally enforced. Every carer observation is permanently stamped with is_carer_entry = true and the carer’s author ID. The patient can inspect all proxy submissions in their timeline and retains the unalienable right under GDPR Article 7(3) to unilaterally revoke carer proxy access at any time with immediate effect.
Can a carer alter medications or dismiss clinical alerts?
No. Carers have strictly bounded permissions. Carers can only submit observational symptom notes, adherence reports, and contextual voice notes. They cannot alter medication plans, dismiss clinician deterioration alerts, reassign healthcare providers, or delete longitudinal medical history.
Who is clinically responsible for reviewing deterioration alerts?
The assigned attending clinician. Cura is strictly an asynchronous between-visit memory and clinical synthesis aid, not an automated emergency response system. Clinicians review pre-visit briefs and early-warning alerts during scheduled encounters and exercise independent professional medical judgment.
Who owns the health logs submitted to Cura?
Patients retain complete ownership of their personal health narratives and self-reported data. Cura acts strictly as a secure data processor and memory custodian for you and your direct care team.
How do I export my health data or request account deletion?
You may export your complete longitudinal history, symptom logs, and pre-visit briefs at any time via your account settings. You may also request account deletion under GDPR Article 17, subject to mandatory statutory medical archive retention obligations (such as the Dutch WGBO 20-year retention rule for clinical notes).

Who it is for

  • Patients and carers
  • Clinicians
  • Sign in
  • Create account

Compliance

  • Security
  • Data controls

About us

  • About Cura
  • Contact us

Legal

  • Privacy policy
  • Terms of service
  • Cookie policy

© 2026 Cura Labs. All rights reserved. · Hosted in the EU

Photographs and illustrations on this site are illustrative. Demo patients are not real records.