Privacy Policy
Privacy Policy
Privacy Policy
Privacy Policy
This Privacy Policy explains how Radii Health, Inc. (“Radii,” “we,” “us,” or “our”) collects, uses, shares, and safeguards personal information—including Protected Health Information (“PHI”)—when you or your institution use any part of the Radii Platform (Radii Core, Radii Sector, Radii Circle), visit our websites, or interact with our support or sales teams. It also describes the rights and choices available to patients, clinicians, researchers, and other users (“you” or “Users”).
If you do not agree with this Policy, please do not use our Services.
This Privacy Policy explains how Radii Health, Inc. (“Radii,” “we,” “us,” or “our”) collects, uses, shares, and safeguards personal information—including Protected Health Information (“PHI”)—when you or your institution use any part of the Radii Platform (Radii Core, Radii Sector, Radii Circle), visit our websites, or interact with our support or sales teams. It also describes the rights and choices available to patients, clinicians, researchers, and other users (“you” or “Users”).
If you do not agree with this Policy, please do not use our Services.
This Privacy Policy explains how Radii Health, Inc. (“Radii,” “we,” “us,” or “our”) collects, uses, shares, and safeguards personal information—including Protected Health Information (“PHI”)—when you or your institution use any part of the Radii Platform (Radii Core, Radii Sector, Radii Circle), visit our websites, or interact with our support or sales teams. It also describes the rights and choices available to patients, clinicians, researchers, and other users (“you” or “Users”).
If you do not agree with this Policy, please do not use our Services.
1 Scope
1 Scope
1 Scope
This policy applies to:
Radii Core (on-premises and cloud deployments)
Radii Sector research portal
Radii Circle dashboards
Public websites, including radiihealth.com
Marketing emails, webinars, and hosted events
Third-party apps embedding Radii APIs (limited to data Radii receives)
It does not apply to external websites that link to Radii.
This policy applies to:
Radii Core (on-premises and cloud deployments)
Radii Sector research portal
Radii Circle dashboards
Public websites, including radiihealth.com
Marketing emails, webinars, and hosted events
Third-party apps embedding Radii APIs (limited to data Radii receives)
It does not apply to external websites that link to Radii.
This policy applies to:
Radii Core (on-premises and cloud deployments)
Radii Sector research portal
Radii Circle dashboards
Public websites, including radiihealth.com
Marketing emails, webinars, and hosted events
Third-party apps embedding Radii APIs (limited to data Radii receives)
It does not apply to external websites that link to Radii.
2 Information We Collect
2 Information We Collect
2 Information We Collect
We may process the following categories of data:
Patient Health Data (PHI): Includes demographics, vitals, diagnoses, lab results, clinical notes, medical images, and clinician-recorded voice dictations. These are entered by clinicians using Radii Core or imported from connected devices and EMRs.
Research Data: Includes de-identified cohort data, derived features, and analytic notebooks. These are provided by authorized researchers or generated by Radii’s de-identification pipeline.
Administrative Data: Includes facility names, license numbers, contact details, and institutional agreements.
Usage and Device Data: Includes IP addresses, browser and device information, session logs, crash reports, and cookies.
Support and Marketing Data: Includes helpdesk emails, feedback surveys, and event registration details.
Biometric and Payment Data: In some cases, Radii may collect fingerprint templates or facial authentication tokens for secure clinical sign-in, as well as masked payment details (e.g., card PAN) for billing or licensing.
We may process the following categories of data:
Patient Health Data (PHI): Includes demographics, vitals, diagnoses, lab results, clinical notes, medical images, and clinician-recorded voice dictations. These are entered by clinicians using Radii Core or imported from connected devices and EMRs.
Research Data: Includes de-identified cohort data, derived features, and analytic notebooks. These are provided by authorized researchers or generated by Radii’s de-identification pipeline.
Administrative Data: Includes facility names, license numbers, contact details, and institutional agreements.
Usage and Device Data: Includes IP addresses, browser and device information, session logs, crash reports, and cookies.
Support and Marketing Data: Includes helpdesk emails, feedback surveys, and event registration details.
Biometric and Payment Data: In some cases, Radii may collect fingerprint templates or facial authentication tokens for secure clinical sign-in, as well as masked payment details (e.g., card PAN) for billing or licensing.
We may process the following categories of data:
Patient Health Data (PHI): Includes demographics, vitals, diagnoses, lab results, clinical notes, medical images, and clinician-recorded voice dictations. These are entered by clinicians using Radii Core or imported from connected devices and EMRs.
Research Data: Includes de-identified cohort data, derived features, and analytic notebooks. These are provided by authorized researchers or generated by Radii’s de-identification pipeline.
Administrative Data: Includes facility names, license numbers, contact details, and institutional agreements.
Usage and Device Data: Includes IP addresses, browser and device information, session logs, crash reports, and cookies.
Support and Marketing Data: Includes helpdesk emails, feedback surveys, and event registration details.
Biometric and Payment Data: In some cases, Radii may collect fingerprint templates or facial authentication tokens for secure clinical sign-in, as well as masked payment details (e.g., card PAN) for billing or licensing.
2.1 Children & Minors
2.1 Children & Minors
2.1 Children & Minors
Radii websites and marketing content are not directed at children under 13 (or under 16 in the EEA/UK). We do not knowingly collect personal data directly from such individuals.
When Radii Core is used in clinical settings, healthcare providers may lawfully enter minors’ medical records. It is their responsibility to obtain parental or legal guardian consent, or use another lawful basis (e.g., vital interest).
De-identified pediatric records may be used in Radii Sector only if approved by the originating IRB or ethics committee.
In jurisdictions like the EU, Kenya, or Nigeria, Radii supports parental access or correction requests via the healthcare facility that entered the data.
Radii websites and marketing content are not directed at children under 13 (or under 16 in the EEA/UK). We do not knowingly collect personal data directly from such individuals.
When Radii Core is used in clinical settings, healthcare providers may lawfully enter minors’ medical records. It is their responsibility to obtain parental or legal guardian consent, or use another lawful basis (e.g., vital interest).
De-identified pediatric records may be used in Radii Sector only if approved by the originating IRB or ethics committee.
In jurisdictions like the EU, Kenya, or Nigeria, Radii supports parental access or correction requests via the healthcare facility that entered the data.
Radii websites and marketing content are not directed at children under 13 (or under 16 in the EEA/UK). We do not knowingly collect personal data directly from such individuals.
When Radii Core is used in clinical settings, healthcare providers may lawfully enter minors’ medical records. It is their responsibility to obtain parental or legal guardian consent, or use another lawful basis (e.g., vital interest).
De-identified pediatric records may be used in Radii Sector only if approved by the originating IRB or ethics committee.
In jurisdictions like the EU, Kenya, or Nigeria, Radii supports parental access or correction requests via the healthcare facility that entered the data.
3 How We Use the Information
3 How We Use the Information
3 How We Use the Information
We use personal and institutional data for:
Providing healthcare services via Radii Core under contractual necessity and public interest in care.
Supporting scientific research via Radii Sector under executed Data Use Agreements (DUAs).
Delivering analytics dashboards in Radii Circle for public health planning.
Training AI systems (only on de-identified or aggregated data) to improve transcription or triage models.
Ensuring security and performance, including system diagnostics and threat monitoring.
Complying with legal obligations, including HIPAA, NDPA, GDPR, and POPIA.
Marketing and administrative communications, based on your consent or Radii’s legitimate interest (opt-out available).
For EU/UK users, soft opt-in may apply to existing customers; explicit consent is required for new prospects.
We use personal and institutional data for:
Providing healthcare services via Radii Core under contractual necessity and public interest in care.
Supporting scientific research via Radii Sector under executed Data Use Agreements (DUAs).
Delivering analytics dashboards in Radii Circle for public health planning.
Training AI systems (only on de-identified or aggregated data) to improve transcription or triage models.
Ensuring security and performance, including system diagnostics and threat monitoring.
Complying with legal obligations, including HIPAA, NDPA, GDPR, and POPIA.
Marketing and administrative communications, based on your consent or Radii’s legitimate interest (opt-out available).
For EU/UK users, soft opt-in may apply to existing customers; explicit consent is required for new prospects.
We use personal and institutional data for:
Providing healthcare services via Radii Core under contractual necessity and public interest in care.
Supporting scientific research via Radii Sector under executed Data Use Agreements (DUAs).
Delivering analytics dashboards in Radii Circle for public health planning.
Training AI systems (only on de-identified or aggregated data) to improve transcription or triage models.
Ensuring security and performance, including system diagnostics and threat monitoring.
Complying with legal obligations, including HIPAA, NDPA, GDPR, and POPIA.
Marketing and administrative communications, based on your consent or Radii’s legitimate interest (opt-out available).
For EU/UK users, soft opt-in may apply to existing customers; explicit consent is required for new prospects.
4 AI-Specific Disclosures
4 AI-Specific Disclosures
4 AI-Specific Disclosures
Radii AI models are never trained on identifiable PHI.
Public Model Factsheets describe intended use, limitations, accuracy metrics, and demographic performance.
All outputs are advisory and must be interpreted by qualified humans.
Institutions may opt out of de-identified data use for general AI model improvement by emailing: team@radiihealth.com.
Radii AI models are never trained on identifiable PHI.
Public Model Factsheets describe intended use, limitations, accuracy metrics, and demographic performance.
All outputs are advisory and must be interpreted by qualified humans.
Institutions may opt out of de-identified data use for general AI model improvement by emailing: team@radiihealth.com.
Radii AI models are never trained on identifiable PHI.
Public Model Factsheets describe intended use, limitations, accuracy metrics, and demographic performance.
All outputs are advisory and must be interpreted by qualified humans.
Institutions may opt out of de-identified data use for general AI model improvement by emailing: team@radiihealth.com.
5 Cookies & Similar Technologies
5 Cookies & Similar Technologies
5 Cookies & Similar Technologies
We use a limited number of browser-based tracking tools. These include:
Strictly Necessary Cookies: Required for login sessions, CSRF protection, and server routing. Cannot be disabled.
Functional Cookies: Store language and display preferences. Optional; enabled via cookie banner.
Performance & Analytics Tools: Matomo, Google Analytics 4, and (optionally) Hotjar. IPs are anonymized; tools respect "Do Not Track".
Security Cookies: Cloudflare uses short-lived device fingerprints to detect bots or fraud.
Marketing Pixels: HubSpot may embed an open-tracking pixel in emails, but only when users have explicitly opted in. You can manage cookie preferences in-app via the “Cookie Settings” panel or through your browser.
Legal basis: Strictly necessary and security cookies rely on legitimate interest; analytics and marketing require consent where applicable.
We use a limited number of browser-based tracking tools. These include:
Strictly Necessary Cookies: Required for login sessions, CSRF protection, and server routing. Cannot be disabled.
Functional Cookies: Store language and display preferences. Optional; enabled via cookie banner.
Performance & Analytics Tools: Matomo, Google Analytics 4, and (optionally) Hotjar. IPs are anonymized; tools respect "Do Not Track".
Security Cookies: Cloudflare uses short-lived device fingerprints to detect bots or fraud.
Marketing Pixels: HubSpot may embed an open-tracking pixel in emails, but only when users have explicitly opted in. You can manage cookie preferences in-app via the “Cookie Settings” panel or through your browser.
Legal basis: Strictly necessary and security cookies rely on legitimate interest; analytics and marketing require consent where applicable.
We use a limited number of browser-based tracking tools. These include:
Strictly Necessary Cookies: Required for login sessions, CSRF protection, and server routing. Cannot be disabled.
Functional Cookies: Store language and display preferences. Optional; enabled via cookie banner.
Performance & Analytics Tools: Matomo, Google Analytics 4, and (optionally) Hotjar. IPs are anonymized; tools respect "Do Not Track".
Security Cookies: Cloudflare uses short-lived device fingerprints to detect bots or fraud.
Marketing Pixels: HubSpot may embed an open-tracking pixel in emails, but only when users have explicitly opted in. You can manage cookie preferences in-app via the “Cookie Settings” panel or through your browser.
Legal basis: Strictly necessary and security cookies rely on legitimate interest; analytics and marketing require consent where applicable.
6 Sharing & Disclosure
6 Sharing & Disclosure
6 Sharing & Disclosure
Radii does not sell your personal information.
We may share data only with:
Your institution (e.g., hospital, health ministry): to fulfill our contract and support audit trails.
Approved researchers: only de-identified data under DUA terms prohibiting re-identification.
Cloud and infrastructure vendors: AWS, GCP, and Azure provide secure hosting under HIPAA or data processing agreements.
Regulators or public authorities: as required by law or breach reporting rules.
Professional advisors: auditors, legal counsel, and tax consultants under confidentiality obligations.
Buyers or investors: during mergers or acquisitions, with safeguards and institutional notice.
Radii does not sell your personal information.
We may share data only with:
Your institution (e.g., hospital, health ministry): to fulfill our contract and support audit trails.
Approved researchers: only de-identified data under DUA terms prohibiting re-identification.
Cloud and infrastructure vendors: AWS, GCP, and Azure provide secure hosting under HIPAA or data processing agreements.
Regulators or public authorities: as required by law or breach reporting rules.
Professional advisors: auditors, legal counsel, and tax consultants under confidentiality obligations.
Buyers or investors: during mergers or acquisitions, with safeguards and institutional notice.
Radii does not sell your personal information.
We may share data only with:
Your institution (e.g., hospital, health ministry): to fulfill our contract and support audit trails.
Approved researchers: only de-identified data under DUA terms prohibiting re-identification.
Cloud and infrastructure vendors: AWS, GCP, and Azure provide secure hosting under HIPAA or data processing agreements.
Regulators or public authorities: as required by law or breach reporting rules.
Professional advisors: auditors, legal counsel, and tax consultants under confidentiality obligations.
Buyers or investors: during mergers or acquisitions, with safeguards and institutional notice.
7 International Data Transfers
7 International Data Transfers
7 International Data Transfers
We host data in AWS Africa (Cape Town), Azure West Africa, and AWS US West. Cross-border transfers are permitted only where legally justified.
Mechanisms include:
EEA/UK to third countries: EU Standard Contractual Clauses (SCCs) or UK IDTA.
Nigeria: NDPA Data Transfer Agreement (DTA) or NDPC adequacy ruling.
Kenya: ODPC Transfer Impact Assessment (TIA) and ministerial approval.
South Africa: POPIA §72(1) contracts; §57 exemptions for research.
Other AU states: Malabo Convention–aligned contracts or local export permits.
HIPAA PHI exports: Only with patient authorization or covered exceptions.
Brazil / UAE: Contractual clauses approved by the ANPD or UAE DPA.
Emergencies: Public health crises may override restrictions under GDPR Art. 49, NDPA §43, or POPIA.
All transfers are encrypted and logged. Researchers can only access data from regions approved in their DUAs.
We host data in AWS Africa (Cape Town), Azure West Africa, and AWS US West. Cross-border transfers are permitted only where legally justified.
Mechanisms include:
EEA/UK to third countries: EU Standard Contractual Clauses (SCCs) or UK IDTA.
Nigeria: NDPA Data Transfer Agreement (DTA) or NDPC adequacy ruling.
Kenya: ODPC Transfer Impact Assessment (TIA) and ministerial approval.
South Africa: POPIA §72(1) contracts; §57 exemptions for research.
Other AU states: Malabo Convention–aligned contracts or local export permits.
HIPAA PHI exports: Only with patient authorization or covered exceptions.
Brazil / UAE: Contractual clauses approved by the ANPD or UAE DPA.
Emergencies: Public health crises may override restrictions under GDPR Art. 49, NDPA §43, or POPIA.
All transfers are encrypted and logged. Researchers can only access data from regions approved in their DUAs.
We host data in AWS Africa (Cape Town), Azure West Africa, and AWS US West. Cross-border transfers are permitted only where legally justified.
Mechanisms include:
EEA/UK to third countries: EU Standard Contractual Clauses (SCCs) or UK IDTA.
Nigeria: NDPA Data Transfer Agreement (DTA) or NDPC adequacy ruling.
Kenya: ODPC Transfer Impact Assessment (TIA) and ministerial approval.
South Africa: POPIA §72(1) contracts; §57 exemptions for research.
Other AU states: Malabo Convention–aligned contracts or local export permits.
HIPAA PHI exports: Only with patient authorization or covered exceptions.
Brazil / UAE: Contractual clauses approved by the ANPD or UAE DPA.
Emergencies: Public health crises may override restrictions under GDPR Art. 49, NDPA §43, or POPIA.
All transfers are encrypted and logged. Researchers can only access data from regions approved in their DUAs.
8 Security Measures
8 Security Measures
8 Security Measures
Our technical and organizational safeguards include:
AES-256 and ChaCha20 encryption (at rest), TLS 1.3 (in transit)
Role-based access control (RBAC), MFA, and SSO
Secure offline storage with remote wipe
Immutable logs and intrusion detection
Zero-trust architecture with least-privilege microservices
SOC 2 Type II certification (last audited March 2025)
Annual penetration testing
Our technical and organizational safeguards include:
AES-256 and ChaCha20 encryption (at rest), TLS 1.3 (in transit)
Role-based access control (RBAC), MFA, and SSO
Secure offline storage with remote wipe
Immutable logs and intrusion detection
Zero-trust architecture with least-privilege microservices
SOC 2 Type II certification (last audited March 2025)
Annual penetration testing
Our technical and organizational safeguards include:
AES-256 and ChaCha20 encryption (at rest), TLS 1.3 (in transit)
Role-based access control (RBAC), MFA, and SSO
Secure offline storage with remote wipe
Immutable logs and intrusion detection
Zero-trust architecture with least-privilege microservices
SOC 2 Type II certification (last audited March 2025)
Annual penetration testing
9 Data Retention
9 Data Retention
9 Data Retention
Clinical PHI: Retained for 10 years or as required by national health law.
De-identified research data: Retained indefinitely unless restricted by DUA.
Usage logs: Security logs are kept for 12 months; full IP logs for 30 days.
Support/marketing records: Retained for 3 years or until unsubscribed.
Backups are retained for 35 days before secure deletion.
Clinical PHI: Retained for 10 years or as required by national health law.
De-identified research data: Retained indefinitely unless restricted by DUA.
Usage logs: Security logs are kept for 12 months; full IP logs for 30 days.
Support/marketing records: Retained for 3 years or until unsubscribed.
Backups are retained for 35 days before secure deletion.
Clinical PHI: Retained for 10 years or as required by national health law.
De-identified research data: Retained indefinitely unless restricted by DUA.
Usage logs: Security logs are kept for 12 months; full IP logs for 30 days.
Support/marketing records: Retained for 3 years or until unsubscribed.
Backups are retained for 35 days before secure deletion.
10 Your Rights
10 Your Rights
10 Your Rights
Depending on your jurisdiction, you may request:
Access to personal data
Correction of inaccuracies
Erasure (under lawful grounds)
Restriction or objection to processing
Data portability in machine-readable format
Withdrawal of consent (where applicable)
Radii will verify your identity via two-factor checks or institutional authentication before fulfilling PHI-related requests.
Depending on your jurisdiction, you may request:
Access to personal data
Correction of inaccuracies
Erasure (under lawful grounds)
Restriction or objection to processing
Data portability in machine-readable format
Withdrawal of consent (where applicable)
Radii will verify your identity via two-factor checks or institutional authentication before fulfilling PHI-related requests.
Depending on your jurisdiction, you may request:
Access to personal data
Correction of inaccuracies
Erasure (under lawful grounds)
Restriction or objection to processing
Data portability in machine-readable format
Withdrawal of consent (where applicable)
Radii will verify your identity via two-factor checks or institutional authentication before fulfilling PHI-related requests.
10.1 How to Exercise Your Rights
9 Intellectual Property, Data Ownership &
Licensing
10.1 How to Exercise Your Rights
Patients: Contact your healthcare provider or email team@radiihealth.com with proof of identity.
Researchers or others: Contact your institutional lead or email team@radiihealth.com.
We aim to respond within 30 days (NDPA/GDPR) or 45 days (HIPAA/CCPA).
Patients: Contact your healthcare provider or email team@radiihealth.com with proof of identity.
Researchers or others: Contact your institutional lead or email team@radiihealth.com.
We aim to respond within 30 days (NDPA/GDPR) or 45 days (HIPAA/CCPA).
Patients: Contact your healthcare provider or email team@radiihealth.com with proof of identity.
Researchers or others: Contact your institutional lead or email team@radiihealth.com.
We aim to respond within 30 days (NDPA/GDPR) or 45 days (HIPAA/CCPA).
11 Data Breach Notification
11 Data Breach Notification
11 Data Breach Notification
In the event of a breach:
Investigation begins within 4 hours
Regulatory notification within 72 hours
Institutional notification within 48 hours
Affected individuals notified within 96 hours, if high-risk
Kenya’s 72-hour rule and other regional breach laws are observed. Evidence is retained for 18 months.
In the event of a breach:
Investigation begins within 4 hours
Regulatory notification within 72 hours
Institutional notification within 48 hours
Affected individuals notified within 96 hours, if high-risk
Kenya’s 72-hour rule and other regional breach laws are observed. Evidence is retained for 18 months.
In the event of a breach:
Investigation begins within 4 hours
Regulatory notification within 72 hours
Institutional notification within 48 hours
Affected individuals notified within 96 hours, if high-risk
Kenya’s 72-hour rule and other regional breach laws are observed. Evidence is retained for 18 months.
12 Changes to This Policy
12 Changes to This Policy
12 Changes to This Policy
We may revise this Privacy Policy periodically. Material changes will be communicated at least 30 days in advance. This page’s “Last Updated” date will also change.
We may revise this Privacy Policy periodically. Material changes will be communicated at least 30 days in advance. This page’s “Last Updated” date will also change.
We may revise this Privacy Policy periodically. Material changes will be communicated at least 30 days in advance. This page’s “Last Updated” date will also change.
13 Contact Us
13 Contact Us
13 Contact Us
Data Protection and Privacy Inquiries: team@radiihealth.com
Data Protection and Privacy Inquiries: team@radiihealth.com
Data Protection and Privacy Inquiries: team@radiihealth.com
Quick Reference: African Jurisdictions
Quick Reference: African Jurisdictions
Quick Reference: African Jurisdictions
Nigeria (NDPA 2023): 30-day window; local DPO appointed (Abuja)
Kenya (DPA 2019): 30-day window; local DPO appointed (Nairobi)
South Africa (POPIA): ≤30-day response; onshore processing enforced
Côte d’Ivoire (Law 2013-450): 1-month window; local representative (Abidjan)
Uganda (DP Act 2019): 30-day window; TBD local representative
Malabo Convention states: Case-by-case alignment
Nigeria (NDPA 2023): 30-day window; local DPO appointed (Abuja)
Kenya (DPA 2019): 30-day window; local DPO appointed (Nairobi)
South Africa (POPIA): ≤30-day response; onshore processing enforced
Côte d’Ivoire (Law 2013-450): 1-month window; local representative (Abidjan)
Uganda (DP Act 2019): 30-day window; TBD local representative
Malabo Convention states: Case-by-case alignment
Nigeria (NDPA 2023): 30-day window; local DPO appointed (Abuja)
Kenya (DPA 2019): 30-day window; local DPO appointed (Nairobi)
South Africa (POPIA): ≤30-day response; onshore processing enforced
Côte d’Ivoire (Law 2013-450): 1-month window; local representative (Abidjan)
Uganda (DP Act 2019): 30-day window; TBD local representative
Malabo Convention states: Case-by-case alignment
[ 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.