Current ALPR location/direction entries73Published entries — not a verified camera count
Original 2019 proposed locations37Public RFP announcement
Confirmed / implementing technology categories4Other products are contracted or announced but not yet verified deployed
10-year Safe City payment schedule$6.92MPublic contract; cover-page discrepancy remains flagged
ROUTE EXPOSURE ESTIMATOR

How visible is your drive?

Choose a start and destination to compare your route with estimated ALPR reference points derived from the City of Mt. Juliet’s published Guardian Shield “Active ALPR Locations” list. The dots are approximate grouped locations—not exact camera coordinates—and one dot does not necessarily equal one physical camera.

Estimated locationsGrouped map pointsRoute proximity only

This tool is for estimation, not exact camera tracking. Passing near a mapped point does not prove that a camera was aimed at your lane, operating, read your plate, or captured an image.

Try the route estimatorManual mode keeps your drawn route out of geocoding and routing services.
PUBLIC VERIFIABILITY

Provisional transparency score

This score measures how easily a resident can independently verify scope, spending, rules, sharing, audits, outcomes and governance. It does not score legality, police integrity, crime reduction, or whether the technology should exist.

55/100

System inventory & scope

8 / 15
Partial

Public: Current ALPR location/direction list; DFR page; police acknowledges city-wide LPR and camera networks.

Gap: No consolidated product-by-product deployment inventory; no authoritative physical ALPR camera count; Condor/Raven/mobile/integration quantities are not publicly enumerated; no camera/feed-level disclosure of AI feature activation.

Improve: Publish an annual inventory by product/device/feed with physical count, location, ownership, activation date, funding source, Flock integration status, and enabled AI/automation features.

Primary source

Spending & procurement

11 / 15
Good but incomplete

Public: Major Flock contract, payment schedule and Board approval records are public.

Gap: No single actual-spending/invoice ledger; original Rekor procurement/transition is incomplete in one place; public Flock order form contains a corrected/uncorrected total discrepancy.

Improve: Publish invoices, amendments, grants and cumulative actual spend in one annual technology report.

Primary source

Rules & legal documents

15 / 20
Good but fragmented

Public: City ordinance, current ALPR general order, state-law references and contract are publicly accessible.

Gap: Prior policy versions/redlines are not presented together; broader Safe City products do not have one consolidated governance framework comparable to the ALPR policy; public rules for Guardian Mode, people detection, FreeForm video search and AI on integrated cameras are not clearly identified.

Improve: Publish policy history/redlines and technology-specific rules for video integration, automated PTZ tracking, people detection/alerts, AI video search, acoustic sensors, drones and other Safe City features.

Primary source

Access & data-sharing transparency

8 / 15
Partial

Public: MJPD describes sharing standards and publishes an access-agreement/transparency area.

Gap: No aggregate outside-agency query counts; no public inventory of integrated private/public video feeds; actual FlockOS network sharing and outside-jurisdiction video settings are not disclosed; AI-enabled/shared video-feed configuration is not public.

Improve: Publish sharing configuration, connected-feed inventory, AI-enabled feed list, agencies with access by data type, request/query counts and revocations.

Primary source

Audit & compliance publication

5 / 20
Major verification gap

Public: Current policy contains detailed audit/logging requirements and says administrators audit every 30 days.

Gap: No recurring public monthly audit results or completed annual ALPR report was located in this review; the public cannot see audit sample size, exceptions, unauthorized use or corrective action.

Improve: Publish monthly aggregate audit metrics plus the annual report already contemplated by policy; add periodic independent audit.

Primary source

Use & outcome reporting

6 / 10
Partial

Public: MJPD publishes successful-interception examples and frequent public-safety announcements.

Gap: Success examples are agency-selected and do not provide a denominator for all alerts, searches, stops, false alerts or no-action outcomes.

Improve: Publish total alerts/searches/stops, verified hits, no-action outcomes, false/incorrect alerts, investigations assisted and disposition metrics.

Primary source

Public governance & change control

2 / 5
Limited

Public: Major contracts and Board votes are public records.

Gap: Product-level activation can occur under a broad Safe City agreement; major items have sometimes had little recorded public discussion; no clear public impact-review trigger for adding a new surveillance/data capability or enabling materially different AI features on existing cameras.

Improve: Require Board/public notice for major new data types, integrations, retention changes, automated person/vehicle tracking, AI video search/alerts or sharing expansions and publish impact assessments.

Primary source
How the score is built Each category shows what is public, what is missing, and what would improve the score. The score is intended to change as new verifiable audit reports, inventories, spending records, or other public documentation become available.
SAFE CITY TECHNOLOGY EXPLORER

What can the system actually do?

Start with a question, then open a technology card. The first view stays simple; the evidence, AI features, retention, sharing and unresolved configuration questions are one click deeper.

Confirmed deployed / implementingPublicly announcedContracted / available capability
License plate recognitionConfirmed deployed

Flock Safety LPR — Codename: Falcon

Reads plates & vehicle details

Captures plate/vehicle images and supports hot-list alerts, historical searches and vehicle-description searches.

PUBLICLY IDENTIFIED SCOPE73 public location/direction entries; exact physical unit count unknown
Explore capabilities & evidence
Evidence status
Confirmed local deployment
Data / sensor
Images, license plates, vehicle characteristics, date/time/location
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
MJPD current policy: 7 days unless tied to an active investigation/case; 2025 order form states 30 days.
Third-party integration
FlockOS supports community network access and broader LPR network sharing.
Outside-agency capability
Contract includes state/nationwide plate lookup and direct-access requests to other law-enforcement devices.
Actual Mt. Juliet sharing
MJPD publishes agencies with access agreements; exact query volume and network configuration are not public on the city page.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

Do not equate 73 public entries with 73 distinct physical Falcons until device inventory is obtained.

Open primary source ↗
Live / recorded videoContracted capability; deployment quantity not verified

Flock Safety Video Camera PTZ — Codename: Condor

Remote pan / tilt / zoom video

Live-streamed pan/tilt/zoom video with edge storage and VMS. Flock video cameras can also support configurable AI video analytics.

MT. JULIET CONFIGURATION

Not publicly verified. No Mt. Juliet source located in this review states whether Guardian Mode, People Detection Alerts, Visual Alerts or FreeForm are enabled on any local Condor/PTZ camera.

Explore capabilities & evidence
Evidence status
Product is in city Flock contract; exact deployment not verified
Data / sensor
Live and recorded video
AI / automation
Flock says its PTZ video cameras can use Guardian Mode to automatically detect and locate people or vehicles, zoom in, follow movement within the camera field of view, and capture detailed imagery. Flock also lists People Detection Alerts, Visual Alerts and FreeForm among its video-camera AI features.
Retention / storage
Contract describes 30 days of edge storage.
Third-party integration
Can appear with other video sources in FlockOS.
Outside-agency capability
FlockOS contract feature set includes access to live/recorded video outside agency jurisdiction when enabled/shared.
Actual Mt. Juliet sharing
Which Mt. Juliet Condor feeds, if any, are shared outside MJPD has not been publicly verified.
What would verify the local setup?
Condor/PTZ count and locations; feature enablement by camera; Guardian Mode schedules/zones; People Detection/Visual Alert settings; FreeForm enablement; retention; users/roles; audit logs and external sharing configuration.Open question

Automated PTZ following within a camera field of view is different from facial recognition or proving continuous citywide identity tracking. The local configuration remains the key unanswered question.

Open primary source ↗
AI video analyticsAvailable Flock capability; Mt. Juliet activation unknown

Guardian Mode — automated PTZ subject tracking

Automatically follows a subject in view

Available for Flock PTZ cameras. Flock says Guardian Mode automatically detects and locates people and vehicles, zooms in, follows movements within the camera field of view, and captures detailed imagery without a camera operator continuously steering the PTZ.

MT. JULIET CONFIGURATION

Not publicly verified. No public Mt. Juliet record located states whether Guardian Mode is enabled or disabled on local Condor/PTZ cameras.

Explore capabilities & evidence
Evidence status
Flock capability confirmed; Mt. Juliet enablement not publicly verified
Data / sensor
AI analysis of PTZ video; people/vehicle detection and automated camera movement
AI / automation
Automatic within-field-of-view person/vehicle acquisition, PTZ following/zooming and evidence capture.
Retention / storage
Underlying video-camera retention/configuration applies; Mt. Juliet local Guardian Mode retention effects are not separately published.
Third-party integration
Flock documentation reviewed describes Guardian Mode for Flock PTZ cameras. This review did not establish that Wing can add Condor-style automatic pan/tilt/zoom following to an ordinary third-party PTZ camera.
Outside-agency capability
If resulting video is shared through FlockOS, authorized outside users may have access depending on sharing settings; Guardian Mode-specific outside access is not publicly established for Mt. Juliet.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Whether Guardian Mode is enabled; number/location of enabled cameras; schedules/areas where enabled; policy and training; users able to configure it; audit logs; sharing/access settings.Open question

This is not facial recognition. It is also narrower than continuous identity tracking across the city: the documented feature follows a detected subject within the PTZ camera’s view.

Open primary source ↗
Live / recorded videoPublicly announced; device inventory not published

City-wide fixed camera network

Extends the city camera network

Fixed public-safety video cameras across the city, including cameras observed/referenced at public facilities and parks. The city has not published a consolidated model/location inventory.

MT. JULIET CONFIGURATION

Unknown. Mt. Juliet does not publicly identify which existing city cameras are connected to FlockOS/Wing, which feeds have AI processing enabled, or which are enabled for FreeForm people/video search.

Explore capabilities & evidence
Evidence status
MJPD recruiting page confirms a “City-Wide Camera Network”; product models/locations incomplete
Data / sensor
Video
AI / automation
If compatible city-owned cameras are connected through Flock video integration, Flock says enabled third-party video feeds can receive AI-driven analytics and can be searchable with FreeForm using visible, non-biometric characteristics such as clothing or accessories. This does not establish Condor-style automatic PTZ following on ordinary third-party cameras.
Retention / storage
Varies by system; not established here.
Third-party integration
Potentially integrable into FlockOS if connected through Flock video integration products.
Outside-agency capability
Unknown for Mt. Juliet configuration.
Actual Mt. Juliet sharing
Not publicly verified by feed or camera.
What would verify the local setup?
Inventory of city video cameras; model/location/owner; whether each feed is connected to Flock; gateway/channel assignment; AI features enabled; FreeForm eligibility; retention; sharing/access by agency.Open question

Keep this inventory separate from ALPR so a park video camera is not accidentally counted as a Falcon.

Open primary source ↗
Third-party camera integrationContracted capability; activation not verified

Flock Video Integration Gateway 2.0 — Codename: Wing

Brings existing cameras into Flock

Connects existing third-party cameras/video systems to the Flock platform; local order form describes a 16-stream gateway with 16TB storage and 8-channel AI capability.

MT. JULIET CONFIGURATION

Contracted capability; actual deployment/configuration not publicly verified. The public record reviewed does not identify how many gateways are installed, which feeds occupy the available channels, or which channels have AI enabled.

Explore capabilities & evidence
Evidence status
Capability explicitly in contract; local enablement/sharing unknown
Data / sensor
Third-party live/recorded video
AI / automation
Mt. Juliet’s order form describes a 16-stream gateway with 8-channel AI capability. Flock says Wing Gateway 2.0 adds AI-driven analytics to integrated third-party video; compatible enabled feeds can also work with FreeForm.
Retention / storage
Contract description states 30 days of storage for the gateway product.
Third-party integration
Yes — core purpose is integrating non-Flock/public/private video feeds.
Outside-agency capability
The same contracted FlockOS feature set says agencies can view shared live/recorded footage from neighboring agencies, schools, traffic cameras and third-party feeds.
Actual Mt. Juliet sharing
No public evidence located establishing which Mt. Juliet integrated feeds are actually available to outside agencies.
What would verify the local setup?
Gateway quantity/serial inventory; each connected feed; AI-enabled channel list; analytics enabled per feed; FreeForm enablement; retention configuration; outside-agency/shared-video permissions.Open question

This is the key bridge between Mt. Juliet’s existing non-Flock cameras and the broader Flock ecosystem. Contract capability does not prove a particular camera/feed is connected or AI-enabled.

Open primary source ↗
AI / investigative searchContracted capability; activation not verified

FreeForm AI search

Searches video using plain-language descriptions

Natural-language search across enabled video and LPR evidence. For people, Flock says searches use observable non-biometric characteristics such as clothing and visible accessories; people search is not available on LPR-only feeds.

MT. JULIET CONFIGURATION

Contracted capability; Mt. Juliet activation and feed-level configuration are not publicly verified. It is not publicly clear whether any city-owned non-Flock camera is enabled for FreeForm people search or alerts.

Explore capabilities & evidence
Evidence status
Flock product capability confirmed; included in Mt. Juliet contract; local activation/configuration not verified
Data / sensor
Searches LPR images/video metadata and imagery
AI / automation
Searches enabled video for descriptions such as a person’s clothing/accessories and can provide configurable alerts when potentially relevant matches appear. Flock says compatible third-party video integrations can be used when setup requirements are met.
Retention / storage
Underlying source retention applies.
Third-party integration
Yes — Flock’s current FreeForm documentation says compatible third-party video integrations can be searched when setup compatibility requirements are met and the feeds are enabled.
Outside-agency capability
Flock says authorized users may search permission-based shared footage from participating agencies or other approved partners where sharing is enabled.
Actual Mt. Juliet sharing
Unknown for Mt. Juliet, including whether FreeForm can search any externally shared or locally integrated video feeds.
What would verify the local setup?
Whether FreeForm is enabled; authorized users/roles; enabled cameras/feeds; people-search and alert configuration; query justification requirements; search/audit logs; cross-agency/shared-feed permissions.Open question

Flock states FreeForm does not use facial recognition or biometric person recognition.

Open primary source ↗
Public-private integrationProgram capability publicly described; exact connected inventory unknown

Community Network / private-camera partnerships

Connects private camera partners

Allows private Flock customers/partners to share footage or, under contracted FlockOS features, allows law enforcement to request access to privately owned Flock LPR feeds.

Explore capabilities & evidence
Evidence status
Current MJPD page + Flock contract capability
Data / sensor
Private LPR/video feeds when owners opt in/share
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Depends on source system and agreement.
Third-party integration
Yes.
Outside-agency capability
Potentially, depending on the owner’s sharing settings and law-enforcement network configuration.
Actual Mt. Juliet sharing
MJPD says private customers cannot access law-enforcement data; exact downstream access to private feeds by outside agencies has not been publicly established.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

A records request should ask for registered/integrated camera counts, MOUs, sharing settings and outside-agency access rules.

Open primary source ↗
Operations / data platformContracted

FlockOS Premium

Puts sensors, alerts & video on one screen

Central operational interface combining LPR, video, audio, maps, alerts, audits and integrations.

MT. JULIET CONFIGURATION

Mt. Juliet-specific feature configuration is not fully public.

Explore capabilities & evidence
Evidence status
Included in contract
Data / sensor
Aggregates data from connected systems
AI / automation
FlockOS can unify connected LPR, video and other data sources. AI/search features depend on the products and permissions enabled in the account.
Retention / storage
Depends on underlying data source/product.
Third-party integration
Yes — contract lists public/private video, CAD, AVL, body-camera location and other integrations.
Outside-agency capability
Yes at platform capability level, including law-enforcement network access and outside-jurisdiction video where enabled.
Actual Mt. Juliet sharing
Mt. Juliet-specific settings are not fully public.
What would verify the local setup?
Enabled modules, connected data sources, role permissions, sharing settings and audit/reporting configuration.Open question

The existence of a feature in FlockOS does not prove MJPD has enabled it.

Open primary source ↗
911 / real-time responseConfirmed deployed

Flock911

Brings live 911 context into FlockOS

Delivers live 911 call information into FlockOS to provide real-time context to responding personnel.

PUBLICLY IDENTIFIED SCOPEAgency-wide software integration; exact user count unknown
Explore capabilities & evidence
Evidence status
MJPD publicly announced deployment after testing
Data / sensor
911 call audio/context/location information
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Not established here.
Third-party integration
Integrates 911/CAD context into FlockOS.
Outside-agency capability
Not established for Mt. Juliet.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

This is not an ALPR camera, but it demonstrates that the Safe City platform now extends well beyond plate readers.

Open primary source ↗
Acoustic detectionContracted capability; local activation not verified

Flock Safety Gunshot Detection (formerly Raven)

Listens for suspected gunfire

Detects acoustic signatures associated with gunfire and generates location-based alerts.

PUBLICLY IDENTIFIED SCOPEUnknown; contract licenses by coverage area, not unit count
Explore capabilities & evidence
Evidence status
Included in Mt. Juliet Flock contract; deployment not independently confirmed
Data / sensor
Acoustic sensor events
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Not established from the local order form excerpt.
Third-party integration
FlockOS contract describes unified LPR, video and audio alerts.
Outside-agency capability
Platform-level sharing/integration capabilities exist; local Raven-sharing configuration not verified.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

Do not call every observed “listening device” a Raven without model/location confirmation.

Open primary source ↗
Acoustic detectionPublicly announced as Safe City technology

Acoustic car-crash detection

Listens for possible crashes

Acoustic detection associated with crash-response technology, as described by MJPD in its Safe City/Flock911 announcement.

Explore capabilities & evidence
Evidence status
Public announcement; exact hardware/product configuration needs verification
Data / sensor
Acoustic event detection
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Unknown
Third-party integration
Part of broader Safe City ecosystem as publicly described.
Outside-agency capability
Unknown.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

Track separately from Raven gunshot detection unless the city confirms they use the same hardware.

Open primary source ↗
Mobile video / deterrenceContracted capability; local Flock trailer deployment not verified

Flock Mobile Security Trailer

Moves PTZ video where needed

Mobile trailer with deterrence light, two PTZ cameras, 360-degree multisensor camera and audio talk-down.

Explore capabilities & evidence
Evidence status
Included in contract; do not equate every MJPD surveillance tower with this product
Data / sensor
Video / audio talk-down
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Not established separately in local contract description.
Third-party integration
Integrated with Flock platform.
Outside-agency capability
Depends on sharing configuration.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

Needs serial/model/site confirmation before adding a local quantity.

Open primary source ↗
Drone / aerial videoConfirmed implementation/testing

Flock Aerodome Drone as First Responder

Sends drones to active calls

Dispatches drones to active calls and transmits live aerial video to responders/command staff.

PUBLICLY IDENTIFIED SCOPE2 strategically placed drone docks; city DFR page describes two operational coverage locations
Explore capabilities & evidence
Evidence status
Confirmed local DFR program
Data / sensor
Live aerial video, telemetry, flight logs
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Per DFR policy/portal; exact local retention should be tracked separately.
Third-party integration
FlockOS contract integrates drone live video/GPS.
Outside-agency capability
Assistance to other public-safety agencies is described; live feed sharing specifics should be verified.
Actual Mt. Juliet sharing
Not fully documented on public page.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

City page says active-incident use, not random patrol, and promises a public flight transparency portal once launched.

Open primary source ↗
Radar / airspace sensingConfirmed implementation/testing

Flock Aerodome DFR Radar

Monitors airspace for drone operations

Detect-and-avoid / airspace monitoring supporting beyond-visual-line-of-sight drone operations.

PUBLICLY IDENTIFIED SCOPE1 radar described as providing citywide coverage
Explore capabilities & evidence
Evidence status
Confirmed on city DFR page
Data / sensor
Radar and airspace sensor data
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Not established on public program page.
Third-party integration
Integrated with DFR platform.
Outside-agency capability
Not relevant/unknown.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

The Flock drone contract also references radar and radio-frequency sensor data as Flock Drone IP.

Open primary source ↗
Data integration / intelligenceContracted capability; usage not verified

Flock Nova — Customer Data / OSINT

Combines agency and open-source data

Centralizes agency CAD/RMS/digital evidence data and, separately, offers open-source intelligence/shared inter-agency data.

PUBLICLY IDENTIFIED SCOPESoftware subscription capability
Explore capabilities & evidence
Evidence status
Included in contract
Data / sensor
Agency records, dispatch, digital evidence, OSINT and shared data
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Not established in local order-form description.
Third-party integration
Yes.
Outside-agency capability
Shared inter-agency data is part of the described capability.
Actual Mt. Juliet sharing
Specific Mt. Juliet datasets and connections not publicly verified.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

This is broader than ALPR and should have its own governance/records questions.

Open primary source ↗
Traffic analyticsContracted capability; activation not verified

Traffic Analytics

Counts and categorizes traffic

Aggregates vehicle counts in 15-minute bins and supports breakdowns by class, state and make.

Explore capabilities & evidence
Evidence status
Included in contract
Data / sensor
Aggregate vehicle-count analytics
AI / automation
No additional AI/automation capability established in this inventory beyond the product description.
Retention / storage
Contract says aggregate counts may be hosted up to 5 years.
Third-party integration
Part of Flock platform.
Outside-agency capability
Unknown.
Actual Mt. Juliet sharing
Unknown.
What would verify the local setup?
Product-specific configuration/deployment records as needed to verify local use.Open question

This retention is for aggregate analytics and should not be confused with individual ALPR plate-read retention.

