HubSpot reversed a July 2026 terms-of-service change that would have pooled customer data and allowed AI-model training, after customer backlash

The problem

Effective July 1, 2026, HubSpot updated its Customer Terms of Service and related legal documents to support a new “Contact Discovery” feature and a shared data-enrichment dataset (source). HubSpot’s own legal-update notice told customers “On August 4, Contact Discovery launches” (source). The same notice stated that customer data could be used to train HubSpot’s AI models unless a super admin turned that off: “If you turn off AI model training, your customer data is no longer used to train AI models, including models that improve enrichment features” (source).

Independent press reported that participation was set on by default. CXToday wrote that HubSpot chose to “set opt-out as the default setting, meaning customers were automatically enrolled unless they manually took action to remove themselves” (source). CMSWire reported that customers objected to being “automatically enrolled rather than asked, with critics arguing the plan treated customer-built CRM data as HubSpot’s to redistribute” (source).

The “default opt-out / automatically enrolled” framing is the load-bearing weak point of this story: it comes from the two independent newsrooms (Tier 2) and from HubSpot’s own June-25 notice, not from an audited setting-by-setting record — and in its own reversal post HubSpot later framed enrichment as having been “always intended” to be opt-in, so the two accounts of intent are shown here, not merged.

What was built

This is a Terms-of-Service reversal after a data-and-AI backlash — not a technical deployment. HubSpot’s own notice told customers they could opt out “of your data being used for AI model training and stop using enrichment features before August 4” (source). Customers pushed back hard, especially on LinkedIn (source).

The outcome

On July 5, 2026, HubSpot Chief Product and Technology Officer Duncan Lennox posted an official HubSpot Community reversal (source). He wrote: “We made a mistake. Nothing matters more to us than the trust of our customers, and with our recent terms of service update we let you down. We are sorry about that. We will not move forward with the terms of service changes we communicated on July 1, 2026” (source). He added: “First, we will not move forward with the terms of service changes we announced on July 1” (source).

CMSWire reported that HubSpot “announced a July 1 terms change allowing customer enrichment data to be shared across accounts, then fully reversed it by July 5 after sustained backlash, especially on LinkedIn” (source). CXToday reported that Lennox “used an official company community post to backtrack and confirm that the terms of service changes will no longer go ahead” (source).

How this was verified

Method: both criticals rest on Wayback-captured, on-disk copies. The July-1 change and the July-5 reversal are quoted from the two first-party HubSpot Community posts (notice 151430, reversal 152063), and corroborated by two independent newsrooms (CMSWire and CXToday). Each load-bearing quote above was string-matched against the archived capture on disk. This is a corporate-policy event, not a court or audited-metric event, so no court-style byte-tie is asserted; provenance is archived-capture plus verbatim quote-match. Verified 2026-08-09.

Path to green

This story caps at its honest band on the independent public record. What would raise it further is not a confirmation from HubSpot — a subject confirming its own numbers is a testimonial, not an audit — but more of the public record: the live or archived reverted terms pages showing the July-1 change was withdrawn, and independent reporting adjudicating whether enrollment was in fact default-on versus HubSpot’s post-hoc “always intended … strictly opt-in” framing. Absent an independent record that settles the default-on question, that one characterization stays attributed to the newsrooms, and the story is closed at its achieved band rather than chased. This June/July-2026 HubSpot event is distinct from the WeTransfer (July 2025) and Adobe (June 2024) AI-training terms walk-backs and must not be conflated with them.

Related case files

• WeTransfer removed an AI-training clause from its terms after backlash — the closest sibling walk-back
• Adobe clarified its terms of use over AI-training fears after backlash
• Slack updated its AI privacy principles after a user backlash over ML-training opt-out
• Dropbox added a third-party-AI (OpenAI) toggle and clarified it does not train models on customer data

Sources

1. HubSpot Community (first party) · “July 1, 2026: Contact Discovery is Coming Soon + Legal Update” (notice 151430) · 2026-06-25 · Tier 1 · https://community.hubspot.com/t/july-1-2026-contact-discovery-is-coming-soon-legal-update/151430
2. HubSpot Community (first party) · “We Got This Wrong. And We Are Fixing It” (reversal 152063, author Duncan Lennox / dlennox, CPTO) · 2026-07-05 · Tier 1 · https://community.hubspot.com/t/we-got-this-wrong-and-we-are-fixing-it/152063
3. CMSWire · “HubSpot Reverses Customer Data Enrichment Plan After Customer Backlash” (Dom Nicastro) · 2026-07-06 · Tier 2 · https://www.cmswire.com/customer-experience/hubspot-reverses-customer-data-enrichment-plan-after-customer-backlash/
4. CXToday · “HubSpot Data Enrichment Reversal” · 2026-07-06 · Tier 2 · https://www.cxtoday.com/crm/hubspot-data-enrichment-reversal/