What the HubSpot’s AI Backlash Says About Salesforce Data Governance

Ana P.
July 14, 2026

On July 1, HubSpot announced a change to its terms that would let customer enrichment data,  things like business contact details, employer information, and email deliverability signals, be shared across accounts to power new data discovery and intelligence features, including a tool called Contact Discovery set to launch August 4. Customers were automatically enrolled. To be excluded, they’d have needed to actively opt out before the launch date.

The backlash was swift (Source: Salesforce Ben). Within the HubSpot community, the framing that stuck was simple and pointed: “your data” was quietly becoming “our data.” By July 5, HubSpot reversed course entirely. Founder and CTO Dharmesh Shah publicly acknowledged the misstep, and Chief Product and Technology Officer Duncan Lennox wrote that the rollout had made customers feel like the relationship they had with their own CRM was shifting underneath them.

Whether you think HubSpot made the right call or not almost misses the point. The episode exposed something every CRM customer should understand: AI features don’t exist in isolation. They’re built on top of your data, which means governance matters just as much as capability.

Why Opt-In vs. Opt-Out Counts

The detail that matters most in this story is how consent from customers was obtained. They weren’t asked to participate in enrichment sharing. They were enrolled by default and had to locate the right settings to opt back out.

That distinction is bigger than it looks. Opt-out models rely on inattentiveness and most people don’t comb through a terms-of-service update the day it lands in their inbox. Opt-in models require an active, informed decision. The pattern is industry-wide, not vendor-specific. As AI features get built on top of Salesforce data, the question of consent keeps resurfacing because customers are paying closer attention than ever.

If you’re evaluating any platform with AI features built on your CRM data, this is the first question worth asking: Are you being asked, or assumed?

The Data Governance Questions Every Salesforce Organization Should Be Asking

If you’re evaluating any platform with AI features built on your Salesforce data. This is a good moment to revisit the basics of AI data governance. These are the first questions worth asking:

It’s also worth making a habit, on Salesforce, of periodically checking your own admin settings, not because something is necessarily wrong, but because settings can change with a terms update, and “you technically agreed” isn’t the same as “you noticed.”

Titan AI Studio for Built-In Governance

Titan AI is built on the principle that your Salesforce data stays yours, and stays within your organization’s control. Security and governance aren’t a layer added after the fact, they’re part of how the AI features were designed from day one, running natively within Salesforce’s trusted data boundaries rather than routing information out to external systems.

Put simply: Titan never touches your data. 

The Bigger Takeaway

The lesson from the past week isn’t to avoid AI features for Salesforce. AI-powered enrichment, automation, and insights are genuinely useful, and most vendors building them have good intentions. HubSpot itself framed its original goal as improving accuracy and outcomes across the board. 

However, transparency and consent can’t be an afterthought when customer data is involved, and that consent given quietly, by default, isn’t the same as consent given actively.

As AI becomes a standard part of how CRMs, like Salesforce, operate, the vendors worth trusting will be the ones who make governance a visible, verifiable part of the product, not a policy update customers find out about subsequently.


Have questions about how Titan AI Studio handles data governance and security? Slack a Titan expert

All-in-One Web Studio for Salesforce


Slack an expert