Uwazi

Uwazi is a web-based database application designed for human rights defenders to manage collections of information, including documents, evidence, cases and complaints.

Website: https://huridocs.org/technology/uwazi/

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?

  • 16. Peace and Justice Strong Institutions

    Evidence: We collaborate with local activist groups, national human rights institutions, large international NGOs and many organisations in between. Some of our partners specialise in specific issues such as arbitrary arrest, freedom of expression, historical memory, and transitional justice, while others focus on human rights-related mechanisms such as the United Nations Human Rights Treaty System. Beyond their shared commitment to dignity and freedom, our partners have an important thing in common: they achieve greater impact when the information they need is easy to access, navigate and understand.

    Link to Evidence: https://huridocs.org/initiatives/developing-uwazi-a-human-rights-database-tool/

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://uwazi.io/en/page/w4feakb1j3p/about

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:

Uwazi has an import and export functionality for CSV files. It also has an API.

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:

  • GDPR

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):

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)

No

Which standards does this project support (please list)

  • HTML
  • CSS
  • JSON
  • JavaScript
  • REST API

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)

  • Design With the User
  • Understand the Existing Ecosystem
  • Design for Scale
  • Build for Sustainability
  • Be Data Driven
  • Use Open Standards, Open Data, Open Source, and Open Innovation
  • Reuse and Improve
  • Address Privacy & Security
  • Be Collaborative
  • Agile Principles
  • Automated Testing

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?

Internal security review of all code and regular 3rd party security audits.

9.a. Data Privacy & Security

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

Yes

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

  • Uwazi only uses cookies for users that log in into the platform, for example, to upload content into the instance.
  • We might also use third party cookies, on the request of a partner, for example, Google Analytics.
  • We collect IP address information for security reasons and statistical analysis of the traffic, and keep an access log during 3 months.
  • Uwazi is often used to record and manage information about human rights violations, but this information is accessible only to the organisations managing a respective collection.

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

Yes

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

  • Hosting and processing: the HURIDOCS Websites and HURIDOCS Applications/Tools are hosted by third party service providers and therefore any personal details you submit through a HURIDOCS Website and/or HURIDOCS Applications/Tools may be processed by that third party service provider. We may also use other third parties to process your personal details. For example, such third parties may process your personal information to process donations to HURIDOCS on our behalf or process and forward mailing information for users to sign up to our online actions and/or choose to subscribe to our email updates. All of these third party services providers will process your personal information only on HURIDOCS’ behalf and will be bound by strict confidentiality conditions. Link: https://huridocs.org/privacy-policy/

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:

Uwazi only uses cookies for users that log in into the platform, for example, to upload content into the instance. We might also use third party cookies, on the request of a partner, for example, Google Analytics. We collect IP address information for security reasons and statistical analysis of the traffic, and keep an access log during 3 months. For more details visit the Cookies Policy - https://huridocs.org/cookies-policy/

9.b. Inappropriate & Illegal Content

Does this project collect, store or distribute content?

Yes

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

Human rights documentation (information on human rights violations, general human rights information, legal documents, court cases, academic resources, legal resources, photos, audio files, videos and other information that users see fit to upload to their collections.

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

No

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?

Yes

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):

Since we work with human rights organisations, we anticipate that this is taken care of by selecting who we work with.

9.c. Protection from harassment

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

Yes

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

Yes

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

  • We have provided an email address for reporting abuse, harassment or improper conduct. This goes directly to our Chief Technology Officer and Director of Programmes, who will review and investigate any issues further.

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

Yes

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

Development & deployment countries

List of countries this project was developed in.

  • Argentina
  • Costa Rica
  • Egypt
  • Ecuador
  • El Salvador
  • France
  • Hungary
  • India
  • Italy
  • Kenya
  • Mexico
  • Nepal
  • Senegal
  • South Africa
  • Spain
  • Sri Lanka
  • Switzerland
  • Turkey
  • United States of America
  • Uruguay
  • Poland

List of countries this project is actively deployed in.

  • Argentina
  • Bangladesh
  • Bolivia
  • Egypt
  • France
  • Gambia
  • Germany
  • India
  • Iran
  • Kenya
  • Lebanon
  • Libya
  • Malaysia
  • Mexico
  • Myanmar
  • Nigeria
  • North Korea
  • Palestine State
  • Peru
  • Russia
  • South Africa
  • South Korea
  • Sri Lanka
  • Switzerland
  • Syria
  • Thailand
  • Turkey
  • United Kingdom
  • Uganda
  • Ukraine
  • Uzbekistan
  • Vietnam
  • Yemen
  • Zimbabwe