All 12 criteria of the published standard, including
the 9 not yet examined. A criterion that has not been
assessed is shown as unexamined rather than omitted — otherwise a record
could look complete by leaving out the awkward questions.
-
01
No persistent mass ALPR program
Not yet examined The municipality does not operate a persistent automated license plate reader program that routinely records ordinary traffic and builds a searchable history of people’s movements.
Unexamined, and decisive. A rigorous approval process is entirely compatible with having approved an ALPR system. What is currently approved and operating must be established before this criterion resolves in either direction.
What would resolve it Municipal code, procurement records, department policy, technology inventory, council minutes.
-
02
No vendor workaround
Not yet examined The municipality has not simply replaced one platform with another providing substantially equivalent dragnet capability.
Not yet examined.
What would resolve it Procurement records across all vendors, not only the one that attracted public attention.
-
03
No routine access to another agency’s dragnet
Not yet examined The municipality does not evade the standard by routinely querying regional, private, vendor, or neighbouring ALPR databases as a substitute for operating its own network.
Not yet examined.
What would resolve it Mutual-aid agreements, regional fusion or task-force participation, vendor account access, department policy.
-
04
Targeted investigative exception only under defined lawful authority
Not yet examined Short-term or case-specific use is tied to individualized legal justification, a warrant or court order where required, or a tightly defined exigent circumstance documented by policy.
Not yet examined.
What would resolve it Written department policy, authorization logs, ordinance text.
-
05
No persistent facial recognition or biometric identification of the public
Not yet examined No persistent facial-recognition or biometric identification system aimed at the general public.
Not yet examined.
What would resolve it Municipal code, department policy, technology inventory, procurement records.
-
06
No purchase of sensitive historical location data from data brokers
Not yet examined The municipality does not purchase sensitive historical location data to circumvent warrant or court-order requirements.
Not yet examined.
What would resolve it Procurement records, purchase orders, department policy.
-
07
Democratic control of new surveillance technology
Met New systems capable of identifying, tracking, or profiling the public require advance public notice, an impact and use policy, and approval by the elected legislative body or an equivalently accountable process.
The municipal code subjects surveillance technology — expressly including ALPRs and biometric surveillance — to an approval process, and requires review of preexisting uses rather than grandfathering whatever was already installed. This is the criterion Yellow Springs satisfies most convincingly.
Village of Yellow Springs, Ohio · Village of Yellow Springs, Ohio — checked Aug 14, 2026
-
08
Public surveillance technology inventory
Not yet examined The municipality publishes what surveillance technologies it uses and for what purpose.
Not yet examined.
What would resolve it Published inventory, currency of the most recent version.
-
09
Retention and deletion limits
Not yet examined Personally identifying surveillance data is minimized and deleted on defined schedules unless legitimately tied to a specific investigation or legal obligation.
Not yet examined.
What would resolve it Written retention schedule, department policy, contract terms.
-
10
Sharing controls
Not yet examined Sensitive data is not casually pooled, sold, or made broadly searchable by outside agencies; sharing rules and legal standards are public.
Not yet examined.
What would resolve it Sharing configuration, data-sharing agreements, published policy.
-
11
Annual transparency reporting
Met The municipality publishes meaningful annual reports covering use, sharing, complaints, audits, policy violations, costs, and material changes.
The code requires annual reporting for approved surveillance systems. Whether reports have in fact been published on schedule is a separate question, listed as open below.
Village of Yellow Springs, Ohio — checked Aug 14, 2026
-
12
Function-over-brand protection
Met Policies apply to capabilities rather than vendor names, so future technology cannot bypass the spirit of the standard by changing product labels.
The code regulates surveillance technology by capability and category rather than by vendor or product name, and makes conflicting contracts prohibited.
Village of Yellow Springs, Ohio · Village of Yellow Springs, Ohio — checked Aug 14, 2026