This analysis describes what Google Cloud'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 prohibition defines a hard boundary on permissible use, distinguishing these services from GCP and Looker which customers may integrate into their own applications.
Interpretive note: The excerpt as quoted explicitly names all three services (Google Workspace, SecOps, Cloud Identity) in the integration prohibition but then references only 'Google Workspace Services' in the create-or-host prohibition. The canonical claim merges both prohibitions; the precise scope of the create-or-host prohibition as to SecOps and Cloud Identity Services is uncertain from the truncated excerpt.
The updated terms authorize Google Cloud to impose full-month billing charges if it determines a customer engaged in bad-faith dealing, dishonesty, or attempted to avoid fees or circumvent usage limits, and to charge for all end-user accounts active during that month regardless of whether any were later disabled. The revised policy also permits immediate service suspension if Google reasonably determines a customer using a delayed payment method poses a non-payment risk, without requiring actual late payment or cure time. Additionally, Google may now terminate the agreement immediately if it reasonably determines a customer's material breach is incapable of being cured, eliminating the previous 30-day cure period. Customers using bank transfers or similar delayed authorization payment methods should review their account practices for any activity Google might classify as 'Customer Malfeasance' under the new definition.
View change record →Customers are prohibited from building, hosting, or integrating Customer Applications using Google Workspace Services, SecOps Services, or Cloud Identity Services.
How other platforms handle this
Send bulk emails, meaning commercial or marketing emails directed to a number of individuals with the same content, through Mailchimp Inbox.
Customer's choice not to deploy Maintenance or Updates as they become available may result in issues with operability, compatibility and interoperability and result in the Software in use being non-conforming to later Software documentation.
You may not display any personal contact, banking, or peer-to-peer payment information, whether in relation to you or any other person (for example, names, home addresses or postcodes, telephone numbers, email addresses, URLs, credit/debit card...)
"Customer may not integrate the Google Workspace Services, SecOps Services, or Cloud Identity Services into Customer Applications or create or host Customer Applications using the Google Workspace Services...Excerpt from Google Cloud's Terms
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 prohibition defines a hard boundary on permissible use, distinguishing these services from GCP and Looker which customers may integrate into their own applications.
Customers are prohibited from building, hosting, or integrating Customer Applications using Google Workspace Services, SecOps Services, or Cloud Identity Services.
ConductAtlas has identified this type of provision across 282 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Google Cloud.