Open primary source ↗
Condor AI question: Flock documents Guardian Mode as an available PTZ feature that can automatically detect and follow people or vehicles within the camera’s field of view. This project has not located a public Mt. Juliet record stating whether Guardian Mode, People Detection Alerts, Visual Alerts or FreeForm are enabled on local Condor/PTZ cameras.
Existing-camera AI question: Mt. Juliet’s contract includes a video-integration gateway with 8-channel AI capability, and Flock says compatible third-party feeds can receive AI analytics and FreeForm search. What remains unknown is which city/private feeds are actually connected, which have AI enabled, and whether those feeds are shared outside MJPD.
POWER-USER VIEWView the full comparison tableAll fields side by side — best on a large screen.
Product / systemCategoryEvidence statusQuantityWhat it doesDataRetentionThird-party integrationOutside-agency capabilityActual Mt. Juliet sharingAI / automation capabilityMt. Juliet AI statusSource
Flock Safety LPR — Codename: Falcon
Do not equate 73 public entries with 73 distinct physical Falcons until device inventory is obtained.
License plate recognitionConfirmed deployed
Confirmed local deployment
73 public location/direction entries; exact physical unit count unknownCaptures plate/vehicle images and supports hot-list alerts, historical searches and vehicle-description searches.Images, license plates, vehicle characteristics, date/time/locationMJPD current policy: 7 days unless tied to an active investigation/case; 2025 order form states 30 days.FlockOS supports community network access and broader LPR network sharing.Contract includes state/nationwide plate lookup and direct-access requests to other law-enforcement devices.MJPD publishes agencies with access agreements; exact query volume and network configuration are not public on the city page.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Flock Safety Video Camera PTZ — Codename: Condor
Automated PTZ following within a camera field of view is different from facial recognition or proving continuous citywide identity tracking. The local configuration remains the key unanswered question.
Live / recorded videoContracted capability; deployment quantity not verified
Product is in city Flock contract; exact deployment not verified
UnknownLive-streamed pan/tilt/zoom video with edge storage and VMS. Flock video cameras can also support configurable AI video analytics.Live and recorded videoContract describes 30 days of edge storage.Can appear with other video sources in FlockOS.FlockOS contract feature set includes access to live/recorded video outside agency jurisdiction when enabled/shared.Which Mt. Juliet Condor feeds, if any, are shared outside MJPD has not been publicly verified.Flock says its PTZ video cameras can use Guardian Mode to automatically detect and locate people or vehicles, zoom in, follow movement within the camera field of view, and capture detailed imagery. Flock also lists People Detection Alerts, Visual Alerts and FreeForm among its video-camera AI features.Not publicly verified. No Mt. Juliet source located in this review states whether Guardian Mode, People Detection Alerts, Visual Alerts or FreeForm are enabled on any local Condor/PTZ camera.
Records needed: Condor/PTZ count and locations; feature enablement by camera; Guardian Mode schedules/zones; People Detection/Visual Alert settings; FreeForm enablement; retention; users/roles; audit logs and external sharing configuration.
Open
City-wide fixed camera network
Keep this inventory separate from ALPR so a park video camera is not accidentally counted as a Falcon.
Live / recorded videoPublicly announced; device inventory not published
MJPD recruiting page confirms a “City-Wide Camera Network”; product models/locations incomplete
UnknownFixed public-safety video cameras across the city, including cameras observed/referenced at public facilities and parks. The city has not published a consolidated model/location inventory.VideoVaries by system; not established here.Potentially integrable into FlockOS if connected through Flock video integration products.Unknown for Mt. Juliet configuration.Not publicly verified by feed or camera.If compatible city-owned cameras are connected through Flock video integration, Flock says enabled third-party video feeds can receive AI-driven analytics and can be searchable with FreeForm using visible, non-biometric characteristics such as clothing or accessories. This does not establish Condor-style automatic PTZ following on ordinary third-party cameras.Unknown. Mt. Juliet does not publicly identify which existing city cameras are connected to FlockOS/Wing, which feeds have AI processing enabled, or which are enabled for FreeForm people/video search.
Records needed: Inventory of city video cameras; model/location/owner; whether each feed is connected to Flock; gateway/channel assignment; AI features enabled; FreeForm eligibility; retention; sharing/access by agency.
Open
Flock Safety Gunshot Detection (formerly Raven)
Do not call every observed “listening device” a Raven without model/location confirmation.
Acoustic detectionContracted capability; local activation not verified
Included in Mt. Juliet Flock contract; deployment not independently confirmed
Unknown; contract licenses by coverage area, not unit countDetects acoustic signatures associated with gunfire and generates location-based alerts.Acoustic sensor eventsNot established from the local order form excerpt.FlockOS contract describes unified LPR, video and audio alerts.Platform-level sharing/integration capabilities exist; local Raven-sharing configuration not verified.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Acoustic car-crash detection
Track separately from Raven gunshot detection unless the city confirms they use the same hardware.
Acoustic detectionPublicly announced as Safe City technology
Public announcement; exact hardware/product configuration needs verification
UnknownAcoustic detection associated with crash-response technology, as described by MJPD in its Safe City/Flock911 announcement.Acoustic event detectionUnknownPart of broader Safe City ecosystem as publicly described.Unknown.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Flock Video Integration Gateway 2.0 — Codename: Wing
This is the key bridge between Mt. Juliet’s existing non-Flock cameras and the broader Flock ecosystem. Contract capability does not prove a particular camera/feed is connected or AI-enabled.
Third-party camera integrationContracted capability; activation not verified
Capability explicitly in contract; local enablement/sharing unknown
UnknownConnects existing third-party cameras/video systems to the Flock platform; local order form describes a 16-stream gateway with 16TB storage and 8-channel AI capability.Third-party live/recorded videoContract description states 30 days of storage for the gateway product.Yes — core purpose is integrating non-Flock/public/private video feeds.The same contracted FlockOS feature set says agencies can view shared live/recorded footage from neighboring agencies, schools, traffic cameras and third-party feeds.No public evidence located establishing which Mt. Juliet integrated feeds are actually available to outside agencies.Mt. Juliet’s order form describes a 16-stream gateway with 8-channel AI capability. Flock says Wing Gateway 2.0 adds AI-driven analytics to integrated third-party video; compatible enabled feeds can also work with FreeForm.Contracted capability; actual deployment/configuration not publicly verified. The public record reviewed does not identify how many gateways are installed, which feeds occupy the available channels, or which channels have AI enabled.
Records needed: Gateway quantity/serial inventory; each connected feed; AI-enabled channel list; analytics enabled per feed; FreeForm enablement; retention configuration; outside-agency/shared-video permissions.
Open
Community Network / private-camera partnerships
A records request should ask for registered/integrated camera counts, MOUs, sharing settings and outside-agency access rules.
Public-private integrationProgram capability publicly described; exact connected inventory unknown
Current MJPD page + Flock contract capability
UnknownAllows private Flock customers/partners to share footage or, under contracted FlockOS features, allows law enforcement to request access to privately owned Flock LPR feeds.Private LPR/video feeds when owners opt in/shareDepends on source system and agreement.Yes.Potentially, depending on the owner’s sharing settings and law-enforcement network configuration.MJPD says private customers cannot access law-enforcement data; exact downstream access to private feeds by outside agencies has not been publicly established.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Flock Mobile Security Trailer
Needs serial/model/site confirmation before adding a local quantity.
Mobile video / deterrenceContracted capability; local Flock trailer deployment not verified
Included in contract; do not equate every MJPD surveillance tower with this product
UnknownMobile trailer with deterrence light, two PTZ cameras, 360-degree multisensor camera and audio talk-down.Video / audio talk-downNot established separately in local contract description.Integrated with Flock platform.Depends on sharing configuration.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
FlockOS Premium
The existence of a feature in FlockOS does not prove MJPD has enabled it.
Operations / data platformContracted
Included in contract
Agency software platformCentral operational interface combining LPR, video, audio, maps, alerts, audits and integrations.Aggregates data from connected systemsDepends on underlying data source/product.Yes — contract lists public/private video, CAD, AVL, body-camera location and other integrations.Yes at platform capability level, including law-enforcement network access and outside-jurisdiction video where enabled.Mt. Juliet-specific settings are not fully public.FlockOS can unify connected LPR, video and other data sources. AI/search features depend on the products and permissions enabled in the account.Mt. Juliet-specific feature configuration is not fully public.
Records needed: Enabled modules, connected data sources, role permissions, sharing settings and audit/reporting configuration.
Open
Flock Nova — Customer Data / OSINT
This is broader than ALPR and should have its own governance/records questions.
Data integration / intelligenceContracted capability; usage not verified
Included in contract
Software subscription capabilityCentralizes agency CAD/RMS/digital evidence data and, separately, offers open-source intelligence/shared inter-agency data.Agency records, dispatch, digital evidence, OSINT and shared dataNot established in local order-form description.Yes.Shared inter-agency data is part of the described capability.Specific Mt. Juliet datasets and connections not publicly verified.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
FreeForm AI search
Flock states FreeForm does not use facial recognition or biometric person recognition.
AI / investigative searchContracted capability; activation not verified
Flock product capability confirmed; included in Mt. Juliet contract; local activation/configuration not verified
Software add-on capabilityNatural-language search across enabled video and LPR evidence. For people, Flock says searches use observable non-biometric characteristics such as clothing and visible accessories; people search is not available on LPR-only feeds.Searches LPR images/video metadata and imageryUnderlying source retention applies.Yes — Flock’s current FreeForm documentation says compatible third-party video integrations can be searched when setup compatibility requirements are met and the feeds are enabled.Flock says authorized users may search permission-based shared footage from participating agencies or other approved partners where sharing is enabled.Unknown for Mt. Juliet, including whether FreeForm can search any externally shared or locally integrated video feeds.Searches enabled video for descriptions such as a person’s clothing/accessories and can provide configurable alerts when potentially relevant matches appear. Flock says compatible third-party video integrations can be used when setup requirements are met.Contracted capability; Mt. Juliet activation and feed-level configuration are not publicly verified. It is not publicly clear whether any city-owned non-Flock camera is enabled for FreeForm people search or alerts.
Records needed: Whether FreeForm is enabled; authorized users/roles; enabled cameras/feeds; people-search and alert configuration; query justification requirements; search/audit logs; cross-agency/shared-feed permissions.
Open
Flock911
This is not an ALPR camera, but it demonstrates that the Safe City platform now extends well beyond plate readers.
911 / real-time responseConfirmed deployed
MJPD publicly announced deployment after testing
Agency-wide software integration; exact user count unknownDelivers live 911 call information into FlockOS to provide real-time context to responding personnel.911 call audio/context/location informationNot established here.Integrates 911/CAD context into FlockOS.Not established for Mt. Juliet.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Flock Aerodome Drone as First Responder
City page says active-incident use, not random patrol, and promises a public flight transparency portal once launched.
Drone / aerial videoConfirmed implementation/testing
Confirmed local DFR program
2 strategically placed drone docks; city DFR page describes two operational coverage locationsDispatches drones to active calls and transmits live aerial video to responders/command staff.Live aerial video, telemetry, flight logsPer DFR policy/portal; exact local retention should be tracked separately.FlockOS contract integrates drone live video/GPS.Assistance to other public-safety agencies is described; live feed sharing specifics should be verified.Not fully documented on public page.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Flock Aerodome DFR Radar
The Flock drone contract also references radar and radio-frequency sensor data as Flock Drone IP.
Radar / airspace sensingConfirmed implementation/testing
Confirmed on city DFR page
1 radar described as providing citywide coverageDetect-and-avoid / airspace monitoring supporting beyond-visual-line-of-sight drone operations.Radar and airspace sensor dataNot established on public program page.Integrated with DFR platform.Not relevant/unknown.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Traffic Analytics
This retention is for aggregate analytics and should not be confused with individual ALPR plate-read retention.
Traffic analyticsContracted capability; activation not verified
Included in contract
Software capabilityAggregates vehicle counts in 15-minute bins and supports breakdowns by class, state and make.Aggregate vehicle-count analyticsContract says aggregate counts may be hosted up to 5 years.Part of Flock platform.Unknown.Unknown.No additional AI/automation capability established in this inventory beyond the product description.Not separately established in this review.
Records needed: Product-specific configuration/deployment records as needed to verify local use.
Open
Guardian Mode — automated PTZ subject tracking
This is not facial recognition. It is also narrower than continuous identity tracking across the city: the documented feature follows a detected subject within the PTZ camera’s view.
AI video analyticsAvailable Flock capability; Mt. Juliet activation unknown
Flock capability confirmed; Mt. Juliet enablement not publicly verified
UnknownAvailable for Flock PTZ cameras. Flock says Guardian Mode automatically detects and locates people and vehicles, zooms in, follows movements within the camera field of view, and captures detailed imagery without a camera operator continuously steering the PTZ.AI analysis of PTZ video; people/vehicle detection and automated camera movementUnderlying video-camera retention/configuration applies; Mt. Juliet local Guardian Mode retention effects are not separately published.Flock documentation reviewed describes Guardian Mode for Flock PTZ cameras. This review did not establish that Wing can add Condor-style automatic pan/tilt/zoom following to an ordinary third-party PTZ camera.If resulting video is shared through FlockOS, authorized outside users may have access depending on sharing settings; Guardian Mode-specific outside access is not publicly established for Mt. Juliet.Unknown.Automatic within-field-of-view person/vehicle acquisition, PTZ following/zooming and evidence capture.Not publicly verified. No public Mt. Juliet record located states whether Guardian Mode is enabled or disabled on local Condor/PTZ cameras.
Records needed: Whether Guardian Mode is enabled; number/location of enabled cameras; schedules/areas where enabled; policy and training; users able to configure it; audit logs; sharing/access settings.
Open
WHO CAN CHANGE THE RULES?

State law, city ordinance, contract, police policy and public statements are not the same

The ordering below is about durability and external constraint, not a complete legal hierarchy. Federal/constitutional law can also control. This is a transparency framework, not legal advice.

AI / VIDEO GOVERNANCE GAP

Having the capability is different from having a public rule for its use.

MJPD publishes an ALPR General Order, but this review has not located a city ordinance or clearly identified departmental policy specifically governing Guardian Mode automated PTZ tracking, People Detection Alerts, FreeForm person/video searches, or AI analytics applied to integrated non-Flock cameras. This gap is already reflected in the Rules & legal documents transparency score.

State law

Tennessee ALPR retention limit — T.C.A. § 55-10-302

External legal constraintMJPD change alone: No

Main protection: Government-captured plate data may not generally be stored more than 90 days unless part of an ongoing investigation, with additional destruction rules.

How it changes: Requires state legislative/legal change, subject to controlling federal/constitutional law.

If violated: Binding law; legal consequences are determined through applicable civil/criminal/judicial processes, not merely department discipline.

MJPD chooses a stricter 7-day limit by policy; city ordinance is stricter than state maximum at 30 days. State law is an external floor/ceiling applicable to the city; it does not prevent Mt. Juliet from adopting stronger local restrictions where lawful.

Read source
State law

Tennessee confidentiality of captured ALPR data

External legal constraintMJPD change alone: No

Main protection: Restricts public inspection of captured plate data.

How it changes: State legislative change. Public Chapter 672 (2026) removed the scheduled sunset of this confidentiality provision.

If violated: Captured plate data is treated as confidential and not open for general public inspection under the public-records statute.

Limits what citizens can obtain directly, which makes aggregate audit/public reporting more important for external verification. The confidentiality rule protects plate data but also limits public ability to independently inspect individual reads.

Read source
City ordinance

Mt. Juliet Ordinance 2019-40

Local law adopted by elected boardMJPD change alone: No

Main protection: 30-day city retention cap (subject to investigation exception), no unmanned traffic enforcement, restrictions on non-governmental disclosure, and public listing of automatically shared governmental agencies.

How it changes: Board action is required to amend/repeal an ordinance.

If violated: City law rather than an internal police procedure.

More durable than a police general order, but it does not contain all of the detailed audit/query controls in the current police policy. The ordinance preamble expressly contemplated privacy and abuse risks when the city adopted ALPR rules in 2019.

Read source
City contract

Flock Safety Safe City order form / agreement

Contractual obligation / purchased capabilityMJPD change alone: Generally no for material contract terms

Main protection: Defines purchased products, services and some retention/product terms; the 2025 order form states a 30-day retention period.

How it changes: Contract amendment/renewal and whatever city approvals are legally or administratively required.

If violated: Creates contractual rights/obligations between the parties; not the same thing as a public criminal or civil statute governing officers.

Current MJPD ALPR policy says 7 days; the actual configured setting should be verified and the contract/policy difference reconciled. The contract is also important because it reveals capabilities not obvious from the Guardian Shield ALPR webpage.

Read source
Police policy / General Order

MJPD General Order 10D.6 — Automated License Plate Recognition Program

Internal departmental ruleMJPD change alone: The department can amend the general order through its policy process; it is expressly “subject to amendment.”

Main protection: 7-day retention, individual accounts, legitimate-purpose/query justification, case/call information, audit logging, 30-day administrator audits, monthly records and annual reporting requirements.

How it changes: Departmental policy amendment; current document directs readers to PowerDMS for the most recent version.

If violated: The policy expressly says violations of the General Order form the basis for departmental administrative sanctions; violations of law are handled separately in a judicial setting.

Detailed safeguards are useful, but they are less externally durable than ordinance/state law and require public audit results to verify operation. This is why the site separates “strong policy on paper” from “binding external rule” and from proof that the control is actually operating.

Read source
Public webpage / statement

Guardian Shield public facts, safeguards and transparency claims

Public representationMJPD change alone: Generally yes as website content/communications

Main protection: States 7-day retention, trained/authorized access, logging/auditing, controlled data sharing, no current federal sharing and other privacy assurances.

How it changes: Administrative website update; no ordinance vote required.

If violated: Useful evidence of what the department represents to residents, but not itself a substitute for law, ordinance, contract, or policy.

The site can compare each statement with published records and mark what remains independently unverifiable. Public claims should be preserved with dates because webpage language can change.

Read source
ALPR INVENTORY

How many plate-reader cameras are there, really?

The current city webpage contains 73 active location/direction entries. Behind the Shield treats that as the City’s published reference list, not a verified physical-camera count or proof that every deployed camera appears on the list. A complete device inventory would be needed to establish the physical count.

