All Vendors
data_enrichment

Builtwith

BuiltWith technology profiling service deploys consent bypass during technology detection workflows.

20 IOCs5 detections100% pre-consent5 sites
70
Vendor Risk Score

How This Briefing Works

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

5 detections across 5 sites100% pre-consent activity
CRITICAL

Pre-Consent Activity

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

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps
Customer Impact

What This Means For You

Customers face GDPR violations from pre-consent site profiling. Risk is elevated if BuiltWith deployments are used for visitor identification or account-based marketing, creating secondary processing without consent.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Builtwith

  • Configure BuiltWith to activate only after consent for analytics/profiling collected
  • Verify technology detection occurs server-side (not client-side visitor tracking)
  • Limit BuiltWith use to internal competitive analysis (not visitor-facing deployments)

If You're Evaluating Builtwith

  • Request DPA confirming site profiling data is not used for visitor identification
  • Verify BuiltWith does not deploy client-side tracking for technology detection
  • Assess whether BuiltWith deployment is necessary vs. server-side technology detection alternatives

Negotiation Leverage

  • BuiltWith consent bypass (BTI-C09) during profiling creates pre-consent intelligence gathering—clarify whether deployment is server-side (competitive analysis) or client-side (visitor tracking)
  • If client-side deployment: require technical controls to delay profiling until after consent collection
  • If server-side deployment: verify no visitor-level data collection or retention
Runtime Detections

Runtime Detections

1 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-C09Consent Bypass

Ignoring CMP signals

Impact: Initiates technology profiling and site fingerprinting before consent collection, creating automatic legal violations for intelligence gathering processes.

IOC Manifest

IOC Manifest

16 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

BuiltWith integrates with sales intelligence platforms, competitive analysis tools, and lead generation systems to identify technology stacks. Data flows include detected technologies, site metadata, and profiling results to customer CRM and sales systems.
Evidence

Evidence Artifacts

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

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

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

Vendor Details