How This Briefing Works
This report opens with key findings, then maps the gaps between what HubSpot discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Pre-Consent Activity
HubSpot was observed loading and executing before user consent was obtained on 46% of sites where it was detected.
Pre-Consent Data Collection
47.4% of HubSpot tracking instances fire before consent is obtained
Compliance Claim Mismatch
False certification claims
Scope Creep
Collection exceeds disclosed scope
Claims vs. Observed Behavior
Pre-Consent Data Collection
“GDPR and CCPA compliance certified”
47.4% of HubSpot tracking instances fire before consent is obtained
Runtime detection data from 198 sites shows pre_consent=true on nearly half of detections
Data Sale Disclosure
“Standard CRM and marketing automation”
Explicitly sells/shares personal information to advertising partners
Privacy policy states: In the preceding 12 months, we have sold or shared certain information, including identifiers, to our advertising partners
Commercial Dataset Operation
“Marketing and sales software”
Operates commercial dataset of professionals used for enrichment products
Privacy policy describes maintaining and appending data to commercial dataset for enrichment services
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use HubSpot
- →Audit your CMP integration — ensure HubSpot tracking code fires ONLY after consent, given the 47.4% pre-consent rate across the industry
- →Review your DPA and understand shared controller responsibilities — HubSpot operates beyond standard CRM as a data enrichment vendor
- →Check if enrichment features are enabled — your customer data may flow into HubSpot's commercial dataset accessible to competitors
- →Configure opt-out sync to ensure HubSpot respects your CMP consent signals and GPC headers
- →Verify your privacy policy discloses HubSpot's data sale practices if you use their advertising or enrichment features
If You're Evaluating HubSpot
- →Request SOC2 Type II report (requires NDA) and verify scope covers both CRM platform and tracking code deployed on customer sites
- →Clarify data enrichment scope — ask specifically whether your customer data enters their commercial dataset or advertising partner network
- →Negotiate DPA terms around data use for AI/ML training — opt-out is available but must be explicitly configured
- →Compare pre-consent rates against privacy-focused alternatives like Plausible or self-hosted analytics solutions
- →Factor in that HubSpot is both your CRM vendor and a data enrichment vendor — understand the full scope of data flows before committing
Negotiation Leverage
- →Pre-consent SLA: 47.4% pre-consent rate across 198 sites contradicts GDPR compliance claims. Require contractual guarantee that HubSpot tracking code fires only after consent on your property, with automated consent mode integration.
- →Commercial dataset exclusion: HubSpot maintains commercial datasets of professionals and admits to data sales under CCPA. Require written contractual exclusion of your customer data from their commercial dataset and advertising partner sharing.
- →Data enrichment opt-out: Require explicit opt-out from HubSpot's data enrichment features that flow customer data into shared commercial intelligence pools accessible to competitors.
- →SOC2 access: HubSpot gates SOC2 report behind NDA. Require direct access to current SOC2 Type II report as a contract condition, with right to share findings with your security team.
- →AI training exclusion: Require contractual commitment that your CRM data is not used for AI/ML model training across HubSpot's platform — opt-out must be available and verifiable.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 6 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
259 detection signatures across scripts, domains, cookies, and network endpoints