Help Center/Dataset cards/Responsible AI

Responsible AI

Responsible AI is about building models that are fair, safe, transparent, and compliant. A model is only as good as the data it learns from, so a lot of responsible-AI work starts at the dataset: if the data is biased, unrepresentative, or carries legal or privacy problems, those issues get baked into your model and surface later as unfair outcomes, compliance gaps, or reputational risk.

The Responsible AI tab surfaces those considerations up front, so you can make an informed choice before a dataset ever reaches training. Instead of discovering a problem after deployment, you see the known risks while you're still evaluating candidates.

What the tab shows

  • Known biases — biases documented or discussed for this dataset, such as skew toward certain groups, classes, or conditions that could make a model treat some inputs unfairly
  • Cultural diversity — representation gaps, for example data drawn from a single region, language, or demographic, which limits how well a model generalizes
  • Known limitations — documented constraints the community has raised, such as label noise, collection artifacts, or narrow coverage
  • Ethical concerns — concerns raised online or in published discussion, including how the data was collected and whether consent or sourcing is in question

Why it matters

Regulations like the EU AI Act increasingly expect teams to understand and document the data behind their models, especially for higher-risk use cases. Reviewing this tab helps you:

  • Catch bias early, before it becomes unfair model behaviour in production
  • Judge fit for your specific users and regions
  • Document your due diligence for compliance and governance
  • Decide whether to enrich or rebalance the data (see the How to enrich tab)
Always review this tab before training on a dataset for a production or regulated use case. Bias, PII, and licence terms can affect whether a dataset is safe and compliant for your application. These signals are drawn from public documentation and community discussion, so treat them as a starting point for your own review, not a guarantee.