How This Briefing Works
This report opens with key findings, then maps the gaps between what Pendo 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
“Requires scanner verification of runtime behavior”
Analysis based on Pendo documentation, help center articles, and privacy policy
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Pendo
- →- Re-evaluate Pendo's data collection scope following the 2025 session replay and web analytics feature additions to ensure privacy impact assessments are current. - Configure Do Not Process (DNP) rules for sensitive user segments and application contexts where behavioral tracking is inappropriate. - Audit in-app guide targeting rules to ensure behavioral segments are not exposing sensitive data in guide targeting logic. - Implement Content Security Policy headers that account for Pendo's DOM injection requirements while limiting the scope of injected content. - Review Pendo's data retention policies and configure appropriate limits for behavioral data, session recordings, and survey responses separately.
Negotiation Leverage
- →Leverage: Pendo's rapid feature expansion in 2025 (session replay, web analytics, agent analytics) means the data collection scope is growing faster than most organizations' privacy assessments can keep up. Use this to negotiate feature-specific data processing terms rather than blanket platform access. Key questions: Are session replay features enabled by default or opt-in per customer? Can DOM injection (in-app guides) be restricted to specific pages or user segments? What data does Pendo collect about guide interactions beyond what is visible in the dashboard? Does Pendo use customer behavioral data for product benchmarking or AI model training? Protections to require: Feature-level data processing agreements that cover analytics, session replay, in-app guides, and surveys separately. Contractual notification before new data collection features are enabled. Right to audit DOM injection scope. Prohibition on using behavioral data for cross-customer benchmarking without explicit authorization. Data deletion SLA covering all data types.
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
103 detection signatures across scripts, domains, cookies, and network endpoints