Sunbird UCI

Sunbird UCI (Unified Communications Interface) is an open-source configurable platform to enable multi-channel, personalised chatbot conversations and nudges across various channels such as WhatsApp, Telegram, SMS, email, etc. for governance use cases.

Website: https://uci.sunbird.org

Type of Digital Public Good

  • Open content
  • Open data
  • ✅  Open software
  • Open standard
  • Open AI model

1. Is it relevant to one of the Sustainable Development Goals?

  • 4. Quality Education

    Evidence: Ministry of Education (MoE), Government of India's DIKSHA Platform uses Sunbird UCI as a medium for states to configure interactive WhatsApp chatbot conversations for education use cases. The use cases range from academic quizzes and self-paced learning material distribution for students to academic surveys and forms used by teachers and administrators. Any user can go to the Diksha Tara Bot (+91 93102 00148), type the starting message and start using the bot.

    Link to Evidence: https://drive.google.com/file/d/1wp2QlcLae3plH9zmBQudFs5A0BZwJ-A4/view

  • 8. Decent Work and Economic Growth

    Evidence: The Employment Department, Government of Haryana leveraged Sunbird UCI to create a WhatsApp Bot (Rozgar Bot) for employment linkages. This bot enabled employers to post the job openings and interested candidates to apply for relevant job roles.

    Link to Evidence: https://drive.google.com/file/d/1UJ81Q7pknXjcSN4fiBCXnw8lOr-OIurC/view?usp=sharing

  • 9. Industry, Innovation and Infrastructure

    Evidence: UCI is a digital infrastructure that powers conversational use cases across domains such as education, healthcare delivery, agriculture, employment and skilling, local governance and service delivery et. al. Any adopter across these domains can use UCI to enable two key features: 1) Creation of a 2 way conversations for their end user 2) Direct notification/nudges to a targeted set of relevant end users.

    Link to Evidence: https://uci.sunbird.org/learn/uci-use-cases

2. Does it use an appropriate open license?

Yes, this project is licensed under the following license(s):

3. Is ownership clearly defined?

Is the ownership of the project and everything that the project produces clearly defined and documented?

Yes

If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.

https://uci.sunbird.org/engage/software-license

4. Does the license of libraries/dependencies undermine the openess of the project?

Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?

No

If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?

Not Applicable

If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:

Not Applicable

5. Is there documentation?

Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.

Yes

If yes - please link to the relevant documentation:

6. Is non PII data and/or content accessible?

Does this project collect or use non-personally identifiable information (non-PII) data and/or content?

Yes

If yes - is there a mechanism for extracting or importing non-personally identifiable information (non-PII) from the system in a non-proprietary format?

Yes

If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:

Data can be exported via the Admin console UI and the API in a variety of standard formats. The adopter of UCI can choose to create custom mechanisms to allow extraction of the data. For example, DIKSHA UCI has created its own APIs for data exhaust to allow access of data to authorised users only.

Mechanism is detailed here - https://uci.sunbird.org/use/adopter/data-exhaust-and-analytics

7. Does the project adhere to privacy and other applicable international and domestic laws?

Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)

Yes

If yes, please list some of relevant laws that the project complies with:

  • UCI does not store any PII for the users. The only potential PII that it can collect and store is the user phone number or any other digital address like email address. Additionally, the onus is on the UCI Implementer to manage/flush PII information as per requirement. UCI complies with the following relevant laws - India's Personal Data Protection Bill (2019), The IT Act (2000) for its implementation in India

If yes, please describe the steps this project has taken to ensure adherence (include links to terms of service, privacy policy, or other relevant documentation):

  • The adopter using UCI might decide to collect PII information and this is use case specific. We strongly recommend that applications do not collect this information if not required. We are in conversations with applications on what needs to be done to ensure that their install of UCI is GDPR compliant. This is similar to the ODK and Glific ecosystem, where the various SaaS providers of ODK enforce and implement GDPR compliance. Privacy policy: https://www.sunbird.org/privacy-policy and Terms & conditions: https://www.sunbird.org/terms-conditions

8. Does the project adhere to standards and best practices?

Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)

Yes

Which standards does this project support (please list)

  • OpenWeb Standard such as - HTML, CSS, ECMAScript, LaTeX
  • Standard Content Format such as PDF, MP4, WebM, H5P, ePub, and more
  • XForm Specification
  • Accessibility - WCAG, Internationalisation
  • Security - PKI, HTTPS, JWT

Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)

Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?

Yes

Which principles and best practices does this project support (please list)

9. Does the project do no harm by design?

Has this project taken steps to anticipate, prevent and do no harm by design?

On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?

Yes

Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?

Sunbird software has implemented many best practices to keep user data safe and secure. Users are empowered to safeguard and share their data with appropriate consent management mechanisms. Default software has implemented data collection in an open and transparent manner. Sunbird software implements principles of minimalism, consent, transparency of data collection, and other best practices. Please see earlier and following responses for details about privacy, and data security.

9.a. Data Privacy & Security

Does this project collect or store personally identifiable information (PII) data and/or content?

No

If yes - please list the types of data and/or content collected and/or stored by the project:

Not Applicable

If yes - does this project share this data and/or content with third parties?

No

Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.

Not Applicable

If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.

Yes

If yes - please describe the steps, and include a link to the privacy policy and/or terms of service:

UCI does not store any PII for the users. The only potential PII that it can collect and store is the user phone number or any other digital address like email address. Additionally, the onus is on the UCI Implementer to manage/flush PII information as per requirement. UCI complies with the following relevant laws - India's Personal Data Protection Bill (2019), The IT Act (2000) for its implementation in India

9.b. Inappropriate & Illegal Content

Does this project collect, store or distribute content?

No

If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)

Not Applicable

If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)

Not Applicable

If yes - please link to the relevant policy/guidelines/documentation.

Not Applicable

If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?

Not Applicable

If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):

Not Applicable

9.c. Protection from harassment

Does this project facilitate interactions with or between users or contributors?

No

If yes - does the project take steps to address the safety and security of underage users?

Not Applicable

If yes - please describe the steps this project takes to address risk or prevent access by underage users:

Not Applicable

If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?

Not Applicable

If yes - please describe the steps taken to help users protect themselves.

Not Applicable

Development & deployment countries

List of countries this project was developed in.

  • India

List of countries this project is actively deployed in.

  • India