How This Briefing Works
This report opens with key findings, then maps the gaps between what LeadInfo 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
“Works completely cookieless with no tracking cookies, no device fingerprinting, no cross-site monitoring”
Awaiting scanner verification to confirm no cookies are set and no fingerprinting techniques are used. Cookieless claim is strong but requires runtime validation of the tracking pixel behavior.
data_collection
“Processes only business data — no personal data, no individual tracking, no personal profiles”
Contact enrichment feature provides verified email addresses, mobile phone numbers, and LinkedIn profiles for individuals at identified companies, filtered by seniority and role. This constitutes individual personal data processing layered on top of the company-level identification.
data_retention
“IP addresses are not saved”
Awaiting verification. The claim that IPs are processed for resolution but not stored requires independent technical validation of data retention practices.
consent
“100% GDPR compliant with ISO 27001 certification”
Company-level IP resolution may qualify as legitimate interest processing, but the contact enrichment layer introducing individual employee PII (emails, phones, LinkedIn) from anonymous visits likely requires separate legal basis analysis.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for LeadInfo
- →- Verify LeadInfo's cookieless claim through runtime analysis — confirm no cookies are set and no fingerprinting occurs in the tracking pixel - If using contact enrichment (individual emails, phones, LinkedIn), conduct a separate legal basis analysis under GDPR Article 6 for processing these individuals' personal data - Audit the full list of LeadInfo integrations activated in your account and ensure each downstream system is covered in your data processing inventory - Review Zapier/Make workflows to prevent LeadInfo visitor data from flowing to systems not assessed for privacy compliance - Validate that IP addresses are truly not retained by requesting LeadInfo's technical data flow documentation and retention schedules
Negotiation Leverage
- →LeadInfo's strong privacy positioning (cookieless, ISO 27001, EU data centers, GDPR compliance) provides a solid foundation for negotiation, but the contact enrichment feature creates leverage points. Request explicit documentation separating the legal basis for company-level IP resolution (likely legitimate interest) from the legal basis for providing individual employee contact details (which may require a different justification). Ask for contractual guarantees that IP addresses are processed transiently and not stored or logged.
- →Key leverage points: LeadInfo's 220-million-company database and 300-million-profile contact database draw from 45+ external sources. Request transparency on these data sources and their own GDPR compliance status. If any source has faced regulatory action or data breach, this cascades into LeadInfo's data quality and compliance posture. Negotiate the right to use company-level identification without the contact enrichment layer if your legal team determines the individual PII processing introduces unacceptable risk. Ensure your DPA specifies data deletion obligations that cover both the primary identification and any enrichment data that has been pushed to your CRM systems.
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
172 detection signatures across scripts, domains, cookies, and network endpoints