How This Briefing Works
This report opens with key findings, then maps the gaps between what CANDDi 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
data_collection
“Uses only first-party cookies with no third-party data sources”
AI-powered enrichment features pull company news, social media, and product launches from external sources, expanding data collection beyond first-party interactions
consent
“Only identifies individuals who carry out identifying actions”
Clicking an email link is a low-intent action most users would not associate with enabling persistent behavioral surveillance across all future website visits
pending
“Fully GDPR compliant”
Awaiting scanner verification. Progressive identification from email click to persistent tracking may not satisfy GDPR Article 6 informed consent requirements. Runtime analysis needed to verify pre-consent data collection timing.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for CANDDi
- →- Audit CANDDi cookie persistence settings and verify actual cookie lifetimes match your privacy policy disclosures - Review email marketing integration to ensure recipients are informed that clicking links enables persistent website tracking - Verify that your cookie consent mechanism fires BEFORE CANDDi's JavaScript tracker initializes — test with consent denied - Restrict CRM integration permissions so CANDDi visitor data is only accessible to authorized sales personnel - Conduct a Data Protection Impact Assessment (DPIA) covering the progressive identification workflow from email click to persistent tracking
Negotiation Leverage
- →When negotiating with CANDDi, demand explicit documentation of their data retention periods for visitor profiles, including how long identification persists after last visit. Request contractual guarantees that their JavaScript tracker does not collect or transmit data before cookie consent is granted on your website. Ask for a complete list of sub-processors and third-party data sources used for company enrichment features.
- →Key leverage points: CANDDi's claim of first-party-only cookies should be verifiable through runtime analysis. If their tracker collects any data before consent, or if cookies persist beyond declared lifetimes, this creates immediate contractual and compliance remediation obligations. Request the right to conduct independent technical audits of the tracker's behavior on your properties, and ensure your DPA includes specific provisions for data deletion upon visitor request that cascade through all CRM integrations where CANDDi data has been synced.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses