Connect
Sign up to receive our monthly newsletter.
Inquiries
Have a question? Contact us here.
Job Opportunities
Learn about job openings.
Digital Public Goods Alliance - 2026
Sign up to receive our monthly newsletter.
Have a question? Contact us here.
Learn about job openings.
Open Child Helpline System
OpenCHS is an open-source, multilingual helpline & case management platform that supports governments and NGOs to deliver 24/7 protection, counseling, and referral services, with AI-powered insights for child protection and social services.
Owner
BITZ IT CONSULTING
Type
backend, API, web
Licence
GPL-3.0
Last evaluated
28.04.2026
Origin country
Kenya
contact
info@bitz-itc.comRelease date
-
DPG since
28.04.2026
The following repositories were submitted by the solution and included in our evaluation. Any repositories, add-ons, features not included in here were not reviewed by us.
N/A
UNICEF Venture Funds
Swahili, English, Luganda
N/A
* This information is self-reported and updated annually
SDG 3: Good Health and Well-being OpenCHS supports timely mental health and psychosocial support (Target 3.4) and ensures survivors of violence receive referrals to medical services (Target 3.8). By offering 24/7 counseling and referral workflows, it strengthens access to health and protection services. SDG 16: Peace, Justice and Strong Institutions OpenCHS strengthens institutions by building accountable child protection and GBV response systems (Target 16.3). It promotes inclusive societies by providing safe reporting channels, transparent case handling, and data for evidence-based policy (Target 16.6).
There's a WhatsApp, Whisper, and HuggingFace API for optional use, but well encapsulated for replacement. These are extra features and not core.
Yes
Principles for Digital Development, Privacy by Design, Agile, CI/CD, Code Review
PII data is collected and stored but NOT distributed.
The OpenCHS system is designed with privacy-by-design principles, implementing multiple layers of PII protection, including anonymization, pseudonymization, and strict access controls. The system only collects essential PII for child protection purposes and provides robust mechanisms for data deletion and user rights enforcement. All PII processing is logged and auditable to ensure compliance with GDPR,the Kenya Data Protection Act, and the Uganda Data Protection and Privacy Act. Multi-factor authentication for system access, AES-256 encryption for data at rest and in transit, Comprehensive audit logging of all data access.
Content is collected and stored but NOT distributed.
1. Policies for Identifying Inappropriate and Illegal Content OPENCHS strictly prohibits the storage, sharing, or reproduction of illegal content, including but not limited to: Child Sexual Abuse Materials (CSAM) Images or threats of violence Sexual exploitation content Hate speech and incitement to harm Our Content Management Policy includes clear definitions and red flags for illegal and inappropriate content based on: National child protection and cybersecurity laws (e.g., Kenya's Computer Misuse and Cybercrimes Act) International standards such as those from INTERPOL, UNICEF, and Child Helpline International All staff and contributors undergo training on content sensitivity, legal obligations, and mandatory reporting procedures. 2. Mechanisms for Detecting, Moderating, Reporting, and Removing Content a. AI-Assisted Detection OPENCHS integrates AI tools to automatically flag: Inappropriate language or graphic descriptions during voice and text interactions Keywords commonly associated with abuse, threats, or exploitation b. Human Moderation Flagged content is reviewed in real time or retrospectively by trained moderators and safeguarding officers. Sensitive cases are escalated to child protection agencies where necessary. c. Reporting Pathways If illegal content is detected (e.g., CSAM), our protocols mandate: Immediate reporting to national child protection and law enforcement agencies Secure documentation and evidence handling, in compliance with legal and ethical standards d. Removal and Access Restriction Content found to be illegal or harmful is: Immediately quarantined from public view Permanently deleted once reported and processed Accessed only by authorized personnel under strict logging and auditing e. Audit and Continuous Review Regular audits are conducted to ensure: No unauthorized content access or distribution Policies are updated in line with emerging threats and legal obligations
Yes
OPENCHS is deeply committed to creating a safe, respectful, and secure environment for both contributors and users—particularly underage users who are central to our mission. We achieve this through a combination of clearly articulated policies, well-defined reporting processes, and child-focused safety protocols embedded within our system design. 1. Policies and Processes for Contributor and User Protection a. Contributor Code of Conduct We maintain a publicly accessible Contributor Code of Conduct based on the Contributor Covenant v2.1, which applies to all contributors, maintainers, and users engaging with our platform and its associated development communities. The Code outlines: A clear pledge to foster a welcoming, inclusive, and harassment-free space Acceptable and unacceptable behaviors Clear enforcement protocols Reports of harassment can be made confidentially to codeofconduct@openchs.com, where all concerns are reviewed and handled promptly by the core maintainer team. b. Inclusive Community Practices We actively promote positive collaboration by: Encouraging respectful dialogue and empathy Conducting onboarding for new contributors to clarify behavior expectations Using moderation tools and proactive monitoring on platforms like GitHub and community forums c. Privacy and Safety Controls We enforce robust data protection standards: Anonymous contributions are allowed where possible Personally identifiable information (PII) is safeguarded with strict access controls Contributor communication is secured and monitored for compliance with our code of conduct 2. Processes That Address the Safety and Security of Underage Users a. Safeguarding-First Design As a child helpline solution, OPENCHS embeds child protection into every layer of its technology and operations. Our approach aligns with child protection policies from UNICEF and Child Helpline International. Key measures include: End-to-end encryption of communications Mandatory child safeguarding training for all frontline helpline staff AI tools that monitor for signs of abuse or distress in real-time conversations b. Anonymous and Confidential Access Children using the system are not required to disclose their identity. They receive services anonymously, and any collected data is minimized, anonymized, and encrypted. Parental consent is not required for accessing support in emergencies, in line with child protection best practices. c. Escalation Pathways and Support Services When disclosures of abuse occur, OPENCHS enables: Immediate triage and routing to verified child protection services Collaboration with law enforcement or social workers when needed Secure documentation of cases for follow-up while preserving confidentiality d. Role-Based Access and Audit Trails Only vetted personnel have access to sensitive child data. All access and activity are logged, with regular audits to detect misuse or policy violations. e. AI Safety and Ethical Guardrails Our AI models (used in triage and voice transcription) are trained with strict ethical constraints and are regularly tested for fairness and bias. We incorporate human-in-the-loop mechanisms to ensure that AI decisions are reviewed by trained professionals before triggering escalations. https://github.com/openchlai/ai/blob/main/CODE_OF_CONDUCT.md
2026-04-28 15:29:19
Ricardo Torres (L2 Reviewer) submitted their review of OpenCHS (152) and found it to be a DPG
2026-04-28 15:29:18
System unmarked OpenCHS (12891) as a nominee
2026-04-28 15:29:10
Ricardo Torres (L2 Reviewer) passed 4. Platform Independence for OpenCHS (12891)
2026-04-28 15:28:41
Ricardo Torres (L2 Reviewer) passed General Information for OpenCHS (12891)
2026-04-28 15:28:39
Ricardo Torres (L2 Reviewer) edited General Information for OpenCHS (12891)
2026-04-28 15:25:37
Ricardo Torres (L2 Reviewer) pulled OpenCHS (12891) under review
2026-04-17 15:58:20
Bolaji Ayodeji (L1 Reviewer) submitted their review of OpenCHS (12891)
2026-04-17 15:57:03
Bolaji Ayodeji (L1 Reviewer) passed 9A. Data Privacy & Security for OpenCHS (12891)
2026-04-17 15:56:46
Bolaji Ayodeji (L1 Reviewer) passed 4. Platform Independence for OpenCHS (12891)
2026-04-17 15:55:17
Bolaji Ayodeji (L1 Reviewer) passed General Information for OpenCHS (12891)
2026-04-17 15:55:13
Bolaji Ayodeji (L1 Reviewer) edited General Information for OpenCHS (12891)
2026-04-17 15:52:46
Bolaji Ayodeji (L1 Reviewer) pulled OpenCHS (12891) under review
2026-04-08 18:25:09
New tag (Clarifications) added to application
2026-04-08 18:25:09
Application clarifications submitted, Application move to L1 for review again
2026-03-24 15:53:40
Ricardo Torres (L2 Reviewer) requested clarifications for OpenCHS (12891)
2026-03-24 15:53:39
System marked OpenCHS (12891) as a nominee
2026-03-24 15:53:30
Ricardo Torres (L2 Reviewer) require clarification on 4. Platform Independence for OpenCHS (12891)
2026-03-24 15:51:56
Ricardo Torres (L2 Reviewer) require clarification on General Information for OpenCHS (12891)
2026-03-24 15:10:35
Ricardo Torres (L2 Reviewer) moved OpenCHS (12891) to under review
2026-03-24 15:09:36
Ricardo Torres (L2 Reviewer) finished consultation on 4. Platform Independence for OpenCHS (12891)
2026-03-24 10:08:21
Ivan Perdomo (Expert) submitted their inputs on 4. Platform Independence for OpenCHS (12891) as “input”
2026-03-24 02:59:39
Ricardo Torres (L2 Reviewer) requested consultation on 4. Platform Independence for OpenCHS (12891)
2026-03-24 02:59:27
Ricardo Torres (L2 Reviewer) moved OpenCHS (12891) to under consultation
2026-03-24 02:59:21
Ricardo Torres (L2 Reviewer) passed Scale of Solution for OpenCHS (12891)
2026-03-24 02:59:16
Ricardo Torres (L2 Reviewer) passed 9C. Protection from Harassment for OpenCHS (12891)
2026-03-24 02:59:06
Ricardo Torres (L2 Reviewer) passed 9B. Inappropriate & Illegal Content for OpenCHS (12891)
2026-03-24 02:58:54
Ricardo Torres (L2 Reviewer) edited a note on 9A. Data Privacy & Security for OpenCHS (12891)
2026-03-24 02:58:39
Ricardo Torres (L2 Reviewer) passed 9A. Data Privacy & Security for OpenCHS (12891)
2026-03-24 02:58:37
Ricardo Torres (L2 Reviewer) edited 9A. Data Privacy & Security for OpenCHS (12891)
2026-03-24 02:50:38
Ricardo Torres (L2 Reviewer) passed 8. Standards & Best Practices for OpenCHS (12891)
2026-03-24 02:50:33
Ricardo Torres (L2 Reviewer) passed 7. Privacy & Applicable Laws for OpenCHS (12891)
2026-03-24 02:50:31
Ricardo Torres (L2 Reviewer) edited a note on 7. Privacy & Applicable Laws for OpenCHS (12891)
2026-03-24 02:49:32
Ricardo Torres (L2 Reviewer) edited General Information for OpenCHS (12891)
2026-03-24 02:49:15
Ricardo Torres (L2 Reviewer) passed 6. Mechanism for Extracting Data for OpenCHS (12891)
2026-03-24 02:47:52
Ricardo Torres (L2 Reviewer) passed 5. Documentation for OpenCHS (12891)
2026-03-24 02:47:51
Ricardo Torres (L2 Reviewer) edited a note on 5. Documentation for OpenCHS (12891)
2026-03-24 02:47:44
Ricardo Torres (L2 Reviewer) edited 5. Documentation for OpenCHS (12891)
2026-03-24 02:44:32
Ricardo Torres (L2 Reviewer) edited a note on 4. Platform Independence for OpenCHS (12891)
2026-03-24 02:38:26
Ricardo Torres (L2 Reviewer) edited a note on General Information for OpenCHS (12891)
2026-03-24 02:37:00
Ricardo Torres (L2 Reviewer) edited 4. Platform Independence for OpenCHS (12891)
2026-03-24 02:30:00
Ricardo Torres (L2 Reviewer) passed 3. Clear Ownership for OpenCHS (12891)
2026-03-24 02:29:55
Ricardo Torres (L2 Reviewer) edited a note on 2. Open Licensing for OpenCHS (12891)
2026-03-24 02:29:38
Ricardo Torres (L2 Reviewer) passed 2. Open Licensing for OpenCHS (12891)
2026-03-24 02:28:28
Ricardo Torres (L2 Reviewer) passed 1. SDG Relevance for OpenCHS (12891)
2026-03-24 02:28:01
Ricardo Torres (L2 Reviewer) edited a note on General Information for OpenCHS (12891)
2026-03-24 02:26:33
Ricardo Torres (L2 Reviewer) edited a note on General Information for OpenCHS (12891)
2026-03-24 02:18:42
Ricardo Torres (L2 Reviewer) pulled OpenCHS (12891) under review
2026-02-18 12:17:19
System remove tag Late from OpenCHS (12891)
2026-02-18 12:17:19
Bolaji Ayodeji (L1 Reviewer) submitted their review of OpenCHS (12891)
2026-02-18 12:17:06
Bolaji Ayodeji (L1 Reviewer) passed Scale of Solution for OpenCHS (12891)
2026-02-18 12:17:02
Bolaji Ayodeji (L1 Reviewer) passed 9C. Protection from Harassment for OpenCHS (12891)
2026-02-18 12:17:00
Bolaji Ayodeji (L1 Reviewer) edited 9C. Protection from Harassment for OpenCHS (12891)
2026-02-18 12:16:37
Bolaji Ayodeji (L1 Reviewer) passed 9B. Inappropriate & Illegal Content for OpenCHS (12891)
2026-02-18 12:16:10
Bolaji Ayodeji (L1 Reviewer) failed 9A. Data Privacy & Security for OpenCHS (12891)
2026-02-18 12:14:13
Bolaji Ayodeji (L1 Reviewer) edited a note on 4. Platform Independence for OpenCHS (12891)
2026-02-18 12:12:36
Bolaji Ayodeji (L1 Reviewer) passed 8. Standards & Best Practices for OpenCHS (12891)
2026-02-18 12:12:02
Bolaji Ayodeji (L1 Reviewer) edited 5. Documentation for OpenCHS (12891)
2026-02-18 12:10:28
Bolaji Ayodeji (L1 Reviewer) edited a note on 4. Platform Independence for OpenCHS (12891)
2026-02-18 12:10:09
Bolaji Ayodeji (L1 Reviewer) passed 7. Privacy & Applicable Laws for OpenCHS (12891)
2026-02-18 12:09:13
Bolaji Ayodeji (L1 Reviewer) edited 7. Privacy & Applicable Laws for OpenCHS (12891)
2026-02-18 12:05:07
Bolaji Ayodeji (L1 Reviewer) passed 6. Mechanism for Extracting Data for OpenCHS (12891)
2026-02-18 12:04:55
Bolaji Ayodeji (L1 Reviewer) passed 5. Documentation for OpenCHS (12891)
2026-02-18 12:04:54
Bolaji Ayodeji (L1 Reviewer) edited a note on 5. Documentation for OpenCHS (12891)
2026-02-18 12:04:23
Bolaji Ayodeji (L1 Reviewer) edited 5. Documentation for OpenCHS (12891)
2026-02-18 12:00:46
Bolaji Ayodeji (L1 Reviewer) passed 4. Platform Independence for OpenCHS (12891)
2026-02-18 12:00:44
Bolaji Ayodeji (L1 Reviewer) edited a note on 4. Platform Independence for OpenCHS (12891)
2026-02-18 11:57:14
Bolaji Ayodeji (L1 Reviewer) edited a note on 4. Platform Independence for OpenCHS (12891)
2026-02-11 16:00:02
System add new tag Late to OpenCHS (12891)
2026-02-11 07:11:10
Bolaji Ayodeji (L1 Reviewer) passed 3. Clear Ownership for OpenCHS (12891)
2026-02-11 07:11:05
Bolaji Ayodeji (L1 Reviewer) passed 2. Open Licensing for OpenCHS (12891)
2026-02-11 07:11:03
Bolaji Ayodeji (L1 Reviewer) edited a note on 2. Open Licensing for OpenCHS (12891)
2026-02-11 07:10:47
Bolaji Ayodeji (L1 Reviewer) edited 2. Open Licensing for OpenCHS (12891)
2026-02-11 07:09:31
Bolaji Ayodeji (L1 Reviewer) passed 1. SDG Relevance for OpenCHS (12891)
2026-02-11 07:09:24
Bolaji Ayodeji (L1 Reviewer) edited 1. SDG Relevance for OpenCHS (12891)
2026-02-11 07:09:16
Bolaji Ayodeji (L1 Reviewer) edited a note on 1. SDG Relevance for OpenCHS (12891)
2026-02-11 07:08:57
Bolaji Ayodeji (L1 Reviewer) passed General Information for OpenCHS (12891)
2026-02-11 07:08:55
Bolaji Ayodeji (L1 Reviewer) edited General Information for OpenCHS (12891)
2026-02-11 07:05:25
Bolaji Ayodeji (L1 Reviewer) pulled OpenCHS (12891) under review
2025-10-09 00:55:12
Mercy Kamau (Applicant) submitted application for OpenCHS (12891)
