Behind the Shield MJ

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.95MCorrected second modified agreement

HISTORICAL SURVEILLANCE MAP

See the archived system by site and device type

Explore a historical Mt. Juliet extract that separates Wing-integrated video sites, ALPR devices, PTZ/video devices, other Flock equipment, and approximate gateway relationships.

Historical snapshotWing sites, not marker clustersApproximate locations labeled

Dataset records are not automatically physical-camera counts. Unresolved and mobile records remain available as text without guessed map points.

Explore the historical mapSeparate from the route estimator and not a current device inventory.

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.

Evidence & sources (5)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The reviewed page does not provide camera/feed-level AI enablement details.
Drone as a First ResponderOfficial webpage
Mt. Juliet Police Department
Original source
Official statement
Join Mt. Juliet Police DepartmentOfficial webpage
Mt. Juliet Police Department
Original source
Official statement
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contracted
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Implementation scope Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The SOW identifies contracted implementation scope but does not identify completed camera/feed-level AI enablement or configuration.

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; the superseded June order form contained an internal total discrepancy that the later second modification corrected but that still requires clear historical labeling.

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

Evidence & sources (6)

Flock Safety Safe City order form and agreementContractSuperseded version
City of Mt. Juliet and Flock Safety
Legistar file 1274 order form created 2025-06-02Document created June 2, 2025
Location: Billing Schedule · p. 3 · Contract Total
Original source
Contracted Supports: The superseded June 2 billing schedule displayed a conflicting Contract Total of $6,920,300.
Preserves the erroneous $6,920,300 billing-schedule total in the superseded June version rather than treating it as the corrected contract total.
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Contract Total · Billing Schedule · p. 3 · Contract Total
Original source
Contracted Supports: The corrected second-modification Safe City agreement displays a consistent Contract Total of $6,950,300.
The corrected order-form page displays $6,950,300.
Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-06-09 meetingMeeting June 9, 2025
Location: Agenda item 14.M · File 1274 · Resolution 50-2025
Original source
Official statement Supports: On June 9, 2025, the Mt. Juliet Board adopted the modified Flock agreement under file 1274 as Resolution 50-2025.
Establishes the government approval event only; it is not the order form's created, publication, or execution-based effective date.
Mt. Juliet Board minutes — July 28, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-07-28 meetingMeeting July 28, 2025
Location: Agenda item 10.C · File 1331 · Resolution 61-2025
Original source
Official statement Supports: On July 28, 2025, the Mt. Juliet Board adopted the second modified Flock agreement under file 1331 as Resolution 61-2025.
Establishes adoption of the second modified agreement. It does not establish execution by both contract parties or the contractual effective date.
MJPD ALPR proposal and potential locationsOfficial announcementHistorical
Mt. Juliet Police Department
Published 2019-11-27Published Nov. 27, 2019
Original source
Official statement
Rekor selected for Guardian ShieldOfficial announcementHistorical
Mt. Juliet Police Department
Published 2020-01-08Published Jan. 8, 2020
Original source
Official statement

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.

Evidence & sources (5)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Written policy Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.
Directly supports the current written seven-day maximum and investigation exception. Written policy does not establish the live Flock account setting.
Written policy Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified written seven-day policy is not proof of the active vendor configuration.
Mt. Juliet Ordinance 2019-40City ordinanceCurrent
Mt. Juliet Board of Commissioners
Ordinance 2019-40 adopted textAdopted Sept. 9, 2019
Original source
City ordinance Documents this statement: Mt. Juliet Ordinance 2019-40 establishes a 30-day city retention cap, subject to an investigation exception.
Supports the legal cap described in legacy records; the ordinance does not establish the vendor's active configuration. A precise source locator remains unavailable.
City ordinance Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
A legal maximum does not identify the shorter period, if any, configured in the system.
Tennessee Code § 55-10-302 — ALPR retentionState law
Justia · Tennessee General Assembly
Original source
State law
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Retention Period
Original source
Contracted Supports: The applicable corrected Flock Safe City order form displays an agreement-level Retention Period of 30 Days.
Directly supports the agreement-level 30-day field in the corrected version. The Safe City bundle covers multiple technologies, and the field does not prove an ALPR-only term or the live configured value.
Contracted Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified agreement-level 30-day field does not prove the currently configured ALPR value or operational practice, and the multi-technology bundle does not make that field ALPR-exclusive.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Implementation scope

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.

Evidence & sources (3)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Information is shared only with authorized government agencies for legitimate law-enforcement purposes and required documentation.
Supports the existence of the official sharing statement, not actual sharing activity or configuration.
Official statement Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The reviewed page does not provide camera/feed-level AI enablement details.
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contracted
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Implementation scope Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The SOW identifies contracted implementation scope but does not identify completed camera/feed-level AI enablement or configuration.

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.

Evidence & sources (2)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Original source
Written policy
Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Every search is logged and subject to supervisory review and regular audits.
Supports the existence of the official logging and audit statement, not operational compliance.

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.

Evidence & sources (3)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement
MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome
MJPD News Guardian Shield archiveOfficial news archive
Mt. Juliet Police Department
Original source
Official statement

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.

Evidence & sources (4)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contracted
Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-06-09 meetingMeeting June 9, 2025
Location: Agenda item 14.M · File 1274 · Resolution 50-2025
Original source
Official statement Supports: On June 9, 2025, the Mt. Juliet Board adopted the modified Flock agreement under file 1274 as Resolution 50-2025.
Establishes the government approval event only; it is not the order form's created, publication, or execution-based effective date.
Mt. Juliet Board minutes — July 28, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-07-28 meetingMeeting July 28, 2025
Location: Agenda item 10.C · File 1331 · Resolution 61-2025
Original source
Official statement Supports: On July 28, 2025, the Mt. Juliet Board adopted the second modified Flock agreement under file 1331 as Resolution 61-2025.
Establishes adoption of the second modified agreement. It does not establish execution by both contract parties or the contractual effective date.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Implementation scope Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The SOW identifies contracted implementation scope but does not identify completed camera/feed-level AI enablement or configuration.

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.

PEOPLE & VIDEOCan a camera automatically follow a person?See Guardian Mode → EXISTING CAMERASCan Mt. Juliet's non-Flock cameras gain AI?See Wing integration → SHARINGCan video move beyond MJPD?See FlockOS & integrations → LICENSE PLATESWhat is capturing vehicles around the city?See Falcon ALPR →

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.

Evidence & sources (3)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Local status
Confirmed local deployment Supports: local deployment or program status, publicly identified scope, described function
Sharing and integration
Official statement Context only Relevant to third-party integration, outside-agency capability, local sharing status.
Published capability and sharing rules do not establish query volume or current account configuration.
Unresolved locally
Official statement Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
A public statement of a retention period does not establish the active vendor configuration.
MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Retention and storage
Written policy Context only Relevant to retention or storage.
The 7-day written policy and 30-day agreement field do not establish the live ALPR configuration.
Unresolved locally
Written policy Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified written seven-day policy is not proof of the active vendor configuration.
Supporting context
Written policy Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.
Directly supports the current written seven-day maximum and investigation exception. Written policy does not establish the live Flock account setting.
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Retention Period
Original source
Contract and implementation
Contracted Context only Relevant to retention or storage.
The 7-day written policy and 30-day agreement field do not establish the live ALPR configuration.
Contracted Context only Relevant to third-party integration, outside-agency capability, local sharing status.
Published capability and sharing rules do not establish query volume or current account configuration.
Contracted Supports: The applicable corrected Flock Safe City order form displays an agreement-level Retention Period of 30 Days.
Directly supports the agreement-level 30-day field in the corrected version. The Safe City bundle covers multiple technologies, and the field does not prove an ALPR-only term or the live configured value.
Unresolved locally
Contracted Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified agreement-level 30-day field does not prove the currently configured ALPR value or operational practice, and the multi-technology bundle does not make that field ALPR-exclusive.

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.

Evidence & sources (3)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, retention or storage, evidence basis
The agreement establishes purchased capability, not completed deployment.
Unresolved locally
Contracted Does not establish this on its own Relevant to local activation or configuration, local sharing status.
The agreement does not establish Mt. Juliet deployment, enablement, or sharing configuration.
Flock Condor video-camera product pageVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: described function, automation capability
Vendor documentation establishes product capability only.
Unresolved locally
Vendor-described capability Does not establish this on its own Relevant to local activation or configuration.
Vendor capability documentation does not establish local activation.
Flock AI video analytics — Guardian Mode and People Detection AlertsVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: described function, automation capability
Vendor documentation establishes product capability only.
Unresolved locally
Vendor-described capability Does not establish this on its own Relevant to local activation or configuration.
Vendor capability documentation does not establish local activation.

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.

Evidence & sources (3)

Flock AI video analytics — Guardian Mode and People Detection AlertsVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: described function, automation capability
Unresolved locally
Vendor-described capability Does not establish this on its own Relevant to local deployment or program status, local activation or configuration.
Vendor capability does not establish Mt. Juliet activation.
Flock Condor video-camera product pageVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: described function, automation capability
Unresolved locally
Vendor-described capability Does not establish this on its own Relevant to local deployment or program status, local activation or configuration.
Vendor capability does not establish Mt. Juliet activation.
Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Unresolved locally
Official statement Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The local public page does not disclose camera-level AI configuration.

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.

Evidence & sources (3)

Join Mt. Juliet Police DepartmentOfficial webpage
Mt. Juliet Police Department
Original source
Local status
Official statement Supports: local deployment or program status, described function, evidence basis
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Context only Relevant to third-party integration.
The SOW establishes contracted integration scope but does not prove completed feed integration.
Unresolved locally
Implementation scope Does not establish this on its own Relevant to local activation or configuration.
Flock Wing Gateway 2.0 announcementVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Context only Relevant to automation capability.
Vendor material describes capability but does not prove local AI enablement.

Third-party camera integrationHistorical local Wing integration confirmed in archived late-2025 device data

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.

PUBLICLY IDENTIFIED SCOPE333 Wing-classified video-feed records in the Mt. Juliet historical extract; not a count of physical gateway appliances

MT. JULIET CONFIGURATION

The SOW specifies gateways intended to enable Flock AI, including Free Form Search capability. Reviewed evidence does not establish per-feed FreeForm or analytics enablement, the current gateway inventory, or current configuration.

Explore capabilities & evidence

Evidence status: Historical local Wing integration is confirmed by archived late-2025 device data; contracted architecture is separately documented; current deployment/configuration remains 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 reviewed evidence establishes current sharing/access configuration or which historical integrated feeds, if any, were available to outside agencies.
What would verify the local setup?: Current gateway quantity/serial inventory; current connected-feed list; AI-enabled channel list; analytics and FreeForm enablement by feed; retention configuration; outside-agency/shared-video permissions.Open question

The historical extract contains Wing-classified feed records, while the SOW separately specifies contracted gateway and stream-integration architecture. Neither source establishes the current 2026 feed or gateway inventory, and Wing classification does not prove per-feed AI or FreeForm enablement.

Evidence & sources (4)

Flock Surveillance Map — archived Flock device datasetThird-party reportingHistorical
Joshua Michael / FlockSurveillance.org
December 2025 archive; public table observed 2026-09-24Observed Sept. 24, 2026
Original source
Unresolved locally
Independent verification Does not establish this on its own Relevant to local activation or configuration, local sharing status, records needed to verify the local setup.
Wing classification does not establish current configuration, sharing, per-feed analytics, or per-feed FreeForm enablement.
Supporting context
Independent verification Supports: local deployment or program status, publicly identified scope, evidence basis
The historical extract establishes Wing-classified records and the 333-row/feed count, not physical gateway quantity or current deployment.
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: described function, retention or storage, evidence basis
The contract and SOW establish purchase and implementation scope, not completed installation, current configuration, or per-feed use.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Location: PDF p. 1 · §Project Summary.10 16-channel Gateways; 355 camera streams
Original source
Contract and implementation
Implementation scope Supports: described function, retention or storage, evidence basis
The contract and SOW establish purchase and implementation scope, not completed installation, current configuration, or per-feed use.
Implementation scope Context only Relevant to third-party integration.
Unresolved locally
Implementation scope Does not establish this on its own Relevant to local activation or configuration, local sharing status.
Flock Wing Gateway 2.0 announcementVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: automation capability
Vendor documentation establishes Wing capability, not local enablement.

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.

Evidence & sources (4)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, evidence basis
FreeForm is contracted and included in implementation scope; activation is not established.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Supports: local deployment or program status, evidence basis
FreeForm is contracted and included in implementation scope; activation is not established.
Unresolved locally
Implementation scope Does not establish this on its own Relevant to local activation or configuration, local sharing status.
The SOW does not establish enabled feeds, users, searches, or sharing settings.
Implementation scope Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The SOW identifies contracted implementation scope but does not identify completed camera/feed-level AI enablement or configuration.
Flock FreeForm product pageVendor documentation
Flock Safety
Original source
Capability
Vendor-described capability Supports: described function, third-party integration, outside-agency capability, automation capability
Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Unresolved locally
Official statement Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The local public page does not identify enabled feeds, users, searches, or sharing settings.

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.

