How This Briefing Works
This dossier opens with key findings, then maps the gap between what Hithorizons discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 1 sites
vendor fires before consent
Briefing
Hithorizons operates as a B2B contact enrichment service that appends firmographic, technographic, and behavioral data to CRM records. The platform uses cross-domain tracking and identity resolution to link anonymous website visitors to known contacts. Core threat lies in the data sharing ecosystem that pools enrichment data across customers and the consent bypass mechanisms enabling tracking without user notification.
What This Means For You
Sales and marketing teams using Hithorizons for contact enrichment face three critical liabilities: (1) Data quality corruption as probabilistic matching creates false enrichment that pollutes segmentation, (2) Competitive intelligence leakage as contact data feeds the platform's cooperative improving competitor enrichment accuracy, (3) Severe GDPR exposure from behavioral tracking, identity resolution, and consent bypass creating per-contact violation risk. The platform's data sharing model makes it impossible to provide individuals with meaningful transparency about data sources.
Risk Channel Breakdown
Hithorizons introduces data quality corruption by appending enrichment data from probabilistic matching, creating false precision in contact records that pollutes segmentation and targeting models.
Contact enrichment data is pooled across the platform's customer base to improve match rates, meaning your CRM contact intelligence feeds competitor enrichment. Every enriched record becomes a data asset shared across the network.
Expands attack surface
Behavioral biometrics collection and identity resolution without explicit user consent violates GDPR controller transparency requirements. Cross-domain tracking enables surveillance across unrelated websites. The platform's data sharing model creates GDPR Article 28 processor liability as enrichment sources are not disclosed to data subjects.
Threat Indicators
Runtime-observed (BTI-C)
Keystroke/mouse tracking
Identity stitching
Ignoring CMP signals
PII deanonymization
Container/loader (neutral)
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed Hithorizons's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
4 for current users · 4 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →