How This Briefing Works
This report opens with key findings, then maps the gaps between what Livestorm 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
“Awaiting scanner verification”
Livestorm runtime behavior including cookies set during webinar sessions, scripts loaded on event pages, and actual tracking pixel deployments has not yet been observed via scanner analysis. Current assessment is based on documented features, privacy policy, and support documentation.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Livestorm
- →- Audit all custom JavaScript and tracking pixels deployed on Livestorm event and registration pages — these operate outside Livestorm's core privacy controls. - Verify that attendee consent mechanisms cover not just Livestorm cookies but also organizer-deployed third-party scripts and pixels. - Review the scope of data flowing from Livestorm into CRM and marketing automation systems via native integrations and Zapier. - Confirm that Livestorm's EU hosting and ISO 27001 certification extend to the specific data processing activities relevant to your use case. - Assess whether the privacy trust signal from Livestorm's certifications creates a false sense of security for attendees exposed to organizer-deployed tracking.
Negotiation Leverage
- →Livestorm's EU hosting and ISO 27001 certification provide a strong baseline, but the DPA should explicitly address organizer-deployed custom scripts and tracking pixels. Negotiate clarity on: data processing boundaries between Livestorm-controlled and organizer-controlled tracking, attendee data retention after events conclude, whether Livestorm uses aggregated engagement data for its own analytics or benchmarking, and deletion procedures for attendee records across both the platform and connected integrations. The custom JavaScript feature should be evaluated as a potential compliance gap in regulated industries.
IOC Manifest
Indicators of compromise across 3 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
432 detection signatures across scripts, domains, cookies, and network endpoints