/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Zoom updates its terms of service and a recent blog post to explicitly say that the company won't use “communications-like customer content” to train AI models

Jay Peters / The Verge :

The Verge Jay Peters

Context & Ripple Effects

Days after language allowing AI training on some customer data drew attention, Zoom narrowed the boundary around communications content in its terms. The change resembles OpenAI’s earlier opt-in position on API data for model training, where customer-controlled data became a distinct policy category.

The wider coverage shows platforms treating AI-training rights as a sensitive terms-of-service issue: Adobe later clarified that customer work would not train Firefly. Zoom’s clarification matters because communications data carries especially direct expectations of confidentiality.

First-order effects

  • Zoom customers receive an explicit commitment that communications-like content will not be used to train the company’s AI models.
  • Zoom must distinguish communications-like content from other customer data in its AI-training policies and related disclosures.

Second-order effects

  • Rival collaboration and cloud software providers face greater pressure to state, in similarly specific terms, whether meeting, chat, and work-product data can train their models.
  • Enterprise buyers gain a clearer policy point for procurement and data-governance reviews, making vague references to “customer data” harder to accept.

Third-order effects

  • If such clarifications become standard, AI training policies are likely to move from broad platform terms toward data-type-specific consent and exclusion rules.
  • The pattern reinforces a public-data permission boundary: firms may increasingly compete on how narrowly and transparently they define permissible inputs for model development.

The trend: AI providers are being pushed to separate access to customer data from permission to use particular categories of that data as model-training input.

Discussion

  • @linkletter Ian Linkletter on x
    We won! Zoom has backed down, announcing they will no longer use private meeting data to train AI models. Sharing information in the public interest is essential to protecting our rights. https://www.theverge.com/...