{"resourceId":"404media-vidizmo-flock-fr-20260929","versions":[{"version":"external-c58efc05bb6001a4df24fa6aaf5c0d18a199beee6b636bfc3000ed95e3d240c3","resource":{"id":"404media-vidizmo-flock-fr-20260929","title":"404 Media: VIDIZMO pitches facial recognition and race/gender filters on Flock camera data Flock says it will not offer","organization":"404 Media","sector":"Independent investigative technology journalism","geography":"United States (Johnson City, Tennessee pitch; national Flock footprint)","publishedAt":"September 29, 2026","publicationDate":"2026-09-29","eventDate":"2026-09-29","sourceName":"404 Media","sourceLabel":"404 Media investigation on VIDIZMO sales pitch to add FR/behavior/race-gender analysis to Flock/Axon data","sourceUrl":"https://www.404media.co/surveillance-company-tells-cops-it-wants-to-add-facial-recognition-to-flock-cameras/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["infrastructure","data-security","governance-procurement","operating-model"],"finding":"On Sept. 29, 2026, 404 Media reported that VIDIZMO is advertising export of FlockOS footage into its platforms for facial recognition, behavior prediction, and racial/gender analysis, pitching Johnson City, Tennessee’s deputy police chief in a May email (obtained by DeFlock Johnson City) that VIDIZMO Intelligence Hub “closes that gap” between Flock plate/clips and Axon evidence with search “by face, vehicle, or object.” Flock CEO Garrett Langley has said the company will not add facial recognition to its devices. VIDIZMO CEO Nadeem Khan told 404 Media the company has not yet run FR on Flock footage and has not built the specific export tool advertised, but “would love to do the integration,” claims agencies can import plate reads/clips under their own access without informing Flock, and markets age/gender/race attribute filters across seven race categories. Johnson City PD said it did not take a call with the company. Privacy expert Chris Gilliard called the race/gender filters appalling and argued Flock’s infrastructure enables more invasive third-party layers regardless of Flock’s own FR pledge. Flock and Axon did not comment.","sledRelevance":"Policing surveillance ecosystem risk: ALPR/camera grids as substrate for third-party biometric AI beyond primary vendor promises.","evidence":"404 Media Sept. 29 piece with public-records email excerpts, on-record CEO interview, vendor documentation quotes, Johnson City PD statement, and Gilliard critique; notes integration not yet built/operational on Flock footage.","architectureImplications":"If agencies can export Flock clips under their own credentials into third-party FR hubs, procurement must control egress, watchlist enrollment, and attribute search—not only Flock device feature flags.","governanceImplications":"Vendor “we will not do FR” statements are insufficient when resellers/startups pitch gap-closing; councils need export bans, secondary-processor clauses, and public notice before any biometric overlay.","securityPrivacyImplications":"Race/gender/age classifiers plus live watchlist naming amplify misidentification and discriminatory query risk; CEO claims of case-number and audit logging are unverified here; Flock not informed of imports per Khan.","caveats":"Integration not built/operational per CEO; May email is older than publication but newly reported Sept. 29; Johnson City declined engagement; Flock/Axon no comment; marketing docs may overclaim.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: the Sept. 29 VIDIZMO story is a secondary-processor discovery trigger—customers who believe Flock’s no-FR pledge still need export controls, biometric overlay bans, and watchlist governance. Sell an egress and secondary-AI contract review plus a public biometric policy, not a new FR product. Unsupported claims include that VIDIZMO FR is already live on Flock nationwide, or that Flock’s pledge alone blocks third parties from analyzing exported clips.","engineering":"Engineering framing: inventory Flock and Axon export paths; block or ticket bulk clip export to unknown AI hubs; require secondary-processor clauses for any analytics tool; disable race/gender attribute search if any tool is trialed. Prerequisites include an export allowlist and download audit logging. Proof of value is a negative test showing a VIDIZMO-style import cannot silently proceed under agency credentials without approval.","delivery":"Delivery framing: issue a cease-and-policy notice on third-party facial-recognition overlays, update procurement prohibited-uses language, train investigators that watchlist facial recognition is out of policy unless council-authorized, and brief command using the Johnson City email as a tabletop. Ownership sits with the evidence custodian and city attorney for secondary-processor clauses. Risk includes shadow IT pilots that reintroduce biometrics under ordinary investigation-tool labels."},"roleDetails":{"sales":{"customerProblem":"Agencies relying on Flock’s no-facial-recognition pledge face third parties pitching FR, behavior, and race/gender search on exported Flock/Axon data.","stakeholders":["Police chief/CIO","City attorney","City council","Privacy officer","Prosecutors","Community advocates","Primary vendors Flock/Axon"],"discoveryQuestions":["What export paths exist from FlockOS/Axon to third-party AI tools today?","Does policy ban biometric overlays on ALPR/BWC exports?","Who would authorize watchlist enrollment and match thresholds?","Are race/gender attribute filters prohibited?"],"valueHypothesis":"Bounded value is contractual and technical egress control that makes third-party FR a deliberate, council-visible decision—not a sales email.","potentialEngagement":"3–5 week secondary-processor and egress-control review with policy redlines and negative testing plan.","unsupportedClaims":["That VIDIZMO FR is operational on Flock cameras today","That Flock’s pledge technically prevents third-party FR","That Johnson City adopted VIDIZMO","Accuracy of race/gender classifiers"]},"engineering":{"fit":"Flock/Axon agencies whose investigators can export clips and who receive third-party AI pitches.","architectureIntegration":"Flock/Axon evidence through a controlled export gateway to allowlisted processors only; block ad-hoc FR hubs; log every bulk export; separate identity gallery governance if ever authorized.","prerequisites":["Export inventory","Contract secondary-use prohibitions","Identity gallery policy (default deny)","Audit logging on downloads"],"constraints":["Integration advertised but not built per VIDIZMO CEO","Agencies can import under own access without informing Flock","Marketing claims of race/gender filters","No Flock/Axon comment"],"security":"Default deny biometric secondary processing; require case-bound exports; prohibit race/gender attribute search; monitor for shadow AI tools.","proofOfValue":["Completed egress inventory","Blocked test of unauthorized FR import path","Council-facing secondary-processor register"]},"delivery":{"work":"Inventory exports, update prohibited-use policy, brief council, and run a tabletop on third-party FR pitches.","dependencies":["Evidence platform admins","City attorney","Procurement","Internal affairs/audit"],"ownership":"Police CIO/evidence custodian with city attorney co-owner for secondary-processor clauses.","skillsAdoption":"Train investigators not to enroll faces into third-party libraries; train procurement to spot gap-closing FR pitches.","governanceCheckpoints":["Policy update approved","Egress allowlist published internally","Council brief on biometric overlay risk"],"acceptanceCriteria":["Written ban on unauthorized FR overlays","Export logging enabled","No shadow VIDIZMO-style pilot without council action"],"risks":["Silent investigator pilots","Vendor marketing outrunning built capability (false comfort either way)","Discriminatory attribute search if filters enabled"]}},"retrievedAt":"2026-09-30T02:58:44Z","enrichedAt":"2026-09-30T03:06:44Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Investigators need clear ban guidance; privacy officers need capacity to review AI vendor pitches; councils need plain-language briefings on secondary biometric layers.","procurementImplications":"Add secondary-processor and export-control clauses to ALPR/BWC contracts; treat “no FR on device” as insufficient without egress limits.","operatingModelImplications":"Assume surveillance ecosystems attract gap-closing vendors; make biometric overlays an explicit council decision with public notice.","sourceVerification":{"openedUrl":"https://www.404media.co/surveillance-company-tells-cops-it-wants-to-add-facial-recognition-to-flock-cameras/","referenceExcerpt":"has not yet started running facial recognition tech on footage from Flock cameras","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}