What is "human data" and why is it important to source responsibly?

APPLIES TO: Python SDK azure-ai-ml v2 (current)

APPLIES TO: Azure CLI ml extension v2 (current)

Human data is data collected directly from, or about, people. Human data may include personal data such as names, age, images, or voice clips and sensitive data such as genetic data, biometric data, gender identity, religious beliefs, or political affiliations.

Collecting this data can be important to building AI systems that work for all users. But certain practices should be avoided, especially ones that can cause physical and psychological harm to data contributors.

The best practices in this article will help you conduct manual data collection projects from volunteers where everyone involved is treated with respect, and potential harms—especially those faced by vulnerable groups—are anticipated and mitigated. This means that:

  • People contributing data are not coerced or exploited in any way, and they have control over what personal data is collected.
  • People collecting and labeling data have adequate training.

These practices can also help ensure more-balanced and higher-quality datasets and better stewardship of human data.

These are emerging practices, and we are continually learning. The best practices below are a starting point as you begin your own responsible human data collections. These best practices are provided for informational purposes only and should not be treated as legal advice. All human data collections should undergo specific privacy and legal reviews.

General best practices

We suggest the following best practices for manually collecting human data directly from people.

Best Practice

Why?


Obtain voluntary informed consent.

  • Participants should understand and consent to data collection and how their data will be used.
  • Data should only be stored, processed, and used for purposes that are part of the original documented informed consent.
  • Consent documentation should be properly stored and associated with the collected data.

Compensate data contributors appropriately.

  • Data contributors should not be pressured or coerced into data collections and should be fairly compensated for their time and data.
  • Inappropriate compensation can be exploitative or coercive.

Let contributors self-identify demographic information.

  • Demographic information that is not self-reported by data contributors but assigned by data collectors may 1) result in inaccurate metadata and 2) be disrespectful to data contributors.

Anticipate harms when recruiting vulnerable groups.

  • Collecting data from vulnerable population groups introduces risk to data contributors and your organization.

Treat data contributors with respect.

  • Improper interactions with data contributors at any phase of the data collection can negatively impact data quality, as well as the overall data collection experience for data contributors and data collectors.

Qualify external suppliers carefully.

  • Data collections with unqualified suppliers may result in low quality data, poor data management, unprofessional practices, and potentially harmful outcomes for data contributors and data collectors (including violations of human rights).
  • Annotation or labeling work (e.g., audio transcription, image tagging) with unqualified suppliers may result in low quality or biased datasets, insecure data management, unprofessional practices, and potentially harmful outcomes for data contributors (including violations of human rights).

Communicate expectations clearly in the Statement of Work (SOW) (contracts or agreements) with suppliers.

  • A contract which lacks requirements for responsible data collection work may result in low-quality or poorly collected data.

Qualify geographies carefully.

  • When applicable, collecting data in areas of high geopolitical risk and/or unfamiliar geographies may result in unusable or low-quality data and may impact the safety of involved parties.

Be a good steward of your datasets.

  • Improper data management and poor documentation can result in data misuse.

Note

This article focuses on recommendations for human data, including personal data and sensitive data such as biometric data, health data, racial or ethnic data, data collected manually from the general public or company employees, as well as metadata relating to human characteristics, such as age, ancestry, and gender identity, that may be created via annotation or labeling.

Download the full recommendations here

Best practices for collecting age, ancestry, and gender identity

In order for AI systems to work well for everyone, the datasets used for training and evaluation should reflect the diversity of people who will use or be affected by those systems. In many cases, age, ancestry, and gender identity can help approximate the range of factors that might affect how well a product performs for a variety of people; however, collecting this information requires special consideration.

If you do collect this data, always let data contributors self-identify (choose their own responses) instead of having data collectors make assumptions, which might be incorrect. Also include a “prefer not to answer” option for each question. These practices will show respect for the data contributors and yield more balanced and higher-quality data.

These best practices have been developed based on three years of research with intended stakeholders and collaboration with many teams at Microsoft: fairness and inclusiveness working groups, Global Diversity & Inclusion, Global Readiness, Office of Responsible AI, and others.

To enable people to self-identify, consider using the following survey questions.

Age

How old are you?

Select your age range

[Include appropriate age ranges as defined by project purpose, geographical region, and guidance from domain experts]

  • # to #
  • # to #
  • # to #
  • Prefer not to answer

Ancestry

Please select the categories that best describe your ancestry

May select multiple

[Include appropriate categories as defined by project purpose, geographical region, and guidance from domain experts]

  • Ancestry group
  • Ancestry group
  • Ancestry group
  • Multiple (multiracial, mixed Ancestry)
  • Not listed, I describe myself as: _________________
  • Prefer not to answer

Gender identity

How do you identify?

May select multiple

[Include appropriate gender identities as defined by project purpose, geographical region, and guidance from domain experts]

  • Gender identity
  • Gender identity
  • Gender identity
  • Prefer to self-describe: _________________
  • Prefer not to answer

Caution

In some parts of the world, there are laws that criminalize specific gender categories, so it may be dangerous for data contributors to answer this question honestly. Always give people a way to opt out. And work with regional experts and attorneys to conduct a careful review of the laws and cultural norms of each place where you plan to collect data, and if needed, avoid asking this question entirely.

Download the full guidance here.

Next steps

For more information on how to work with your data:

Follow these how-to guides to work with your data after you've collected it: