Merced Police | Vigilant license plate readers
Merced Police operates Motorola Vigilant license plate readers. In April 2026, the department said it disabled sharing connections to certain federal agencies after an internal review.
How it happened
- Context
Department issues an ALPR policy
Policy 436 governs official use, alert verification, access logs, audits, retention, and sharing. It is a historical policy and may not describe the current configuration. [2]
- Incident
Department announces a sharing review
Merced Police says prior configurations allowed sharing with certain federal agencies. It says those connections were disabled and that further audits would follow. [1]
What the department disclosed
On April 23, 2026, Merced Police said an internal review found that prior license plate reader configurations had allowed sharing with certain federal agencies. The department said it disabled those connections and would conduct further audits. It identified the system as Motorola Vigilant, not Flock Safety.[1]
The statement does not identify the agencies, the dates of access, or the number and purpose of searches. It also does not say that the system was shut down.
The published historical rules
The department’s May 2019 Policy 436 permits ALPR use for official law-enforcement purposes and does not require reasonable suspicion before a search. It directs members to verify an alert through CLETS when practical and requires access logs and periodic audits.[2]
That policy states that server data is kept for at least one year and permits sharing with law-enforcement and prosecutorial agencies. It predates the April 2026 configuration change, so it should not be read as a complete statement of the current sharing network.[2][1]
The city’s transparency page links a current ALPR Agency Report, but the document host returned a 403 response to the automated fetcher. That report, current configuration records, and audit results are the next records needed.
Questions
- Does Merced Police use Flock cameras?
- The department says its ALPR vendor is Motorola Vigilant, not Flock Safety. A separate county Sheriff program uses Flock. [1]
- Did federal agencies have access?
- Merced Police says an internal review found prior configurations that allowed sharing with certain federal agencies. It says those connections were disabled. [1]
- How long is plate data kept?
- The 2019 policy states at least one year, but the current configuration and current Agency Report were not available to the automated review. [2]
- Does an alert have to be confirmed?
- The 2019 policy directs members to verify an alert through CLETS when practical. [2]
On the map
The community has mapped 62 devices of this type in the county on OpenStreetMap. These are community reports: the vendor and operator of each point are unverified, and none is confirmed to belong to this system. See them on the map →
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
Street names from reverse geocoding — © OpenStreetMap contributors (ODbL).
What we do not know
- What does the current ALPR Agency Report say about retention, searches, sharing, and audits?
- Which federal connections existed, when were they enabled, and which searches were run?
- What configuration and policy changes were completed after the April 2026 statement?
- How many fixed and mobile cameras are operational?
What you can do
Show up
Systems like this one are approved by boards, councils and committees that meet in public. We have not yet confirmed where each of them meets in Merced County.
What we have documented in Merced County →Protect yourself
Practical steps to shrink your personal data trail. Our guides publish at launch; until then, EFF's Surveillance Self-Defense is the best starting point.
Surveillance Self-Defense →Sources
- 1. Merced Police statement on ALPR data sharing, April 23, 2026 · Primary document · · accessed · archived copy
- 2. Merced Police policy manual, May 6, 2019, Policy 436 · Primary document · · accessed · archived copy
Get the digest
A regular digest of what changed in the world of surveillance: the counties we published, the devices that appeared on the map, and the public meetings where these decisions get made. We send it when there is enough to report.
One click to unsubscribe. What we do with your address is on the newsletter page.