From the Public Safety edition of September 29, 2026
404 Media: VIDIZMO pitches facial recognition and race/gender filters on Flock camera data Flock says it will not offer
404 Media · Independent investigative technology journalism · United States (Johnson City, Tennessee pitch; national Flock footprint)
- Publisher
- 404 Media
- Original publication
- September 29, 2026
- Source retrieved
- 2026-09-30
- Event date
- 2026-09-29
What happened
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.
Why it matters
Policing surveillance ecosystem risk: ALPR/camera grids as substrate for third-party biometric AI beyond primary vendor promises.
Evidence and measured results
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.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- Bounded value is contractual and technical egress control that makes third-party FR a deliberate, council-visible decision—not a sales email.
- Potential engagement
- 3–5 week secondary-processor and egress-control review with policy redlines and negative testing plan.
- Unsupported claims
- 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
Pre-sales engineering
Role takeaway
- Fit
- Flock/Axon agencies whose investigators can export clips and who receive third-party AI pitches.
- Architecture and integration
- 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.
- Proof of value
- Completed egress inventory
- Blocked test of unauthorized FR import path
- Council-facing secondary-processor register
Delivery
Role takeaway
- 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.
- Skills and adoption
- Train investigators not to enroll faces into third-party libraries; train procurement to spot gap-closing FR pitches.
- Governance checkpoints
- Policy update approved
- Egress allowlist published internally
- Council brief on biometric overlay risk
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
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.
Security and privacy
What data, permissions and controls need testing?
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.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Investigators need clear ban guidance; privacy officers need capacity to review AI vendor pitches; councils need plain-language briefings on secondary biometric layers.
Procurement
What should contracts, pricing and exit terms secure?
Add secondary-processor and export-control clauses to ALPR/BWC contracts; treat “no FR on device” as insufficient without egress limits.
Operating model
Which teams own the service once it runs?
Assume surveillance ecosystems attract gap-closing vendors; make biometric overlays an explicit council decision with public notice.
Publication history
- 2026-09-29Public Safety · Issue 234 resources
Stable resource ID: 404media-vidizmo-flock-fr-20260929