How This Briefing Works
This report opens with key findings, then maps the gaps between what SyftData 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
Pre-Consent Activity
SyftData was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Runtime detection shows C06 (behavioral biometrics), C07 (session recording), C09 (consent bypass), C14 (identity resolution), C15 (tag manager)
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use SyftData
- →IMMEDIATE: Audit SyftData initialization timing — pre-consent activation creates critical liability
- →Implement consent-gated deployment for all de-anonymization capabilities
- →Review session recording scope and implement PII redaction
If You're Evaluating SyftData
- →Document identity resolution methodology and data sources
- →Request written confirmation of data deletion procedures and third-party sharing restrictions
- →Obtain technical specification for disabling behavioral biometrics per-visitor
Negotiation Leverage
- →Pre-consent de-anonymization: CRITICAL liability — identity resolution and session recording activate before consent. Require technical controls to defer ALL tracking until authorization.
- →Session recording: Full replay captures sensitive visitor data — demand PII redaction and explicit session recording consent separate from analytics consent.
- →Identity resolution sales: Visitor profiles sold to sales/marketing platforms — negotiate restrictions on data resale and demand deletion rights.
- →Behavioral biometrics: Mouse/scroll patterns persist beyond opt-out — require specific deletion timelines and verification procedures.
- →Tag manager control: Dynamic capability additions bypass customer oversight — require approval workflow and quarterly capability audits.
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
Full session replay
Ignoring CMP signals
PII deanonymization
Container/loader (neutral)
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
79 detection signatures across scripts, domains, cookies, and network endpoints