How This Briefing Works
This report opens with key findings, then maps the gaps between what Sendoso 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”
Sendoso web-side tracking footprint (cookies, pixels, scripts on customer sites) has not yet been observed via runtime analysis. Current assessment is based on documented integrations and platform capabilities.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Sendoso
- →- Audit CRM-to-Sendoso data sync scope: confirm which contact fields (especially physical addresses) are shared and whether recipients have been notified. - Review Sendoso sub-processor list to understand which fulfillment partners receive personal data. - Evaluate attribution claims critically — gifting-to-pipeline correlation does not equal causation. - Ensure DPA coverage extends to physical fulfillment partners in the Sendoso supply chain. - Confirm data retention policies for recipient addresses and engagement history within Sendoso.
Negotiation Leverage
- →Sendoso processes physical mailing addresses — a higher sensitivity class than digital identifiers. Negotiate DPA terms that explicitly cover fulfillment partner data sharing, address data retention limits, and recipient notification requirements. Request the complete sub-processor list and confirm deletion procedures for contact data when a subscription ends. The attribution model should be evaluated independently rather than accepted at face value for budget justification.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Keystroke/mouse tracking
Impact: The OAuth-based CRM sync and Chrome extension create data pipelines that may not be visible to security teams. Contact data extracted from Salesforce flows through Sendoso infrastructure to third-party fulfillment vendors.
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
4 detection signatures across scripts, domains, cookies, and network endpoints