#Public location entryDirectionStatusPhysical camera/groupLast verifiedSource
1E Division St WB @ Golden Bear GtwyWBActive on city webpageUnknown2026-08-06City list
2East Division St @ Ramp to Golden Bear Gtwy SBSBActive on city webpageUnknown2026-08-06City list
3Pleasant Grove Rd @ Triple Crowne Pkwy - EBEBActive on city webpageUnknown2026-08-06City list
4Pleasant Grove Rd @ Triple Crowne Pkwy - WBWBActive on city webpageUnknown2026-08-06City list
5Lebanon Rd @ Pin Oak Dr EBEBActive on city webpageUnknown2026-08-06City list
6Providence Pkwy @ S Mount Juliet Rd - EBEBActive on city webpageUnknown2026-08-06City list
7S Mount Juliet Rd @ Crossings Circle - EBEBActive on city webpageUnknown2026-08-06City list
8S Mount Juliet Rd @ Providence Way/Belinda – EBEBActive on city webpageUnknown2026-08-06City list
9Pleasant Grove Rd @ Old Pleasant Grove Rd - EBEBActive on city webpageUnknown2026-08-06City list
10Old Lebanon Dirt Rd @ Cobbleston Landing EBEBActive on city webpageUnknown2026-08-06City list
11Central Pike WB @ Walton's Grove Subdivision / WestboundWBActive on city webpageUnknown2026-08-06City list
12South Mt. Juliet Rd SB @ Central Pike / South BoundSBActive on city webpageUnknown2026-08-06City list
13Central Pike EB @ Mt JulietEBActive on city webpageUnknown2026-08-06City list
14Central Pike NB @ Adams LaneNBActive on city webpageUnknown2026-08-06City list
15North Mt. Juliet Rd NB @ Pleasant Grove / NorthboundNBActive on city webpageUnknown2026-08-06City list
16North Mt. Juliet Rd. SB @ Pleasant Grove / South BoundSBActive on city webpageUnknown2026-08-06City list
17Central Pk EB from S MJ RdEBActive on city webpageUnknown2026-08-06City list
18North Mt. Juliet Rd. SB @ Hwy 70 / South BoundSBActive on city webpageUnknown2026-08-06City list
19Hwy 70 EB @ North Mt. Juliet Rd. / EastboundEBActive on city webpageUnknown2026-08-06City list
20Hwy 70 WB @ North Mt. Juliet Rd / West BoundWBActive on city webpageUnknown2026-08-06City list
21Robinson Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
22Mundy Park - InboundInboundActive on city webpageUnknown2026-08-06City list
23Beckwith Rd @ Wilfong Pkwy - SBSBActive on city webpageUnknown2026-08-06City list
24Grace Road- Bradshaw Farms Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
25Mt. Juliet Soccer Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
26Ethan Page Park Trailhead - InboundInboundActive on city webpageUnknown2026-08-06City list
27Cedar Creek Greenway - InboundInboundActive on city webpageUnknown2026-08-06City list
28Belinda Pkwy EB @ Providence Trail - EBEBActive on city webpageUnknown2026-08-06City list
29South Rutland Rd @ Baird Farms Construction Entrance - NBEntranceActive on city webpageUnknown2026-08-06City list
30Providence Pkwy @ Central Pike - WBWBActive on city webpageUnknown2026-08-06City list
31N Mt Juliet Rd @ Division St - NBNBActive on city webpageUnknown2026-08-06City list
32Nonaville Rd SB @ Saundersville Rd - SBSBActive on city webpageUnknown2026-08-06City list
33South Green Hill NB @ West Division St - NBNBActive on city webpageUnknown2026-08-06City list
34Lebanon Rd @ Terrace Hill Rd WBWBActive on city webpageUnknown2026-08-06City list
35Lebanon Rd E of Curd Rd EBEBActive on city webpageUnknown2026-08-06City list
36Old Lebanon Dirt Rd @ N Mt Juliet Rd - WBWBActive on city webpageUnknown2026-08-06City list
37Providence Way @ S Mount Juliet Rd - WBWBActive on city webpageUnknown2026-08-06City list
38N Mount Juliet Rd @ E Division St - WBWBActive on city webpageUnknown2026-08-06City list
39Old Lebanon Dirt Rd @ N Mt Juliet Rd - EBEBActive on city webpageUnknown2026-08-06City list
40Old Lebanon Dirt Rd @ Davidson County Line - WBWBActive on city webpageUnknown2026-08-06City list
41Golden Bear Gtwy @ Vanner Rd - NBNBActive on city webpageUnknown2026-08-06City list
42Charlie Daniels Park - InboundInboundActive on city webpageUnknown2026-08-06City list
43Golden Bear Gtwy @ Hwy 70 - SBSBActive on city webpageUnknown2026-08-06City list
44West Division St @ Davidson County Line - WBWBActive on city webpageUnknown2026-08-06City list
45Del Web Blvd @ S Rutland Rd - ExitExitActive on city webpageUnknown2026-08-06City list
46Providence Pkwy @ Central Pike - EBEBActive on city webpageUnknown2026-08-06City list
47Del Web Blvd @ S Rutland Rd - EntranceEntranceActive on city webpageUnknown2026-08-06City list
48Old Pleasant Grove Rd @ Pleasant Grove Pl - EBEBActive on city webpageUnknown2026-08-06City list
49Pleasant Grove Rd @ WalMart - EBEBActive on city webpageUnknown2026-08-06City list
50Providence Pkwy @ Providence Trl - WBWBActive on city webpageUnknown2026-08-06City list
51S Rutland Rd @ Beckwith Rd - WBWBActive on city webpageUnknown2026-08-06City list
52Golden Bear Gateway @ Vanner Rd - SBSBActive on city webpageUnknown2026-08-06City list
53Lebanon Rd @ Nonaville Rd - EBEBActive on city webpageUnknown2026-08-06City list
54Belinda Pkwy @ Providence Trl - WBWBActive on city webpageUnknown2026-08-06City list
55Leesa Ann Ln @ Darrington Way - WBWBActive on city webpageUnknown2026-08-06City list
56Old Lebanon Dirt Rd @ Kelsey Glen Dr - EBEBActive on city webpageUnknown2026-08-06City list
57Pleasant Grove Rd @ Old Pleasant Grove Rd - WBWBActive on city webpageUnknown2026-08-06City list
58Golden Bear Gateway @ I 40 On Ramp - SB (Covers WB Ramp)WBActive on city webpageUnknown2026-08-06City list
59Belinda Pkwy EB @ I-40 Ramp - EBEBActive on city webpageUnknown2026-08-06City list
60Beckwith Rd @ Summit Blvd - NBNBActive on city webpageUnknown2026-08-06City list
61Golden Bear Gtwy @ Beckwith Rd - NBNBActive on city webpageUnknown2026-08-06City list
62North Mt. Juliet Rd. NB @ I-40 / NorthboundNBActive on city webpageUnknown2026-08-06City list
63I-40 On-Ramps @ North Mt. Juliet Rd / WestboundWBActive on city webpageUnknown2026-08-06City list
64North Mt. Juliet Rd SB @ Division St. / South BoundSBActive on city webpageUnknown2026-08-06City list
65Hwy 70 WB @ Davidson County Line / WestboundWBActive on city webpageUnknown2026-08-06City list
66Hwy 70 EB @ Davidson County Line / EastboundEBActive on city webpageUnknown2026-08-06City list
67Pleasant Grove Rd @ WalMart - WBWBActive on city webpageUnknown2026-08-06City list
68South Mt. Juliet Rd. @ I-40 / Southbound on Mt. Juliet Rd @ I-40SBActive on city webpageUnknown2026-08-06City list
69South Mt. Juliet Rd NB @ Central Pike / North BoundNBActive on city webpageUnknown2026-08-06City list
70South Mt. Juliet Rd. @ I-40 / I-40 Eastbound On-RampEBActive on city webpageUnknown2026-08-06City list
71Lebanon Rd @ S Greenhill Rd EBEBActive on city webpageUnknown2026-08-06City list
72Lebanon Rd @ S Greenhill Rd SBSBActive on city webpageUnknown2026-08-06City list
73Lebanon Rd @ Sunset Dr - WBWBActive on city webpageUnknown2026-08-06City list
PUBLIC SPENDING

Contracts, invoices and commitments

Track actual spending, annual costs and long-term commitments separately.

2025-07-01Flock Safety

Safe City Year 1 invoice schedule

$185,000

Year 1

First scheduled invoice under the expanded agreement.

View source
2025-06-09Flock Safety

Modified 10-year Safe City agreement

$6,920,300

10-year payment schedule

The order form contains a separate cover-page total of $6,950,300; this discrepancy should be reconciled.

View source
2020-01-08Rekor Systems

