1 Definitions

1 Definitions

1 Definitions

  • User: Anyone who accesses the Services, including clinicians, researchers, administrators, policymakers, and patients.

  • Radii Core: Offline‑capable Electronic Medical Records (EMR) system for hospitals and clinics to capture, store, and manage patient data, plus optional clinical decision‑support features.

  • Radii Sector: Secure research data portal providing governed access to standardized, de‑identified health datasets for approved researchers, data scientists, and ML engineers.

  • Radii Circle: Strategic intelligence and analytics suite that delivers real‑time dashboards, system‑level KPIs, and policy‑simulation tools for health‑system administrators, funders, and government ministries.

  • PHI: “Protected Health Information” as defined under HIPAA or comparable local law.

  • De‑identified Data: Data stripped of direct personal identifiers in accordance with HIPAA Safe Harbor, GDPR anonymization, or equivalent standards.

  • Authorized User: A User granted explicit permission by Radii or a partner institution to access specific products, datasets, or APIs.

  • Aggregated Data: Non‑identifiable data that have been combined across multiple patients so that no individual can be re‑identified.

  • k‑Anonymisation: A privacy technique that guarantees each record is indistinguishable from at least k – 1 other records on selected quasi‑identifiers.

  • Model Factsheet: A public document describing an AI model’s purpose, training data, metrics, limitations, and update history.

  • Offline Storage Key: An AES‑256 or ChaCha20‑Poly1305 key generated in the healthcare facility’s Hardware Security Module and used to encrypt data stored locally before synchronisation.

  • User: Anyone who accesses the Services, including clinicians, researchers, administrators, policymakers, and patients.

  • Radii Core: Offline‑capable Electronic Medical Records (EMR) system for hospitals and clinics to capture, store, and manage patient data, plus optional clinical decision‑support features.

  • Radii Sector: Secure research data portal providing governed access to standardized, de‑identified health datasets for approved researchers, data scientists, and ML engineers.

  • Radii Circle: Strategic intelligence and analytics suite that delivers real‑time dashboards, system‑level KPIs, and policy‑simulation tools for health‑system administrators, funders, and government ministries.

  • PHI: “Protected Health Information” as defined under HIPAA or comparable local law.

  • De‑identified Data: Data stripped of direct personal identifiers in accordance with HIPAA Safe Harbor, GDPR anonymization, or equivalent standards.

  • Authorized User: A User granted explicit permission by Radii or a partner institution to access specific products, datasets, or APIs.

  • Aggregated Data: Non‑identifiable data that have been combined across multiple patients so that no individual can be re‑identified.

  • k‑Anonymisation: A privacy technique that guarantees each record is indistinguishable from at least k – 1 other records on selected quasi‑identifiers.

  • Model Factsheet: A public document describing an AI model’s purpose, training data, metrics, limitations, and update history.

  • Offline Storage Key: An AES‑256 or ChaCha20‑Poly1305 key generated in the healthcare facility’s Hardware Security Module and used to encrypt data stored locally before synchronisation.

  • User: Anyone who accesses the Services, including clinicians, researchers, administrators, policymakers, and patients.

  • Radii Core: Offline‑capable Electronic Medical Records (EMR) system for hospitals and clinics to capture, store, and manage patient data, plus optional clinical decision‑support features.

  • Radii Sector: Secure research data portal providing governed access to standardized, de‑identified health datasets for approved researchers, data scientists, and ML engineers.

  • Radii Circle: Strategic intelligence and analytics suite that delivers real‑time dashboards, system‑level KPIs, and policy‑simulation tools for health‑system administrators, funders, and government ministries.

  • PHI: “Protected Health Information” as defined under HIPAA or comparable local law.

  • De‑identified Data: Data stripped of direct personal identifiers in accordance with HIPAA Safe Harbor, GDPR anonymization, or equivalent standards.

  • Authorized User: A User granted explicit permission by Radii or a partner institution to access specific products, datasets, or APIs.

  • Aggregated Data: Non‑identifiable data that have been combined across multiple patients so that no individual can be re‑identified.

  • k‑Anonymisation: A privacy technique that guarantees each record is indistinguishable from at least k – 1 other records on selected quasi‑identifiers.

  • Model Factsheet: A public document describing an AI model’s purpose, training data, metrics, limitations, and update history.

  • Offline Storage Key: An AES‑256 or ChaCha20‑Poly1305 key generated in the healthcare facility’s Hardware Security Module and used to encrypt data stored locally before synchronisation.