Evidence & sources (3)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Sharing and integration
Official statement Supports: local deployment or program status, described function, local sharing status
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Context only Relevant to third-party integration, outside-agency capability.
Contract and SOW establish capability and contracted community-gateway scope, not the connected inventory or actual sharing state.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Context only Relevant to third-party integration, outside-agency capability.
Contract and SOW establish capability and contracted community-gateway scope, not the connected inventory or actual sharing state.

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.

Evidence & sources (2)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, described function, third-party integration, evidence basis
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Supports: local deployment or program status, described function, third-party integration, evidence basis
Unresolved locally
Implementation scope Does not establish this on its own Relevant to local sharing status, local activation or configuration.
The SOW lists implementation scope but not completed configuration, permissions, or operational use.

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.

Evidence & sources (3)

MJPD Flock911 and Safe City announcementOfficial announcementHistorical
Mt. Juliet Police Department
Published 2026-02-04Published Feb. 4, 2026
Original source
Local status
Confirmed local use Supports: local deployment or program status, described function, evidence basis
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Context only Relevant to third-party integration.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Context only Relevant to third-party integration.

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.

Evidence & sources (1)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, described function, evidence basis
Contracted capability does not establish local activation.

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.

Evidence & sources (1)

MJPD Flock911 and Safe City announcementOfficial announcementHistorical
Mt. Juliet Police Department
Published 2026-02-04Published Feb. 4, 2026
Original source
Local status
Official statement Supports: local deployment or program status, described function, evidence basis

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.

Evidence & sources (1)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, described function, evidence basis
Included in the agreement; local deployment quantity remains unverified.

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.

Evidence & sources (3)

Drone as a First ResponderOfficial webpage
Mt. Juliet Police Department
Original source
Local status
Official statement Supports: local deployment or program status, publicly identified scope, described function, evidence basis
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Context only Relevant to third-party integration, outside-agency capability.
The agreement and SOW establish purchased integration scope, not completed DroneSense integration or operational use.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Context only Relevant to third-party integration, outside-agency capability.
The agreement and SOW establish purchased integration scope, not completed DroneSense integration or operational use.

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.

Evidence & sources (2)

Drone as a First ResponderOfficial webpage
Mt. Juliet Police Department
Original source
Local status
Official statement Supports: local deployment or program status, publicly identified scope, described function, evidence basis
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Context only Relevant to third-party integration.

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.

Evidence & sources (2)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, described function, third-party integration, evidence basis
Purchased capability and implementation scope do not establish which datasets are connected or used.
FlockOS Premium Statement of Work for Mt. Juliet PDContractCurrent
City of Mt. Juliet and Flock Safety
Effective 2025-06-03, Revision 1, SOW Version 2.0Effective June 3, 2025
Original source
Contract and implementation
Implementation scope Supports: local deployment or program status, described function, third-party integration, evidence basis
Purchased capability and implementation scope do not establish which datasets are connected or used.

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.

Evidence & sources (1)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Contract and implementation
Contracted Supports: local deployment or program status, described function, retention or storage, evidence basis
Contracted capability does not establish local activation or use.

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 / system	Category	Evidence status	Quantity	What it does	Data	Retention	Third-party integration	Outside-agency capability	Actual Mt. Juliet sharing	AI / automation capability	Mt. Juliet AI status	Source
Flock Safety LPR — Codename: Falcon Do not equate 73 public entries with 73 distinct physical Falcons until device inventory is obtained.	License plate recognition	Confirmed deployed Confirmed local deployment	73 public location/direction entries; exact physical unit count unknown	Captures plate/vehicle images and supports hot-list alerts, historical searches and vehicle-description searches.	Images, license plates, vehicle characteristics, date/time/location	MJPD 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 video	Contracted capability; deployment quantity not verified Product is in city Flock contract; exact deployment not verified	Unknown	Live-streamed pan/tilt/zoom video with edge storage and VMS. Flock video cameras can also support configurable AI video analytics.	Live and recorded video	Contract 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 video	Publicly announced; device inventory not published MJPD recruiting page confirms a “City-Wide Camera Network”; product models/locations incomplete	Unknown	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.	Video	Varies 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 detection	Contracted capability; local activation not verified Included in Mt. Juliet Flock contract; deployment not independently confirmed	Unknown; contract licenses by coverage area, not unit count	Detects acoustic signatures associated with gunfire and generates location-based alerts.	Acoustic sensor events	Not 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 detection	Publicly announced as Safe City technology Public announcement; exact hardware/product configuration needs verification	Unknown	Acoustic detection associated with crash-response technology, as described by MJPD in its Safe City/Flock911 announcement.	Acoustic event detection	Unknown	Part 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 The historical extract contains Wing-classified feed records, while the SOW separately specifies contracted gateway and stream-integration architecture. Neither source establishes the current 2026 feed or gateway inventory, and Wing classification does not prove per-feed AI or FreeForm enablement.	Third-party camera integration	Historical local Wing integration confirmed in archived late-2025 device data Historical local Wing integration is confirmed by archived late-2025 device data; contracted architecture is separately documented; current deployment/configuration remains unknown	333 Wing-classified video-feed records in the Mt. Juliet historical extract; not a count of physical gateway appliances	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.	Third-party live/recorded video	Contract 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 reviewed evidence establishes current sharing/access configuration or which historical integrated feeds, if any, were 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.	The SOW specifies gateways intended to enable Flock AI, including Free Form Search capability. Reviewed evidence does not establish per-feed FreeForm or analytics enablement, the current gateway inventory, or current configuration. Records needed: Current gateway quantity/serial inventory; current connected-feed list; AI-enabled channel list; analytics and FreeForm enablement by feed; 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 integration	Program capability publicly described; exact connected inventory unknown Current MJPD page + Flock contract capability	Unknown	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.	Private LPR/video feeds when owners opt in/share	Depends 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 / deterrence	Contracted capability; local Flock trailer deployment not verified Included in contract; do not equate every MJPD surveillance tower with this product	Unknown	Mobile trailer with deterrence light, two PTZ cameras, 360-degree multisensor camera and audio talk-down.	Video / audio talk-down	Not 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 platform	Contracted Included in contract	Agency software platform	Central operational interface combining LPR, video, audio, maps, alerts, audits and integrations.	Aggregates data from connected systems	Depends 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 / intelligence	Contracted capability; usage not verified Included in contract	Software subscription capability	Centralizes agency CAD/RMS/digital evidence data and, separately, offers open-source intelligence/shared inter-agency data.	Agency records, dispatch, digital evidence, OSINT and shared data	Not 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 search	Contracted capability; activation not verified Flock product capability confirmed; included in Mt. Juliet contract; local activation/configuration not verified	Software add-on capability	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.	Searches LPR images/video metadata and imagery	Underlying 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 response	Confirmed deployed MJPD publicly announced deployment after testing	Agency-wide software integration; exact user count unknown	Delivers live 911 call information into FlockOS to provide real-time context to responding personnel.	911 call audio/context/location information	Not 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 video	Confirmed implementation/testing Confirmed local DFR program	2 strategically placed drone docks; city DFR page describes two operational coverage locations	Dispatches drones to active calls and transmits live aerial video to responders/command staff.	Live aerial video, telemetry, flight logs	Per 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 sensing	Confirmed implementation/testing Confirmed on city DFR page	1 radar described as providing citywide coverage	Detect-and-avoid / airspace monitoring supporting beyond-visual-line-of-sight drone operations.	Radar and airspace sensor data	Not 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 analytics	Contracted capability; activation not verified Included in contract	Software capability	Aggregates vehicle counts in 15-minute bins and supports breakdowns by class, state and make.	Aggregate vehicle-count analytics	Contract 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 analytics	Available Flock capability; Mt. Juliet activation unknown Flock capability confirmed; Mt. Juliet enablement not publicly verified	Unknown	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.	AI analysis of PTZ video; people/vehicle detection and automated camera movement	Underlying 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.