Original Guardian Shield ALPR service

$89,000

Approximate annual cost announced during selection

MJPD described cost as near $89,000 per year pending final negotiations.

View source
2019-07-01Not selected

Initial ALPR program funding

$100,000

FY 2019–20

MJPD later reported that $100,000 had been allocated for the fiscal year.

View source
DECISIONS, VOTES & PUBLIC PARTICIPATION

Guardian Shield / Safe City timeline

Implementation, vendor changes, votes, policy amendments, network growth and whether citizen comment was located.

FY 2019–20 (beginning July 2019)

City funding set aside and vendor evaluation begins

Budget / planningVote record not yet locatedVerified public statement; underlying vote needed

MJPD later reported that the city had allocated $100,000 for the fiscal year and that police and IT personnel began evaluating ALPR technology.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Ordinance process followed in August–September 2019.

Source
August 26, 2019

ALPR privacy ordinance receives first reading

Law / ordinanceIndividual roll call not yet locatedVerified date; roll call missing

Ordinance 2019-40 received its first reading. It was designed to limit ALPR uses and provide public transparency.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Proposed restrictions included retention limits, no unmanned traffic enforcement, restrictions on nongovernmental disclosure, and publication of automatically shared governmental agencies.

Source
September 9, 2019

Ordinance 2019-40 adopted

Law / ordinancePassed; individual roll call not yet locatedVerified passage; roll call missing

The Board gave final passage to the city's ALPR ordinance, which was signed by then-Mayor Ed Hagerty.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day city retention ceiling, no automated traffic enforcement, no sale/provision to nongovernmental entities except as authorized by law, and website listing of agencies receiving automatic sharing.

Source
November 27, 2019

RFP released after roughly 60-day single-site pilot

Procurement / pilotAdministrative procurement stepVerified

The city released a request for proposals after testing one ALPR site for about 60 days. MJPD identified 37 proposed fixed-camera locations.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day internal retention was described, although state law allowed up to 90 days.

Source
January 8, 2020

Rekor selected as original Guardian Shield vendor

Vendor selectionCouncil authorization / contract vote not yet linkedVerified announcement; approval packet needed

After testing and review, the city and MJPD announced Rekor Systems as the selected ALPR vendor.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Images described as retained for 30 days.

Source
February 24, 2020

MJPD ALPR policy issued

Policy / oversightAdministrative policy; no council vote identifiedIssue date verified; original version missing

General Order 10D.6 lists an original issue date of February 24, 2020. The currently posted copy was later amended and now references Flock.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The current copy contains access, justification, logging, auditing, retention, sharing, and public-reporting rules; those provisions cannot all be assumed to have existed unchanged in 2020.

Source
April 1, 2020

Guardian Shield begins operation

ImplementationNo separate launch vote identifiedVerified

MJPD later identified April 1, 2020 as the start of the Guardian Shield program.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Thirty-day retention was publicly described at launch.

Source
February 25, 2021

MJPD announces 100 successful interceptions

Performance reportNo voteVerified

MJPD reported that Guardian Shield had surpassed 100 successful interceptions since its April 2020 start.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Operational-success reporting; no audit or misuse statistics were included in this announcement.

Source
November 2024 — exact meeting date pending

Initial Flock authorization referenced as Resolution 67-2024

Vendor transitionResolution passed; exact roll call not yet verifiedPartially verified; official vote record needed

Later city records identify Resolution 67-2024 as an earlier authorization for the transition to Flock. A November 2024 report also described commissioners approving a Flock contract.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Later March 2025 records call Flock the new LPR vendor and describe approvals for transition.

Source
March 24, 2025

Board unanimously approves continued Flock LPR transition

Council vote5–0, unanimousVerified roll call

Resolution 31-2025 authorized the mayor to sign an agreement with Flock for the license-plate-reader program.

Yes: Art Giles; Bill Trivett; James Maness; Jennifer Milele; Scott Hefner

No: None recorded

Citizen comments: No citizen comments recorded in the reviewed meeting minutes.

Written comments: Not determined.

Agreement and transition documents were attached to the agenda item.

Source
June 9, 2025

Board approves modified 10-year Safe City agreement

Council vote / expansion5–0, unanimousVerified roll call and contract

Resolution 50-2025 authorized a modified Flock agreement that consolidated services and expanded the platform beyond ALPR.

Yes: Art Giles; Bill Trivett; James Maness; Jennifer Milele; Scott Hefner

No: None recorded

Citizen comments: Many citizens spoke on other topics; no Flock/ALPR comment was identified in the recorded citizen-comment summaries.

Written comments: Minutes note citizen/business emails were distributed to commissioners, but topics were not identified as Flock-related.

The order form lists a 30-day retention period. The current MJPD policy states 21 days, creating a contract-policy point that should be reconciled publicly.

Source
July 1, 2025

Billing and installation period begins under expanded agreement

Contract implementationAuthorized through Resolution 50-2025Verified contract term

The order form scheduled the first $185,000 invoice for July 1, 2025 and prohibited installation before that date.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Contracted products and actual deployed products should be tracked separately.

Source
February 4, 2026

MJPD announces Flock911 and Safe City upgrades

Technology expansionNo separate vote identified in the announcementVerified

MJPD announced Flock911, which delivers real-time 911 information to officers, and stated that its Flock Safe City designation provides ongoing automatic upgrades to the wider Flock suite.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The website timeline should distinguish council-approved contract authority from later administrative activation of individual products.

Source
June 15, 2026

MJPD ALPR policy amended

Policy / oversightAdministrative policy; no council vote identifiedVerified amendment date; redline missing

The currently posted General Order 10D.6 is marked amended June 15, 2026.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Current policy calls for 30-day system audits, monthly records, annual public reporting, and 21-day retention.

Source
August 6, 2026 snapshot

Public location list has grown from 37 proposed entries to 73 active entries

Network growthExpansion votes by location not yet tracedVerified current list; physical-camera count requires clarification

The current Guardian Shield page lists 73 active ALPR location/direction entries, compared with 37 proposed locations in November 2019.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The current policy requires annual reporting of camera totals, but the historical expansion path is not evident from one consolidated public timeline.

Source
MJPD-PUBLISHED OUTCOMES

What MJPD says Guardian Shield has helped intercept

The Mt. Juliet Police Department labels this dataset “Successful Interceptions” and links to a Google spreadsheet that it says is updated monthly. Behind the Shield shows a small set of recent entries here and links directly to the City’s full dataset.

Published records421Data rows, excluding the header · counted August 8, 2026
Published period2020–2026Dates represented in the City spreadsheet
City update noteMonthlyMJPD says the linked spreadsheet is updated monthly
RECENT REPORTS

Six recent entries from the City spreadsheet

City Guardian Shield page ↗
Stolen Vehicle

Stolen Volkswagen alert led to Kentucky fugitive arrest

Wanted Person

MJPD reports Guardian Shield alerted officers to a stolen Volkswagen Passat from Kentucky. Officers stopped the vehicle on Lebanon Road and arrested the driver after confirming full-extradition warrants from Kentucky.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 100
Missing Person

Missing-person vehicle alert led officers to a wanted passenger

Wanted Person

MJPD reports Flock cameras alerted officers to a vehicle associated with a missing person. Officers located the missing person and also arrested a passenger who had active warrants.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 4
Investigative Alert

Locally entered investigative alert helped locate a fleeing suspect

Wanted Person

MJPD reports a vehicle entered into Flock after fleeing officers the previous day generated an alert. Officers located the vehicle, detained the driver and transported the suspect to Wilson County Jail.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 5
Investigative Alert

Investigative alert connected to counterfeit-money investigation

Wanted PersonDrugs

MJPD reports Flock alerted officers to a vehicle added to a local hotlist during a counterfeit-money investigation. A wanted suspect was detained and other occupants were arrested on separate warrants or drug charges.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 6
Investigative Alert

Attempted-robbery vehicle alert led officers to Walmart

Wanted Person

MJPD reports LPR cameras alerted officers to a vehicle connected to an attempted robbery in Spring Hill. Officers located the vehicle at Walmart and arrested a suspect wanted in Maury County.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 7
Stolen Vehicle