2 Eligibility & Account Registration

2 Eligibility & Account Registration

2 Eligibility & Account Registration

  • You must be 18 years or older and legally able to enter a contract.

  • Access to Radii Core or Radii Sector on behalf of an institution requires valid affiliation (e.g., hospital, university, NGO).

  • During registration you agree to:

    1. Provide accurate information;

    2. Keep credentials confidential;

    3. Notify Radii immediately of any unauthorized use.

  • You must be 18 years or older and legally able to enter a contract.

  • Access to Radii Core or Radii Sector on behalf of an institution requires valid affiliation (e.g., hospital, university, NGO).

  • During registration you agree to:

    1. Provide accurate information;

    2. Keep credentials confidential;

    3. Notify Radii immediately of any unauthorized use.

  • You must be 18 years or older and legally able to enter a contract.

  • Access to Radii Core or Radii Sector on behalf of an institution requires valid affiliation (e.g., hospital, university, NGO).

  • During registration you agree to:

    1. Provide accurate information;

    2. Keep credentials confidential;

    3. Notify Radii immediately of any unauthorized use.

3 Scope of Services

3 Scope of Services

3 Scope of Services

  • Radii Core: Clinical records, workflow automation, AI‑powered charting, and care‑coordination tools designed for low‑connectivity environments.

  • Radii Sector: Ethics‑aligned sandbox for cohort building, statistical analysis, and machine‑learning experimentation on de‑identified datasets under Data Use Agreements (DUAs).

  • Radii Circle: Population‑level analytics offering real‑time dashboards on disease burden, resource utilization, and operational performance; scenario modeling and policy impact simulations; scheduled reports to inform funding and strategic planning.


    Each product may be subject to additional licensing terms, SLAs, or institutional MOUs.

  • Radii Core: Clinical records, workflow automation, AI‑powered charting, and care‑coordination tools designed for low‑connectivity environments.

  • Radii Sector: Ethics‑aligned sandbox for cohort building, statistical analysis, and machine‑learning experimentation on de‑identified datasets under Data Use Agreements (DUAs).

  • Radii Circle: Population‑level analytics offering real‑time dashboards on disease burden, resource utilization, and operational performance; scenario modeling and policy impact simulations; scheduled reports to inform funding and strategic planning.


    Each product may be subject to additional licensing terms, SLAs, or institutional MOUs.

  • Radii Core: Clinical records, workflow automation, AI‑powered charting, and care‑coordination tools designed for low‑connectivity environments.

  • Radii Sector: Ethics‑aligned sandbox for cohort building, statistical analysis, and machine‑learning experimentation on de‑identified datasets under Data Use Agreements (DUAs).

  • Radii Circle: Population‑level analytics offering real‑time dashboards on disease burden, resource utilization, and operational performance; scenario modeling and policy impact simulations; scheduled reports to inform funding and strategic planning.


    Each product may be subject to additional licensing terms, SLAs, or institutional MOUs.

3.1 Scope of Services

3.1 Scope of Services

3.1 Scope of Services

  • Data Ingestion: Clinical data entered in Radii Core are stored locally on the facility device, encrypted (see § 4.1, “Offline Storage”), and then synchronised to Radii’s cloud when connectivity is available.

  • De‑identification Pipeline: Upon arrival in the cloud, PHI undergoes automated redaction and tokenisation. Direct identifiers are removed; quasi‑identifiers are generalised or k‑anonymised before any dataset is promoted to Radii Sector or aggregated into Radii Circle.

  • Analytic & Policy Layers: Only de‑identified or aggregated data feed Sector workspaces and Circle dashboards. Reverse data flow—from Circle back into Core—never contains patient‑identifying fields.

  • Audit Trail: All transformations are logged in an immutable ledger, with dataset provenance visible to institutional Data Protection Officers (DPOs).

  • Data Ingestion: Clinical data entered in Radii Core are stored locally on the facility device, encrypted (see § 4.1, “Offline Storage”), and then synchronised to Radii’s cloud when connectivity is available.

  • De‑identification Pipeline: Upon arrival in the cloud, PHI undergoes automated redaction and tokenisation. Direct identifiers are removed; quasi‑identifiers are generalised or k‑anonymised before any dataset is promoted to Radii Sector or aggregated into Radii Circle.

  • Analytic & Policy Layers: Only de‑identified or aggregated data feed Sector workspaces and Circle dashboards. Reverse data flow—from Circle back into Core—never contains patient‑identifying fields.

  • Audit Trail: All transformations are logged in an immutable ledger, with dataset provenance visible to institutional Data Protection Officers (DPOs).

  • Data Ingestion: Clinical data entered in Radii Core are stored locally on the facility device, encrypted (see § 4.1, “Offline Storage”), and then synchronised to Radii’s cloud when connectivity is available.

  • De‑identification Pipeline: Upon arrival in the cloud, PHI undergoes automated redaction and tokenisation. Direct identifiers are removed; quasi‑identifiers are generalised or k‑anonymised before any dataset is promoted to Radii Sector or aggregated into Radii Circle.

  • Analytic & Policy Layers: Only de‑identified or aggregated data feed Sector workspaces and Circle dashboards. Reverse data flow—from Circle back into Core—never contains patient‑identifying fields.

  • Audit Trail: All transformations are logged in an immutable ledger, with dataset provenance visible to institutional Data Protection Officers (DPOs).

