Captured before automated identity checks (Oct 14, 2026): accurate as of its capture on Oct 14, 2026; our capture on Oct 21, 2026 found the same text, but its identity was not checked by them.
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
This page describes what the document states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability may vary by jurisdiction. Methodology
This document describes the safety testing Google conducted before releasing Gemini 3.1 Pro and the rules governing how it can be accessed and used. It confirms the model passed child safety launch thresholds, but active safety mitigations for chemical/biological/radiological/nuclear and cybersecurity risks are still being deployed. The actual rules about what users can and cannot do with the model are not here — they are in a separate document called the Gemini 3 Pro model card.
This model card establishes the frontier safety evaluation framework and deployment status of Google Gemini's Gemini 3.1 Pro model. It sets out that acceptable use terms and safety policies are governed by the Gemini 3 Pro model card, a separate document, while AI Studio and Gemini API access is subject to the Gemini API Additional Terms of Service, and Vertex AI access is subject to the Google Cloud Platform Terms of Service. The card establishes that Gemini 3.1 Pro underwent additional cyber-domain testing because its predecessor, Gemini 3 Pro, had previously reached the alert threshold, and that ongoing mitigations remain active in both the CBRN and cyber domains. The operative safety measure is a 'safety buffer' framework under which a model that does not reach the alert threshold for a critical capability level is considered to carry an acceptable safety profile, with evaluation conducted on a fixed cadence and upon detection of significant capability jumps.
For an individual user, this document establishes that Gemini 3.1 Pro cleared defined child safety thresholds before launch, that safety mitigations in the CBRN and cyber domains are ongoing rather than finalized, and that the rules governing permitted and prohibited uses are set out in the Gemini 3 Pro model card rather than in this document. Users who want to understand what they are and are not allowed to do with the model must consult that separate document. Users accessing the model through AI Studio or the Gemini API must additionally review the Gemini API Additional Terms of Service, and those using Vertex AI must review the Google Cloud Platform Terms of Service.
Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.
1 important change detected
7 versions captured · Latest change detected by ConductAtlas: October 2026
We withheld clauses we had published from this document. Each withholding is recorded in our correction log:
Every distinct legal provision identified in this document. Featured provisions appear above with analysis.
Google Gemini has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.
Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.
Cross-platform context
See how other platforms handle Acceptable Usage Governed by Gemini 3 Pro Card and similar clauses.
Compare across platforms →Governance Monitoring
Structured alerts for policy changes, governance events, and provision updates across 343 platforms.