License-plate readers · Wicomico County

Wicomico County

Using license-plate readers · 2 agencies documented

← Statewide map
Allegany County CountyAnne Arundel County CountyBaltimore County CountyBaltimore city CountyCalvert County CountyCaroline County CountyCarroll County CountyCecil County CountyCharles County CountyDorchester County CountyFrederick County CountyGarrett County CountyHarford County CountyHoward County CountyKent County CountyMontgomery County CountyPrince George's County CountyQueen Anne's County CountySomerset County CountySt. Mary's County CountyTalbot County CountyWashington County CountyWicomico County CountyWorcester County County

Wicomico County Sheriff's Office

Status
Program documented, current use unconfirmed
Vendors
Vendor not named in source
Cameras
Count not documented
No count found. A 2011 general order covers mobile (vehicle) and fixed plate readers.
  1. July 1, 2011 The Sheriff's Office issued a general order setting rules for its plate-reader program, with data kept on its own server and use limited to official law-enforcement purposes. (Wicomico County Sheriff's Office (document hosted by the ACLU), July 1, 2011)
  2. 2015 The office was listed among 14 Maryland agencies running their own plate-reader data server in 2015; the state report shows no reads submitted from it that year. (Maryland Coordination and Analysis Center, March 1, 2016)
Conflicts and open questions
  • No source after 2016 found; the office does not appear in the 2024-2026 state reports' lists of agencies reporting their own systems.

From agency records.

Salisbury Police Department

Status
Using license-plate readers
Vendors
Flock Safety
Cameras
40
40 Flock license plate readers plus 40 pan-tilt-zoom video cameras and three mobile camera trailers when fully deployed; police said in August 2026 the system was about 70% deployed.
Contract
Flock Safety: $1,107,070 term · from Dec. 2025 · approved by Salisbury City Council, 2025-12 (unanimous, per The Baltimore Sun) · Three-year total as reported by WBOC before the vote: $398,890 in year one for equipment and installation, then $354,090 a year. Mayor Randy Taylor put it at about $1.1 million over three years (WMDT). Covers the license plate readers and the video cameras together. (WBOC, Dec. 15, 2025; WMDT 47abc, Dec. 22, 2025; The Baltimore Sun (via Yahoo News), Feb. 1, 2026)
  1. 2015 Salisbury police were listed among 14 Maryland agencies running their own plate-reader data server in 2015; the state report shows no reads submitted from it that year. (Maryland Coordination and Analysis Center, March 1, 2016)
  2. Dec. 2025 The City Council unanimously approved a three-year Flock agreement for 40 plate readers and 40 video cameras. (WBOC, Dec. 15, 2025; The Baltimore Sun (via Yahoo News), Feb. 1, 2026)
  3. July 2026 The Wicomico County NAACP asked the city for information on camera placement, data use and outside access; Mayor Taylor said placement follows crime data and the system was about 75% in place. (WBOC, July 30, 2026)
  4. Aug. 2026 Police said plate data is kept 30 days, searches by outside agencies are run by Salisbury officers only with a case number, and the system has no facial recognition or audio. (WBOC, Aug. 7, 2026; WMDT 47abc, Aug. 7, 2026; The Baltimore Sun (republished by WBFF FOX45), Aug. 21, 2026)
  5. Aug. 6, 2026 Police Chief Dave Meienschein issued an open letter on the Flock system, and the department opened an online Flock transparency portal. (WBOC, Aug. 6, 2026)
Conflicts and open questions
  • Dated by month: WBOC (Dec. 15, 2025) said the vote was expected that Monday night; The Baltimore Sun (Feb. 1, 2026) says only that the council approved it in December.
  • The Sun gives the contract as nearly $400,000 (the first-year figure); WBOC gives the three-year total.
  • Flock transparency portal not reachable in this run (blocked).

Reported by news outlets; agency records not yet obtained.

