August 3, 2026: HubSpot’s Contact Discovery goes live tomorrow, with data-use clarifications and opt-out guidance
The main difference between what HubSpot promised earlier this summer and what rolls out tomorrow is the scope of Contact Discovery’s professional data sharing and the controls customers can apply. As of Monday, August 3, 2026, HubSpot executives and admins are circulating final reminders about the August 4 launch, alongside clarifications on how the feature uses professional enrichment data and how to opt out where needed.
Contact Discovery start date and what changes for HubSpot data enrichment
HubSpot’s marketing leader Jon Dick said in a recent LinkedIn update that “Contact Discovery” begins on August 4 and outlined how it enhances lead profiles using aggregated, professional signals across the customer base, with administrative controls available to limit participation where required. His post frames the rollout as part of HubSpot’s broader AI and data strategy rather than a silent policy shift, and points customers to opt-out mechanics if they prefer a narrower data footprint. You can read the executive’s details in Jon Dick’s LinkedIn update on the August 4 launch.
Customer notices and the final 24-hour window before the switch
A widely shared customer screenshot and summary from consultant Matt Zelasko reiterates that the rollout starts August 4, highlighting that the feature enriches contact records with business-relevant attributes and deliverability signals while giving admins control over participation. The reminder is prompting many teams to review their privacy posture today, August 3, ahead of the change. For context on what customers received, see the LinkedIn post collecting the rollout email and key points.
How HubSpot describes the underlying data handling
Beyond social posts, HubSpot’s legal documentation describes how “Professional Enrichment Data” can be processed to append and improve datasets that power product features like Contact Discovery. The language in HubSpot’s Data Processing Agreement sets expectations for data categories, processing purposes, and deletion rights, which is why many admins are cross-referencing it today to confirm their compliance stance before the launch. The relevant definitions are outlined in HubSpot’s Data Processing Agreement.
Practical implications for admins and RevOps teams this week
In practice, three workstreams matter right now:
- Governance and consent: Confirm your internal basis for processing professional enrichment data, especially if you operate in regulated industries or handle mixed B2B/B2C datasets. Many teams are aligning the launch with a quick data inventory and record-of-processing entries.
- Systems impact: Expect new enrichment signals to touch scoring rules, segmentation, and email deliverability logic. A common issue is inflated lead scores when enrichment adds firmographic fields that your models treat as intent; review thresholds and exceptions before those signals flow.
- Controls and documentation: If your policy is to minimize shared enrichment, ensure the opt-out setting is applied consistently across portals and that you’ve documented the rationale. Teams that manage multiple brands or regions typically establish a standard position, then carve out exceptions for specific business units.
Why this matters beyond compliance
What typically happens after enrichment features go live is a visible uptick in match rates and de-duplication quality, followed by short-term noise in attribution and scoring as new fields populate. The trade-off is straightforward: broader signal sharing can accelerate prospect identification and deliverability tuning, while stricter limits reduce data exposure but may slow AI-driven discovery. If you’re running intent-led sequences, sandbox the change on a lower-risk segment first and watch reply rates and spam-complaint ratios for a week before widening exposure.
Share With Others
Platinum
