# Flock Audio Detection and Raven Raven, now marketed as Flock Audio Detection, is an acoustic-event sensor. The current vendor account, an older device teardown, and reporting about a discontinued human-distress pilot must be kept separate by date and evidence type. ## Current vendor account, July 2026 Flock says the sensor continuously processes roughly five-second rolling windows on-device; nonmatching audio is not retained, while a qualifying event produces an encrypted short clip, localization, and an alert. The vendor says there is no customer live-audio feed, while acknowledging that incidental nearby words can enter a qualifying event clip. It also says a confirmed event can surface vehicles seen near the event through nearby Flock LPR cameras (vendor primary/self-description, [How Flock's Audio Detection works](../../web%20archive/2026-07-20/flocksafety.com/how-flocks-audio-detection-works.md)). These statements describe the vendor's current design and policy; they are not an independent classifier, retention, or access-control audit. The same July 2026 account says a limited pilot attempted to detect human distress, including screaming, was never broadly released, and was removed. EFF independently reported that Flock ended the distress-detection rollout (vendor primary/self-description, [Flock Audio Detection account](../../web%20archive/2026-07-20/flocksafety.com/how-flocks-audio-detection-works.md); web research 2026-07-20, [EFF report](../../web%20archive/2026-07-20/eff.org/flock-ends-audio-distress-detection-human-voices.md)). Historical claims about that pilot must not be written as current capability. ## Version-specific technical evidence A public security teardown identifies the examined device as Raven model v1.2 with a particular package, firmware, and application version and describes ESP32/Syntiant components. It does not establish the architecture of later Audio Detection devices (third-party security research, [Raven v1.2 teardown](../../web%20archive/2026-07-20/gainsec.com/raven-v1-2-teardown.md)). The associated public vulnerability records are summarized at [[Vendor Information Security Posture]]. ## Arkansas evidence boundary The LRPD corpus contains [[SoundThinking ShotSpotter and CaseBuilder Correspondence]], documenting a different acoustic-detection vendor. That is not evidence LRPD bought Raven. No Tier-1 Arkansas record currently establishes Flock Audio Detection deployment, its event classes, retention, diagnostic sampling, or its LPR-association settings at an Arkansas agency. ## Open questions - Do any Arkansas agencies possess Raven/Audio Detection solicitations, trials, orders, maps, calibration tests, classifier audits, or event logs? - What model/build and event classes are in service, and what clips or diagnostic samples are retained, by whom, and for how long? - Are nearby-vehicle associations enabled, and are those queries and results independently audited?