Statewide

  1. April 14, 2014 The governor signed SB 699 (Chapter 192 of 2014), effective Oct. 1, 2014. It limits police use of captured plate data to a "legitimate law enforcement purpose," shields reader data from the Public Information Act, requires the State Police and agencies using readers to adopt operating and audit procedures, and requires annual reports to the General Assembly starting in 2016. (Maryland General Assembly, April 14, 2014; Maryland Department of Legislative Services, 2015)
  2. March 18, 2015 The House Judiciary Committee gave an unfavorable report to HB 417, which would have barred police from stopping a driver solely because plate-reader data showed the owner held a handgun carry permit. A similar bill, HB 1398, was filed in 2017; the legislature's site shows a March 14 hearing scheduled and no later action. (Maryland General Assembly, March 18, 2015; Maryland Department of Legislative Services, 2015; Maryland General Assembly, 2017)
  3. Oct. 1, 2015 MCAC sent its model audit policy for plate-reader data, developed in August 2015, to all Maryland law enforcement agencies. Under it, agencies audit a random sample of at least 1% of searches (minimum 50). (Maryland State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 5, 2025; Maryland Department of State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 1, 2026)
  4. May 16, 2024 The governor signed HB 1081 and SB 840 (Chapters 875 and 876 of 2024), effective Oct. 1, 2024. The law covers plate data stored in the cloud, makes captured data the property of the agency that collected it, bars its sale, allows certain data to be uploaded to MCAC, and extends penalties to vendors working for police. The House passed it 119-17 and the Senate 47-0. (Maryland General Assembly, May 16, 2024; Maryland General Assembly, 2024)
  5. Feb. 4, 2025 MCAC's report to legislators for calendar 2024 counted 857 reader units connected to the center and 1,010,086,796 reads retained from 18 agencies. It logged 5,221 requests to the center, 732 of them federal (609 resulting in a release), and reported no breaches. (Maryland State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 5, 2025)
  6. Feb. 27, 2026 MCAC's report for calendar 2025 counted 1,077 reader units connected to the center and 1,188,559,099 reads from 19 agencies. It logged 4,737 requests, 674 of them federal (570 resulting in a release), and reported no breaches. MCAC said it could not confirm that the agencies whose reports it forwarded were the only ones in Maryland using plate readers. (Maryland Department of State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 1, 2026; The Baltimore Sun (via WBFF FOX45), Aug. 25, 2026)
  7. Aug. 2026 After a Baltimore Sun analysis of the state reports, Sen. Charles Sydnor III (D-Baltimore County) said his office had begun collecting information to decide whether more legislation is needed. In October, The Banner reported that Sydnor, Senate Minority Leader Steven Hershey and Del. N. Scott Phillips want the 2027 session to look at private-sector plate readers, which state law does not regulate. (The Baltimore Sun (via WBFF FOX45), Aug. 25, 2026; The Baltimore Banner, Oct. 1, 2026)

State agencies

Maryland State Police (Maryland Coordination and Analysis Center)

Status
Using license-plate readers
Vendors
Vendor not named in source
Cameras
Count not documented
No unit count given for the State Police's own readers. MCAC runs the state's central plate-data server, and 1,077 units statewide were connected to it in 2025.
  1. Feb. 4, 2025 MCAC reported 73,402,736 reads from its own (State Police) readers in 2024, with 58 MCAC employees authorized to search the database. (Maryland State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 5, 2025)
  2. Feb. 27, 2026 MCAC reported 79,915,710 reads from State Police readers in 2025. It audited 80 of the 4,737 requests it received, and 58 employees were authorized to search. (Maryland Department of State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 1, 2026)
  3. April 1, 2026 In an April 1, 2026 letter on HB 1166, a front-plate bill, the State Police said plate readers used by Maryland law enforcement include fixed and mobile units, and that program figures show 30% to 40% of plates read by mobile units are front plates. (Maryland Department of State Police, Government Affairs Section, April 1, 2026)
Conflicts and open questions
  • Vendor not stated in the records found.

From agency records.

Maryland Transportation Authority Police

Status
Using license-plate readers
Vendors
Vendor not named in source
Cameras
126
126 cameras in 2025: 86 at nine fixed locations and 40 on 20 mobile units (124 in 2024).
  1. 2016 The State Police report for 2015 listed MDTA Police with 54,246,732 reads from fixed units and 1,519,931 from mobile units. (Maryland Coordination and Analysis Center, March 1, 2016)
  2. 2025 MDTA Police said its readers made 288,972,074 reads in 2024 and 303,253,851 in 2025, all sent to MCAC. Its own server keeps reads for no more than 14 days. MCAC's table counted 296,536,235 MDTA reads for 2025, the most of any agency. (Maryland State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 5, 2025; Maryland Department of State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 1, 2026)
  3. Feb. 19, 2026 The MDTA Office of Audits' compliance audit of 2025 plate-reader use (report INT 2026-07) found controls working and no reportable findings. (Maryland Department of State Police / Maryland Coordination and Analysis Center (via Department of Legislative Services Library), March 1, 2026)
Conflicts and open questions
  • The Banner (Oct. 1, 2026) gave 1.5 million reads for 2015, which matches the mobile-unit count in the 2016 state report only.
  • Report figures differ: MDTA's own total and MCAC's table for 2025 are not the same; both are given as filed.

From agency records.