How This Briefing Works
This report opens with key findings, then maps the gaps between what Invoca 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”
Analysis based on public documentation, Invoca product pages, press releases, and integration specifications
pending
“Voice biometric data handling unverified”
Invoca references patented voice biometric technologies but specific data retention and processing details have not been independently verified
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Invoca
- →Audit the Invoca JavaScript snippet and cookie behavior to understand the full scope of visitor data collection and session tracking on your properties.
- →Review call recording consent mechanisms across all jurisdictions where your business receives calls—ensure Invoca's recording and AI transcription are disclosed to callers before conversations begin.
- →Map every active Invoca integration to understand where call data, transcriptions, and AI-derived insights are flowing—particularly bidirectional connections to Google Ads, Meta, and Salesforce.
- →Evaluate the voice biometric processing—request documentation on what biometric data is collected, how long it is retained, and whether it is used for any purpose beyond the stated service.
- →Assess whether conversation intelligence data flowing to ad platforms for lookalike audience creation and retargeting aligns with your privacy policy disclosures and data subject consent.
Negotiation Leverage
- →Invoca's enterprise positioning and compliance certifications (HIPAA, SOC 2, PCI DSS) provide leverage for demanding rigorous contractual protections. Key negotiation points: request a complete data sub-processor list including all platforms that receive call data through integrations. Require contractual commitment that AI models (Signal AI, GPT Call Analysis) are not trained on your organization's call recordings or transcriptions. Negotiate data retention limits for recordings, transcriptions, and voice biometric data with contractual deletion guarantees. Ask specifically how Invoca handles call recordings that contain incidental PII (credit cards, SSNs spoken during calls)—is this data automatically redacted before storage and before transmission to integrated platforms? For the advertising integrations, request documentation of exactly what data elements are sent to Google, Meta, and other ad platforms when call conversions are reported. Invoca's HIPAA compliance claim should be backed by a signed BAA if your organization handles protected health information.
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.
Identity stitching
Long-lived identifiers
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