How This Briefing Works
This report opens with key findings, then maps the gaps between what Finch 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
Finch was observed loading and executing before user consent was obtained on 14% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown”
Requires claims extraction via CDT
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Finch
- →Demand contractual transparency on employment data retention and access controls
- →Require data processing agreement explicitly prohibiting workforce data sharing for competitive benchmarking
- →Implement worker notification process for all Finch data processing activities
- →Configure HRIS integration to log all external API calls for GDPR Article 30 compliance
If You're Evaluating Finch
- →Request third-party audit of consent bypass mechanisms and session recording practices
- →Evaluate alternative HR data integration tools with documented worker consent flows
- →Consider direct HRIS API integrations to eliminate third-party data aggregation risk
- →Assess whether unified API access justifies worker privacy violation and competitive intelligence leakage
Negotiation Leverage
- →Finch VRS 80 = Broker (65) + Counselor (85) threat. Employment data aggregation = competitive intelligence leakage. Demand data minimization commitments.
- →Session recording (BTI-C07) of HRIS interactions = special category data processing. Require explicit legal basis documentation and worker notification.
- →Consent bypass (BTI-C09) violates GDPR controller transparency. Workers must be notified of all data processing; request technical remediation plan.
- →Employment data sharing across customers for benchmarking = competitive intelligence. Negotiate exclusive data processing or seek alternatives.
- →Ask: What employment data is retained after API call completion? How are worker privacy rights (access, deletion) handled? What is the data breach notification history?
- →Integration convenience must be weighed against worker privacy violations and competitive intelligence risk. Demand legal review before renewal.
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.
Evasion infrastructure, auditor bypass
Impact: Tag-level deception allows Finch to present different data collection behavior to privacy tools versus actual employment data processing, defeating consent mechanisms.
Full session replay
Impact: Full capture of HRIS interactions including benefits enrollment, compensation adjustments, and performance data creates extreme PII exposure risk.
Ignoring CMP signals
Impact: Employment data collection continues without explicit worker consent, violating GDPR controller transparency requirements and creating per-worker violation liability.
Device identification
Impact: Worker identification across multiple employer systems enables employment history tracking that individuals cannot detect or control, violating privacy expectations.
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
93 detection signatures across scripts, domains, cookies, and network endpoints