# Flock Search and Association Analytics Flock's public product materials describe search and association functions that extend beyond exact optical recognition of a plate. The relevant question for an investigation is not whether a marketing page names a capability, but whether a particular tenant licensed it, enabled it, used it, retained its results, and logged the query. ## Capability layers | Layer | Publicly described function | Evidence boundary | |---|---|---| | Plate and hot-list search | Exact-plate search, alerting, network sharing, and opt-in National Lookup | A full-plate restriction or required reason is a governance control, not proof of proper use. | | Plate-optional vehicle search | Vehicle Signature, “vehicle fingerprint” attributes, Visual Search, and FreeForm natural-language search | Vendor-described retrieval; no public per-SKU confusion matrix was located. | | Video people search | Search by visible non-facial traits and movement in shared video | Flock calls it non-biometric/no facial recognition; observable traits and associations can still identify or profile. | | Association and pattern tools | Catalog names include convoy, multi-geography, hotspot, and Nova-related services | A catalog listing proves availability for sale on that date, not purchase, configuration, or use. | Flock's current LPR page says Vehicle Signature and FreeForm can produce searchable evidence without a readable plate, while the FreeForm page describes natural-language searching over visible vehicle and people attributes (vendor primary/self-description, [current LPR product page](../../web%20archive/2026-07-20/flocksafety.com/license-plate-readers.md); vendor primary/self-description, [Flock FreeForm](../../web%20archive/2026-07-20/flocksafety.com/flock-freeform.md)). The May 26, 2026 catalog provides the dated SKU/service-name record (official procurement attachment / vendor catalog, [Flock price list](../../web%20archive/2026-07-20/omniapartners.com/r250203-flock-pricing-2026-05-26.md)). Patent language about object fingerprints and similarity search is evidence of claimed embodiments, not proof of production implementation (primary public record, [US 10,795,933](../../web%20archive/2026-07-20/image-ppubs.uspto.gov/us10795933b1.md)). ## Arkansas evidence boundary LRPD's Tier-1 procurement record identifies a renewal amount that included “license plate recognition camera with vehicle fingerprint software” ([[Resolution 16489 and the 30-Cameras Discrepancy]], Emails 1-24.pdf p. 102). Conway's Tier-1 platform notice says vehicle-fingerprint information was removed from the cross-agency Network Audit view ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]], December 2025 notice). Those records establish an Arkansas procurement/use context for vehicle-fingerprint data. They do not establish that FreeForm, people search, Convoy, Multi-Geo, Visual Search, hotspots, or Nova were enabled in those tenants. ## Accuracy and profiling limits No current independent public precision/recall study was located for the named Flock retrieval and association functions across weather, lighting, plate type, camera angle, demographic proxy, or jurisdiction. Marketing examples and successful-case stories are not substitutes for a denominator, false-match rate, miss rate, or stratified validation. Association outputs also introduce distinct risks: a correct object observation can still be linked to the wrong person, trip, group, or investigation. ## Open questions - Produce tenant entitlement/configuration exports showing which analytics were licensed and enabled during each relevant period. - Produce query logs with feature, parameters, confidence settings, reason/case number, result count, user, and downstream action—without republishing subject PII. - Produce validation, threshold-change, model-version, false-match, complaint, and corrective-action records for each enabled function.