On July 1, 2026, HubSpot followed in the footsteps of the countless tech giants that have violated customer trust. It notified customers that starting August 4, contact enrichment data in their CRM (“business contact details, employer information, and email deliverability signals”) “may be shared with other customers.” 1 Source 1 HubSpot customer email, July 1, 2026. Verbatim text confirmed via CMSWire and HubSpot Community thread #151789. Opt-out by default. The feature had an internal name: Trusted Prospecting.
The announcement landed at the start of a July 4th holiday week. Many observers noted the timing immediately: a terms change of this consequence, disclosed in a routine update right before a long weekend, with an August 4 deadline set while most teams were on holiday. Note the timing; don’t read conspiracy into it. What it does suggest is that the company understood how it would land.
Four days later, on July 5, HubSpot reversed. CPTO Duncan Lennox posted on the Community forum: “We got this wrong, and we are fixing it.” 2 Source 2 Duncan Lennox, HubSpot Community post, July 5 2026. Thread Cloudflare-gated; quote confirmed via his LinkedIn mirror. Co-founder Dharmesh Shah replied to Gabe Larsen’s viral LinkedIn post: “You are right. We made a mistake.” 8 Source 8 Dharmesh Shah, LinkedIn reply to Gabe Larsen, July 5 2026. Confirmed via CMSWire.
Most coverage this week said HubSpot listened, responded in four days, and did the right thing. On that point, coverage is correct. A co-founder and CPTO publicly owning a mistake within four days is rare in enterprise software. We give credit where it’s due. What strengthened the argument wasn’t competitors piling on — it was longtime HubSpot advocates. Caitlin Bigelow, a recognized voice in the HubSpot community and a historic champion of the platform, was among those who spoke up publicly. 17 Source 17 Caitlin Bigelow, LinkedIn post, ~July 5 2026. linkedin.com/posts/caitlinbigelow_boybye-share-7478810105564569601-tw76/ — Bigelow had been a vocal HubSpot advocate and community figure. Her public reaction was noted by observers as a signal that the backlash extended well beyond competitors and critics. When the pushback comes from people who built their careers in the ecosystem — not just critics from the outside — it lands differently. However, credit for listening and reversing a terms change is not the same thing as control over the customer. The reversal proves the very data ownership risk companies face when buying software like HubSpot. HubSpot decided to take their customers’ private data and share it in a pool with other customers. HubSpot set the opt-out defaults and the August 4 deadline. Finally, HubSpot decided to reverse. At every step, HubSpot was the operative force. The customer decided nothing.
We addressed exactly this in our Five Locks framework. Lock 2, the Data Lock: “the data is yours architecturally, not just contractually.” This episode is the live proof that the contractual layer doesn’t hold up. HubSpot rewrote the contract twice in five days.
Do you actually own your CRM data?
No, not if it lives on a vendor’s managed infrastructure. What you hold there is a contractual right of access, not ownership. HubSpot’s July 2026 episode made the difference concrete: the terms said your data was yours, then the terms were rewritten to permit sharing, then rewritten again when the backlash hit. A right that can be redefined by email was never a property right.
Architectural ownership is a different kind of thing. Your data in a warehouse you control, under your own database permissions, cannot be pooled into a shared dataset because no vendor has a hand on the switch. That’s not a better contract. It’s a system where the contract barely matters. The four illusions below are what the contractual version looks like when it’s tested.
Four Illusions Exposed by HubSpot’s Change to Terms of Service
Illusion 1: Ownership you can lose by email was never ownership
The customer’s only “control” in this episode was the right to complain after the fact. That’s a right of appeal, not ownership. Nothing in the CRM’s architecture gave the customer a veto over how HubSpot used the enrichment data sitting on its infrastructure. The terms changed by email; the only lever on the customer’s side was objecting loudly enough to move a news cycle.
If you disagree with a terms change, the recourse is to cancel and leave. That’s exactly the trap that years of data lock-in, thousands of contacts, and sunk-cost maintenance are designed to prevent. The architecture holds you in place precisely when it matters most.
Lennox’s reversal post puts the dynamic plainly. He thanks customers for “the feedback, the pushback, and the honesty.” That phrasing is honest: the correction came from outside. HubSpot responding to customer pressure is accountability, but accountability after the fact is not the same as a structural right that existed before the email landed.
Illusion 2: “Control” that doesn’t survive a settings save
The clearest evidence of this sits in public, in one of only a handful of replies to Lennox’s own apology thread. A paying customer wrote:
“We specifically turned this feature off; yet, it was on. When we turned it off again, it was turned back on again. How are you ensuring… you are deleting all of the customer information that you obtained by turning on this feature and that it is not used in your ‘commercial dataset’?” 3 Source 3 Paying HubSpot customer, replying to Duncan Lennox’s July 5 Community post (community.hubspot.com/t/152063) — one of only a handful of replies on the thread, publicly viewable there. Lennox did not answer the deletion question.
Lennox never answered the deletion question.
A setting that re-enables itself after you turn it off isn’t a control; it’s merely the illusion of consent while the system does what it pleases. HubSpot’s help page states that if a contact “withdraws their deletion request or re-consents, their data may be reintroduced into HubSpot’s enrichment dataset.” 6 Source 6 HubSpot Knowledge Base, “Understand opt-out notices for HubSpot’s enrichment dataset,” May 4 2026. Data once pooled cannot be reliably unpooled.
This wasn’t one unlucky admin. The State of Brand found that AI training, enrichment participation, and tracking-code intent sharing were three separate toggles in three separate settings, “so turning off one did nothing to the others, and for an in-scope account the whole arrangement behaved like default participation with an opt-out path.” 4 Source 4 The State of Brand, “HubSpot Spent 20 Years Selling Trust,” July 5 2026. There was no single switch. A diligent admin who hunted down all three and turned them off still had no guarantee they would stay off. For any leader who relies on an ops team to manage these settings, that’s the practical exposure today.
A setting that re-enables itself after you turn it off isn’t a control; it’s merely the illusion of consent while the system does what it pleases.
This is not a HubSpot anomaly. It’s the standard SaaS playbook for any feature that turns customer data into product. Facebook spent a decade shipping privacy controls whose defaults quietly favored sharing; the FTC fined it $5 billion in 2019 for misrepresenting how much control users actually had. 12 Source 12 U.S. FTC, “$5 Billion Penalty and Sweeping New Privacy Restrictions on Facebook,” July 2019 — the order followed findings that data was shared with third-party apps even for users on the most restrictive settings. Google shipped Gmail’s AI “smart features”, which has access to read all customer emails, switched on by default for U.S. users and off by default in Europe; a November 2025 class action alleges it did so without consent. 13 Source 13 Snopes, Nov 21 2025; class action filed N.D. Cal., Nov 11 2025. Google says it does not use Gmail content to train Gemini — the dispute is about default-on access, not model training.
The pattern is the point. Whether a data-sharing feature ships on by default (HubSpot; Gmail in the U.S.) or off by default (Gmail in Europe), the switch lives on the vendor’s side of the wall. The default direction is a distraction. The moment such a feature exists in an account you don’t control, your exposure is governed by the vendor’s roadmap and corporate agenda, not by you.
Illusion 3: Default-on is the revealed preference
Lennox stated in the reversal post that HubSpot “always intended for enrichment to remain strictly opt-in.” 5 Source 5 Duncan Lennox, per CMSWire, July 6 2026. The feature shipped opt-out.
You cannot accidentally build an opt-out enrollment flow. Some team designed it, tested it, documented it, and deployed it. That team knew what they were building. The “always intended opt-in” framing is retroactive. The intent was revealed in the update they shipped.
The placement of the terms is just as telling as the opt-out default. A routine terms-of-service update with a list of redline summaries, with the data-sharing change tucked “between a product rename (Commerce Hub is now Revenue Hub) and a note about Google reCAPTCHA.” 14 Source 14 The State of Brand, “HubSpot Spent 20 Years Selling Trust,” July 5 2026. reCAPTCHA is Google’s “prove you’re not a robot” bot-check widget. reCAPTCHA is the most boilerplate line in any legal update. Put the most consequential change to the customer relationship in years in that slot, in that format, and you’ve told the reader what you think of it. As State of Brand wrote: “When you communicate a trust decision in the format reserved for housekeeping, customers conclude you were hoping they wouldn’t read it.” That’s a tell any buyer can learn to spot. Watch where a vendor files a change, not just what it says.
A vendor who genuinely believed the data was yours would ask before sharing it. Jon Dick, HubSpot’s CCO, posted during the backlash window: “And if you don’t want to use or participate in enrichment, you can turn it off at any time. We believe in customer choice.” 10 Source 10 Jon Dick, HubSpot CCO, LinkedIn post ~July 1-2 2026. The choice on offer was the choice to object. Opt-out enrollment treats your CRM as HubSpot’s shared asset until you file a complaint. For a RevOps team, the practical implication is this: any enrichment feature HubSpot ships in the future requires your active scrutiny of the default setting, not just the feature itself.
Illusion 4: The “business card” distinction collapses under pooling
Lennox drew a line between CRM contact records (yours) and “business card-level” enrichment data (poolable). The line sounds reasonable until you look at how enrichment works.
Enrichment fields don’t float separately from your contacts — they attach to them inside your CRM. The employer information, the verified email, the deliverability signal: those fields live on your contact records. Your team spent time and money cleaning and maintaining them. When those fields flow into a shared dataset, a competitor querying the pool benefits from the refinement layer you paid for. The “business card” is the same record your sales team is working from. The distinction Lennox drew exists in the terms, not in the database.
There’s a second cost buried in that pooling: the legal exposure doesn’t travel with the data. When enrichment fields you shared cross into someone else’s CRM, HubSpot’s own help page puts the compliance burden back on you. “Customers are responsible for providing adequate notices and, where required, obtaining consents from their contacts.” 15 Source 15 HubSpot Knowledge Base, “Understand opt-out notices for HubSpot’s enrichment dataset,” May 4 2026. Under GDPR or CCPA, sharing personal data for a purpose beyond the original contract needs a lawful basis, and “opt-out by default” is a shaky one. The arrangement pooled the asset HubSpot wanted while leaving the regulatory risk on the customer’s balance sheet. That’s the line a CFO should read twice.
State of Brand put the strategic logic plainly: “HubSpot, sitting on hundreds of thousands of live CRMs, has the best raw position in the industry to build the freshest B2B dataset on earth. Which is exactly why the company tried to legislate its way there through a terms update instead of selling its way there through a value proposition.” 16 Source 16 The State of Brand, “HubSpot Spent 20 Years Selling Trust,” July 5 2026. HubSpot’s CRM customer count is State of Brand’s estimate. A CRM in the UI with a data co-op in the architecture is exactly what Contact Discovery was building toward.
Why doesn’t reversing the terms fix the problem?
Because reversing the terms restored a policy, not a right. “HubSpot reversed in four days — that’s accountability working” is true, and worth saying: the response was fast, public, and executive-level, with Dharmesh Shah and Duncan Lennox out front instead of a comms team. But accountability for a bad decision is not the same as a structural guarantee the customer holds. The reversal proves HubSpot responds to pushback. It doesn’t prove the customer had any lever except pushback — and pushback runs on the news cycle, which moves on.
Four things that were true on July 1 are still true today:
- The pooling infrastructure still exists. The machinery to collect, pool, and redistribute enrichment data was never dismantled, and Lennox’s post says HubSpot is “taking time to determine the right approach before relaunching Contact Discovery.” 11 Source 11 Duncan Lennox, Community post, July 5 2026. Confirms relaunch is planned, not cancelled. The prize is still the prize.
- The opt-out default is how they chose to ship once. The team that built that enrollment flow can build it again with a different product name, a quieter rollout, a narrower first scope.
- The re-enabling switch is unaddressed. Lennox never acknowledged the toggle that flipped itself back on, and never answered the deletion question. The one-way ratchet is still in place.
- The new promise is made of the old material. Lennox’s commitment to keep enrichment “strictly opt-in” is a terms clause, the exact instrument that was rewritten twice in five days. As State of Brand put it: “The apology reverses the terms. It does not reverse the strategy.”
The obvious response, when this happens, is to switch platforms. Move to Attio. Move to Notion CRM. Move to anything that isn’t HubSpot today. That instinct is understandable, and switching might well be the right call for your business. But switching CRMs doesn’t solve the underlying problem. Today it’s HubSpot’s Contact Discovery. Tomorrow it’s whatever the next platform decides to do with the data you’ve imported, cleaned, and enriched on their infrastructure. The platform changes; the dynamic doesn’t. If you’re renting your software — paying to access data and workflows that live on someone else’s servers, under someone else’s terms — then you’re always one ToS update away from this conversation again. The question isn’t which vendor to trust. It’s whether you want to keep structuring the relationship as a trust question at all.
HubSpot says “your data belongs to you.” This month, HubSpot decided to share it, decided the default, decided the deadline, and then decided to stop. The customer decided nothing. You cannot both “control” a thing and need the other party’s permission to keep controlling it. What HubSpot restored was its policy, but it kept all of its control.
Gabe Larsen framed what happened as clearly as anyone: “I bought the software. I imported the contacts. I cleaned the data. I enriched the records. I paid my team to maintain it. Somewhere along the way, SaaS companies forgot who the customer is.” 9 Source 9 Gabe Larsen, CRO at Atonom, LinkedIn post July 5 2026. linkedin.com/posts/gabelarsen_what-the-hell-is-hubspot-thinking-imagine-activity-7479228431818481664-rN5P He’s right. And when a company is down 65% and looking for new revenue streams 7 Source 7 David Elkington, LinkedIn post, ~July 5 2026. HubSpot stock (HUBS) was down roughly 65% from its 2021 peak at time of posting. , the carefully maintained CRM data of its customers starts looking like an asset to be monetized.
What Mid-Market Leaders Should Do Now
The reversal is behind us. The capability and the incentive aren’t. Three things worth doing this week:
Audit what you’ve actually built in-platform. Workflows, custom properties, reports, enrichment reliance, and map out what you’d genuinely lose if you had to migrate. Most teams discover they’re more locked in than they thought, and most discover the lock-in is uneven: some workflows are portable, some aren’t. Knowing the difference is the beginning of real optionality.
Read your enrichment, AI-training, and tracking terms separately. They’re often separate toggles in separate settings pages (The State of Brand counted three distinct ones in this episode). Turning off one did nothing to the others. This isn’t a one-and-done settings check, it’s an ongoing audit item any time HubSpot ships a new AI or enrichment feature.
Separate contractual ownership from architectural ownership. Your HubSpot contract says your data is yours. This week showed what that means in practice: a right to object, with no veto. Evaluate the real exit cost, because a terms promise is only as durable as the vendor’s next earnings call. That gap between what the contract says and what the architecture allows is the actual risk to manage.
The Architecture Is the Answer
The companies that watched this episode without reaching for their opt-out settings were the ones whose data never lived on HubSpot’s infrastructure. No toggle to flip because there was no toggle. No shared dataset to opt out of because there was no shared dataset.
When your contact data lives in a warehouse you control, “data sharing” requires your explicit action to set up. That’s what we mean when we say the data is yours architecturally, not just contractually.
The Sovereign Stack blueprint is the implementation: a CRM where your data lives under your database permissions, where enrichment runs on your own pipeline, where no vendor term can reach your records without your deliberate act of connecting it. That’s not a promise from a vendor. It’s a property of the system.
This isn’t a HubSpot problem. It’s a renting-vs-owning problem. Every SaaS platform is structurally capable of what HubSpot attempted — pooling customer data, building shared datasets, monetizing the asset base — because every SaaS platform holds your data on their infrastructure. Most platforms haven’t done it yet. Some have done it quietly, in areas you aren’t watching. The pattern across Facebook, Google, and now HubSpot is the same: the feature ships, the default favors the vendor, the terms carry the liability to you. What changes between these episodes is the brand, the product name, and how fast the backlash lands.
Architectural ownership breaks the pattern for good. When your data lives in infrastructure you control, there’s nothing for a vendor to pool. The trust question disappears, because trust was never in the architecture to begin with — only access. And ownership pays forward: your contact data and the enrichment layer you paid to build become training data for your own AI agents, the join that connects content engagement to closed-won revenue, a compounding asset no vendor can quietly draft into their own product roadmap. The company that tried to pool everyone’s CRMs was reaching for exactly that advantage.
HubSpot will relaunch Contact Discovery, under that name or another. The next platform you move to will eventually reach the same crossroads. The only durable answer isn’t a better vendor. It’s a different architecture.
The research is free. So is the diagnosis — 60 seconds →