Evidence & sources (3)

Tennessee Code § 55-10-302 — ALPR retentionState law
Justia · Tennessee General Assembly
Original source
Supports: stated protection
Mt. Juliet Ordinance 2019-40City ordinanceCurrent
Mt. Juliet Board of Commissioners
Ordinance 2019-40 adopted textAdopted Sept. 9, 2019
Original source
Context only Relevant to current local limit.
Documents this statement: Mt. Juliet Ordinance 2019-40 establishes a 30-day city retention cap, subject to an investigation exception.
MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Context only Relevant to current local limit.
Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.

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.

Evidence & sources (1)

Tennessee SB1879 / Public Chapter 672 — ALPR confidentialityState lawHistorical
Tennessee General Assembly
SB1879, 114th General Assembly legislative record
Original 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.

Evidence & sources (1)

Mt. Juliet Ordinance 2019-40City ordinanceCurrent
Mt. Juliet Board of Commissioners
Ordinance 2019-40 adopted textAdopted Sept. 9, 2019
Original source
Documents this statement: Mt. Juliet Ordinance 2019-40 establishes a 30-day city retention cap, subject to an investigation exception.

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.

Evidence & sources (2)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Retention Period
Original source
Supports: stated protection
Context only Relevant to current local limit.
The agreement term remains distinct from policy and does not prove the active configuration.
Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified agreement-level 30-day field does not prove the currently configured ALPR value or operational practice, and the multi-technology bundle does not make that field ALPR-exclusive.
MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Context only Relevant to current local limit.
The written policy establishes the current rule, not the active configuration.
Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.
Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified written seven-day policy is not proof of the active vendor configuration.

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.

