All Vendors
data_enrichment

Dropcontact

Dropcontact (email enrichment) exhibits behavioral biometrics (C06), cross-domain sync (C08), and consent bypass (C09). 65% Broker risk reflects B2B identity graph data sharing.

7 IOCs3 detections67% pre-consent2 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Dropcontact 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

Key Findings

3 detections across 2 sites67% pre-consent activity
CRITICAL

Pre-Consent Activity

Dropcontact was observed loading and executing before user consent was obtained on 67% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps

pending

UNKNOWN
They Claim

“Unknown - requires claims extraction via CDT”

Observed Behavior

Runtime evidence shows C06/C08/C09 patterns

Customer Impact

What This Means For You

Cross-domain B2B tracking creates competitive intelligence leakage. Visitor data on your site enriches shared prospecting database used by competitors for targeting. GDPR Article 6 requires lawful basis before processing; consent bypass eliminates this.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Dropcontact

  • →Audit what visitor data feeds Dropcontact identity graph
  • →Confirm consent before enrichment tracking starts
  • →Review data sharing: who accesses the B2B graph?

If You're Evaluating Dropcontact

  • →Request data flow diagram showing cross-domain sync scope
  • →Test: does Dropcontact fire before consent banner?
  • →Verify privacy policy discloses B2B identity graph participation

Negotiation Leverage

  • →C08 cross-domain sync feeds B2B identity graph used by competitors. Is this disclosed?
  • →C09 consent bypass creates GDPR Article 6 lawful basis gap. How do you enforce consent-first operation?
  • →Visitor data enriches shared prospecting database. Can you restrict competitive use?
Runtime Detections

Runtime Detections

3 BTI-C CODES

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.

BTI-C06Behavioral Biometrics

Keystroke/mouse tracking

BTI-C08Cross-Domain Sync

Identity stitching

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

4 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

B2B prospecting stack. Often paired with Clearbit, ZoomInfo, Lusha. Cross-domain sync means visitor behavior on your site feeds shared identity graph used by competitors.
Loads (1)
Segment
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

7 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details