Data Hazard labels#
This page contains the Data Hazard labels themselves. These labels, descriptions, examples, and safety precautions will evolve as we develop the hazard labels with the communities who will use them. We welcome you to suggest changes, so please check our contribution guidelines if you would like to.
You can download a printable set of Data Hazards cards here.
Each hazard has:
Hazard image, title, and description which represents and describes the risk.
Examples to clarify what the hazard covers.
Safety Precautions - things that we would want to see done before the research is deployed.
They are designed to help us think about the different types of hazards.
We also collect a series of mitigation resources and tools (scroll down) to help apply the safety precautions to your project.
Reinforces Existing Biases
Reinforces unfair treatment of individuals and groups. This may be due to for example input data, algorithm or software design choices, or society at large.
Note: this is a hazard in it’s own right, even if it isn’t then used to harm people directly, due to e.g. reinforcing stereotypes.
Ranks Or Classifies People
Ranking and classifications of people are hazards in their own right and should be handled with care.
To see why, we can think about what happens when the ranking/classification is inaccurate, when people disagree with how they are ranked/classified, as well as who the ranking/classification is and is not working for, how it can be gamed, and what it is used to justify or explain.
Difficult To Understand
There is a danger that the technology is difficult to understand. This could be because of the technology itself is hard to interpret (e.g. neural nets), or problems with it’s implementation (i.e. code is not provided, or not documented).
Depending on the circumstances of its use, this could mean that incorrect results are hard to identify, or that the technology is inaccessible to people (difficult to implement or use).
Automates Decision Making
Automated decision making can be hazardous for a number of reasons, and these will be highly dependent on the field in which it is being applied. We should ask ourselves whose decisions are being automated, what automation can bring to the process, and who is benefitted/harmed from this automation.