Evidence & sources (1)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.

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.

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Documents this statement: Images not used for an investigation are generally retained no more than 7 days.
Documents this statement: Every search is logged and subject to supervisory review and regular audits.
Documents this statement: Only trained and authorized personnel may access the ALPR system.
Documents this statement: Guardian Shield does not track people.
Documents this statement: Information is shared only with authorized government agencies for legitimate law-enforcement purposes and required documentation.
Documents this statement: Officers must have a documented investigative reason and, when required, reasonable suspicion to search the system.

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 entry	Direction	Status	Physical camera/group	Last verified
1	E Division St WB @ Golden Bear Gtwy	WB	Active on city webpage	Unknown	2026-08-06
2	East Division St @ Ramp to Golden Bear Gtwy SB	SB	Active on city webpage	Unknown	2026-08-06
3	Pleasant Grove Rd @ Triple Crowne Pkwy - EB	EB	Active on city webpage	Unknown	2026-08-06
4	Pleasant Grove Rd @ Triple Crowne Pkwy - WB	WB	Active on city webpage	Unknown	2026-08-06
5	Lebanon Rd @ Pin Oak Dr EB	EB	Active on city webpage	Unknown	2026-08-06
6	Providence Pkwy @ S Mount Juliet Rd - EB	EB	Active on city webpage	Unknown	2026-08-06
7	S Mount Juliet Rd @ Crossings Circle - EB	EB	Active on city webpage	Unknown	2026-08-06
8	S Mount Juliet Rd @ Providence Way/Belinda – EB	EB	Active on city webpage	Unknown	2026-08-06
9	Pleasant Grove Rd @ Old Pleasant Grove Rd - EB	EB	Active on city webpage	Unknown	2026-08-06
10	Old Lebanon Dirt Rd @ Cobbleston Landing EB	EB	Active on city webpage	Unknown	2026-08-06
11	Central Pike WB @ Walton's Grove Subdivision / Westbound	WB	Active on city webpage	Unknown	2026-08-06
12	South Mt. Juliet Rd SB @ Central Pike / South Bound	SB	Active on city webpage	Unknown	2026-08-06
13	Central Pike EB @ Mt Juliet	EB	Active on city webpage	Unknown	2026-08-06
14	Central Pike NB @ Adams Lane	NB	Active on city webpage	Unknown	2026-08-06
15	North Mt. Juliet Rd NB @ Pleasant Grove / Northbound	NB	Active on city webpage	Unknown	2026-08-06
16	North Mt. Juliet Rd. SB @ Pleasant Grove / South Bound	SB	Active on city webpage	Unknown	2026-08-06
17	Central Pk EB from S MJ Rd	EB	Active on city webpage	Unknown	2026-08-06
18	North Mt. Juliet Rd. SB @ Hwy 70 / South Bound	SB	Active on city webpage	Unknown	2026-08-06
19	Hwy 70 EB @ North Mt. Juliet Rd. / Eastbound	EB	Active on city webpage	Unknown	2026-08-06
20	Hwy 70 WB @ North Mt. Juliet Rd / West Bound	WB	Active on city webpage	Unknown	2026-08-06
21	Robinson Park Trailhead - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
22	Mundy Park - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
23	Beckwith Rd @ Wilfong Pkwy - SB	SB	Active on city webpage	Unknown	2026-08-06
24	Grace Road- Bradshaw Farms Trailhead - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
25	Mt. Juliet Soccer Park Trailhead - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
26	Ethan Page Park Trailhead - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
27	Cedar Creek Greenway - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
28	Belinda Pkwy EB @ Providence Trail - EB	EB	Active on city webpage	Unknown	2026-08-06
29	South Rutland Rd @ Baird Farms Construction Entrance - NB	Entrance	Active on city webpage	Unknown	2026-08-06
30	Providence Pkwy @ Central Pike - WB	WB	Active on city webpage	Unknown	2026-08-06
31	N Mt Juliet Rd @ Division St - NB	NB	Active on city webpage	Unknown	2026-08-06
32	Nonaville Rd SB @ Saundersville Rd - SB	SB	Active on city webpage	Unknown	2026-08-06
33	South Green Hill NB @ West Division St - NB	NB	Active on city webpage	Unknown	2026-08-06
34	Lebanon Rd @ Terrace Hill Rd WB	WB	Active on city webpage	Unknown	2026-08-06
35	Lebanon Rd E of Curd Rd EB	EB	Active on city webpage	Unknown	2026-08-06
36	Old Lebanon Dirt Rd @ N Mt Juliet Rd - WB	WB	Active on city webpage	Unknown	2026-08-06
37	Providence Way @ S Mount Juliet Rd - WB	WB	Active on city webpage	Unknown	2026-08-06
38	N Mount Juliet Rd @ E Division St - WB	WB	Active on city webpage	Unknown	2026-08-06
39	Old Lebanon Dirt Rd @ N Mt Juliet Rd - EB	EB	Active on city webpage	Unknown	2026-08-06
40	Old Lebanon Dirt Rd @ Davidson County Line - WB	WB	Active on city webpage	Unknown	2026-08-06
41	Golden Bear Gtwy @ Vanner Rd - NB	NB	Active on city webpage	Unknown	2026-08-06
42	Charlie Daniels Park - Inbound	Inbound	Active on city webpage	Unknown	2026-08-06
43	Golden Bear Gtwy @ Hwy 70 - SB	SB	Active on city webpage	Unknown	2026-08-06
44	West Division St @ Davidson County Line - WB	WB	Active on city webpage	Unknown	2026-08-06
45	Del Web Blvd @ S Rutland Rd - Exit	Exit	Active on city webpage	Unknown	2026-08-06
46	Providence Pkwy @ Central Pike - EB	EB	Active on city webpage	Unknown	2026-08-06
47	Del Web Blvd @ S Rutland Rd - Entrance	Entrance	Active on city webpage	Unknown	2026-08-06
48	Old Pleasant Grove Rd @ Pleasant Grove Pl - EB	EB	Active on city webpage	Unknown	2026-08-06
49	Pleasant Grove Rd @ WalMart - EB	EB	Active on city webpage	Unknown	2026-08-06
50	Providence Pkwy @ Providence Trl - WB	WB	Active on city webpage	Unknown	2026-08-06
51	S Rutland Rd @ Beckwith Rd - WB	WB	Active on city webpage	Unknown	2026-08-06
52	Golden Bear Gateway @ Vanner Rd - SB	SB	Active on city webpage	Unknown	2026-08-06
53	Lebanon Rd @ Nonaville Rd - EB	EB	Active on city webpage	Unknown	2026-08-06
54	Belinda Pkwy @ Providence Trl - WB	WB	Active on city webpage	Unknown	2026-08-06
55	Leesa Ann Ln @ Darrington Way - WB	WB	Active on city webpage	Unknown	2026-08-06
56	Old Lebanon Dirt Rd @ Kelsey Glen Dr - EB	EB	Active on city webpage	Unknown	2026-08-06
57	Pleasant Grove Rd @ Old Pleasant Grove Rd - WB	WB	Active on city webpage	Unknown	2026-08-06
58	Golden Bear Gateway @ I 40 On Ramp - SB (Covers WB Ramp)	WB	Active on city webpage	Unknown	2026-08-06
59	Belinda Pkwy EB @ I-40 Ramp - EB	EB	Active on city webpage	Unknown	2026-08-06
60	Beckwith Rd @ Summit Blvd - NB	NB	Active on city webpage	Unknown	2026-08-06
61	Golden Bear Gtwy @ Beckwith Rd - NB	NB	Active on city webpage	Unknown	2026-08-06
62	North Mt. Juliet Rd. NB @ I-40 / Northbound	NB	Active on city webpage	Unknown	2026-08-06
63	I-40 On-Ramps @ North Mt. Juliet Rd / Westbound	WB	Active on city webpage	Unknown	2026-08-06
64	North Mt. Juliet Rd SB @ Division St. / South Bound	SB	Active on city webpage	Unknown	2026-08-06
65	Hwy 70 WB @ Davidson County Line / Westbound	WB	Active on city webpage	Unknown	2026-08-06
66	Hwy 70 EB @ Davidson County Line / Eastbound	EB	Active on city webpage	Unknown	2026-08-06
67	Pleasant Grove Rd @ WalMart - WB	WB	Active on city webpage	Unknown	2026-08-06
68	South Mt. Juliet Rd. @ I-40 / Southbound on Mt. Juliet Rd @ I-40	SB	Active on city webpage	Unknown	2026-08-06
69	South Mt. Juliet Rd NB @ Central Pike / North Bound	NB	Active on city webpage	Unknown	2026-08-06
70	South Mt. Juliet Rd. @ I-40 / I-40 Eastbound On-Ramp	EB	Active on city webpage	Unknown	2026-08-06
71	Lebanon Rd @ S Greenhill Rd EB	EB	Active on city webpage	Unknown	2026-08-06
72	Lebanon Rd @ S Greenhill Rd SB	SB	Active on city webpage	Unknown	2026-08-06
73	Lebanon Rd @ Sunset Dr - WB	WB	Active on city webpage	Unknown	2026-08-06

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.

Evidence & sources (3)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Original source
Supports: contract amount, contract term, historical or explanatory note
Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-06-09 meetingMeeting June 9, 2025
Location: Agenda item 14.M · File 1274 · Resolution 50-2025
Original source
Context only Relevant to approval body, vote result.
Supports: On June 9, 2025, the Mt. Juliet Board adopted the modified Flock agreement under file 1274 as Resolution 50-2025.
Mt. Juliet Board minutes — July 28, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-07-28 meetingMeeting July 28, 2025
Location: Agenda item 10.C · File 1331 · Resolution 61-2025
Original source
Context only Relevant to approval body, vote result.
Supports: On July 28, 2025, the Mt. Juliet Board adopted the second modified Flock agreement under file 1331 as Resolution 61-2025.

2025-06-09Flock Safety

Modified 10-year Safe City agreement

$6,950,300

10-year payment schedule

Current corrected contract total from the second modified agreement approved July 28, 2025. The superseded June 2 order form showed $6,950,300 on its summary but an erroneous $6,920,300 billing-schedule total. Contract authorization is not proof of invoiced or paid spending.

