The Terms of Service and Privacy Notice documentation for the Gemini CLI (Command-Line Interface) reveals a complex and highly differentiated structure of privacy and data-use policies, critically dependent on the authentication method and account type used. This document is crucial because it determines whether the user's prompts, responses, and associated code will be collected and potentially used for model training.
Four Distinct Authentication Scenarios
Scenario 1: Google account + Gemini Code Assist for Individuals Users are subject to the general Google Terms of Service and a specific Privacy Notice for Code Assist Individuals. Under this arrangement, prompts, responses, and associated code are collected and may be used to improve Google products, including model training purposes.
Scenario 2: Google account + Gemini Code Assist for Standard/Enterprise Users The Google Cloud Platform Terms of Service and a distinct Privacy Notice for Standard/Enterprise apply. Crucially, for these users, prompts, responses, and code are treated as confidential, are not collected, and are explicitly not used for model training.
Scenario 3: Gemini API key + Gemini Developer API Terms differ depending on unpaid vs paid service. Unpaid services: the Gemini API Terms of Service for Unpaid Services apply, permitting collection of prompts/answers/code for model improvement. Paid services: the Gemini API Terms of Service for Paid Services govern, treating inputs as confidential and preventing collection for model training.
Scenario 4: Gemini API key + Vertex AI GenAI API Subject to the Google Cloud Platform Service Terms and the Google Cloud Privacy Notice. In this scenario, prompts, responses, and code are considered confidential, are not collected, and are not used for model training.
Usage Statistics: Unified Control, Variable Scope
The document also addresses "Usage Statistics," serving as a single control for all optional data collection in the Gemini CLI. The scope of data collected via this setting varies by account type. For individual Code Assist users and unpaid Developer API users, enabling Usage Statistics permits collection of anonymous telemetry PLUS prompts/answers/code for model improvement. For Standard/Enterprise Code Assist users and Vertex AI GenAI API users, this setting controls only anonymous telemetry, since their prompts and code are never collected. Paid Developer API users have their prompts/responses logged for a limited time solely for policy violation detection. All users can opt out of Usage Statistics collection.
This documentation structure highlights a clear monetization strategy: free services fund their operational cost through data collection for model improvement, while paid and enterprise services guarantee full confidentiality as a premium value proposition.