How This Briefing Works
This report opens with key findings, then maps the gaps between what Hushly 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
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“1st-Party opt-in database”
Awaiting scanner verification to determine how this enrichment database interacts with customer-deployed scripts at runtime and what data is transmitted to Hushly servers during visitor sessions
pending
“GDPR compliant as data controller”
Runtime observation needed to confirm whether behavioral tracking and enrichment lookups occur before or after consent capture on customer properties
pending
“AI-powered lead qualification”
Scope of automated profiling and decision-making about visitors needs direct observation to characterize under GDPR Article 22 automated decision-making requirements
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Hushly
- →- Audit enrichment scope: Request from Hushly a complete inventory of what data points are captured and enriched beyond the visible form fields visitors submit. - Review data controller relationship: Clarify the legal basis under which Hushly processes your visitor data through its centralized enrichment database as a data controller (not processor). - Map export destinations: Document exactly what enriched data is exported to your CRM and marketing automation platforms, and verify this matches what your privacy policy discloses. - Assess consent coverage: Verify that your consent management platform captures explicit consent for the behavioral tracking and enrichment activities Hushly performs, not just for the visible form submission. - Evaluate data isolation: Confirm whether your visitor data is segregated within Hushly's enrichment database or commingled with data from other customers.
Negotiation Leverage
- →Hushly's data controller status over its enrichment database is the key leverage point in negotiations. As a data controller, Hushly has independent decision-making authority over how it processes your visitor data — push for contractual limitations on this authority, including restrictions on using your visitor data to enrich other customers' records. Demand data isolation guarantees and audit rights over the enrichment database. Request explicit documentation of the legal basis Hushly relies on for each data processing activity (behavioral tracking, enrichment lookups, profile building, data export). If operating under GDPR, clarify the controller-to-controller data sharing arrangement and ensure appropriate safeguards are contractually binding.
IOC Manifest
Indicators of compromise across 4 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
206 detection signatures across scripts, domains, cookies, and network endpoints