Evidence & sources (4)

Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Contract Total · Billing Schedule · p. 3 · Contract Total
Original source
Supports: contract amount, contract term
Context only Relevant to historical or explanatory note.
Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-06-09 meetingMeeting June 9, 2025
Location: Agenda item 14.M · File 1274 · Resolution 50-2025
Original source
Supports: record date, approval body, vote result
Flock Safety Safe City order form and agreementContractSuperseded version
City of Mt. Juliet and Flock Safety
Legistar file 1274 order form created 2025-06-02Document created June 2, 2025
Location: Order Form · p. 2 · Contract Total · Billing Schedule · p. 3 · Contract Total
Original source
Context only Relevant to historical or explanatory note.
Supports: The superseded June 2 order-form summary displayed a Contract Total of $6,950,300.
Supports: The superseded June 2 billing schedule displayed a conflicting Contract Total of $6,920,300.
Mt. Juliet Board minutes — July 28, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-07-28 meetingMeeting July 28, 2025
Location: Agenda item 10.C · File 1331 · Resolution 61-2025
Original source
Context only Relevant to historical or explanatory note.
Supports: On July 28, 2025, the Mt. Juliet Board adopted the second modified Flock agreement under file 1331 as Resolution 61-2025.

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.

Evidence & sources (1)

Rekor selected for Guardian ShieldOfficial announcementHistorical
Mt. Juliet Police Department
Published 2020-01-08Published Jan. 8, 2020
Original 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.

Evidence & sources (1)

MJPD ALPR proposal and potential locationsOfficial announcementHistorical
Mt. Juliet Police Department
Published 2019-11-27Published Nov. 27, 2019
Original 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.

Evidence & sources (1)

MJPD ALPR proposal and potential locationsOfficial announcementHistorical
Mt. Juliet Police Department
Published 2019-11-27Published Nov. 27, 2019
Original source
Official statement

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.

Evidence & sources (1)

Mt. Juliet Ordinance 2019-40City ordinanceCurrent
Mt. Juliet Board of Commissioners
Ordinance 2019-40 adopted textAdopted Sept. 9, 2019
Original source
City ordinance

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.

Evidence & sources (1)

Mt. Juliet Ordinance 2019-40City ordinanceCurrent
Mt. Juliet Board of Commissioners
Ordinance 2019-40 adopted textAdopted Sept. 9, 2019
Original source
City ordinance Documents this statement: Mt. Juliet Ordinance 2019-40 establishes a 30-day city retention cap, subject to an investigation exception.
Supports the legal cap described in legacy records; the ordinance does not establish the vendor's active configuration. A precise source locator remains unavailable.

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.

Evidence & sources (1)

MJPD ALPR proposal and potential locationsOfficial announcementHistorical
Mt. Juliet Police Department
Published 2019-11-27Published Nov. 27, 2019
Original source
Official statement

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.

Evidence & sources (1)

Rekor selected for Guardian ShieldOfficial announcementHistorical
Mt. Juliet Police Department
Published 2020-01-08Published Jan. 8, 2020
Original source
Official statement

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.

Evidence & sources (1)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Original source
Written policy Supports: record date, summary, verification status
The current copy records the original issue date; it does not preserve the 2020 text.

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.

Evidence & sources (1)

MJPD News Guardian Shield archiveOfficial news archive
Mt. Juliet Police Department
Original source
Official statement

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.

Evidence & sources (1)

MJPD News Guardian Shield archiveOfficial news archive
Mt. Juliet Police Department
Original source
Official statement

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.

Evidence & sources (1)

Mt. Juliet Flock transition authorization attachmentAgenda Attachment
City of Mt. Juliet
Original 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.

Evidence & sources (1)

Mt. Juliet Flock transition authorization attachmentAgenda Attachment
City of Mt. Juliet
Original 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 superseded June order form displayed a 30-day agreement-level retention field. Historical legacy records described a 21-day MJPD policy; the current August 19, 2026 written policy is 7 days. None of those records establishes the actual configured ALPR retention.

Evidence & sources (2)

Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-06-09 meetingMeeting June 9, 2025
Location: Agenda item 14.M · File 1274 · Resolution 50-2025
Original source
Official statement Supports: record date, action, motion, mover, seconder, vote result, yes votes, no votes, discussion
Flock Safety Safe City order form and agreementContractSuperseded version
City of Mt. Juliet and Flock Safety
Legistar file 1274 order form created 2025-06-02Document created June 2, 2025
Location: Order Form · p. 2 · Contract Total · Billing Schedule · p. 3 · Contract Total · Order Form · p. 2 · Retention Period
Original source
Contracted Supports: cost scope, historical or explanatory note
These figures describe the superseded June version, including its internal total discrepancy; they are not the corrected current total or actual ALPR configuration.

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.

Evidence & sources (1)

Flock Safety Safe City order form and agreementContractSuperseded version
City of Mt. Juliet and Flock Safety
Legistar file 1274 order form created 2025-06-02Document created June 2, 2025
Original source
Contracted

July 28, 2025

Board approves second modified Safe City agreement

Council vote / contract correctionAdopted; see published minutesVerified approval event and corrected agreement total

Resolution 61-2025 adopted the second modified Flock agreement under file 1331. The corrected agreement displays matching $6,950,300 summary and billing-schedule totals.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

This event supersedes the June billing-schedule total as a current contract figure while preserving the June discrepancy as history.

Evidence & sources (2)

Mt. Juliet Board minutes — July 28, 2025Meeting minutesHistorical
Mt. Juliet Board of Commissioners
Minutes for the 2025-07-28 meetingMeeting July 28, 2025
Location: Agenda item 10.C · File 1331 · Resolution 61-2025
Original source
Official statement Supports: record date, action, verification status
Flock Safety Safe City order form and agreementContractCurrent
City of Mt. Juliet and Flock Safety
Second modification, Docusign envelope 9064D018-99CB-47C5-B74B-82ED15EDEA7AVendor signed July 17, 2025
Location: Order Form · p. 2 · Contract Total · Billing Schedule · p. 3 · Contract Total
Original source
Contracted Supports: summary, cost scope, historical or explanatory note

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.

Evidence & sources (1)

MJPD Flock911 and Safe City announcementOfficial announcementHistorical
Mt. Juliet Police Department
Published 2026-02-04Published Feb. 4, 2026
Original source
Official statement

June 15, 2026

Legacy dataset recorded an earlier policy-amendment date

Policy / oversightAdministrative policy; no council vote identifiedHistorical legacy description; underlying June 15 version missing

Legacy public data described General Order 10D.6 as amended June 15, 2026 and calling for 21-day retention. No immutable copy of that revision is currently preserved, so this is retained as historical provenance rather than current policy.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

The historical 21-day description is not current. It also did not establish actual system configuration.

