132 Total
Stay ahead of the changes
Track Google Cloud and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Summary
Generated by a model from the captured document; not read by a person

This document sets out the rules for using Google Cloud services: you keep ownership of your data and applications, but Google Cloud can change its prices at any time unless you have a written agreement locking them in, and your obligation to pay cannot be cancelled. If you or your end users violate the acceptable use policy and don't fix it within 24 hours, Google Cloud can suspend your access; and if a third party sues over your data or applications, you are responsible for defending Google.

Analysis

The Google Cloud Terms establish the core rights, obligations, and limitations governing the customer's use of Google Cloud services. Google Cloud retains discretion to change Fees at any time absent a written lock in an addendum or Order Form, while the customer's obligation to pay all Fees is non-cancellable unless law requires otherwise. Customer Data and Customer Applications remain the intellectual property of the customer, and Google Cloud's access to and processing of Customer Data is strictly bounded by the Cloud Data Processing Addendum. The agreement allocates indemnification obligations bilaterally: the customer defends and indemnifies Google against third-party claims arising from Customer Data, applications, brand features, projects, or AUP breaches, while Google defends and indemnifies the customer against third-party intellectual property infringement claims concerning Google's own Services or Brand Features. Google Cloud disclaims all warranties to the fullest extent permitted by applicable law and reserves the right to suspend services upon an unresolved AUP violation within 24 hours, with a 12-month advance notice obligation before discontinuing any Service or material functionality.

What this means for you

As an individual user or customer, your data and applications remain yours, and Google Cloud is contractually limited to processing your data only as described in the Cloud Data Processing Addendum. However, your fee obligations cannot be cancelled, Google Cloud can change fees at any time without a written lock, and all warranties are disclaimed to the fullest extent the law allows. If Google Cloud's tools detect a potential policy violation, your prompts may be logged and reviewed for that purpose. You should ensure any fee terms important to you are captured in a written addendum or Order Form, as that is the only mechanism the agreement identifies for locking fees.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

2 important changes detected

6 versions captured · Latest change detected by ConductAtlas: October 2026

What changed Google Cloud expanded its acceptable use restrictions to explicitly cover 'AI Agents' in addition to the Services themselves. The updated terms now prohibit customers and end users from using AI Agents for high-risk activities, in violation of the acceptable use policy, to avoid fees, for cryptocurrency mining without approval, for telecommunications services, emergency calls, ITAR-controlled materials, export control violations, and other restricted purposes. The change also added a definition stating that 'AI Agent' has the meaning described in the applicable Service Specific Terms, and modified the indemnification clause to include breaches involving AI Agents. Additionally, the definition of 'Export Control Laws' was revised to remove the phrase 're-export' from the opening language.
Why this matters The updated terms now explicitly extend Google Cloud's acceptable use restrictions to cover AI Agents. Customers and end users are prohibited from using AI Agents for high-risk activities, to circumvent fees or usage limits, for cryptocurrency mining without prior written approval, for telecommunications services, emergency calls, materials subject to ITAR, or in violation of export control laws. The change clarifies that these restrictions apply not only to the Services themselves but also to any AI Agents deployed through Google Cloud. The indemnification obligation also now covers breaches involving AI Agents.
View full change record →
What changed Google Cloud expanded the definition of 'Fee Accrual Period' to include Google Workspace Services (GWS Services) in addition to GCP Services. Previously, the spend-threshold billing option applied only to GCP Services; the updated terms now extend this billing frequency option to GWS Services as well.
Why this matters The updated terms now permit customers to structure billing for Google Workspace Services using the same spend-threshold option previously available only for GCP Services. This expands the billing frequency choices available to organizations using both product lines, allowing them to consolidate billing structures across Google Cloud and Workspace services.
View full change record →

Clauses withheld

We withheld clauses we had published from this document. Each withholding is recorded in our correction log:

Featured provisions
Generated by a model from the captured document; not read by a person

Complete Provision Index

Every distinct legal provision identified in this document. Featured provisions appear above with analysis.

132 provisions
12 featured
22 clause types
General Contract Terms 35
Show all 35 general contract terms provisions
AI / Automated Decision-Making 1
Stay ahead of the changes

Monitoring

Google Cloud has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

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 12-month notice for backwards-incompatible API changes and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured October 13, 2026 01:10 UTC
Last successful capture October 21, 2026 00:55 UTC
Date stated by the document October 12, 2026 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000646
Version ID CA-V-007504
SHA-256 (extracted text, extractor v5) cc418dc21ef9693105c0bd86c23194706af33ae1561dc586b4e59813861b54d2
Archived bytes SHA-256 (anchor) 20044d39971b990a419c88c33321d320ba63ee211298418752b34b370375349a
✓ Snapshot stored ✓ Archived bytes anchored (verified Oct. 13, 2026)

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans