The Model Cards framework specifies that documentation should include intended uses, out-of-scope uses, potential biases and limitations, training data descriptions, and model architecture details. These fields are part of the recommended model card structure published by Hugging Face.
This analysis describes what Hugging Face's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes the disclosure fields that constitute a complete model card under the Hugging Face framework, which downstream users, auditors, and regulators may reference when assessing model suitability, compliance with responsible AI standards, or conformance with AI transparency regulations.
Interpretive note: The document describes these fields as recommended components of the model card structure but does not clearly state whether all fields are mandatory for Hub-hosted models, creating ambiguity about baseline disclosure requirements.
Provision was consolidated into a single field combining intended use, limitations, bias disclosure, and training information with expanded scope to include model architecture details.
View full change record →This provision establishes that users accessing models on the Hub can reference intended use, out-of-scope use, and limitations fields to evaluate whether a model is appropriate for their application. The agreement recommends these disclosures but the document does not state they are mandatory for all models on the platform.
How other platforms handle this
We will make it clear by notice to you which (if any) goods or services, or website links, we receive a benefit from by featuring them on our Platform.
In certain situations, Glassdoor may be required to disclose personal data in response to lawful requests by public authorities, including to meet national security or law enforcement requirements.
Customer must report upon NVIDIA's email request, no more than monthly, the Software in use by Customer Personnel and Customer End Users Customer enabled, quantity, start and end dates, and any other reasonably required information...
"Model cards should describe: Intended uses and out-of-scope uses. Potential biases and limitations. How the model was trained, including the training data and evaluation. Model architecture and parameters.Excerpt from Hugging Face's Model Card Guidelines
(1) REGULATORY LANDSCAPE: The intended use, out-of-scope use, and limitations disclosure fields described here directly engage EU AI Act technical documentation requirements for AI systems, particularly those in high-risk categories.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision establishes the disclosure fields that constitute a complete model card under the Hugging Face framework, which downstream users, auditors, and regulators may reference when assessing model suitability, compliance with responsible AI standards, or conformance with AI transparency regulations.
This provision establishes that users accessing models on the Hub can reference intended use, out-of-scope use, and limitations fields to evaluate whether a model is appropriate for their application. The agreement recommends these disclosures but the document does not state they are mandatory for all models on the platform.
ConductAtlas has identified this type of provision across 273 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Hugging Face.