Evidence & sources (1)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policy
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
Original source
Historical Context only Relevant to record date, title, summary, historical or explanatory note, verification status.
No immutable June 15 policy version is preserved; this record is historical provenance, not the current policy.

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.

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement

August 13, 2026

Flock announces a 7-day recommended/default ALPR retention period

Vendor retention guidanceNo city vote; vendor announcementVerified vendor announcement; local adoption unresolved

Flock announced a change from its 30-day recommendation/default to 7 days while stating that existing customers would keep their existing periods unless they adopted the recommendation.

Citizen comments: Not applicable.

Written comments: Not applicable.

Keep vendor guidance separate from MJPD written policy and actual system configuration.

Evidence & sources (1)

Flock Updates Privacy, Accountability, Security, and Transparency SafeguardsVendor documentationHistorical
Flock Safety
Published 2026-08-13Published Aug. 13, 2026
Location: Section “Privacy”
Original source
Vendor-described capability Supports: On August 13, 2026, Flock changed its recommended/default ALPR retention period from 30 days to 7 days while stating that existing customers would keep their current periods unless they adopted the recommendation.
Supports the vendor's recommendation/default change and its express existing-customer caveat; it does not establish a Mt. Juliet setting or policy decision.
Vendor-described capability Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
A vendor recommendation/default change does not establish whether an existing Mt. Juliet account adopted it.

August 19, 2026

Current MJPD ALPR policy amended

Policy / oversightAdministrative policy; no council vote identifiedVerified current amendment and written retention rule

The verified current General Order 10D.6 is marked amended August 19, 2026 and sets a maximum 7-day retention period for license-plate reads, subject to its investigation exception and destruction conditions.

Citizen comments: Not yet determined.

Written comments: Not yet determined.

Current written policy: 7 days. Actual configured ALPR retention remains unresolved.

Evidence & sources (1)

MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent
Mt. Juliet Police Department · Tyler Chandler, Chief of Police
General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026
Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing
Original source
Written policy Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions.
Directly supports the current written seven-day maximum and investigation exception. Written policy does not establish the live Flock account setting.
Written policy Does not establish this on its own The currently active MJPD ALPR retention configuration is not established by the reviewed public statements, written policy, ordinance, contract language, or vendor recommendation.
The verified written seven-day policy is not proof of the active vendor configuration.

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.

Open full MJPD spreadsheet ↗

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 ↗

Jul 30, 2026Stolen 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.

MJPD spreadsheet row 100

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

May 31, 2026Missing 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.

MJPD spreadsheet row 4

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

Apr 30, 2026Investigative 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.

MJPD spreadsheet row 5

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

Feb 11, 2026Investigative 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.

MJPD spreadsheet row 6

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

Jan 10, 2026Investigative 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.

MJPD spreadsheet row 7

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

Jan 8, 2026Stolen 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.

MJPD spreadsheet row 8

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

DOCUMENTED USE LOG

Selected cases with ALPR’s reported role

This separate research log preserves the reported alert role, outcome, and verification limits for selected incidents. It does not replace the recent-entry view above or add facts beyond MJPD’s published account.

2026-05-31Mt. Juliet Police Department

Missing-person vehicle alert led officers to vehicle and wanted passenger

ALPR triggered officer response

MJPD report: MJPD says Flock cameras alerted officers to the missing-person vehicle.

Reported result: Missing person located and welfare checked; passenger with warrants transported to jail.

Entered from MJPD public successful-interceptions spreadsheet; underlying case report not yet reviewed.

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

2026-04-30Mt. Juliet Police Department

Investigative hotlist alert used to locate fleeing suspect

ALPR triggered officer response

MJPD report: A locally created investigative alert in Flock triggered the response.

Reported result: Vehicle stopped; suspect detained and transported to Wilson County Jail.

Useful example of a locally created investigative alert rather than an automatic stolen-vehicle hit.

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

2026-02-11Mt. Juliet Police Department

Investigative alert connected to counterfeit-money investigation

ALPR triggered officer response

MJPD report: MJPD says Flock generated an alert from a locally added investigative entry.

Reported result: Wanted suspect detained; other passengers also arrested for separate warrants/drug charges.

Underlying incident report not yet reviewed.

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

2025-01-30Mt. Juliet Police Department

Stolen Chrysler alert preceded attempted stop and later arrests

ALPR triggered officer response

MJPD report: MJPD says Guardian Shield alerted officers to the stolen car entering Mt. Juliet.

Reported result: MJPD attempted a stop; vehicle fled; surrounding agencies later located it and two people were arrested.

Shows an ALPR alert beginning a multi-agency response even when MJPD did not complete the initial stop.

Evidence & sources (1)

MJPD Guardian Shield documented-use spreadsheetOfficial spreadsheet
Mt. Juliet Police Department
Original source
Department-reported outcome

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Images not used for an investigation are generally retained no more than 7 days.
The documented 2026-08-24 webpage observation is the source of the seven-day statement; it does not verify the active vendor configuration.

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Every search is logged and subject to supervisory review and regular audits.
Supports the existence of the official logging and audit statement, not operational compliance.

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Only trained and authorized personnel may access the ALPR system.
Supports the existence of the official access-control statement, not operational compliance.

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

Evidence & sources (2)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Guardian Shield does not track people.
Supports that MJPD made the statement in the ALPR-focused Guardian Shield explanation.
Flock AI video analytics — Guardian Mode and People Detection AlertsVendor documentation
Flock Safety
Original source
Vendor-described capability Context only Guardian Shield does not track people.
Legacy records describe vendor people/vehicle detection and following capability, but no defensible source version or local purchase, enablement, configuration, or use is established.

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Information is shared only with authorized government agencies for legitimate law-enforcement purposes and required documentation.
Supports the existence of the official sharing statement, not actual sharing activity or configuration.

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Documents this statement: Officers must have a documented investigative reason and, when required, reasonable suspicion to search the system.
Supports the existence of the official query-justification statement, not operational compliance.

Video AI configuration

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

Not established / unresolved

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

Evidence & sources (1)

Guardian Shield License Plate Reader ProgramOfficial webpageCurrent
Mt. Juliet Police Department
Observed 2026-08-24Observed Aug. 24, 2026
Original source
Official statement Does not establish this on its own The public can determine which city video cameras have automated person detection, tracking or AI search enabled.
The reviewed page does not provide camera/feed-level AI enablement details.

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.