4 Data Use, Security & Compliance

4 Data Use, Security & Compliance

4 Data Use, Security & Compliance

  • Radii employs a defence‑in‑depth security model and complies with applicable privacy statutes in the United States, the European Union, and multiple African jurisdictions.

  • Radii employs a defence‑in‑depth security model and complies with applicable privacy statutes in the United States, the European Union, and multiple African jurisdictions.

  • Radii employs a defence‑in‑depth security model and complies with applicable privacy statutes in the United States, the European Union, and multiple African jurisdictions.

4.1 Technical Safeguards

4.1 Technical Safeguards

4.1 Technical Safeguards

  • Encryption at Rest: All PHI and de‑identified datasets are encrypted with AES‑256 on FIPS 140‑2 validated hardware‑backed keys (AWS KMS / GCP Cloud HSM).

  • Encryption in Transit: TLS 1.3 with forward‑secrecy; HSTS enforced; mutual‑TLS available for hospital‑to‑cloud VPN tunnels.

  • Access Control: Fine‑grained RBAC enforced by Open Policy Agent. MFA required for privileged roles; SSO via SAML 2.0 / OIDC.

  • Least‑Privilege Service Mesh: Every microservice runs in its own namespace with network‑policy isolation and signed SPIFFE IDs.

  • Audit & Tamper‑Evident Logs: All access events streamed to an immutable ledger (AWS Q‑LDB) and a SIEM with real‑time anomaly detection.

  • Network Security: Layer‑7 WAF, IDS/IPS, and eBPF‑based runtime intrusion detection. Production subnet is segregated by VPC peering.

  • Secure Development: Static, dynamic, and SCA scanning in CI/CD; signed SBOMs; supply‑chain controls with gitleaks and sigstore.

  • Back‑ups & DR: Encrypted, versioned backups; RPO ≤ 15 min, RTO ≤ 2 h; cross‑region replication in the same data‑sovereignty zone.

  • Device‑Level Controls: Workstations that handle PHI must have full‑disk encryption, EDR, and remote‑wipe capability.

  • Offline Storage: On‑device SQLite/Realm stores are encrypted with ChaCha20‑Poly1305 using keys derived from the facility’s Hardware Security Module. Data auto‑locks after 10 minutes of inactivity and is wiped after 10 consecutive failed log‑ins or upon remote‑wipe command from the Radii admin console.

  • Encryption at Rest: All PHI and de‑identified datasets are encrypted with AES‑256 on FIPS 140‑2 validated hardware‑backed keys (AWS KMS / GCP Cloud HSM).

  • Encryption in Transit: TLS 1.3 with forward‑secrecy; HSTS enforced; mutual‑TLS available for hospital‑to‑cloud VPN tunnels.

  • Access Control: Fine‑grained RBAC enforced by Open Policy Agent. MFA required for privileged roles; SSO via SAML 2.0 / OIDC.

  • Least‑Privilege Service Mesh: Every microservice runs in its own namespace with network‑policy isolation and signed SPIFFE IDs.

  • Audit & Tamper‑Evident Logs: All access events streamed to an immutable ledger (AWS Q‑LDB) and a SIEM with real‑time anomaly detection.

  • Network Security: Layer‑7 WAF, IDS/IPS, and eBPF‑based runtime intrusion detection. Production subnet is segregated by VPC peering.

  • Secure Development: Static, dynamic, and SCA scanning in CI/CD; signed SBOMs; supply‑chain controls with gitleaks and sigstore.

  • Back‑ups & DR: Encrypted, versioned backups; RPO ≤ 15 min, RTO ≤ 2 h; cross‑region replication in the same data‑sovereignty zone.

  • Device‑Level Controls: Workstations that handle PHI must have full‑disk encryption, EDR, and remote‑wipe capability.

  • Offline Storage: On‑device SQLite/Realm stores are encrypted with ChaCha20‑Poly1305 using keys derived from the facility’s Hardware Security Module. Data auto‑locks after 10 minutes of inactivity and is wiped after 10 consecutive failed log‑ins or upon remote‑wipe command from the Radii admin console.

  • Encryption at Rest: All PHI and de‑identified datasets are encrypted with AES‑256 on FIPS 140‑2 validated hardware‑backed keys (AWS KMS / GCP Cloud HSM).

  • Encryption in Transit: TLS 1.3 with forward‑secrecy; HSTS enforced; mutual‑TLS available for hospital‑to‑cloud VPN tunnels.

  • Access Control: Fine‑grained RBAC enforced by Open Policy Agent. MFA required for privileged roles; SSO via SAML 2.0 / OIDC.

  • Least‑Privilege Service Mesh: Every microservice runs in its own namespace with network‑policy isolation and signed SPIFFE IDs.

  • Audit & Tamper‑Evident Logs: All access events streamed to an immutable ledger (AWS Q‑LDB) and a SIEM with real‑time anomaly detection.

  • Network Security: Layer‑7 WAF, IDS/IPS, and eBPF‑based runtime intrusion detection. Production subnet is segregated by VPC peering.

  • Secure Development: Static, dynamic, and SCA scanning in CI/CD; signed SBOMs; supply‑chain controls with gitleaks and sigstore.

  • Back‑ups & DR: Encrypted, versioned backups; RPO ≤ 15 min, RTO ≤ 2 h; cross‑region replication in the same data‑sovereignty zone.

  • Device‑Level Controls: Workstations that handle PHI must have full‑disk encryption, EDR, and remote‑wipe capability.

  • Offline Storage: On‑device SQLite/Realm stores are encrypted with ChaCha20‑Poly1305 using keys derived from the facility’s Hardware Security Module. Data auto‑locks after 10 minutes of inactivity and is wiped after 10 consecutive failed log‑ins or upon remote‑wipe command from the Radii admin console.