Stolen GMC alert led to arrest at a local restaurant

Wanted Person

MJPD reports LPR cameras alerted officers to a stolen GMC Envoy from Lawrence County. Officers located the vehicle at Slim Chickens and arrested the driver on the stolen-vehicle case and an outstanding warrant.

Source: MJPD “Successful Interceptions” spreadsheet · sheet row 8
CLAIMS VS. EVIDENCE

What the city says—and what would verify it

The goal is not to assume a claim is false. It is to identify the records that would demonstrate the safeguard is operating as described.

Retention

“Images not used for an investigation are generally retained no more than 7 days.”

Official claim only

Current public Guardian Shield page states 7 days; city ordinance allows up to 30 days.

Useful verification: Current configured retention setting, exception logs, and counts of records preserved beyond the standard period.Open question
Official source
Auditing

“Every search is logged and subject to supervisory review and regular audits.”

Needs independent verification

Policy/public page describes logging and audits; aggregate audit results are needed to verify scope, frequency, findings, and follow-up.

Useful verification: Monthly audit reports, audit methodology, number of queries reviewed, exceptions, and corrective actions.Open question
Official source
Access

“Only trained and authorized personnel may access the ALPR system.”

Needs independent verification

Public policy states restricted access. Current counts of users by role are not shown on the public page.

Useful verification: Authorized-user count by role, access reviews, account deactivations, and training completion in aggregate.Open question
Official source
Tracking / scope of Guardian Shield

“Guardian Shield does not track people.”

Statement requires context

The public Guardian Shield explanation is framed around ALPR/Falcon vehicle data. The broader Flock Safe City ecosystem includes PTZ video cameras and AI video capabilities. Flock documents Guardian Mode as automatically following people/vehicles within a PTZ camera’s field of view, while FreeForm can search enabled video for visible non-biometric person characteristics. Mt. Juliet’s local activation/configuration of those capabilities has not been publicly verified.

Useful verification: Condor/PTZ inventory and Guardian Mode enablement; People Detection/Visual Alert settings; Wing-connected city/private feeds; AI-enabled channels; FreeForm-enabled video feeds; policies, audit logs and external sharing settings.Open question
Official source
Data sharing

“Information is shared only with authorized government agencies for legitimate law-enforcement purposes and required documentation.”

Needs independent verification

City publishes agencies with access agreements; aggregate access frequency and outside-agency query counts are not on the public page.

Useful verification: Outside-agency query counts, approvals/revocations, audit findings, and sharing changes by agency in aggregate.Open question
Official source
Search justification

“Officers must have a documented investigative reason and, when required, reasonable suspicion to search the system.”

Needs independent verification

The policy states the requirement. Audit results can show whether case/call numbers and reasons are actually present and valid.

Useful verification: Aggregate number of queries missing/using invalid case references or requiring corrective follow-up.Open question
Official source
Video AI configuration

“The public can determine which city video cameras have automated person detection, tracking or AI search enabled.”

Contradicted / needs reconciliation

No public Mt. Juliet inventory located in this review identifies Condor Guardian Mode status, AI-enabled Wing channels, or which city/non-Flock video feeds are enabled for FreeForm person search or alerts.

Useful verification: Camera/feed-level AI configuration inventory: owner/model/location, Flock integration status, Guardian Mode, People Detection Alerts, Visual Alerts, FreeForm, AI channel assignment, retention and sharing permissions.Open question
Official source

Audit data

Awaiting records

No aggregate audit report has been entered yet.

SOURCE LIBRARY

Documents behind the site

Policies, ordinances, contracts, invoices, minutes, posts, reporting, laws and open-records responses.

DateTypeTitlePublisherSummaryLink
2019-09-09OrdinanceOrdinance 2019-40 — ALPR regulationMt. Juliet Board of CommissionersCity ordinance addressing retention, automated traffic enforcement, disclosure, and automatic sharing.Open
2026-06-15Police policyMJPD General Order 10D.6 — Automated License Plate Recognition ProgramMt. Juliet Police DepartmentCurrent amended policy covering use, query justification, audit trail, retention, audits, sharing, and reporting.Open
2025-06-09ContractFlock Safe City order formMt. Juliet / Flock SafetyTen-year Safe City agreement and payment schedule.Open
2025-06-09Meeting minutesBoard minutes — Resolution 50-2025Mt. Juliet Board of CommissionersPublished minutes showing unanimous approval of modified Flock Safe City agreement.Open
2025-06-02ContractFlock Safety Safe City order form — product and feature descriptionsCity of Mt. Juliet / Flock SafetyLists Falcon LPR, Condor PTZ, Raven gunshot detection, mobile trailers, FlockOS/Nova/FreeForm, video integration/Wing, Flock911, traffic analytics, DFR drones/radar and network/video-integration capabilities.Open
2026-08-06City webpageMJPD Drone as a First Responder program pageMt. Juliet Police DepartmentPublic program details including implementation/testing status, two strategically placed drone docks, one radar with citywide coverage and promised flight transparency portal.Open
2026-08-06City webpageMJPD recruiting page — Safe City, city-wide LPR and camera networksMt. Juliet Police DepartmentMJPD publicly describes an advanced Flock Safe City program, funded DFR program, city-wide LPR network and city-wide camera network.Open
2026-04-07State lawTennessee Public Chapter 672 / SB1879 — ALPR captured-data confidentiality sunset removedTennessee General AssemblyRemoves the scheduled sunset of the Tennessee public-records confidentiality provision for captured ALPR data.Open
2026-06-26OtherFlock AI video analytics — Guardian Mode and People Detection AlertsFlock SafetyFlock describes Guardian Mode for PTZ cameras as automatically detecting/locating people and vehicles, following movements, zooming and capturing detailed imagery; also describes configurable People Detection Alerts.Open
2026-08-07OtherFlock video cameras / Condor product pageFlock SafetyCurrent Flock video-camera page lists Guardian Mode, People Detection Alerts, Visual Alerts and FreeForm as AI features.Open
2026-08-07OtherFlock FreeForm product pageFlock SafetyFlock says FreeForm searches enabled video with natural-language descriptions, supports visible non-biometric person characteristics and configurable alerts, and can work with compatible third-party video integrations.Open
2026-08-07OtherFlock Wing Gateway 2.0 — third-party video integration and AI analyticsFlock SafetyFlock describes Wing Gateway 2.0 as integrating existing third-party cameras into Flock and adding AI-driven analytics. Mt. Juliet’s local order form separately describes a 16-stream gateway with 8-channel AI capability.Open
HELP VERIFY THE RECORD

Know of a public source we’re missing?

Behind the Shield MJ is built from verifiable records. If you know of a document, meeting record, city statement, policy, or other public source that answers an open question, send it for private review.

Private conversationNothing is published automatically.
HELP VERIFY THE RECORD

Share a public source

Send a lead for private review. Submissions never publish automatically and do not change the site or transparency score until independently checked.

Review first

Your submission is stored privately. Information is independently checked before anything is added to the public site.

Methodology

Who runs this site: Behind the Shield MJ is an independent citizen project created and maintained by a Mount Juliet resident. It has no affiliation with the City of Mount Juliet, the Mt. Juliet Police Department, or Flock Safety and is not an official government or police website.

It catalogs what Mt. Juliet and other sources publicly state, the records supporting those statements, and gaps where additional documentation would be useful.

Evidence discipline: “contracted capability” is not “deployed”; “city-listed ALPR location” is not automatically one physical camera; and “police policy” is not the same as a city ordinance or state statute. The transparency score measures public verifiability only.

Outcome-reporting scope: the “MJPD-published outcomes” section summarizes the department’s own “Successful Interceptions” spreadsheet and links to the complete City source. The homepage displays only recent examples for readability. These department-authored summaries are not an independent audit, and the spreadsheet is not a denominator for all police stops, arrests, ALPR reads, alerts, false positives, or unsuccessful responses.

Route-estimator limitation: map points are manually placed estimates derived from the City of Mt. Juliet’s Guardian Shield “Active ALPR Locations” descriptions, not exact camera coordinates. One dot may group multiple listed directions and/or multiple physical cameras. Route proximity is not proof of an actual plate read or image capture.