Date	Type	Title	Publisher	Summary	Canonical provenance
2019-09-09	Ordinance	Ordinance 2019-40 — ALPR regulation	Mt. Juliet Board of Commissioners	City ordinance addressing retention, automated traffic enforcement, disclosure, and automatic sharing.	Evidence & sources (1) Mt. Juliet Ordinance 2019-40City ordinanceCurrent Mt. Juliet Board of Commissioners Ordinance 2019-40 adopted textAdopted Sept. 9, 2019 Original source City ordinance
2026-08-19	Police policy	MJPD General Order 10D.6 — Automated License Plate Recognition Program	Mt. Juliet Police Department	Current amended policy covering use, query justification, audit trail, 7-day written retention, audits, sharing, and reporting; actual configured ALPR retention remains unresolved.	Evidence & sources (1) MJPD General Order 10D.6 — Automated License Plate Recognition ProgramDepartment policyCurrent Mt. Juliet Police Department · Tyler Chandler, Chief of Police General Order 10D.6 amended 2026-08-19Amended Aug. 19, 2026 Location: PDF p. 6 · §4.D.V · Data Storage, Retention, & Sharing Original source Written policy Supports: The current amended MJPD General Order 10D.6 sets a maximum seven-day retention period for license-plate reads unless they are retained as part of an ongoing investigation, subject to the policy's destruction conditions. Directly supports the current written seven-day maximum and investigation exception. Written policy does not establish the live Flock account setting.
2025-06-09	Contract	Flock Safe City order form	Mt. Juliet / Flock Safety	Ten-year Safe City agreement and payment schedule.	Evidence & sources (1) Flock Safety Safe City order form and agreementContractSuperseded version City of Mt. Juliet and Flock Safety Legistar file 1274 order form created 2025-06-02Document created June 2, 2025 Original source Contracted
2025-06-09	Meeting minutes	Board minutes — Resolution 50-2025	Mt. Juliet Board of Commissioners	Published minutes showing unanimous approval of modified Flock Safe City agreement.	Evidence & sources (1) Mt. Juliet Board minutes — June 9, 2025Meeting minutesHistorical Mt. Juliet Board of Commissioners Minutes for the 2025-06-09 meetingMeeting June 9, 2025 Location: Agenda item 14.M · File 1274 · Resolution 50-2025 Original source Official statement Supports: On June 9, 2025, the Mt. Juliet Board adopted the modified Flock agreement under file 1274 as Resolution 50-2025. Establishes the government approval event only; it is not the order form's created, publication, or execution-based effective date.
2025-06-02	Contract	Flock Safety Safe City order form — product and feature descriptions	City of Mt. Juliet / Flock Safety	Lists 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.	Evidence & sources (1) Flock Safety Safe City order form and agreementContractSuperseded version City of Mt. Juliet and Flock Safety Legistar file 1274 order form created 2025-06-02Document created June 2, 2025 Original source Contracted
2026-08-06	City webpage	MJPD Drone as a First Responder program page	Mt. Juliet Police Department	Public program details including implementation/testing status, two strategically placed drone docks, one radar with citywide coverage and promised flight transparency portal.	Evidence & sources (1) Drone as a First ResponderOfficial webpage Mt. Juliet Police Department Original source Official statement
2026-08-06	City webpage	MJPD recruiting page — Safe City, city-wide LPR and camera networks	Mt. Juliet Police Department	MJPD publicly describes an advanced Flock Safe City program, funded DFR program, city-wide LPR network and city-wide camera network.	Evidence & sources (1) Join Mt. Juliet Police DepartmentOfficial webpage Mt. Juliet Police Department Original source Official statement
2026-04-07	State law	Tennessee Public Chapter 672 / SB1879 — ALPR captured-data confidentiality sunset removed	Tennessee General Assembly	Removes the scheduled sunset of the Tennessee public-records confidentiality provision for captured ALPR data.	Evidence & sources (1) Tennessee SB1879 / Public Chapter 672 — ALPR confidentialityState lawHistorical Tennessee General Assembly SB1879, 114th General Assembly legislative record Original source State law
2026-06-26	Other	Flock AI video analytics — Guardian Mode and People Detection Alerts	Flock Safety	Flock 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.	Evidence & sources (1) Flock AI video analytics — Guardian Mode and People Detection AlertsVendor documentation Flock Safety Original source Vendor-described capability
2026-08-07	Other	Flock video cameras / Condor product page	Flock Safety	Current Flock video-camera page lists Guardian Mode, People Detection Alerts, Visual Alerts and FreeForm as AI features.	Evidence & sources (1) Flock Condor video-camera product pageVendor documentation Flock Safety Original source Vendor-described capability
2026-08-07	Other	Flock FreeForm product page	Flock Safety	Flock 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.	Evidence & sources (1) Flock FreeForm product pageVendor documentation Flock Safety Original source Vendor-described capability
2026-08-07	Other	Flock Wing Gateway 2.0 — third-party video integration and AI analytics	Flock Safety	Flock 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.	Evidence & sources (1) Flock Wing Gateway 2.0 announcementVendor documentation Flock Safety Original source Vendor-described capability

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.

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.

See the archived system by site and device type

How visible is your drive?

Provisional transparency score

System inventory & scope

Spending & procurement

Rules & legal documents

Access & data-sharing transparency

Audit & compliance publication

Use & outcome reporting

Public governance & change control

What can the system actually do?

Flock Safety LPR — Codename: Falcon

Local status

Sharing and integration

Unresolved locally

Retention and storage

Unresolved locally

Supporting context

Contract and implementation

Unresolved locally

Flock Safety Video Camera PTZ — Codename: Condor

Contract and implementation

Unresolved locally

Capability

Unresolved locally

Capability

Unresolved locally

Guardian Mode — automated PTZ subject tracking

Capability

Unresolved locally

Capability

Unresolved locally

Unresolved locally

City-wide fixed camera network

Local status

Contract and implementation

Unresolved locally

Capability

Flock Video Integration Gateway 2.0 — Codename: Wing

Unresolved locally

Supporting context

Contract and implementation

Contract and implementation

Unresolved locally

Capability

FreeForm AI search

Contract and implementation

Contract and implementation

Unresolved locally

Capability

Unresolved locally

Community Network / private-camera partnerships

Sharing and integration

Contract and implementation

Contract and implementation

FlockOS Premium

Contract and implementation

Contract and implementation

Unresolved locally

Flock911

Local status

Contract and implementation

Contract and implementation

Flock Safety Gunshot Detection (formerly Raven)

Contract and implementation

Acoustic car-crash detection

Local status

Flock Mobile Security Trailer

Contract and implementation

Flock Aerodome Drone as First Responder

Local status

Contract and implementation

Contract and implementation

Flock Aerodome DFR Radar

Local status

Contract and implementation

Flock Nova — Customer Data / OSINT

Contract and implementation

Contract and implementation

Traffic Analytics