4.2 Data‑Breach Notification Procedures

4.2 Data‑Breach Notification Procedures

4.2 Data‑Breach Notification Procedures

  • Definition: A “Personal Data Breach” is any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to PHI or other personal data.

  • Internal Response: Incidents are triaged within 4 hours, with containment and forensic logging initiated immediately.

  • Regulatory Notice: Where PHI is involved, Radii notifies the relevant supervisory authority within 72 hours of confirmation and partner institutions’ DPOs within 48 hours.

  • Affected Individuals: If a breach is likely to result in high risk, Radii notifies affected users within 96 hours.

  • Radii cooperates with institutional audits and preserves evidence for 18 months.

  • Definition: A “Personal Data Breach” is any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to PHI or other personal data.

  • Internal Response: Incidents are triaged within 4 hours, with containment and forensic logging initiated immediately.

  • Regulatory Notice: Where PHI is involved, Radii notifies the relevant supervisory authority within 72 hours of confirmation and partner institutions’ DPOs within 48 hours.

  • Affected Individuals: If a breach is likely to result in high risk, Radii notifies affected users within 96 hours.

  • Radii cooperates with institutional audits and preserves evidence for 18 months.

  • Definition: A “Personal Data Breach” is any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to PHI or other personal data.

  • Internal Response: Incidents are triaged within 4 hours, with containment and forensic logging initiated immediately.

  • Regulatory Notice: Where PHI is involved, Radii notifies the relevant supervisory authority within 72 hours of confirmation and partner institutions’ DPOs within 48 hours.

  • Affected Individuals: If a breach is likely to result in high risk, Radii notifies affected users within 96 hours.

  • Radii cooperates with institutional audits and preserves evidence for 18 months.

4.3 Region‑Specific Compliance

4.3 Region‑Specific Compliance

