How This Briefing Works
This report opens with key findings, then maps the gaps between what Omnisend 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
consent
“GDPR compliant as EU-based company”
Data stored on U.S. servers; third-party synced contacts lack consent records per own documentation
data_sharing
“Never sells or shares mobile numbers”
Google Ads integration exports customer segments to advertising networks; 174 integrations create broad data sharing surface
pending
“Awaiting scanner verification”
Runtime behavior analysis pending to confirm tracking script behavior, cookie deployment timing, and consent gate implementation
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Omnisend
- →- Audit all Omnisend integrations and disable unnecessary data sharing pathways, particularly Google Ads segment export and third-party contact syncs without consent records. - Review consent collection mechanisms for all channels (email, SMS, push) and verify that Omnisend tracking scripts respect consent state before activating behavioral monitoring. - Evaluate whether Omnisend AI-powered personalization features are processing data beyond the scope of your privacy notice disclosures. - Request a data processing audit from Omnisend detailing all third-party sub-processors and data retention periods for behavioral tracking data. - Consider implementing server-side integration to limit Omnisend client-side tracking footprint and reduce direct visitor exposure.
Negotiation Leverage
- →Omnisend's leverage position is weakened by three documented issues: the structural consent gap for third-party synced contacts (acknowledged in their own support docs), the breadth of behavioral data collection powering their AI features, and the 174-integration ecosystem that creates lateral data export pathways. In contract negotiations, demand explicit DPA provisions covering: consent inheritance requirements for all integration-sourced contacts, restrictions on behavioral data use for AI model training, data retention limits for anonymous visitor tracking, and audit rights for sub-processor data flows. The U.S. data storage under EU-U.S. Data Privacy Framework should be addressed with supplementary measures given the framework's uncertain legal standing.
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
137 detection signatures across scripts, domains, cookies, and network endpoints