The document explicitly defers disclosure of known limitations, acceptable usage policies, risks and mitigations, training data, training data processing, hardware details, ethics evaluation approach, and safety policies to the Gemini 3 Pro model card rather than reproducing them in this document.
This analysis describes what Google Gemini'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 a layered disclosure structure where a complete governance picture for Gemini 3.1 Pro requires review of at least two separate documents: this model card and the Gemini 3 Pro model card. Compliance teams conducting vendor assessments or regulatory documentation cannot rely on this document alone to satisfy disclosure review requirements.
Under this structure, users and deployers seeking information about known limitations, acceptable usage, training data, and risk mitigations for Gemini 3.1 Pro are directed to the Gemini 3 Pro model card rather than finding that information in this document. This means that a complete understanding of the model's governance disclosures requires accessing and reviewing the prior model's documentation.
Cross-platform context
See how other platforms handle Cross-Referenced Disclosure Structure and similar clauses.
Compare across platforms →"For more information about the known limitations for Gemini 3.1 Pro, see the Gemini 3 Pro model card. Acceptable Usage: For more information about the acceptable usage for Gemini 3.1 Pro, see the Gemini 3 Pro model card. For more information about the risks and mitigations for Gemini 3.1 Pro, see the Gemini 3 Pro model card.Excerpt from Google Gemini's Gemini 3.1 Pro Model Card
(1) REGULATORY LANDSCAPE: The cross-referenced disclosure structure may engage EU AI Act requirements for technical documentation of general-purpose AI models, which specify that documentation should be sufficiently detailed for competent authorities to assess compliance.
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 a layered disclosure structure where a complete governance picture for Gemini 3.1 Pro requires review of at least two separate documents: this model card and the Gemini 3 Pro model card. Compliance teams conducting vendor assessments or regulatory documentation cannot rely on this document alone to satisfy disclosure review requirements.
Under this structure, users and deployers seeking information about known limitations, acceptable usage, training data, and risk mitigations for Gemini 3.1 Pro are directed to the Gemini 3 Pro model card rather than finding that information in this document. This means that a complete understanding of the model's governance disclosures requires accessing and reviewing the prior model's documentation.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Google Gemini.