4.3 Region‑Specific Compliance

  • Nigeria: Nigeria Data Protection Act 2023; NITDA Health Data Regulations. Data residency in AWS Africa (Cape Town) or Azure West Africa, unless a DTA authorises cross‑border transfer.

  • Kenya: Data Protection Act 2019 & Health Act 2017. Local representative appointed; breach notice delivered to the ODPC & MoH.

  • South Africa: POPIA 2013; National Health Act & HPCSA Ethical Rules. Onshore processing required for identifiable data; de‑identified data may transit under Section 57 exemptions.

  • Ghana / Rwanda: Ghana Data Protection Act 2012; Rwanda Law 058/2021. Radii participates in AU Malabo‑Convention alignment initiatives.

  • Côte d’Ivoire: Law 2013‑450 on Personal Data Protection. Radii stores identifiable data in Azure West Africa and appoints a local representative with the APDP.

  • Pan‑African Research: Lead‑ethics clearance plus each national ethics committee’s approval. Radii Sector enforces DUA‑level geo‑fencing; Radii Circle offers aggregation controls to prevent re‑identification.

  • Other AU Member States: Radii complies with country‑specific health‑data regulations and, by default, the AU Malabo Convention.

  • Nigeria: Nigeria Data Protection Act 2023; NITDA Health Data Regulations. Data residency in AWS Africa (Cape Town) or Azure West Africa, unless a DTA authorises cross‑border transfer.

  • Kenya: Data Protection Act 2019 & Health Act 2017. Local representative appointed; breach notice delivered to the ODPC & MoH.

  • South Africa: POPIA 2013; National Health Act & HPCSA Ethical Rules. Onshore processing required for identifiable data; de‑identified data may transit under Section 57 exemptions.

  • Ghana / Rwanda: Ghana Data Protection Act 2012; Rwanda Law 058/2021. Radii participates in AU Malabo‑Convention alignment initiatives.

  • Côte d’Ivoire: Law 2013‑450 on Personal Data Protection. Radii stores identifiable data in Azure West Africa and appoints a local representative with the APDP.

  • Pan‑African Research: Lead‑ethics clearance plus each national ethics committee’s approval. Radii Sector enforces DUA‑level geo‑fencing; Radii Circle offers aggregation controls to prevent re‑identification.

  • Other AU Member States: Radii complies with country‑specific health‑data regulations and, by default, the AU Malabo Convention.

  • Nigeria: Nigeria Data Protection Act 2023; NITDA Health Data Regulations. Data residency in AWS Africa (Cape Town) or Azure West Africa, unless a DTA authorises cross‑border transfer.

  • Kenya: Data Protection Act 2019 & Health Act 2017. Local representative appointed; breach notice delivered to the ODPC & MoH.

  • South Africa: POPIA 2013; National Health Act & HPCSA Ethical Rules. Onshore processing required for identifiable data; de‑identified data may transit under Section 57 exemptions.

  • Ghana / Rwanda: Ghana Data Protection Act 2012; Rwanda Law 058/2021. Radii participates in AU Malabo‑Convention alignment initiatives.

  • Côte d’Ivoire: Law 2013‑450 on Personal Data Protection. Radii stores identifiable data in Azure West Africa and appoints a local representative with the APDP.

  • Pan‑African Research: Lead‑ethics clearance plus each national ethics committee’s approval. Radii Sector enforces DUA‑level geo‑fencing; Radii Circle offers aggregation controls to prevent re‑identification.

  • Other AU Member States: Radii complies with country‑specific health‑data regulations and, by default, the AU Malabo Convention.

5 Patient Consent & Privacy

5 Patient Consent & Privacy

5 Patient Consent & Privacy

Patients (or their legal representatives) may exercise access, rectification, or deletion rights by:


1. Submitting a request at the originating facility, or
2. Emailing team@radiihealth.com with verifiable identity documentation.



Radii routes requests to the Data Controller and provides technical tooling—record‑locator hashes, export APIs, deletion jobs—to fulfil the request within legal timeframes.

Institutions may enable a patient portal for self‑service record access and corrections.

Patients (or their legal representatives) may exercise access, rectification, or deletion rights by:


1. Submitting a request at the originating facility, or
2. Emailing team@radiihealth.com with verifiable identity documentation.



Radii routes requests to the Data Controller and provides technical tooling—record‑locator hashes, export APIs, deletion jobs—to fulfil the request within legal timeframes.

Institutions may enable a patient portal for self‑service record access and corrections.

Patients (or their legal representatives) may exercise access, rectification, or deletion rights by:


1. Submitting a request at the originating facility, or
2. Emailing team@radiihealth.com with verifiable identity documentation.



