8 Total
Stay ahead of the changes
Track Google 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

By using Chrome or ChromeOS, you automatically agree to two sets of Google terms. The built-in AVC video technology is licensed only for personal, non-commercial use—if you use it in a way that earns money, that use is not covered. Most of Chrome's source code is freely available under open source licenses, but not all of it, and different parts of Chrome may be subject to their own specific rules.

Analysis

This document establishes the contractual framework governing use of Google Chrome and ChromeOS, requiring users to agree to both the Google Terms of Service and the Google Chrome and ChromeOS Additional Terms of Service as a condition of use. The terms apply specifically to the executable code versions of Chrome and ChromeOS, with certain components carrying their own distinct requirements. The document defines the scope of the AVC patent portfolio license, limiting it to personal consumer use or non-remunerated use, and specifying that it covers only encoding of AVC-compliant video and decoding of video encoded by consumers in personal activity, or video obtained from a licensed AVC video provider. No license is granted or implied for AVC uses beyond those expressly described, and most—but not all—of Chrome's source code is made available under open source license agreements.

What this means for you

Using Chrome or ChromeOS binds you to both the Google Terms of Service and the Chrome and ChromeOS Additional Terms of Service. The AVC patent portfolio license embedded in Chrome covers your personal, non-commercial video encoding and decoding, and covers video obtained from providers that are themselves licensed for AVC—but it does not cover commercial or remunerated uses, and no implied rights exist to extend coverage beyond what is expressly stated. Different components of Chrome and ChromeOS may carry their own separate legal requirements that apply to your use of those specific components. You can review the open source license agreements that govern most of Chrome's source code at chrome://credits.

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.

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.

8 provisions
8 featured
3 clause types
Restricted or Prohibited Content/Industries 1
Stay ahead of the changes

Monitoring

We have not recorded a change to this document since we began capturing it. 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 Additional Terms Apply to Chrome and ChromeOS and similar clauses.

Compare across platforms →

Related Analysis

Privacy · May 5, 2026
Chrome Installed 4GB of On-Device AI. What Google's Policies Authorize.

Google deployed Gemini Nano through Chrome updates, enabling on-device AI features for some users — often without clear user awareness or e…

Privacy · April 16, 2026
What Google Actually Knows About You

Google's Privacy Policy covers Search, Gmail, YouTube, Maps, and every site running Google Analytics. Here is what it actually authorizes.

Dependency Governance · May 27, 2026
Zero-Click Governance: What Google's AI Search Transition Means for Traffic-Dependent Businesses

AI Mode, AI Overviews, and embedded advertising are shifting search from referral infrastructure toward platform-contained answers.

Archival ProvenanceSource & Archival Record
This version captured October 17, 2026 00:11 UTC
Last successful capture October 21, 2026 00:10 UTC
Date stated by the document September 30, 2025 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000752
Version ID CA-V-007651
SHA-256 (extracted text, extractor v5) 8a2c4314c90ac3477e51ddbeef44871e6c565b3b97a11bea2496ee6967babeda
Archived bytes SHA-256 (anchor) 46d9c28ad5bde39fffa0f410d3cf982d99c2b59b23ed0d2fb7e51b5ffae8f43a
✓ Snapshot stored ✓ Archived bytes anchored (verified Oct. 17, 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