How This Briefing Works
This report opens with key findings, then maps the gaps between what Dealfront 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
Dealfront was observed loading and executing before user consent was obtained on 82% of sites where it was detected.
Consent Compliance
81.8% pre-consent tracking rate across monitored deployments
Undisclosed Party
Not in privacy policy
Marketing Mismatch
Behavior contradicts marketing
Compliance Claim Mismatch
False certification claims
Claims vs. Observed Behavior
Consent Compliance
“GDPR Compliant with ISO 27701 Privacy Certification”
81.8% pre-consent tracking rate across monitored deployments
22 detections across 20 sites show tracking fires before consent in majority of cases
Subprocessor Disclosure
“Full transparency on data sources and formal agreements with all sub-processors”
17+ third-party vendors on dealfront.com not listed in subprocessor documentation
Runtime scan shows ActiveCampaign, HubSpot, Intercom, LinkedIn, and others not in official list
Marketing Claims
“Born in Europe with compliance, transparency, and privacy in its DNA”
US-based AI subprocessors (OpenAI, Perplexity) and high pre-consent tracking contradict European privacy positioning
Subprocessor list shows US data transfers; runtime shows pre-consent behavior
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Dealfront
- →Audit your CMP configuration — ensure Dealfront scripts are blocked until explicit consent is obtained, given 81.8% pre-consent rate across the industry
- →Review your GDPR Article 30 records — pre-consent visitor identification may expose you to regulatory action as the data controller
- →Update privacy policy to disclose Dealfront as a third-party data processor with visitor identification capabilities
- →Request updated subprocessor list — their official list is incomplete based on 17+ undisclosed vendors on their own site
- →Consider contractual protections — ensure your DPA covers the pre-consent tracking liability and indemnification requirements
If You're Evaluating Dealfront
- →Note the gap between 'Europe-native' GDPR positioning and 81.8% pre-consent rate — this contradiction is material for EU-based procurement decisions
- →Request ISO 27001/27701 certificates and verify scope covers visitor identification technology, not just internal operations
- →Ask specifically how they reconcile GDPR compliance claims with pre-consent visitor identification across 20+ monitored sites
- →Require pre-deployment consent architecture verification — test in your environment with consent denied to verify tracking cessation
- →Compare against alternatives with demonstrable consent-first behavior and transparent subprocessor documentation
Negotiation Leverage
- →Pre-consent SLA: 81.8% pre-consent rate contradicts 'Europe-native' GDPR positioning. Require contractual guarantee of 0% pre-consent visitor identification on your property with independent audit verification.
- →Subprocessor transparency: 17+ vendors on dealfront.com undisclosed in subprocessor documentation. Require complete enumeration of all third-party vendors with data flow documentation and 30-day advance notice before additions.
- →Data pool isolation: Merged Leadfeeder+Echobot data covering 60M+ companies and 400M+ contacts. Require contractual guarantee that your visitor identification data is not pooled with other customers' data or used to enrich the shared intelligence database.
- →GDPR compliance verification: As a European company marketing GDPR compliance, their 81.8% pre-consent rate requires explanation. Require documented evidence of GDPR-compliant consent architecture for deployments on your property.
- →ISO certification scope: Request ISO 27001/27701 certificates and verify scope covers their visitor identification technology deployed on customer sites, not just internal infrastructure.
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
Ignoring CMP signals
Device identification
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 5 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
104 detection signatures across scripts, domains, cookies, and network endpoints