Radii routes requests to the Data Controller and provides technical tooling—record‑locator hashes, export APIs, deletion jobs—to fulfil the request within legal timeframes.

Institutions may enable a patient portal for self‑service record access and corrections.

6 User Responsibilities

6 User Responsibilities

6 User Responsibilities

  1. Responsibilities when entering or submitting data

    • Accuracy & Legality: No false, misleading, or unlawful information.

    • Data Quality: Verify completeness and attribution.

    • Consent & Authority: Submit only data you are permitted to handle.

    • Prohibited Content: No IP‑infringing or malicious material.

      



  2. General security & compliance conduct

    • No Reverse Engineering of Radii source code.

    • No Service Disruption (malware, DoS, unauthorized pen‑testing).

    • No Unauthorized Redistribution of Radii Sector raw data or Radii Circle aggregates.

    • Export‑Control Compliance with U.S./international sanctions.

    • Device Hygiene & Patching – encryption, anti‑malware, MFA, updates within 30 days.

  1. Responsibilities when entering or submitting data

    • Accuracy & Legality: No false, misleading, or unlawful information.

    • Data Quality: Verify completeness and attribution.

    • Consent & Authority: Submit only data you are permitted to handle.

    • Prohibited Content: No IP‑infringing or malicious material.

      



  2. General security & compliance conduct

    • No Reverse Engineering of Radii source code.

    • No Service Disruption (malware, DoS, unauthorized pen‑testing).

    • No Unauthorized Redistribution of Radii Sector raw data or Radii Circle aggregates.

    • Export‑Control Compliance with U.S./international sanctions.

    • Device Hygiene & Patching – encryption, anti‑malware, MFA, updates within 30 days.

  1. Responsibilities when entering or submitting data

    • Accuracy & Legality: No false, misleading, or unlawful information.

    • Data Quality: Verify completeness and attribution.

    • Consent & Authority: Submit only data you are permitted to handle.

    • Prohibited Content: No IP‑infringing or malicious material.

      



  2. General security & compliance conduct

    • No Reverse Engineering of Radii source code.

    • No Service Disruption (malware, DoS, unauthorized pen‑testing).

    • No Unauthorized Redistribution of Radii Sector raw data or Radii Circle aggregates.

    • Export‑Control Compliance with U.S./international sanctions.

    • Device Hygiene & Patching – encryption, anti‑malware, MFA, updates within 30 days.

7 Medical & Policy Disclaimers

7 Medical & Policy Disclaimers

7 Medical & Policy Disclaimers

  • Radii Core decision‑support alerts do not replace professional clinical judgment.

  • Radii Circle projections are advisory for public‑health professionals.

  • Radii provides no individual medical advice or official government statistics.

  • Radii Core decision‑support alerts do not replace professional clinical judgment.

  • Radii Circle projections are advisory for public‑health professionals.

  • Radii provides no individual medical advice or official government statistics.

  • Radii Core decision‑support alerts do not replace professional clinical judgment.

  • Radii Circle projections are advisory for public‑health professionals.

  • Radii provides no individual medical advice or official government statistics.

8 Artificial‑Intelligence Features

8 Artificial‑Intelligence Features

8 Artificial‑Intelligence Features

  • Model Training: Radii may use de‑identified or aggregated data for NLP model retraining and decision‑support improvements. Identifiable PHI is never used.

  • Opt‑out: Institutions may email team@radiihealth.com to exclude their de‑identified data from generic model improvement.

  • Explainability & Bias: AI outputs include confidence scores and limitations, documented in Model Factsheets.

  • No Clinical Autopilot: AI outputs are advisory only (see § 7).

  • Model Training: Radii may use de‑identified or aggregated data for NLP model retraining and decision‑support improvements. Identifiable PHI is never used.

  • Opt‑out: Institutions may email team@radiihealth.com to exclude their de‑identified data from generic model improvement.

  • Explainability & Bias: AI outputs include confidence scores and limitations, documented in Model Factsheets.

  • No Clinical Autopilot: AI outputs are advisory only (see § 7).

  • Model Training: Radii may use de‑identified or aggregated data for NLP model retraining and decision‑support improvements. Identifiable PHI is never used.

  • Opt‑out: Institutions may email team@radiihealth.com to exclude their de‑identified data from generic model improvement.

  • Explainability & Bias: AI outputs include confidence scores and limitations, documented in Model Factsheets.

  • No Clinical Autopilot: AI outputs are advisory only (see § 7).

9 Intellectual Property, Data Ownership & Licensing

9 Intellectual Property, Data Ownership &
Licensing

9 Intellectual Property, Data Ownership & Licensing

  1. Platform IP: Radii retains ownership of software, UX, and documentation.

  2. User‑Generated Data

    1. Ownership: Raw PHI and derivative work remain property of the originating institution or patient.

    2. License to Radii: By entering data, you grant Radii a non‑exclusive, worldwide, royalty‑free license to host, process, and transform data for service delivery, compliance, security, and AI training under § 8.

  3. De‑identified & Aggregated Data: Radii may create and own transformed datasets, using them internally or sharing externally under DUAs that prohibit re‑identification and commercial exploitation without further consent.

  1. Platform IP: Radii retains ownership of software, UX, and documentation.

  2. User‑Generated Data

    1. Ownership: Raw PHI and derivative work remain property of the originating institution or patient.

    2. License to Radii: By entering data, you grant Radii a non‑exclusive, worldwide, royalty‑free license to host, process, and transform data for service delivery, compliance, security, and AI training under § 8.

  3. De‑identified & Aggregated Data: Radii may create and own transformed datasets, using them internally or sharing externally under DUAs that prohibit re‑identification and commercial exploitation without further consent.

  1. Platform IP: Radii retains ownership of software, UX, and documentation.

  2. User‑Generated Data

    1. Ownership: Raw PHI and derivative work remain property of the originating institution or patient.

    2. License to Radii: By entering data, you grant Radii a non‑exclusive, worldwide, royalty‑free license to host, process, and transform data for service delivery, compliance, security, and AI training under § 8.

  3. De‑identified & Aggregated Data: Radii may create and own transformed datasets, using them internally or sharing externally under DUAs that prohibit re‑identification and commercial exploitation without further consent.

10 Feedback & Contributions

10 Feedback & Contributions

10 Feedback & Contributions

Any feedback or suggestions you provide may be used by Radii without obligation or compensation and must be non‑confidential.

Any feedback or suggestions you provide may be used by Radii without obligation or compensation and must be non‑confidential.

Any feedback or suggestions you provide may be used by Radii without obligation or compensation and must be non‑confidential.

11 Service Availability & Maintenance

11 Service Availability & Maintenance

11 Service Availability & Maintenance

Radii aims for high availability but does not guarantee uninterrupted service. Planned maintenance and emergency outages will be communicated when practicable.

Radii aims for high availability but does not guarantee uninterrupted service. Planned maintenance and emergency outages will be communicated when practicable.

Radii aims for high availability but does not guarantee uninterrupted service. Planned maintenance and emergency outages will be communicated when practicable.

11.1 AI‑related Service Interruptions

11.1 AI‑related Service Interruptions

11.1 AI‑related Service Interruptions

If Radii must temporarily disable an AI feature (e.g., model rollback due to bias or safety concern), Radii will notify users in‑app and aim to restore service within 72 hours, or provide a non‑AI fallback workflow.

If Radii must temporarily disable an AI feature (e.g., model rollback due to bias or safety concern), Radii will notify users in‑app and aim to restore service within 72 hours, or provide a non‑AI fallback workflow.

If Radii must temporarily disable an AI feature (e.g., model rollback due to bias or safety concern), Radii will notify users in‑app and aim to restore service within 72 hours, or provide a non‑AI fallback workflow.

12 Limitation of Liability

12 Limitation of Liability

12 Limitation of Liability

To the maximum extent permitted by law:




  • Radii disclaims all implied warranties (merchantability, fitness, non‑infringement).

  • Radii is not liable for indirect, incidental, special, or consequential damages—even if advised of the possibility.

  • Radii’s aggregate liability is capped at USD 250,000 where mandatory (e.g., Kenya DPA § 57).

  • Radii shall not be liable for clinical, operational, or policy decisions made in reliance on AI‑generated outputs.

To the maximum extent permitted by law:




  • Radii disclaims all implied warranties (merchantability, fitness, non‑infringement).

  • Radii is not liable for indirect, incidental, special, or consequential damages—even if advised of the possibility.

  • Radii’s aggregate liability is capped at USD 250,000 where mandatory (e.g., Kenya DPA § 57).

  • Radii shall not be liable for clinical, operational, or policy decisions made in reliance on AI‑generated outputs.

To the maximum extent permitted by law:




  • Radii disclaims all implied warranties (merchantability, fitness, non‑infringement).

  • Radii is not liable for indirect, incidental, special, or consequential damages—even if advised of the possibility.

  • Radii’s aggregate liability is capped at USD 250,000 where mandatory (e.g., Kenya DPA § 57).

  • Radii shall not be liable for clinical, operational, or policy decisions made in reliance on AI‑generated outputs.

13 Indemnification

13 Indemnification

13 Indemnification

You agree to indemnify and hold harmless Radii and its affiliates from any claim arising out of your misuse of the Services, violation of these Terms, or IP/privacy infringement by content you upload.

You agree to indemnify and hold harmless Radii and its affiliates from any claim arising out of your misuse of the Services, violation of these Terms, or IP/privacy infringement by content you upload.

You agree to indemnify and hold harmless Radii and its affiliates from any claim arising out of your misuse of the Services, violation of these Terms, or IP/privacy infringement by content you upload.

14 Termination & Suspension

14 Termination & Suspension

14 Termination & Suspension

Radii may suspend or terminate access if you breach these Terms or a DUA, fail to pay fees, or pose a security/compliance risk. Upon termination you may request data export or deletion subject to legal retention obligations.

Radii may suspend or terminate access if you breach these Terms or a DUA, fail to pay fees, or pose a security/compliance risk. Upon termination you may request data export or deletion subject to legal retention obligations.

Radii may suspend or terminate access if you breach these Terms or a DUA, fail to pay fees, or pose a security/compliance risk. Upon termination you may request data export or deletion subject to legal retention obligations.

15 Modifications to Terms

15 Modifications to Terms

15 Modifications to Terms

Radii may update these Terms. Material changes will be announced via email or in‑app notice at least 30 days before taking effect, unless immediate change is required for legal or security reasons.

Radii may update these Terms. Material changes will be announced via email or in‑app notice at least 30 days before taking effect, unless immediate change is required for legal or security reasons.

Radii may update these Terms. Material changes will be announced via email or in‑app notice at least 30 days before taking effect, unless immediate change is required for legal or security reasons.

16 Third‑Party Services

16 Third‑Party Services

16 Third‑Party Services

The Platform may integrate third‑party APIs (e.g., lab devices, payment gateways). Radii is not liable for the availability or accuracy of third‑party content; such use is governed by their terms.

The Platform may integrate third‑party APIs (e.g., lab devices, payment gateways). Radii is not liable for the availability or accuracy of third‑party content; such use is governed by their terms.

The Platform may integrate third‑party APIs (e.g., lab devices, payment gateways). Radii is not liable for the availability or accuracy of third‑party content; such use is governed by their terms.

17 Export Compliance & Sanctions

17 Export Compliance & Sanctions

17 Export Compliance & Sanctions

You agree to comply with U.S. and international export laws and not use the Services in embargoed countries or prohibited end‑uses (e.g., biological‑weapon research), including autonomous‑weapon or other dual‑use AI applications restricted by U.S., EU, or UN regimes.

You agree to comply with U.S. and international export laws and not use the Services in embargoed countries or prohibited end‑uses (e.g., biological‑weapon research), including autonomous‑weapon or other dual‑use AI applications restricted by U.S., EU, or UN regimes.

You agree to comply with U.S. and international export laws and not use the Services in embargoed countries or prohibited end‑uses (e.g., biological‑weapon research), including autonomous‑weapon or other dual‑use AI applications restricted by U.S., EU, or UN regimes.

18 Governing Law & Dispute Resolution

18 Governing Law & Dispute Resolution

18 Governing Law & Dispute Resolution

Unless superseded by institutional agreement:

  • Governing law: State of California, USA.

  • Venue: State or federal courts in San Francisco County, California.

  • Optional arbitration: Radii may elect binding arbitration under AAA rules for disputes under USD 250,000.

Unless superseded by institutional agreement:

  • Governing law: State of California, USA.

  • Venue: State or federal courts in San Francisco County, California.

  • Optional arbitration: Radii may elect binding arbitration under AAA rules for disputes under USD 250,000.

Unless superseded by institutional agreement:

  • Governing law: State of California, USA.

  • Venue: State or federal courts in San Francisco County, California.

  • Optional arbitration: Radii may elect binding arbitration under AAA rules for disputes under USD 250,000.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.

[ JOIN US ]

Let’s Build Together

We’re actively partnering with hospitals, universities, NGOs, and ministries of health — in Africa and around the world. Whether you're interested in piloting our tools, collaborating on research, or supporting the future of health innovation, we’d love to connect.