Consumer Rights Wiki - User contributions [en]

Futurehome Smarthub mandatory subscription fee

2026-03-18T16:44:24Z

Louis: added cargo description

{{IncidentCargo
|Company=Futurehome
|StartDate=2025
|EndDate=
|Status=
|ProductLine=
|Product=
|ArticleType=
|Type=
|Description= Company went bankrupt & then started charging $117/year for services previously free, not advertised as a possibility at time of sale
}}
[[File:Futurehome Smarthub.jpg|thumb|Futurehome’s Smarthub (left) and example compatible devices]]

Futurehome was accused of ransoming customer devices by forcing them to pay a subscription fee, or face disabled core functionality.

In 2025, after the company went bankrupt, Futurehome's new owners announced that '''existing customers would now have to pay an annual subscription to continue using their previously purchased smart-home hubs'''. After a bankruptcy and relaunch, Futurehome imposed an annual fee of 1,188 NOK (around $117 USD) for access to its app and cloud services, locking users out unless they subscribed.<ref name=":0">{{Cite web |last= |date=2025-06-18 |title=FAQ Subscription - Futurehome |url=https://support.futurehome.no/hc/en-no/articles/28158944965277-FAQ-Subscription |url-status=live |archive-url=http://web.archive.org/web/20251126163221/https://support.futurehome.no/hc/en-no/articles/28158944965277-FAQ-Subscription |archive-date=26 Nov 2025|access-date=2025-07-14}}</ref><ref name=":13">{{Cite web |title=Krever abonnement av kundene - Elektro24-7 |trans-title=Requires Subscription from Customers |url=https://www.elektro247.no/krever-abonnement-av-kundene.6722352-567787.html |access-date=2025-07-14 |language=no |archive-url=http://web.archive.org/web/20251218235910/https://www.elektro247.no/krever-abonnement-av-kundene.6722352-567787.html |archive-date=18 Dec 2025}}</ref>

'''Customers who declined to pay lost access to the mobile app (even for local use)''', along with all automations and the hub's local API integrations, leaving only basic on-device (physical) control.

==Company info and background==
'''Futurehome''' AS is a Norwegian smart-home technology company founded in 2013, known for the ''Futurehome Smarthub'', a central gateway device that connects and controls IoT devices. The Smarthub and Futurehome's own product line ''(thermostats, smart plugs, relays, sensors, etc<ref>{{Cite web |title=Products - Futurehome |url=https://www.futurehome.io/en_no/products |access-date=2025-07-14 |archive-url=http://web.archive.org/web/20251212152946/https://www.futurehome.io/en_no/products |archive-date=12 Dec 2025}}</ref>)'' allow users to automate lighting, heating, EV charging, and other home functions via a mobile app and cloud platform.

The hub lets users pair Zigbee-, Z-Wave-, and Futurehome-branded devices and control them locally or remotely through a free mobile app and cloud service; it also exposes local APIs for third-party integrations such as Home Assistant.

The '''Futurehome Smarthub'''<ref name=":3">{{Cite web |title=Futurehome |url=https://www.futurehome.io/en_no/ |access-date=2025-07-14 |archive-url=http://web.archive.org/web/20251124155037/https://www.futurehome.io/en_no/ |archive-date=24 Nov 2025}}</ref> was '''originally sold as a one-time purchase.''' '''Prior to 2025, Futurehome operated on a one-time hardware purchase model''', with app and cloud services included at no extra cost.

Futurehome AS was declared bankrupt on 20 May 2025. The platform and its services were acquired in a 50-50 split by Sikom Connect AS and the former Futurehome owners. The business was relaunched under a new entity: '''FHSD Connect AS.'''<ref name=":0" /> A press release by Sikom Connect AS on the same day clearly depicted their expectation of making every futurehome user into a paying customer for FHSD Connect AS by counting the entire user base of Futurehome into their customer base: "''With the purchase of futurehome, Sikom expands their services to private housing with a combined customer base of more than 70 000 customers''"<ref>{{Cite web |last=Schieflow |first=Torfinn |date=2025-05-20 |title=Strategisk viktig samarbeid |url=https://www.sikom.no/2025/05/20/strategisk-viktig-samarbeid/ |url-status=live |access-date=2025-07-25 |website=www.sikom.no |archive-url=http://web.archive.org/web/20251126092218/https://sikom.no/2025/05/20/strategisk-viktig-samarbeid/ |archive-date=26 Nov 2025}}</ref>(Translated from Norwegian)

==June 2025 subscription rollout==
After the bankruptcy & relaunch, ''any'' continued use now requires an annual subscription of 1,188 NOK (≈ $117). Households that decline are locked out of the application, automations, and the local API interface, leaving only manual, on-device control.<ref name=":0" />

Following the relaunch, FHSD Connect announced that a mandatory subscription would be required to continue using the Smarthub platform. The subscription requirement was activated on 26 June 2025, and both existing and new households were given a four-week trial period before charges apply.<ref name=":0" />

Customers who do not activate the subscription within that trial window face the following restrictions:<ref name=":0" />

*'''App access disabled:''' Users can't use the app remotely via cloud or on the local network.
*'''Automations and modes frozen:''' All user-defined automations, preset modes ''(Home/Away/Night, etc.)'', shortcuts, and energy management features stop working.
*'''Local API and MQTT disabled:''' The hub's developer interfaces remain active only for a short grace period after the trial, then are gradually shut off without an active subscription.
*'''Physical control only:''' Basic manual control of devices continues to work: the smart devices revert to ''"dumb"'' mode with no central coordination.
*'''Support limited:''' Access to customer support channels (chat and phone support) is reserved for paying subscribers.

These limitations were delivered via a firmware update to the hub's software, locking previously available features behind the paywall. One Futurehome software engineer, speaking on condition of anonymity, confirmed that the firmware was designed to enforce this lockout mechanism and compel users to subscribe. As of the changeover, the Futurehome system was reportedly installed in over '''38,000 Norwegian households''',<ref>{{Cite web |title=Futurehome Norge |trans-title=The updated figure of 38,000 is listed only on the Norwegian version of the site |url=https://www.futurehome.io/no/ |access-date=2025-07-13 |language=no |archive-url=http://web.archive.org/web/20260115081530/https://www.futurehome.io/no/ |archive-date=15 Jan 2026}}</ref> all of which had to choose between paying the new fees or losing most "smart" functionality.
[[File:Image(1).png|thumb|Indexed search results from the forum about disabling automatic hub and app updates]]

As part of the ownership transition, FHSD Connect also shut down the official Futurehome user forum, stating they were ''"consolidating support channels"'', further limiting access to help resources for users who don't subscribe.<ref>{{Cite web |title=Futurehome Forum |url=https://forum.futurehome.io |url-status=live |archive-url=https://web.archive.org/web/20250715103026/https://forum.futurehome.io/ |archive-date=2025-07-15 |access-date=2025-07-15}}</ref> The forum contained, among other things, discussions from previous years about how to disable automatic updates for the hub and app ([https://forum-old.futurehome.io/t/smarthub-and-app-update/6400 link to delisted forum thread])<gallery>
</gallery><gallery>
File:Futurehome Subscription App Info 1.PNG|Futurehome app home screen prompting the user to activate a subscription.
File:Futurehome Subscription App Info 2.PNG|Subscription-activation screen showing annual-payment terms; one link opens the subscription FAQ, the other opens a [https://us1.zonka.co/1pBYm3?language=en_US feedback form]
File:Futurehome subscription feedback form.jpg|Feedback form presented to users who decline the subscription ([https://us1.zonka.co/1pBYm3?language=en_US link])
</gallery>

==Futurehome's reply==
FHSD CEO Øyvind Fries justified the subscription model as necessary to ''"secure stable operation, fund product development, and provide high-quality support,"'' according to statements given to [https://www.tek.no/nyheter/nyhet/i/alMe04/rasende-kunder-opplever-smarthjem-utpressing Tek.no] and reiterated in the FAQ.<ref name=":0" /><ref name=":13" /><ref name=":1" /> Fries explained that the subscription was introduced to ensure the '''long-term viability''' of the platform after bankruptcy: without new revenue, they could not guarantee stable operation of the cloud servers or continued updates to the product.<ref name=":1">{{Cite web |title=Rasende kunder opplever smarthjem-utpressing |trans-title=Furious customers experience smart home blackmail |url=https://www.tek.no/nyheter/nyhet/i/alMe04/rasende-kunder-opplever-smarthjem-utpressing |access-date=2025-07-13 |website=Tek.no |language=no |archive-url=http://web.archive.org/web/20251208120232/https://www.tek.no/nyheter/nyhet/i/alMe04/rasende-kunder-opplever-smarthjem-utpressing |archive-date=8 Dec 2025}}</ref>

He stated that the annual fee would help fund ongoing development of new features and maintain a high level of support for customers.<ref name=":0" /> The company also emailed users saying the change would ultimately provide ''"better functionality, more security, and higher value in the solution you already have invested in",'' positioning the subscription as an improvement for the user base.<ref name=":13" />

==Consumer response==
The reaction from Futurehome’s user base was negative. Norwegian customers described the move as a betrayal, given that the original sale included full functionality with no indication that a subscription would be introduced later.

On [[Reddit]]'s r/norge, there is an active discussion thread filled with outrage, legal concerns, and comparisons to ransomware tactics.<ref>{{Cite web |title=Futurehome tvinger eksisterende kunder over til et abonnement, hva nå? : r/norge |url=https://www.reddit.com/r/norge/comments/1lek0p7/futurehome_tvinger_eksisterende_kunder_over_til/ |access-date=2025-07-14}}</ref><ref name=":2" />

One user, muffinmeistro, wrote:<blockquote>''I can't understand how what they're trying to do here is legal. I'd like to hear what u/thomasiversen thinks.''

''They're removing functionality locally in a hub (computer) that I've paid for with an update.''<ref name=":2">{{Cite web |date=2025-06-18 |title=Futurehome is forcing existing customers to switch to a subscription, what now? : r/norge |url=https://www.reddit.com/r/norge/comments/1lek0p7/comment/myhs0sm/?tl=en |url-status= |access-date=2025-07-13}}</ref>

''(Translated from Norwegian)''</blockquote>Another user posted expressing concern for the pushing of the subscription, as well as a poor user experience:<blockquote>''I want to spend my money somewhere else than paying over 1000 kroner a year for half-hearted functionality. What options do I have? I currently have lights and thermostats from Futurehome. Can these devices be used with Home Assistant?<ref>{{Cite web |last=MrGeniusL |date=2025-06-18 |title=Futurehome tvinger eksisterende kunder over til et abonnement, hva nå? |url=http://www.reddit.com/r/norge/comments/1lek0p7/futurehome_tvinger_eksisterende_kunder_over_til/ |access-date=2025-07-14 |website=r/norge |language=no}}</ref>''

''(Translated from Norwegian)''</blockquote>

==Questionable legality==
This issue drew attention to consumer protection laws. Norway is not an EU member but is part of the European Economic Area (EEA), which means EU consumer-protection directives (such as those barring unfair commercial practices) are incorporated into Norwegian law. Observers noted that retroactively charging a subscription for a product that was sold under a no-fee premise might violate these rules, though as of mid-2025 it remained unclear if any official action would be taken. Some users discussed the possibility of legal recourse or a class-action lawsuit in response to Futurehome's move.

==$5000 bounty to crack firmware==
On the 16th of July, 2025, consumer rights advocate Louis Rossman announced that he would pay a $5000 bounty to anyone capable of restoring the previous functions of Futurehome's products. In addition, Rossman would hire a lawyer to defend the individual that provided the solution, if he or she were to be taken to court.

In response to this, FHSD Connect AS CEO, Øyvind Fries, says that:
<blockquote>
It is regrettable that we now have to spend time and resources on strengthening the security around a service in demand, rather than further developing functionality for the benefit of our customers (Translated from Norwegian).
</blockquote>
Fries adds that their focus is on reliable and user-friendly services, with former customers of Futurehome being of primary interest. Regarding the bounty, Fries expressed:
<blockquote>
Although some perceive this as entertainment, it can have serious consequences for several thousand subscribers who use the service daily.

Unauthorized access to software is considered illegal hacking, and is punished according to Norwegian law (Translated from Norwegian).
</blockquote>
When asked by the journalists at Tek.no about what legal actions that FHDS Connect AS would take if someone were to obtain the bounty, Fries said:
<blockquote>
Any offenses are followed up by the police, who have experience with this type of problem (Translated from Norwegian).
</blockquote>

==Similarity to Wink==
In 2020, [[Wink]] suddenly introduced a $4.99 monthly fee for continued use of its previously free smart-home service, giving customers only a one-week ultimatum and warning that devices would stop working if they didn't pay.<ref>{{Cite web |title=Wink smart hub users get one week's notice to pay up or lose access - Ars Technica |url=https://arstechnica.com/information-technology/2020/05/wink-smart-hub-users-get-one-weeks-notice-to-pay-up-or-lose-access/ |access-date=2025-07-13 |website=Wink smart hub users get one week’s notice to pay up or lose access - Ars Technica |archive-url=http://web.archive.org/web/20251126051826/https://arstechnica.com/information-technology/2020/05/wink-smart-hub-users-get-one-weeks-notice-to-pay-up-or-lose-access/ |archive-date=26 Nov 2025}}</ref> That move led to a class-action lawsuit alleging deceptive business practices, breach of warranty, and even ''"trespass to chattels"'' on the grounds that Wink's remote deactivation scheme unlawfully interfered with consumers' owned property.<ref>{{Cite web |title=Greenwald Davidson Radbil PLLC {{!}} Greenwald Davidson Radbil PLLC files amended class action complaint against Wink Labs, Inc. over new monthly charge |url=https://www.gdrlawfirm.com/Wink-class-action |url-status=dead |archive-url=https://web.archive.org/web/20230313203733/https://www.gdrlawfirm.com/Wink-class-action |archive-date=2023-03-13 |access-date=2025-07-13 |website=Greenwald Davidson Radbil PLLC {{!}} Greenwald Davidson Radbil PLLC files amended class action complaint against Wink Labs, Inc. over new monthly charge}}</ref>

Futurehome's forced subscription draws parallels to the Wink case while demonstrating an industry pattern of undermining the '''[[right to own]]''' what one has bought. Critics argue that such practices erode consumers' sense of ownership, turning purchased devices into services that can be revoked or pay-walled at any time.

==Impact on third-party integrations==
Beyond the immediate loss of app functionality, the subscription requirement '''disables all third-party integrations'''. Futurehome previously allowed integration with:

*[[Home Assistant]] via a custom MQTT bridge<ref>{{Cite web |title=runelangseid/hassio-futurehome2mqtt |url=https://github.com/runelangseid/hassio-futurehome2mqtt |access-date=2025-07-14 |archive-url=http://web.archive.org/web/20251128005923/https://github.com/runelangseid/hassio-futurehome2mqtt |archive-date=28 Nov 2025}}</ref>
*[[Homebridge]] via NPM plugin for Apple HomeKit<ref>{{Cite web |last= |first= |title=homebridge-futurehome - npm |url=https://www.npmjs.com/package/homebridge-futurehome |access-date=2025-07-14 |archive-url=http://web.archive.org/web/20250907045629/https://www.npmjs.com/package/homebridge-futurehome |archive-date=7 Sep 2025}}</ref> let Futurehome devices be controlled via Siri and the Apple Home app

These relied on the hub's local API and MQTT server. Once disabled, no data is sent or received, breaking compatibility with these platforms. Once the subscription enforcement kicked in, the hub stopped publishing or accepting local MQTT messages and the API shut down, breaking compatibility.

While some users may migrate to other smart home ecosystems using open protocols like Zigbee2MQTT<ref>{{Cite web |title=Zigbee2MQTT Supported Devices – Futurehome |url=https://www.zigbee2mqtt.io/supported-devices/#v=Futurehome |access-date=2025-07-14 |archive-url=http://web.archive.org/web/20260127094607/https://www.zigbee2mqtt.io/supported-devices/ |archive-date=27 Jan 2026}}</ref>, some Futurehome-branded devices (e.g., the HAN-Sensor and Futurehome Charge EV charger) may lose core features or become inaccessible due to lack of open community drivers.

==Inadequate subscription notice==
Futurehome does not prominently disclose the new subscription requirement in product listings or on its homepage, even as the change was rolled out. The company's official website and online store continued to list the Smarthub and related products with their one-time purchase price only, with no prominent notice about the required annual fee.

The only mention of a subscription on the homepage was buried in fine print upon scrolling, and product pages ''(for devices like the HAN-Sensor or the Futurehome Mode Switch)'' contain no warning that the system requires ongoing payments.

Similarly, the Futurehome app listings on the Apple App Store and Google Play made no reference to a subscription requirement, potentially misleading new customers into thinking the hub's functionality was included in the purchase price.

<gallery mode="slideshow">
File:Subscription.jpg|The only mention of a subscription on [https://www.futurehome.io/en_no/ site homepage] is in fine print on the second scroll page.<ref name=":3" />
File:Homepage futurehome.jpg|Landing view of homepage with no subscription mention.
</gallery>

Further, product and app store pages list only hardware prices, creating the false impression of a one-time purchase.

<gallery>
File:Applefree.jpg|Apple App Store listing for Futurehome, no mention of required subscription.<ref>{{Cite web |title=Futurehome on the App Store |url=https://apps.apple.com/tr/app/futurehome/id1470952171 |access-date=2025-07-13 |archive-url=http://web.archive.org/web/20251128225016/https://apps.apple.com/tr/app/futurehome/id1470952171 |archive-date=28 Nov 2025}}</ref>
File:Androidfree.jpg|Google Play listing for Futurehome app, no mention of subscription.<ref>{{Cite web |title=Futurehome - Apps on Google Play |url=https://play.google.com/store/apps/details?id=no.futurehome.futurehome_app&hl=en_US&gl=US&pli=1 |access-date=2025-07-13 |archive-url=http://web.archive.org/web/20251125155349/https://play.google.com/store/apps/details?pli=1&id=no.futurehome.futurehome_app&hl=en_US&gl=US |archive-date=25 Nov 2025}}</ref>
File:Modusbryter nosub.jpg|Modusbryter page omits any disclosure of subscription lock-in.<ref>{{Cite web |title=Modusbryter (Black) - Futurehome |url=https://www.futurehome.io/en_no/shop/modeswitch-black#tab-description |access-date=2025-07-13 |archive-url=http://web.archive.org/web/20251124155037/https://www.futurehome.io/en_no/ |archive-date=24 Nov 2025}}</ref>
</gallery>

==Network hacking possibility==


First, find out the IP address of the FH device on the network. Since most IPv4 networks use RFC-1918 addresses on the inside of the network, let's say our example IP is 10.20.30.40/24. Once we have this, let's capture all the network traffic being sent to and from the device. If at all possible, create a SPAN/mirror port on the connected switch to include local (multicast and broadcast) traffic. If we can't, let's start at the firewall. Depending on the vendor (Check Point, Fortinet, Cisco, Palo Alto, whatever) the syntax will be unique but we want the capture to look like this:

''tcpdump -nn -vvv -e -s 0 -X -c 100000 -i eth0 host 10.20.30.40''

Assuming that `eth0` is our internal interface, this will capture all non-local traffic to and from the device. Now, if the traffic is not encrypted, we can read the payloads of what's being sent to/from the device which will also include the DNS requests so long as the DNS server is hosted externally. If it's internal, we want to run and gather logs on the DNS server to see what A/AAAA records are being requested by the FH device.

If the traffic is encrypted, this changes things as the firewall won't be able to decrypt the traffic. To bypass this issue, we'd use a tool such as Burp Suite (https://portswigger.net/burp) on our computer to intercept the traffic. This requires our computer to act as a routing device (likely with NAT to avoid ICMP Redirects) which is outside the scope of this blurb. So long as the FH device and service don't use Certificate Pinning and/or HSTS, the Burp device will be able to decrypt all the traffic.

At this point, we should now know:

#The DNS A/AAAA requests and responses that the FH device queries
#The Layer-3 protocols and Layer-4 ports in use by the device
#The commands sent back and forth between the FH device and the FH server
#The responses sent back and forth from item three, above

Armed with this, we will need to create a DNS server that has a local zone (db.rpz.local) for each DNS request by the FH device. These entries should point to (what will eventually become) our custom FH server. For this example, let's use 1.2.3.4 as the server IP. Now, any time the FH device wants to connect to the actual FH server and it's using our DNS server, it will connect to 1.2.3.4 (our custom server) instead.

We now have traffic being routed to our custom server at 1.2.3.4 at which point we need to create software to receive and properly answer the commands being sent to/from the FH device. While I don't know what those would look like, if they're simple commands (ex: temp_set_21 -> command_ok) the server-side could be something as simple as a BASH script wrapped up with NetCat, a python socket server or even a more robust C++ server.

Firmware isn't hacked: We've just created a new tool that the FH device ''happens'' to work with. :)

==Futurehome Debian "Wheezy" software repositories==
The following are two of futurehome`s software repositories:

*Cube-1v1-eu hub: http://archive.futurehome.no/prod-1v1
*Cube-2v0-eu hub: http://archive.futurehome.no/prod-2v0/

==See also==
[[Retroactively amended purchase]]

==References==
{{Reflist}}

[[Category:Futurehome]]
[[Category:Smart home device obsolescence]]
[[Category:Planned obsolescence through software updates]]
[[Category:Forced subscription activation]]
[[Category:Consumer rights]]

VitalSource

2026-03-12T18:27:19Z

Louis: /* "Lifetime" access controversy (December 2024) */

{{CompanyCargo
|Industry=Digital textbooks,Educational technology
|Type=Private
|Website=https://www.vitalsource.com/
|Description=Digital textbook and course material provider for higher education
}}'''VitalSource''' is a digital textbook & course material provider serving students & educational institutions, primarily in the United States higher education market. The company offers digital access to textbooks & other educational content through its online platform & apps, with various license durations including short-term rentals & what it markets as "lifetime" access.

==Consumer-impact summary==
==Incidents==
==="Lifetime" access controversy (December 2024)===
{{Main|VitalSource "Lifetime" false advertising}}
VitalSource markets certain digital textbook licenses as offering "lifetime" access while defining this term as a limited five-year period. The practice came to wider attention in December 2024 when VitalSource published a California disclosure page in response to AB 2426, a state law requiring companies to clearly disclose when digital goods are licensed rather than owned. Despite this disclosure, VitalSource continues to use the term "lifetime" in its storefront marketing without prominently displaying the five-year limitation alongside shorter-duration options that do show explicit expiration dates

[[Category:Companies]]
[[Category:{{PAGENAME}}]]

VitalSource

2026-03-12T18:26:28Z

Louis:

{{CompanyCargo
|Industry=Digital textbooks,Educational technology
|Type=Private
|Website=https://www.vitalsource.com/
|Description=Digital textbook and course material provider for higher education
}}'''VitalSource''' is a digital textbook & course material provider serving students & educational institutions, primarily in the United States higher education market. The company offers digital access to textbooks & other educational content through its online platform & apps, with various license durations including short-term rentals & what it markets as "lifetime" access.

==Consumer-impact summary==
==Incidents==
==="Lifetime" access controversy (December 2024)===
{{Main|VitalSource Lifetime false advertising}}
VitalSource markets certain digital textbook licenses as offering "lifetime" access while defining this term as a limited five-year period. The practice came to wider attention in December 2024 when VitalSource published a California disclosure page in response to AB 2426, a state law requiring companies to clearly disclose when digital goods are licensed rather than owned. Despite this disclosure, VitalSource continues to use the term "lifetime" in its storefront marketing without prominently displaying the five-year limitation alongside shorter-duration options that do show explicit expiration dates.

==Products==
{{Ph-C-P}}

==See also==
{{Ph-C-SA}}
*[[eCampus]]

==References==
{{Reflist}}

[[Category:Companies]]
[[Category:{{PAGENAME}}]]

VitalSource

2026-03-12T18:24:15Z

Louis: Created page with "{{CompanyCargo |Industry=digital textbooks |Type=Private |Website=https://www.vitalsource.com/ |Description=Digital textbook provider }} {{Ph-C-Int}} ==Consumer-impact summary== {{Ph-C-CIS}} ==Incidents== {{Ph-C-Inc}} This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the {{PAGENAME}} category. ===Example incident one (''date'')=== {{Main|link to the..."

{{CompanyCargo
|Industry=digital textbooks
|Type=Private
|Website=https://www.vitalsource.com/
|Description=Digital textbook provider
}}
{{Ph-C-Int}}

==Consumer-impact summary==
{{Ph-C-CIS}}

==Incidents==
{{Ph-C-Inc}}

This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Futurehome

2026-03-12T18:22:56Z

Louis:

{{CompanyCargo
|Founded=2013
|Industry=Smart home,Internet of Things
|CompanyAlias=Futurehome AS,FHSD Connect AS
|Type=Private
|Website=https://www.futurehome.io/,https://www.futurehome.no/
|Description=Norwegian smart-home company known for the Futurehome Smarthub
}}'''Futurehome''' is a Norwegian smart-home technology company founded in 2013, known for the Futurehome Smarthub, a central gateway device that connects and controls IoT devices using Zigbee, Z-Wave, and EnOcean protocols. The company's product line includes thermostats, smart plugs, relays, sensors, and an electric vehicle charger.

Futurehome AS declared bankruptcy on 20 May 2025. The platform was acquired from the bankruptcy estate in a 50–50 split by Sikom Connect AS and the former Futurehome owners, and relaunched under a new entity called '''FHSD Connect AS'''.

==Incidents==
===Mandatory subscription fee (June 2025)===
{{Main|Futurehome Smarthub mandatory subscription fee}}
Following its bankruptcy & relaunch, FHSD Connect AS imposed a mandatory annual subscription of 1,188 NOK which is about $117 US dollars on all existing Smarthub owners. Customers who declined to pay lost access to the mobile app, automations, energy management features, & the hub's local API, leaving only basic manual control of connected devices.

==Products==
==See also==
*[[Wink]]
*[[Retroactively amended purchase]]

==References==
{{Reflist}}

[[Category:Companies]]
[[Category:{{PAGENAME}}]]

Futurehome

2026-03-12T18:20:29Z

Louis: Created page with "{{CompanyCargo |Industry=Smart Home |Type=Private |Website=https://futurehome.io,https;//futurehome.no |Description=Sells smart home products }} {{Ph-C-Int}} ==Consumer-impact summary== {{Ph-C-CIS}} ==Incidents== {{Ph-C-Inc}} This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the {{PAGENAME}} category. ===Example incident one (''date'')=== {{Main|lin..."

{{CompanyCargo
|Industry=Smart Home
|Type=Private
|Website=https://futurehome.io,https;//futurehome.no
|Description=Sells smart home products
}}
{{Ph-C-Int}}

==Consumer-impact summary==
{{Ph-C-CIS}}

==Incidents==
{{Ph-C-Inc}}

This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

VitalSource "Lifetime" false advertising

2026-03-12T18:11:31Z

Louis: added website

{{IncidentCargo
|Company=VitalSource
|StartDate=2024-12-18
|EndDate=
|Status=Active
|ProductLine=
|Product=
|ArticleType=Service
|Type=Broken Promise, Deception, Ownership
|Description=Five-year textbook licenses are misleadingly advertised as "lifetime" licenses.
|Website=https://vitalsource.com/
}}
[[File:Vitalsource calculus textbook.png|alt=Screenshot of vitalsource' product page for a calculus book|thumb|Screenshot of vitalsource' product page for a calculus book as of 2025-02-18 <ref>https://www.vitalsource.com/products/calculus-james-stewart-daniel-k-v9798214339221 ([http://web.archive.org/web/20250708171459/https://www.vitalsource.com/products/calculus-james-stewart-daniel-k-v9798214339221 Archived])</ref> - Notice that there is no place that a user can go to read that the license is not a lifetime license. The only item that links to a disclosure page is a "details" link next to "This is a digital license"]]
[[File:Vitalsource calculus textbook CA disclosure.png|alt=Screenshot of vitalsource' "details" page [1] that is clickable from the bottom of the product page for a calculus book as of 2025-02-18|thumb|Screenshot of vitalsource' "details" page <ref>https://web.archive.org/web/20250126183825/https://support.vitalsource.com/hc/en-us/articles/28012656781847-CA-Disclosure-Support-Page ([http://web.archive.org/web/20260128182259/https://support.vitalsource.com/hc/en-us/articles/28012656781847-CA-Disclosure-Support-Page Archived])</ref> that is clickable from the bottom of the product page for a calculus book as of 2025-02-18 - In the middle of the page it mentions two important points.]]
'''VitalSource "Lifetime" Access Controversy''' is in reference to a practice by VitalSource, a large digital textbook & course material provider for college educational markets in the United States, whereby they market some digital products as having ''"lifetime"'' access; while defining this term as a '''limited 5-year period'''.<ref>https://support.vitalsource.com/hc/en-us/articles/28012656781847-CA-Disclosure-Support-Page ([http://web.archive.org/web/20260128182259/https://support.vitalsource.com/hc/en-us/articles/28012656781847-CA-Disclosure-Support-Page Archived])</ref>

In addition to VitalSource, eCampus, another company that provides similar services, defines "lifetime" similarly.<ref>{{Cite web |title=Digital Goods Disclosure and Licensing Policy |url=https://www.ecampus.com/digital-goods-disclosure-policy |url-status=live |access-date=2025-08-26 |website=eCampus.com |archive-url=http://web.archive.org/web/20251210083327/https://www.ecampus.com/digital-goods-disclosure-policy |archive-date=10 Dec 2025}}</ref>

==Background==

VitalSource operates as a significant provider of digital educational materials, serving students and educational institutions. The company offers various access durations for their digital products, including what they term "lifetime" access.

==Definition and Implementation==

According to VitalSource's documentation, they define "lifetime" access as follows:<ref name="vitalsource">VitalSource Technologies LLC. (2024, December 18). "CA Disclosure Support Page". VitalSource Support. Retrieved January 31, 2025.</ref>
*Five years of online platform access
*Ability to download content to supported devices during this period
*Support limited to device compatibility at time of download

This definition appears in their California Digital Goods Disclosure documentation, published December 18, 2024, in response to AB 2426 compliance requirements with the new law.<ref name="ab2426">California State Legislature. (2024). AB 2426 Consumer protection: false advertising: digital goods. Retrieved January 31, 2025.</ref>

==Overarching problem==

This practice is a perfect demonstrator of the key issue in modern digital goods ownership:

===Redefining Common Terms===
*The term "lifetime" is commonly understood to mean the entire life of either the purchaser or the product
*VitalSource's use of the term to mean a fixed 5-year period is a departure from traditional consumer understanding of the word [https://www.merriam-webster.com/dictionary/lifetime lifetime]

===License vs. Ownership===
*Products marketed with "lifetime" access remain under licensing restrictions
*Access can be revoked or limited based on platform support & device compatibility
*Downloads are contingent on maintaining "supported device" status, a term that they do not clearly define, only indicating it means "the two most recent versions of an operating system" but not identifying on which devices, apps or operating systems downloads of a title are supported.

==Regulatory Response==

California's AB 2426<ref>https://leginfo.legislature.ca.gov/faces/billStatusClient.xhtml?bill_id=202320240AB2426 ([http://web.archive.org/web/20251129062603/https://leginfo.legislature.ca.gov/faces/billStatusClient.xhtml?bill_id=202320240AB2426 Archived])</ref>, effective January 1, 2025, addresses this type of false advertising by requiring companies to:<ref name="ab2426" />
*Explicitly disclose when digital goods are licensed rather than owned
*Clearly and conspicuously<ref>Bill definition: (1) “Clear and conspicuous” means in a manner that clearly calls attention to the language, such as in larger type than the surrounding text, or in contrasting type, font, or color to the surrounding text of the same size, or set off from the surrounding text of the same size by symbols or other marks.</ref> communicate access limitations & conditions
*Obtain affirmative acknowledgment from consumers regarding license terms

==Current Status==

As of January 2025, VitalSource has updated their disclosure documentation '''but continues to use the term "lifetime" in their marketing, with the 5-year definition disclosed in their terms of service and support documentation'''.<ref name="vitalsource" /> Even though they claim to have complied with the regulation, consumers still must dig further to learn that what is marketed as "lifetime" is anything but. When "180 days" and "1 year" options are chosen, the site clearly and conspicuously displays an ''Expires on: <date, e.g. Jul 5, 2026>'' message on the main webshop page, pushing shoppers to the higher priced "Lifetime" option. When "Lifetime" is selected, that is not replaced with another date (e.g. 5 seconds or 5 years out); instead it is hidden, which is deceptive, the opposite of clear and conspicuous. The "eTextbook License" text is not larger or contrasting, and is marked with only a single ℹ︎ symbol.

==References==
<references />

[[Category:Incidents]]
[[Category:VitalSource]]

[[Category:Digital ownership]]
[[Category:License terms]]
[[Category:Educational materials]]

General Motors

2026-03-12T16:53:08Z

Louis: added websites for brands general motors sells under

{{StubNotice}}
{{CompanyCargo
|Description=American auto manufacturer
|Founded=1908
|Industry=Automotive
|Logo=General_Motors.svg
|ParentCompany=
|Type=Public
|Website=https://gm.com/,https://cadillac.com,https://www.chevrolet.com/
}}
'''[[Wikipedia:General Motors|General Motors Company]]''' (GM) is an American multinational, automotive-manufacturing company founded in 1908. It owns many car brands, such as Chevrolet, Buick, GMC, and Cadillac, alongside other companies like OnStar and other GM subsidiaries for parts, financial administration, and insurance.<ref>[https://web.archive.org/web/20250126173621/https://www.gm.com/gm-brands "Our Brands"] - archive.org - archived 2025-01-26</ref>

==Controversies==

===Support for Apple CarPlay and Android Auto===
In 2023, GM decided to abandon Apple CarPlay and Android Auto in its future electric vehicles, initially explained to the public as a "safety concern". When questioned later, GM Infotainment Business Strategy and Planning Manager, Ryan Buffa, said that: “The primary reason is that we’re looking to create a comfort level around the [electric-vehicle] charging experience. With Android Auto or Apple CarPlay environments, the vehicle energy model or road segment data is sending energy usage and everything else associated with it to the phone, and it’s pretty difficult to off-board it from the phone.”<ref>[https://gmauthority.com/blog/2023/12/heres-the-real-reason-that-gm-is-dropping-apple-carplay-android-auto/ "The Real Reason GM Is Dropping Apple CarPlay, Android Auto: Exclusive"] - gmauthority.com - accessed 2025-01-29 ([http://web.archive.org/web/20251219131253/https://gmauthority.com/blog/2023/12/heres-the-real-reason-that-gm-is-dropping-apple-carplay-android-auto/ Archived])</ref>

===Sale of customer data to third parties===
{{Main|General Motors data collection and sharing controversy}}
GM has been accused of collecting and selling consumers' driving data without their knowledge or consent, resulting in increased insurance rates for consumers.<ref>{{Cite news |last=Hill |first=Kashmir |date=2024-03-11 |title=Automakers Are Sharing Consumers’ Driving Behavior With Insurance Companies |url=https://www.nytimes.com/2024/03/11/technology/carmakers-driver-tracking-insurance.html |url-status=live |archive-url=https://web.archive.org/web/20250409192617/https://www.nytimes.com/2024/03/11/technology/carmakers-driver-tracking-insurance.html |archive-date=2025-04-09 |access-date=2025-04-27 |work=The New York Times}}</ref>

In July 2024, Senators Ron Wyden and Ed Markey urged the Federal Trade Commission to investigate GM and other automakers, alleging that GM sold consumers' data to third party [[Verisk|Verisk Analytics]], who then resold the data to insurance companies.<ref>{{Cite web |date=2024-07-26 |title=Wyden-Markey Auto Privacy Letter to FTC |url=https://www.wyden.senate.gov/imo/media/doc/wyden-markey_auto_priavacy_letter_to_ftc.pdf |url-status=live |archive-url=https://web.archive.org/web/20250421103118/https://www.wyden.senate.gov/imo/media/doc/wyden-markey_auto_privacy_letter_to_ftc.pdf |archive-date=2025-04-21 |access-date=2025-04-27 |website=U.S. Senator Ron Wyden of Oregon}}</ref> On January 16, 2025, the FTC banned GM from sharing driving data with consumer reporting agencies for five years, as part of a settlement to these claims.<ref>{{Cite news |last=Veiga |first=Alex |date=2025-01-16 |title=FTC bans GM from sharing driving data to settle claims that the automaker sold data without consent |url=https://apnews.com/article/ftc-gm-driving-data-insurers-a555abb56a0d5f31afa9b73c3eb48287 |url-status=live |archive-url=https://web.archive.org/web/20250211181839/https://apnews.com/article/ftc-gm-driving-data-insurers-a555abb56a0d5f31afa9b73c3eb48287 |archive-date=2025-02-11 |access-date=2025-04-27 |work=The Associated Press}}</ref>

==Safety Recalls and Mechanical Neglect==
GM has repeatedly opted for cost-cutting measures over durable fixes:

*A 2025 recall addressed rear wheel lock-up caused by faulty valve bodies but only implemented a software patch instead of replacing the defective parts. Dealers were barred from ordering replacements, leaving customers stranded without loaners while still making payments

==Historical Ethical Violations==
GM’s misconduct spans decades:

• Ignition switch cover-up (2004–2014): Executives concealed defects, leading to criminal charges and a Supreme Court ruling against shielding liability through bankruptcy.”<ref>[https://www.linkedin.com/pulse/gms-ethical-crisis-excerpt-christopher-vazquez "GM's Ethical Crisis: An Excerpt] -linkedin.com - accessed 2025-03-07 ([http://web.archive.org/web/20260115051030/https://www.linkedin.com/pulse/gms-ethical-crisis-excerpt-christopher-vazquez Archived])</ref>

• Misleading consumers: Drivers were enrolled in data-collection programs through confusing opt-in processes, with many unaware their behavior was being monitored and sold. "<ref>[https://web.archive.org/web/20250305021213/https://www.nytimes.com/2025/01/16/technology/general-motors-driving-data-settlement.html " General Motors Driving Data Settlement] - archive.org - archived 2025-03-05</ref> "<ref>[https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-takes-action-against-general-motors-sharing-drivers-precise-location-driving-behavior-data " FTC Takes Action Against General Motors for Sharing Drivers’ Precise Location and Driving Behavior Data Without Consent] - ftc.gov - accessed 2025-03-07 ([http://web.archive.org/web/20260126215736/https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-takes-action-against-general-motors-sharing-drivers-precise-location-driving-behavior-data Archived])</ref>

==References==
<references />
[[Category:General Motors]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-03-10T00:23:39Z

Louis: added employees of flock being prior city councilmembers & sidestepped laws on revolving door

{{Alert|message = This is a special page dedicated to a specific issue. It will be deleted once moved elsewhere, and is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city — but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.|thumb|Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[wikipedia:Fourth_Amendment_to_the_United_States_Constitution|Fourth Amendment]] jurisprudence and misunderstands the legal standard of "reasonable expectation of privacy" established by the [[wikipedia:Supreme_Court_of_the_United_States|Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches and seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy." This considers the nature, scope, and how intrusive the government monitoring is.

In [[wikipedia:Carpenter_v._United_States|''Carpenter v. United States'' ''(2018)'']], the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[wikipedia:John_Roberts|John Roberts]] wrote that the government's access to 127 days of cell-site location data — tracking movements on public roads — achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |archive-url=https://web.archive.org/web/20180623061246/https://www.law.cornell.edu/supremecourt/text/16-402 |archive-date=2018-06-23 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> The Court said,<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation and Comprehensive Surveillance===

Courts separate isolated instances of police observation and large-scale automated tracking systems. In ''[[wikipedia:United_States_v._Jones_(2012)|United States v. Jones (2012)]]'', Justice [[wikipedia:Sonia_Sotomayor|Sonia Sotomayor's]] influential concurrence explained that [[GPS tracking]]:<blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, and sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-url=https://web.archive.org/web/20120126022816/https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-date=2012-01-26 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref></blockquote>She noted that automated surveillance:<blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources and community hostility."<ref name=":1" />''</blockquote>The [[wikipedia:Massachusetts_Supreme_Judicial_Court|Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy (2020)'', holding:<blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |date=2020-04-16 |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-url=https://web.archive.org/web/20220303203404/https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-date=2022-03-03 |access-date=2025-12-16 |website=Justia}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The [[wikipedia:Mosaic_theory_of_the_Fourth_Amendment|"mosaic theory" of Fourth Amendment protection]] holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[wikipedia:Samuel_Alito|Samuel Alito]] noted in his ''Jones'' concurrence that:<blockquote>''"society's expectation has been that law enforcement agents and others would not; and indeed, in the main, simply could not; secretly monitor and catalogue every single movement of an individual's car for a very long period."<ref name=":1" />''</blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In [[wikipedia:United_States_v._Knotts|''United States v. Knotts (1983)'']], while holding that limited beeper (a radio-emitting surveillance device) tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "[[wikipedia:Dragnet_(policing)|dragnet-type law enforcement practices]]."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |url-status=live |archive-url=https://web.archive.org/web/20120601022257/https://www.law.cornell.edu/supremecourt/text/460/276 |archive-date=2012-06-01 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk (E.D. Va.)'', privacy advocates Lee Schmidt and Crystal Arrington challenged Norfolk's 176-camera Flock Safety ALPR network as unconstitutional. Chief Judge [[wikipedia:Mark_Steven_Davis|Mark S. Davis]] initially denied a motion to dismiss the case in February 2025, finding that plaintiffs had stated a plausible Fourth Amendment claim. During discovery, it emerged that Schmidt's vehicle had been photographed 475 times and Arrington's 325 times over a four-month period in 2025.<ref name="nbc-norfolk">{{cite news |last=Collier |first=Kevin |date=2025-09-18 |title=Police cameras tracked one driver 526 times in four months, lawsuit says |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |url-status=live |archive-url=https://web.archive.org/web/20250918093450/https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |archive-date=2025-09-18 |access-date=2025-12-16 |work=NBC News}}</ref>

However, on January 27, 2026, Judge Davis granted summary judgment in favor of the City, ruling that Norfolk's ALPR system did not violate the Fourth Amendment. In a 51-page opinion, Davis concluded that the plaintiffs could not demonstrate that the system was capable of tracking the entirety of a person's movements. The court found that although the cameras captured snapshots of daily life, they did not continuously track individuals or capture sufficient data to reconstruct whole routines, noting "sizable gaps" between photographs.<ref name="whro-norfolk">{{cite news |last=Cox |first=Toby |date=2026-02-11 |title=A federal judge ruled Norfolk's Flock surveillance cameras don't invade people's privacy – yet |url=https://www.whro.org/business-growth/2026-02-11/a-federal-judge-ruled-norfolks-flock-surveillance-cameras-dont-invade-peoples-privacy-yet |access-date=2026-03-02 |work=WHRO}}</ref><ref name="courthouse-norfolk">{{cite news |date=2026-01-28 |title=Judge holds Norfolk's license plate reader use constitutional |url=https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/ |access-date=2026-03-02 |work=Courthouse News Service}}</ref>

Notably, Judge Davis cautioned that the constitutional analysis could change as ALPR technology expands. He wrote that ''"ALPR surveillance could become too intrusive and run afoul of [constitutional privacy standards] at some point,"'' but concluded that ''"at least in Norfolk, Virginia, the answer is: not today."''<ref name="whro-norfolk" /> The plaintiffs, represented by the Institute for Justice, announced their intention to appeal, with Schmidt stating he remained committed to fighting against what he described as "dragnet warrantless surveillance."<ref name="whro-norfolk" /><ref name="courthouse-norfolk" />

Flock Safety's chief legal officer responded that the decision aligned with rulings by over 30 state and federal courts concluding that fixed-location ALPRs do not constitute a search under the Fourth Amendment.<ref name="courthouse-norfolk" />

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 and 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |last=Maass |first=Dave |last2=Lipton |first2=Beryl |date=2021-04-22 |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-url=https://web.archive.org/web/20181115183012/https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-date=2018-11-15 |access-date=2025-12-16 |website=Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale and the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale and comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[wikipedia:Stalking|stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, and sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge and Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016 |url=https://scholarlycommons.law.northwestern.edu/nulr/vol111/iss1/4/}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly;<ref>{{cite news |last=Kenney |first=Andrew |date=2024-09-19 |title=2 million license plates scanned monthly by Denver's new police cameras |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-url=https://web.archive.org/web/20240919214639/https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-date=2024-09-19 |access-date=2025-12-16 |work=Denverite}}</ref> Norfolk's 176 cameras provide citywide coverage;<ref name="nbc-norfolk" /> and Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |last=Thompson |first=Ben |date=2025-05-20 |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |url-status=live |archive-url=https://web.archive.org/web/20250607131518/https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |archive-date=2025-06-07 |access-date=2025-12-16 |work=Community Impact}}</ref>

==STATE LEGISLATIVE RESPONSES: VIRGINIA AS A CASE STUDY==

Virginia became one of the first states to enact comprehensive statewide ALPR regulation when legislation establishing statewide standards for law enforcement use of ALPR took effect on July 1, 2025. Prior to this date, Virginia had no statewide statutory or regulatory framework governing law enforcement use of ALPR, meaning agencies could operate the technology without any statewide limitations on use, data retention, or data sharing.<ref name="vscc-2026">{{cite web |title=Law Enforcement Use of Automatic License Plate Recognition (ALPR) Update, January 2026 |url=https://vscc.virginia.gov/2026/VSCC%20ALPR%20Report%20January%202026%20FINAL%20REVISED%20Jan%2021%202026.pdf |access-date=2026-03-02 |publisher=Virginia State Crime Commission |date=2026-01}}</ref>

===Overview of Virginia's 2025 ALPR Law===

Under the new statute (Virginia House Bill 2724, codified at Va. Code Ann. § 2.2-5517), law enforcement agencies in Virginia may only use ALPR for criminal investigations, active investigations into missing or endangered persons or human trafficking, and notifications related to missing or endangered persons, outstanding warrants, human trafficking, stolen vehicles, or stolen license plates.<ref name="vscc-2026" />

The law requires ALPR data to be purged after 21 days unless needed for an ongoing investigation, prosecution, or civil action. It also restricts data sharing to other Virginia law enforcement agencies, Commonwealth's Attorneys, criminal defendants or their counsel, ALPR vendors, or pursuant to a court order. The statute does not permit data sharing with out-of-state or federal law enforcement agencies.<ref name="vscc-2026" />

===Compliance Findings from the Virginia State Crime Commission===

In January 2026, the Virginia State Crime Commission published the findings of a statewide survey of all 361 Virginia law enforcement agencies on their use of ALPR. The survey, conducted in November 2025 to capture practices after the new legislation took effect, received responses from 251 agencies (70%). Of responding agencies, 63% (159 of 251) reported using ALPR. A large majority — 86% (137 of 159) — reported [[Flock Safety]] as their ALPR vendor.<ref name="vscc-2026" />

The Crime Commission found that some agencies were not complying with the new statutory requirements:

*'''Data retention violations''': 21% (33 of 159) of agencies using ALPR reported retaining data beyond the statutory 21-day limit. Reported retention periods for fixed cameras ranged from 22 to 60 days; for mobile cameras, 30 to 180 days.<ref name="vscc-2026" />

*'''Unauthorized data sharing with federal and out-of-state agencies''': Despite the statute prohibiting such sharing, 13% (20 of 159) of agencies reported providing continuous access to out-of-state law enforcement agencies, and 6% (9 of 159) reported providing continuous access to federal law enforcement agencies.<ref name="vscc-2026" />

*'''No written ALPR policy''': 16% (26 of 159) of agencies using ALPR reported having no policy on ALPR use, despite the statutory requirement to maintain one. An additional 9% (14 of 159) reported being in the process of implementing a policy.<ref name="vscc-2026" />

*'''No public awareness measures''': 35% (55 of 159) of agencies reported taking no public awareness measures regarding their ALPR use, despite statutory requirements to promote public awareness.<ref name="vscc-2026" />

*'''Non-response''': Almost one-third of law enforcement agencies (110 of 361) did not respond to the survey at all, meaning their ALPR use and compliance status remain unknown.<ref name="vscc-2026" />

The Crime Commission's report stated that the Chair, Delegate Charniele Herring, planned to send letters to agencies whose survey responses indicated non-compliance with the new law, as well as to non-responding agencies.<ref name="vscc-2026" />

===Data Sharing Concerns===

Virginia's experience reflects a national pattern of concerns over ALPR data sharing. A September 2025 investigation by the Virginia Center for Investigative Journalism found that before the new law took effect, federal agencies had attempted to access local Virginia ALPR data thousands of times for immigration enforcement purposes, and one small town's Flock network data had been searched nearly 7 million times by outside agencies in a single year.<ref name="vcij-sept2025">{{cite news |last=Falayi |first=K. |date=2025-09-16 |title=One sleepy Virginia town. Nearly 7 million hits on its surveillance network |url=https://vcij.org/stories/state-of-surveillance |access-date=2026-03-02 |work=Virginia Center for Investigative Journalism}}</ref> At least two Virginia localities — Charlottesville and Staunton — subsequently ended their use of Flock Safety cameras, citing concerns about federal data sharing.<ref name="vscc-2026" />

As of early 2026, at least 30 localities across the United States have either deactivated Flock cameras or canceled their contracts, driven in part by concerns over privacy and federal agency access to locally collected ALPR data.<ref name="npr-flock">{{cite news |date=2026-02-17 |title=Why some cities are canceling Flock license plate reader contracts |url=https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns |access-date=2026-03-02 |work=NPR}}</ref>

==REVOLVING DOOR: SURVEILLANCE VENDOR HIRING OF PUBLIC OFFICIALS==

Multiple documented cases have raised concerns about [[Flock Safety]]'s practice of hiring current or recently departed public officials who hold or held influence over the procurement of the company's products. These cases illustrate gaps in state and local ethics laws that allow public officials to move directly into private-sector roles with vendors whose government contracts they shaped, voted on, or administered.

===Cleveland, Ohio: Former Council Majority Leader Joins Flock===

Kerry McCormack, the Ward 3 council member and Majority Leader of the Cleveland City Council, announced his resignation on September 11, 2025. His last day on council was October 3, 2025. He joined Flock Safety immediately afterward as public affairs lead for the eastern United States. No reporting has identified a gap between his departure from office and his start date at Flock.<ref name="ideastream-mccormack">[https://www.ideastream.org/government-politics/2025-09-11/cleveland-councilmember-kerry-mccormack-resigns-before-end-of-term Ideastream: Cleveland Councilmember Kerry McCormack resigns before end of term]</ref><ref name="wkyc-mccormack">[https://www.wkyc.com/article/news/local/cleveland/cleveland-city-councilman-kerry-mccormack-resign-ward-3-seat-october-majority-leader-flock-safety-lauren-welch/95-6380bc59-b942-4c43-a0fc-b1a61f8f8fea WKYC: Kerry McCormack to resign from Cleveland City Council on Oct. 3]</ref>

Twenty-four days after McCormack's departure, the Bibb administration introduced Ordinance 1367-2025 to Cleveland City Council: a three-year, $2,026,500 sole-source emergency contract with Flock Group, Inc. No Request for Proposals was issued and no competing bids were solicited.<ref name="legistar-flock">[https://cityofcleveland.legistar.com/LegislationDetail.aspx?ID=7714153&GUID=D5D4E9A9-CED2-4198-9998-FCD9349ED5A4&Options=ID%7CText%7CAttachments%7COther%7C&Search=flock Cleveland City Council Legistar: File #1367-2025]</ref>

The administration justified the sole-source designation on two grounds: that Flock was the only vendor offering the specific integrated bundle of services, and that the contract piggybacked on a pre-negotiated Ohio state term purchasing agreement. At the November 14, 2025 Safety Committee hearing, SoundThinking (ShotSpotter's parent company) attended and stated on the record that they offer competing products capable of fulfilling the same requirements, directly contradicting the sole-source rationale.<ref name="axios-flock">[https://www.axios.com/local/cleveland/2025/11/14/cleveland-shotspotter-flock Axios Cleveland: Cleveland mulls shift from ShotSpotter to Flock for gunshot detection]</ref><ref name="signal-shotspotter">[https://signalcleveland.org/cleveland-city-council-shotspotter-study-hearing/ Signal Cleveland: City Council debates: Is ShotSpotter making Cleveland safer?]</ref>

====How the emergency and bidding bypass works====

Cleveland Charter § 36 defines an emergency measure as an ordinance or resolution for the "immediate preservation of the public peace, property, health, or safety" or for the "usual daily operation of a Municipal department." Combined with the § 33 rule suspension mechanism, an emergency designation bypasses the normal three-reading requirement and the 30-day waiting period before a measure takes effect. Emergency passage requires a two-thirds supermajority of all elected council members.<ref name="charter-36">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-252 Cleveland Charter § 36: Emergency Measures]</ref>

Charter § 108 requires competitive bidding for contracts exceeding $50,000, with an exception for cooperative purchasing arrangements with other governmental agencies. Professional services contracts are exempt from sealed bidding but are still expected to go through a Request for Proposals process per the Division of Purchases and Supplies. The Bibb administration issued neither a formal bid nor an RFP for the Flock expansion.<ref name="charter-108">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-627 Cleveland Charter § 108: Authorization of Contracts]</ref><ref name="cle-purchases">[https://www.clevelandohio.gov/city-hall/departments/finance/divisions/purchases-supplies City of Cleveland: Division of Purchases & Supplies]</ref>

====Ohio revolving door law and its limitations====

Ohio Revised Code § 102.03(A)(1) bars former public officials for twelve months from representing any person or entity before any public agency on any "matter" in which the official personally participated during their public service.<ref name="orc-102">[https://codes.ohio.gov/ohio-revised-code/section-102.03 Ohio Revised Code § 102.03]</ref>

However, R.C. 102.03(A)(5) explicitly excludes "legislative matters" — defined as the proposal, consideration, or enactment of statutes, rules, ordinances, resolutions, or charter or constitutional amendments — from the definition of "matter." Because Ordinance 1367-2025 is a piece of legislation requiring formal consideration by City Council, the twelve-month ban arguably does not apply to a former council member lobbying for its passage.<ref name="orc-102" />

Cleveland has no local revolving-door ordinance, no lobbying registration requirement, and no cooling-off period of its own. Chapter 171 of the Cleveland Codified Ordinances covers employment provisions such as hours of work and overtime — not ethics or lobbying. By comparison, Chicago imposes a blanket one-year ban on former aldermen lobbying any city official on any topic.<ref name="cle-171">[https://codelibrary.amlegal.com/codes/cleveland/latest/cleveland_oh/0-0-0-4565 Cleveland Codified Ordinances Chapter 171: Employment Provisions]</ref>

McCormack told Signal Cleveland that he "did not seek an opinion from the Ohio Ethics Commission" and was voluntarily observing the one-year rule as a best practice. However, News 5 Cleveland's investigators obtained McCormack's emails through a public records request and reported that he did contact the Ohio Ethics Commission about restrictions approximately one month before leaving office.<ref name="signal-mccormack">[https://signalcleveland.org/cleveland-city-council-kerry-mccormack-flock-safety-contract/ Signal Cleveland: Kerry McCormack says he had 'no engagement' with city over Flock]</ref><ref name="news5-flock">[https://www.news5cleveland.com/news/local-news/more-questions-raised-about-flock-safety-in-cleveland-data-access-and-whos-watching News 5 Cleveland: More questions raised about Flock Safety in Cleveland]</ref>

McCormack's one-year recusal from Cleveland matters is voluntary and self-enforced. It is not a Flock corporate policy and not a legal requirement under Ohio law given the legislative exemption. McCormack stated: "Whether I have a defined legal conflict or not, regardless, it's best practice I think to sit out."<ref name="signal-mccormack" />

Council member Rebecca Maurer stated at a Safety Committee hearing: "I hope you understand the hesitancy I have given a member of this body just departed to take a job at Flock that we now have a sole source contract without an RFP process."<ref name="news5-flock" />

====Status of the Cleveland contract====

Cleveland's ShotSpotter contract expires in April 2026 and the existing Flock automated license plate reader contract expires in June 2026. The Bibb administration proposed bundling both into a single expanded Flock contract covering cameras, license plate readers, gunshot detection, and audio monitoring — all through one vendor on a sole-source basis.<ref name="fox8-flock">[https://fox8.com/news/cleveland-considers-transition-from-shotspotter-to-flock-council-pushes-back/ Fox 8: Cleveland considers transition from ShotSpotter to Flock, council pushes back]</ref><ref name="signal-replace">[https://signalcleveland.org/cleveland-to-replace-shotspotter-with-flock-safety/ Signal Cleveland: Cleveland to replace ShotSpotter with other gunshot-detection tech]</ref>

Council refused to advance the legislation. Fox 8 reported that council will not move forward until a full review is conducted and a request for proposals has been issued.<ref name="fox8-flock" />

The Bibb administration then asked Safety Committee Chair Michael Polensek to shelve the expansion before year-end 2025. No public explanation was given. Polensek counter-proposed issuing a request for qualification.<ref name="clevescene-flock">[https://www.clevescene.com/news/cleveland-news/cleveland-puts-flock-expansion-on-hold-amid-local-pushback/ Cleveland Scene: Cleveland Puts Flock Expansion on Hold Amid Local Pushback]</ref>

As of March 2026, Ordinance 1367-2025 sits on indefinite hold in the Safety Committee. No vote has been scheduled, no RFP has been issued, and no RFQ has been completed. Approximately 100 Flock license plate reader cameras remain active across Cleveland.<ref name="clevescene-flock" /><ref name="news5-grassroots">[https://www.news5cleveland.com/news/local-news/investigations/grassroots-group-presses-cleveland-to-end-relationship-with-flock-safety-expansion-plans-on-hold News 5 Cleveland: Grassroots group presses Cleveland to end relationship with Flock Safety]</ref>

A grassroots group called Flockno delivered a letter with 275 signatures to City Hall demanding the city cut ties with Flock entirely and remove existing cameras when the June contract expires. Roughly 80 additional signatures have been added since. Organizer Bryn Adams stated: "We want to ask the city to remove, not renew."<ref name="news5-grassroots" /><ref name="clevescene-flock" />

===Moreno Valley, California: Flock Hired a Sitting Mayor===

In February 2024, Flock Safety hired Ulises Cabrera, the sitting mayor of Moreno Valley, California (population 200,000+), as a Community Engagement Manager. A Flock job posting for the position listed a salary of $100,000–$140,000 plus stock options. The role was intended to guide law enforcement customers through the public procurement process in collaboration with Flock's sales team. Cabrera had previously voted as mayor to fund a citywide Flock camera system in Moreno Valley.<ref name="tc">[https://techcrunch.com/2025/01/08/flock-safety-quietly-hired-a-sitting-california-mayor-now-hes-suing-flock/ TechCrunch: Flock Safety quietly hired a sitting California mayor. Now he's suing Flock.]</ref>

During his time at Flock, Cabrera gave presentations promoting the company's technology at city council meetings in at least two other jurisdictions: Whitewater, Kansas and Mammoth Lakes, California.<ref name="tc" />

====Cabrera v. Flock Safety====

In November 2024, Cabrera filed a wrongful termination lawsuit against Flock Safety.<ref name="cabrera-complaint">[https://embed.documentcloud.org/documents/25482232-flock-lawsuit-complaint/?embed=1 DocumentCloud: Cabrera v. Flock Safety — Complaint]</ref> According to the complaint, approximately two weeks after Cabrera started working at Flock, an employee requested that he use his position as mayor of Moreno Valley to benefit the company. Cabrera alleges he refused, forwarded the request to his legal counsel while copying the Flock employee, and that the employee immediately began exhibiting retaliatory behavior. Flock terminated Cabrera in June 2024. He worked at Flock from February to June 2024.<ref name="tc" />

Cabrera also alleges he raised concerns that Flock was significantly underreporting the number of surveillance cameras installed in Carmel-by-the-Sea. A separate Forbes investigation published in February 2024 found that Flock camera installations broke laws in at least five states, including by installing cameras without proper permits.<ref name="tc" />

Flock categorically denies all of Cabrera's allegations and says its hire of a sitting mayor complied with California conflict-of-interest regulations.<ref name="tc" />

====California conflict-of-interest law====

California Government Code § 1090 is a strict liability statute prohibiting public officers from being financially interested in any contract made by the body or board of which they are members. A sitting mayor receiving a salary and stock options from a surveillance vendor while his city council approves that vendor's contracts raises direct questions under this provision.<ref name="tc" />

While campaigning for reelection in November 2024, Cabrera's campaign website cited his earlier vote to fund Moreno Valley's Flock system, but did not disclose that he had subsequently worked for Flock while serving as mayor.<ref name="tc" />

===Broader Pattern===

Albert Fox Cahn, founder of the Surveillance Technology Oversight Project, stated that the allegations in the Moreno Valley case "add to the growing body of evidence that American surveillance is fueled by a broken revolving door between industry and government."<ref name="tc" />

The Cleveland and Moreno Valley cases illustrate different but related gaps in ethics law. In Ohio, the state revolving-door statute's explicit exclusion of "legislative matters" from the cooling-off period means that a former council member may legally lobby for ordinances benefiting a new employer immediately upon leaving office. In California, the strict liability framework of Government Code § 1090 theoretically prohibits the arrangement but relies on self-disclosure and enforcement by the Fair Political Practices Commission. In both cases, municipal-level protections were either absent or insufficient: Cleveland has no local lobbying registration or cooling-off ordinance, while Moreno Valley had no mechanism to prevent a sitting mayor from accepting private employment with a city vendor.

==FALSE POSITIVES AND SYSTEM FAILURES==

Automated surveillance systems carry significant risks of false positives, where innocent individuals are subjected to armed police responses based on system errors. These incidents create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' and I was like, 'What?'"<ref name=":3" />''</blockquote>

Allen was forced to his knees, handcuffed, and searched before officers realized he was unarmed. Allen described watching about eight police cars arrive, with officers pointing guns at him.

<blockquote>''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me."''<ref name=":3" /></blockquote>

When shown the image that triggered the alert, Allen explained:<blockquote>''"I was just holding a Doritos bag – it was two hands and one finger out, and they said it looked like a gun."<ref name=":3" />''</blockquote>

High schools in Baltimore County used the AI gun detection system beginning in 2024, using existing school cameras to scan for potential weapons. The system is operated by [[Omnilert]], which taps into existing camera feeds to detect objects that resemble weapons and then alerts both school safety officers and law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name=":3" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name=":3" /> Omnilert defended its system, claiming it ''"functioned as intended: to prioritize safety and awareness through rapid human verification,"'' though the incident demonstrated the system escalated to armed police response before adequate human review occurred.<ref name=":3">{{cite news |last=Tsui |first=Karina |last2=Sottile |first2=Zoe |date=2025-10-25 |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |url=https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |url-status=live |archive-url=https://web.archive.org/web/20251026050806/https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |archive-date=2025-10-26 |access-date=2025-10-28 |work=CNN}}</ref>

===ALPRs Causing Innocent People to be Held at Gunpoint===

ALPR systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====

In 2018, privacy advocate Brian Hofer and his younger brother were driving to visit their parents for Thanksgiving when they were held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1=Lauren |last2=Clark |first2=Alex |date=2025-07-24 |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |url-status=live |archive-url=https://web.archive.org/web/20250724210641/https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |archive-date=2025-07-24 |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government and corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops and ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====

Body camera footage from a documented police incident shows officers pursuing and detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |date=2025-10-06 |title=Police Body Camera: ALPR False Alert Detention-Police Respond To Girl Being Kidnapped (Full Bodycam) |url=https://youtu.be/lmNxitcaT2Y |url-status=live |archive-url=https://preservetube.com/watch?v=lmNxitcaT2Y |archive-date=2026-02-10 |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====

In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. In one incident, a 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7," according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====

In Aurora, Colorado in 2020, a mother and her family, including her 6-year-old daughter, were pulled over at gunpoint and forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state — a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video and widely condemned, led to a $1.9 million settlement from the city in 2024.<ref name="cbs-alpr" />

===Facial Recognition False Identification===

While the preceding cases involve ALPR misreads, similar risks arise with other automated identification systems, including facial recognition technology deployed in commercial settings.

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

On September 17, 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada. Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |last=Roarty |first=Adam |date=2025-12-09 |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-url=https://web.archive.org/web/20251210222601/https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-date=2025-12-10 |access-date=2025-12-16 |website=CasinoBeats}}</ref><ref name="casino-org">{{Cite web |last=Conneller |first=Philip |date=2025-11-11 |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |access-date=2025-12-16 |website=Casino.org |url-status=live |archive-url=https://web.archive.org/web/20260216033051/https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |archive-date=2026-02-16}}</ref> Ellis's ban was set to expire on September 26, 2023 — nine days after the arrest.<ref name="casinobeats" /> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |last=García |first=Jerome |date=2025-12-11 |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-url=https://web.archive.org/web/20251205215015/https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-date=2025-12-05 |access-date=2026-01-11 |website=Gambling News}}</ref>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, and his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him and called the police.<ref name="casino-org" />

Released police records and driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:<ref name="casinobeats" />

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||6'1"||5'9"
|-
|Eye Color||Blue||Hazel
|}

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue and hazel eyes are ''"by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit, he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up"'' to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' and that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating:<blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |last=Gwilliam |first=Michael |date=2025-12-15 |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-url=https://web.archive.org/web/20251218224228/https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-date=2025-12-18 |access-date=2025-12-16 |website=Dexerto}}</ref></blockquote>

Jager handcuffed Killinger and transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |date=2025-11-14 |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-url=https://web.archive.org/web/20260110235640/http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-date=2026-01-10 |access-date=2025-12-16 |website=Our Town Reno}}</ref> His federal lawsuit against Officer Jager, ''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD, remains active in the U.S. District Court for the District of Nevada.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |archive-url=http://web.archive.org/web/20260210093102/https://www.leagle.com/decision/infdco20250925d22 |archive-date=2026-02-10 |access-date=2025-12-16 |website=Leagle}}</ref>

In a January 22, 2026 deposition, Officer Jager acknowledged that the arrest ''"never should have happened"'' and stated that post-lawsuit training had clarified that facial recognition technology cannot serve as the sole basis for probable cause, but should instead be treated as ''"an investigative lead only"'' requiring further corroboration.<ref name="casino-org-deposition">{{Cite web |last=Conneller |first=Philip |date=2026-01-28 |title=Reno Cop Concedes Peppermill Facial Recognition Arrest was Wrongful |url=https://www.casino.org/news/reno-cop-concedes-peppermill-facial-recognition-arrest-wrongful/ |access-date=2026-03-02 |website=Casino.org}}</ref> Following the deposition, Killinger's attorney moved to add the City of Reno as a defendant, arguing that Jager's testimony demonstrated systemic failure to train officers on the limitations of AI facial recognition technology.<ref name="casino-org-deposition" />

The lawsuit alleges that Jager's actions violated Killinger's [[wikipedia:Fourteenth_Amendment_to_the_United_States_Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner and omitted the fingerprint exoneration from his official report.<ref name="casinobeats" /> He is seeking compensatory, special, and punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> Discovery in the case has been extended to July 2026, with motions due by August 2026.<ref name="unicourt-killinger">{{Cite web |title=Killinger vs Jager – Case Details |url=https://unicourt.com/case/pc-db5-casegucf509a42dd1e-2175767 |access-date=2026-03-02 |website=UniCourt}}</ref>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" /> The case illustrates that when officers prioritize algorithmic identification over physical evidence and valid documentation, innocent individuals can be subjected to unjust detention.

===Common ALPR Error Mechanisms===

These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists.
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (such as matching car plates to motorcycle registrations).
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles and criminal activity.
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners.

==LAW ENFORCEMENT MISUSE AND STALKING INCIDENTS==

Documented cases show that law enforcement officers have misused ALPR systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, and the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department's Flock ALPR system to track his ex-girlfriend. According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner's vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper and attributed them to "desperation and bad judgment." He was placed on administrative leave, barred from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings. A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |last=Kerhin |first=Brian |date=2026-01-09 |title=Menasha police officer accused of using license plate recognition system to track his ex |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-url=https://web.archive.org/web/20260110000858/https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-date=2026-01-10 |access-date=2026-01-11 |work=FOX 11 News}}</ref>

The Menasha case is one in what has become a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes and stalking after using Flock cameras to monitor his estranged wife's movements over several months.<ref>{{cite news |last=Baker |first=Joe |date=2022-10-31 |title=Kechi police lieutenant arrested for using police technology to stalk wife |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-url=https://web.archive.org/web/20221031042853/https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-date=2022-10-31 |work=KWCH}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2025 to using Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |last=Stavola |first=Michael |date=2024-08-17 |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-url=https://web.archive.org/web/20240817105006/https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-date=2024-08-17 |work=Yahoo News}}</ref>

Comparable misuse has been documented involving other police databases and surveillance systems. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing law enforcement databases to stalk a woman he met off duty.<ref>{{cite news |last=McCandless |first=C.C. |date=2024-02-16 |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-url=https://web.archive.org/web/20240216010507/https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-date=2024-02-16 |work=FOX5 Vegas}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |last=Tucker |first=Eric |date=2016-09-27 |title=When cops abuse confidential databases |url=https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-url=https://web.archive.org/web/20230721171815/https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-date=2023-07-21 |work=Associated Press}}</ref>

Auditors and civil liberties organizations note that ALPR systems reduce the cost and effort of stalking by allowing quick searches of historical location data across large geographic areas without real-time supervisory approval. While vendors and agencies rely on access logs and written policies, many cases have demonstrated that these safeguards often fail to prevent or detect misuse quickly enough.<ref>{{cite web |date=2023-02-22 |title=Automated License Plate Readers widely used, subject to abuse |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-url=https://web.archive.org/web/20230617100257/https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-date=2023-06-17 |work=University of Michigan}}</ref><ref>{{cite web |last=Davidson |first=Nikki |date=2024-04-16 |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-url=https://web.archive.org/web/20240417005310/https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-date=2024-04-17 |work=Government Technology}}</ref>

The Virginia State Crime Commission's 2025 survey found that despite statutory restrictions on sharing, 20 Virginia law enforcement agencies were still providing continuous access to out-of-state agencies and 9 were providing continuous access to federal agencies. Town police departments and primary sheriff's offices accounted for the majority of non-compliant sharing.<ref name="vscc-2026" />

==See also==

*[[Flock license plate readers]]
*[[Flock Safety]]

==References==
{{reflist}}

[[Category:Flock Safety]]
[[Category:ALPR]]
[[Category:Surveillance]]
[[Category:AI and automation]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-03-03T04:12:21Z

Louis:

{{Alert|message = This is a special page dedicated to a specific issue. It will be deleted once moved elsewhere, and is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city — but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.|thumb|Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[wikipedia:Fourth_Amendment_to_the_United_States_Constitution|Fourth Amendment]] jurisprudence and misunderstands the legal standard of "reasonable expectation of privacy" established by the [[wikipedia:Supreme_Court_of_the_United_States|Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches and seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy." This considers the nature, scope, and how intrusive the government monitoring is.

In [[wikipedia:Carpenter_v._United_States|''Carpenter v. United States'' ''(2018)'']], the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[wikipedia:John_Roberts|John Roberts]] wrote that the government's access to 127 days of cell-site location data — tracking movements on public roads — achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |archive-url=https://web.archive.org/web/20180623061246/https://www.law.cornell.edu/supremecourt/text/16-402 |archive-date=2018-06-23 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> The Court said,<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation and Comprehensive Surveillance===

Courts separate isolated instances of police observation and large-scale automated tracking systems. In ''[[wikipedia:United_States_v._Jones_(2012)|United States v. Jones (2012)]]'', Justice [[wikipedia:Sonia_Sotomayor|Sonia Sotomayor's]] influential concurrence explained that [[GPS tracking]]:<blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, and sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-url=https://web.archive.org/web/20120126022816/https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-date=2012-01-26 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref></blockquote>She noted that automated surveillance:<blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources and community hostility."<ref name=":1" />''</blockquote>The [[wikipedia:Massachusetts_Supreme_Judicial_Court|Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy (2020)'', holding:<blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |date=2020-04-16 |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-url=https://web.archive.org/web/20220303203404/https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-date=2022-03-03 |access-date=2025-12-16 |website=Justia}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The [[wikipedia:Mosaic_theory_of_the_Fourth_Amendment|"mosaic theory" of Fourth Amendment protection]] holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[wikipedia:Samuel_Alito|Samuel Alito]] noted in his ''Jones'' concurrence that:<blockquote>''"society's expectation has been that law enforcement agents and others would not; and indeed, in the main, simply could not; secretly monitor and catalogue every single movement of an individual's car for a very long period."<ref name=":1" />''</blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In [[wikipedia:United_States_v._Knotts|''United States v. Knotts (1983)'']], while holding that limited beeper (a radio-emitting surveillance device) tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "[[wikipedia:Dragnet_(policing)|dragnet-type law enforcement practices]]."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |url-status=live |archive-url=https://web.archive.org/web/20120601022257/https://www.law.cornell.edu/supremecourt/text/460/276 |archive-date=2012-06-01 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk (E.D. Va.)'', privacy advocates Lee Schmidt and Crystal Arrington challenged Norfolk's 176-camera Flock Safety ALPR network as unconstitutional. Chief Judge [[wikipedia:Mark_Steven_Davis|Mark S. Davis]] initially denied a motion to dismiss the case in February 2025, finding that plaintiffs had stated a plausible Fourth Amendment claim. During discovery, it emerged that Schmidt's vehicle had been photographed 475 times and Arrington's 325 times over a four-month period in 2025.<ref name="nbc-norfolk">{{cite news |last=Collier |first=Kevin |date=2025-09-18 |title=Police cameras tracked one driver 526 times in four months, lawsuit says |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |url-status=live |archive-url=https://web.archive.org/web/20250918093450/https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |archive-date=2025-09-18 |access-date=2025-12-16 |work=NBC News}}</ref>

However, on January 27, 2026, Judge Davis granted summary judgment in favor of the City, ruling that Norfolk's ALPR system did not violate the Fourth Amendment. In a 51-page opinion, Davis concluded that the plaintiffs could not demonstrate that the system was capable of tracking the entirety of a person's movements. The court found that although the cameras captured snapshots of daily life, they did not continuously track individuals or capture sufficient data to reconstruct whole routines, noting "sizable gaps" between photographs.<ref name="whro-norfolk">{{cite news |last=Cox |first=Toby |date=2026-02-11 |title=A federal judge ruled Norfolk's Flock surveillance cameras don't invade people's privacy – yet |url=https://www.whro.org/business-growth/2026-02-11/a-federal-judge-ruled-norfolks-flock-surveillance-cameras-dont-invade-peoples-privacy-yet |access-date=2026-03-02 |work=WHRO}}</ref><ref name="courthouse-norfolk">{{cite news |date=2026-01-28 |title=Judge holds Norfolk's license plate reader use constitutional |url=https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/ |access-date=2026-03-02 |work=Courthouse News Service}}</ref>

Notably, Judge Davis cautioned that the constitutional analysis could change as ALPR technology expands. He wrote that ''"ALPR surveillance could become too intrusive and run afoul of [constitutional privacy standards] at some point,"'' but concluded that ''"at least in Norfolk, Virginia, the answer is: not today."''<ref name="whro-norfolk" /> The plaintiffs, represented by the Institute for Justice, announced their intention to appeal, with Schmidt stating he remained committed to fighting against what he described as "dragnet warrantless surveillance."<ref name="whro-norfolk" /><ref name="courthouse-norfolk" />

Flock Safety's chief legal officer responded that the decision aligned with rulings by over 30 state and federal courts concluding that fixed-location ALPRs do not constitute a search under the Fourth Amendment.<ref name="courthouse-norfolk" />

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 and 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |last=Maass |first=Dave |last2=Lipton |first2=Beryl |date=2021-04-22 |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-url=https://web.archive.org/web/20181115183012/https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-date=2018-11-15 |access-date=2025-12-16 |website=Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale and the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale and comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[wikipedia:Stalking|stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, and sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge and Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016 |url=https://scholarlycommons.law.northwestern.edu/nulr/vol111/iss1/4/}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly;<ref>{{cite news |last=Kenney |first=Andrew |date=2024-09-19 |title=2 million license plates scanned monthly by Denver's new police cameras |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-url=https://web.archive.org/web/20240919214639/https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-date=2024-09-19 |access-date=2025-12-16 |work=Denverite}}</ref> Norfolk's 176 cameras provide citywide coverage;<ref name="nbc-norfolk" /> and Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |last=Thompson |first=Ben |date=2025-05-20 |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |url-status=live |archive-url=https://web.archive.org/web/20250607131518/https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |archive-date=2025-06-07 |access-date=2025-12-16 |work=Community Impact}}</ref>

==STATE LEGISLATIVE RESPONSES: VIRGINIA AS A CASE STUDY==

Virginia became one of the first states to enact comprehensive statewide ALPR regulation when legislation establishing statewide standards for law enforcement use of ALPR took effect on July 1, 2025. Prior to this date, Virginia had no statewide statutory or regulatory framework governing law enforcement use of ALPR, meaning agencies could operate the technology without any statewide limitations on use, data retention, or data sharing.<ref name="vscc-2026">{{cite web |title=Law Enforcement Use of Automatic License Plate Recognition (ALPR) Update, January 2026 |url=https://vscc.virginia.gov/2026/VSCC%20ALPR%20Report%20January%202026%20FINAL%20REVISED%20Jan%2021%202026.pdf |access-date=2026-03-02 |publisher=Virginia State Crime Commission |date=2026-01}}</ref>

===Overview of Virginia's 2025 ALPR Law===

Under the new statute (Virginia House Bill 2724, codified at Va. Code Ann. § 2.2-5517), law enforcement agencies in Virginia may only use ALPR for criminal investigations, active investigations into missing or endangered persons or human trafficking, and notifications related to missing or endangered persons, outstanding warrants, human trafficking, stolen vehicles, or stolen license plates.<ref name="vscc-2026" />

The law requires ALPR data to be purged after 21 days unless needed for an ongoing investigation, prosecution, or civil action. It also restricts data sharing to other Virginia law enforcement agencies, Commonwealth's Attorneys, criminal defendants or their counsel, ALPR vendors, or pursuant to a court order. The statute does not permit data sharing with out-of-state or federal law enforcement agencies.<ref name="vscc-2026" />

===Compliance Findings from the Virginia State Crime Commission===

In January 2026, the Virginia State Crime Commission published the findings of a statewide survey of all 361 Virginia law enforcement agencies on their use of ALPR. The survey, conducted in November 2025 to capture practices after the new legislation took effect, received responses from 251 agencies (70%). Of responding agencies, 63% (159 of 251) reported using ALPR. A large majority — 86% (137 of 159) — reported [[Flock Safety]] as their ALPR vendor.<ref name="vscc-2026" />

The Crime Commission found that some agencies were not complying with the new statutory requirements:

*'''Data retention violations''': 21% (33 of 159) of agencies using ALPR reported retaining data beyond the statutory 21-day limit. Reported retention periods for fixed cameras ranged from 22 to 60 days; for mobile cameras, 30 to 180 days.<ref name="vscc-2026" />

*'''Unauthorized data sharing with federal and out-of-state agencies''': Despite the statute prohibiting such sharing, 13% (20 of 159) of agencies reported providing continuous access to out-of-state law enforcement agencies, and 6% (9 of 159) reported providing continuous access to federal law enforcement agencies.<ref name="vscc-2026" />

*'''No written ALPR policy''': 16% (26 of 159) of agencies using ALPR reported having no policy on ALPR use, despite the statutory requirement to maintain one. An additional 9% (14 of 159) reported being in the process of implementing a policy.<ref name="vscc-2026" />

*'''No public awareness measures''': 35% (55 of 159) of agencies reported taking no public awareness measures regarding their ALPR use, despite statutory requirements to promote public awareness.<ref name="vscc-2026" />

*'''Non-response''': Almost one-third of law enforcement agencies (110 of 361) did not respond to the survey at all, meaning their ALPR use and compliance status remain unknown.<ref name="vscc-2026" />

The Crime Commission's report stated that the Chair, Delegate Charniele Herring, planned to send letters to agencies whose survey responses indicated non-compliance with the new law, as well as to non-responding agencies.<ref name="vscc-2026" />

===Data Sharing Concerns===

Virginia's experience reflects a national pattern of concerns over ALPR data sharing. A September 2025 investigation by the Virginia Center for Investigative Journalism found that before the new law took effect, federal agencies had attempted to access local Virginia ALPR data thousands of times for immigration enforcement purposes, and one small town's Flock network data had been searched nearly 7 million times by outside agencies in a single year.<ref name="vcij-sept2025">{{cite news |last=Falayi |first=K. |date=2025-09-16 |title=One sleepy Virginia town. Nearly 7 million hits on its surveillance network |url=https://vcij.org/stories/state-of-surveillance |access-date=2026-03-02 |work=Virginia Center for Investigative Journalism}}</ref> At least two Virginia localities — Charlottesville and Staunton — subsequently ended their use of Flock Safety cameras, citing concerns about federal data sharing.<ref name="vscc-2026" />

As of early 2026, at least 30 localities across the United States have either deactivated Flock cameras or canceled their contracts, driven in part by concerns over privacy and federal agency access to locally collected ALPR data.<ref name="npr-flock">{{cite news |date=2026-02-17 |title=Why some cities are canceling Flock license plate reader contracts |url=https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns |access-date=2026-03-02 |work=NPR}}</ref>

==FALSE POSITIVES AND SYSTEM FAILURES==

Automated surveillance systems carry significant risks of false positives, where innocent individuals are subjected to armed police responses based on system errors. These incidents create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' and I was like, 'What?'"<ref name=":3" />''</blockquote>

Allen was forced to his knees, handcuffed, and searched before officers realized he was unarmed. Allen described watching about eight police cars arrive, with officers pointing guns at him.

<blockquote>''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me."''<ref name=":3" /></blockquote>

When shown the image that triggered the alert, Allen explained:<blockquote>''"I was just holding a Doritos bag – it was two hands and one finger out, and they said it looked like a gun."<ref name=":3" />''</blockquote>

High schools in Baltimore County used the AI gun detection system beginning in 2024, using existing school cameras to scan for potential weapons. The system is operated by [[Omnilert]], which taps into existing camera feeds to detect objects that resemble weapons and then alerts both school safety officers and law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name=":3" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name=":3" /> Omnilert defended its system, claiming it ''"functioned as intended: to prioritize safety and awareness through rapid human verification,"'' though the incident demonstrated the system escalated to armed police response before adequate human review occurred.<ref name=":3">{{cite news |last=Tsui |first=Karina |last2=Sottile |first2=Zoe |date=2025-10-25 |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |url=https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |url-status=live |archive-url=https://web.archive.org/web/20251026050806/https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |archive-date=2025-10-26 |access-date=2025-10-28 |work=CNN}}</ref>

===ALPRs Causing Innocent People to be Held at Gunpoint===

ALPR systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====

In 2018, privacy advocate Brian Hofer and his younger brother were driving to visit their parents for Thanksgiving when they were held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1=Lauren |last2=Clark |first2=Alex |date=2025-07-24 |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |url-status=live |archive-url=https://web.archive.org/web/20250724210641/https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |archive-date=2025-07-24 |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government and corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops and ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====

Body camera footage from a documented police incident shows officers pursuing and detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |date=2025-10-06 |title=Police Body Camera: ALPR False Alert Detention-Police Respond To Girl Being Kidnapped (Full Bodycam) |url=https://youtu.be/lmNxitcaT2Y |url-status=live |archive-url=https://preservetube.com/watch?v=lmNxitcaT2Y |archive-date=2026-02-10 |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====

In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. In one incident, a 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7," according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====

In Aurora, Colorado in 2020, a mother and her family, including her 6-year-old daughter, were pulled over at gunpoint and forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state — a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video and widely condemned, led to a $1.9 million settlement from the city in 2024.<ref name="cbs-alpr" />

===Facial Recognition False Identification===

While the preceding cases involve ALPR misreads, similar risks arise with other automated identification systems, including facial recognition technology deployed in commercial settings.

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

On September 17, 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada. Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |last=Roarty |first=Adam |date=2025-12-09 |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-url=https://web.archive.org/web/20251210222601/https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-date=2025-12-10 |access-date=2025-12-16 |website=CasinoBeats}}</ref><ref name="casino-org">{{Cite web |last=Conneller |first=Philip |date=2025-11-11 |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |access-date=2025-12-16 |website=Casino.org |url-status=live |archive-url=https://web.archive.org/web/20260216033051/https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |archive-date=2026-02-16}}</ref> Ellis's ban was set to expire on September 26, 2023 — nine days after the arrest.<ref name="casinobeats" /> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |last=García |first=Jerome |date=2025-12-11 |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-url=https://web.archive.org/web/20251205215015/https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-date=2025-12-05 |access-date=2026-01-11 |website=Gambling News}}</ref>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, and his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him and called the police.<ref name="casino-org" />

Released police records and driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:<ref name="casinobeats" />

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||6'1"||5'9"
|-
|Eye Color||Blue||Hazel
|}

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue and hazel eyes are ''"by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit, he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up"'' to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' and that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating:<blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |last=Gwilliam |first=Michael |date=2025-12-15 |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-url=https://web.archive.org/web/20251218224228/https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-date=2025-12-18 |access-date=2025-12-16 |website=Dexerto}}</ref></blockquote>

Jager handcuffed Killinger and transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |date=2025-11-14 |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-url=https://web.archive.org/web/20260110235640/http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-date=2026-01-10 |access-date=2025-12-16 |website=Our Town Reno}}</ref> His federal lawsuit against Officer Jager, ''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD, remains active in the U.S. District Court for the District of Nevada.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |archive-url=http://web.archive.org/web/20260210093102/https://www.leagle.com/decision/infdco20250925d22 |archive-date=2026-02-10 |access-date=2025-12-16 |website=Leagle}}</ref>

In a January 22, 2026 deposition, Officer Jager acknowledged that the arrest ''"never should have happened"'' and stated that post-lawsuit training had clarified that facial recognition technology cannot serve as the sole basis for probable cause, but should instead be treated as ''"an investigative lead only"'' requiring further corroboration.<ref name="casino-org-deposition">{{Cite web |last=Conneller |first=Philip |date=2026-01-28 |title=Reno Cop Concedes Peppermill Facial Recognition Arrest was Wrongful |url=https://www.casino.org/news/reno-cop-concedes-peppermill-facial-recognition-arrest-wrongful/ |access-date=2026-03-02 |website=Casino.org}}</ref> Following the deposition, Killinger's attorney moved to add the City of Reno as a defendant, arguing that Jager's testimony demonstrated systemic failure to train officers on the limitations of AI facial recognition technology.<ref name="casino-org-deposition" />

The lawsuit alleges that Jager's actions violated Killinger's [[wikipedia:Fourteenth_Amendment_to_the_United_States_Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner and omitted the fingerprint exoneration from his official report.<ref name="casinobeats" /> He is seeking compensatory, special, and punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> Discovery in the case has been extended to July 2026, with motions due by August 2026.<ref name="unicourt-killinger">{{Cite web |title=Killinger vs Jager – Case Details |url=https://unicourt.com/case/pc-db5-casegucf509a42dd1e-2175767 |access-date=2026-03-02 |website=UniCourt}}</ref>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" /> The case illustrates that when officers prioritize algorithmic identification over physical evidence and valid documentation, innocent individuals can be subjected to unjust detention.

===Common ALPR Error Mechanisms===

These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists.
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (such as matching car plates to motorcycle registrations).
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles and criminal activity.
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners.

==LAW ENFORCEMENT MISUSE AND STALKING INCIDENTS==

Documented cases show that law enforcement officers have misused ALPR systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, and the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department's Flock ALPR system to track his ex-girlfriend. According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner's vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper and attributed them to "desperation and bad judgment." He was placed on administrative leave, barred from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings. A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |last=Kerhin |first=Brian |date=2026-01-09 |title=Menasha police officer accused of using license plate recognition system to track his ex |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-url=https://web.archive.org/web/20260110000858/https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-date=2026-01-10 |access-date=2026-01-11 |work=FOX 11 News}}</ref>

The Menasha case is one in what has become a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes and stalking after using Flock cameras to monitor his estranged wife's movements over several months.<ref>{{cite news |last=Baker |first=Joe |date=2022-10-31 |title=Kechi police lieutenant arrested for using police technology to stalk wife |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-url=https://web.archive.org/web/20221031042853/https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-date=2022-10-31 |work=KWCH}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2025 to using Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |last=Stavola |first=Michael |date=2024-08-17 |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-url=https://web.archive.org/web/20240817105006/https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-date=2024-08-17 |work=Yahoo News}}</ref>

Comparable misuse has been documented involving other police databases and surveillance systems. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing law enforcement databases to stalk a woman he met off duty.<ref>{{cite news |last=McCandless |first=C.C. |date=2024-02-16 |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-url=https://web.archive.org/web/20240216010507/https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-date=2024-02-16 |work=FOX5 Vegas}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |last=Tucker |first=Eric |date=2016-09-27 |title=When cops abuse confidential databases |url=https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-url=https://web.archive.org/web/20230721171815/https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-date=2023-07-21 |work=Associated Press}}</ref>

Auditors and civil liberties organizations note that ALPR systems reduce the cost and effort of stalking by allowing quick searches of historical location data across large geographic areas without real-time supervisory approval. While vendors and agencies rely on access logs and written policies, many cases have demonstrated that these safeguards often fail to prevent or detect misuse quickly enough.<ref>{{cite web |date=2023-02-22 |title=Automated License Plate Readers widely used, subject to abuse |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-url=https://web.archive.org/web/20230617100257/https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-date=2023-06-17 |work=University of Michigan}}</ref><ref>{{cite web |last=Davidson |first=Nikki |date=2024-04-16 |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-url=https://web.archive.org/web/20240417005310/https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-date=2024-04-17 |work=Government Technology}}</ref>

The Virginia State Crime Commission's 2025 survey found that despite statutory restrictions on sharing, 20 Virginia law enforcement agencies were still providing continuous access to out-of-state agencies and 9 were providing continuous access to federal agencies. Town police departments and primary sheriff's offices accounted for the majority of non-compliant sharing.<ref name="vscc-2026" />

==See also==

*[[Flock license plate readers]]
*[[Flock Safety]]

==References==
{{reflist}}

[[Category:Flock Safety]]
[[Category:ALPR]]
[[Category:Surveillance]]
[[Category:AI and automation]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-03-03T04:02:19Z

Louis:

{{Alert|message = This is a special page dedicated to a specific issue. It will be deleted once moved elsewhere, and is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city — but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.|thumb|Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[wikipedia:Fourth_Amendment_to_the_United_States_Constitution|Fourth Amendment]] jurisprudence and misunderstands the legal standard of "reasonable expectation of privacy" established by the [[wikipedia:Supreme_Court_of_the_United_States|Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches and seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy." This considers the nature, scope, and how intrusive the government monitoring is.

In [[wikipedia:Carpenter_v._United_States|''Carpenter v. United States'' ''(2018)'']], the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[wikipedia:John_Roberts|John Roberts]] wrote that the government's access to 127 days of cell-site location data — tracking movements on public roads — achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |archive-url=https://web.archive.org/web/20180623061246/https://www.law.cornell.edu/supremecourt/text/16-402 |archive-date=2018-06-23 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> The Court said,<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation and Comprehensive Surveillance===

Courts separate isolated instances of police observation and large-scale automated tracking systems. In ''[[wikipedia:United_States_v._Jones_(2012)|United States v. Jones (2012)]]'', Justice [[wikipedia:Sonia_Sotomayor|Sonia Sotomayor's]] influential concurrence explained that [[GPS tracking]]:<blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, and sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-url=https://web.archive.org/web/20120126022816/https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-date=2012-01-26 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref></blockquote>She noted that automated surveillance:<blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources and community hostility."<ref name=":1" />''</blockquote>The [[wikipedia:Massachusetts_Supreme_Judicial_Court|Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy (2020)'', holding:<blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |date=2020-04-16 |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-url=https://web.archive.org/web/20220303203404/https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-date=2022-03-03 |access-date=2025-12-16 |website=Justia}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The [[wikipedia:Mosaic_theory_of_the_Fourth_Amendment|"mosaic theory" of Fourth Amendment protection]] holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[wikipedia:Samuel_Alito|Samuel Alito]] noted in his ''Jones'' concurrence that:<blockquote>''"society's expectation has been that law enforcement agents and others would not; and indeed, in the main, simply could not; secretly monitor and catalogue every single movement of an individual's car for a very long period."<ref name=":1" />''</blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In [[wikipedia:United_States_v._Knotts|''United States v. Knotts (1983)'']], while holding that limited beeper (a radio-emitting surveillance device) tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "[[wikipedia:Dragnet_(policing)|dragnet-type law enforcement practices]]."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |url-status=live |archive-url=https://web.archive.org/web/20120601022257/https://www.law.cornell.edu/supremecourt/text/460/276 |archive-date=2012-06-01 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk (E.D. Va.)'', privacy advocates Lee Schmidt and Crystal Arrington challenged Norfolk's 176-camera Flock Safety ALPR network as unconstitutional. Chief Judge [[wikipedia:Mark_Steven_Davis|Mark S. Davis]] initially denied a motion to dismiss the case in February 2025, finding that plaintiffs had stated a plausible Fourth Amendment claim. During discovery, it emerged that Schmidt's vehicle had been photographed 475 times and Arrington's 325 times over a four-month period in 2025.<ref name="nbc-norfolk">{{cite news |last=Collier |first=Kevin |date=2025-09-18 |title=Police cameras tracked one driver 526 times in four months, lawsuit says |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |url-status=live |archive-url=https://web.archive.org/web/20250918093450/https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |archive-date=2025-09-18 |access-date=2025-12-16 |work=NBC News}}</ref>

However, on January 27, 2026, Judge Davis granted summary judgment in favor of the City, ruling that Norfolk's ALPR system did not violate the Fourth Amendment. In a 51-page opinion, Davis concluded that the plaintiffs could not demonstrate that the system was capable of tracking the entirety of a person's movements. The court found that although the cameras captured snapshots of daily life, they did not continuously track individuals or capture sufficient data to reconstruct whole routines, noting "sizable gaps" between photographs.<ref name="whro-norfolk">{{cite news |last=Cox |first=Toby |date=2026-02-11 |title=A federal judge ruled Norfolk's Flock surveillance cameras don't invade people's privacy – yet |url=https://www.whro.org/business-growth/2026-02-11/a-federal-judge-ruled-norfolks-flock-surveillance-cameras-dont-invade-peoples-privacy-yet |access-date=2026-03-02 |work=WHRO}}</ref><ref name="courthouse-norfolk">{{cite news |date=2026-01-28 |title=Judge holds Norfolk's license plate reader use constitutional |url=https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/ |access-date=2026-03-02 |work=Courthouse News Service}}</ref>

Notably, Judge Davis cautioned that the constitutional analysis could change as ALPR technology expands. He wrote that ''"ALPR surveillance could become too intrusive and run afoul of [constitutional privacy standards] at some point,"'' but concluded that ''"at least in Norfolk, Virginia, the answer is: not today."''<ref name="whro-norfolk" /> The plaintiffs, represented by the Institute for Justice, announced their intention to appeal, with Schmidt stating he remained committed to fighting against what he described as "dragnet warrantless surveillance."<ref name="whro-norfolk" /><ref name="courthouse-norfolk" />

Flock Safety's chief legal officer responded that the decision aligned with rulings by over 30 state and federal courts concluding that fixed-location ALPRs do not constitute a search under the Fourth Amendment.<ref name="courthouse-norfolk" />

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 and 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |last=Maass |first=Dave |last2=Lipton |first2=Beryl |date=2021-04-22 |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-url=https://web.archive.org/web/20181115183012/https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-date=2018-11-15 |access-date=2025-12-16 |website=Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale and the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale and comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[wikipedia:Stalking|stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, and sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge and Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016 |url=https://scholarlycommons.law.northwestern.edu/nulr/vol111/iss1/4/}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly;<ref>{{cite news |last=Kenney |first=Andrew |date=2024-09-19 |title=2 million license plates scanned monthly by Denver's new police cameras |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-url=https://web.archive.org/web/20240919214639/https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-date=2024-09-19 |access-date=2025-12-16 |work=Denverite}}</ref> Norfolk's 176 cameras provide citywide coverage;<ref name="nbc-norfolk" /> and Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |last=Thompson |first=Ben |date=2025-05-20 |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |url-status=live |archive-url=https://web.archive.org/web/20250607131518/https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |archive-date=2025-06-07 |access-date=2025-12-16 |work=Community Impact}}</ref>

==STATE LEGISLATIVE RESPONSES: VIRGINIA AS A CASE STUDY==

Virginia became one of the first states to enact comprehensive statewide ALPR regulation when legislation establishing statewide standards for law enforcement use of ALPR took effect on July 1, 2025. Prior to this date, Virginia had no statewide statutory or regulatory framework governing law enforcement use of ALPR, meaning agencies could operate the technology without any statewide limitations on use, data retention, or data sharing.<ref name="vscc-2026">{{cite web |title=Law Enforcement Use of Automatic License Plate Recognition (ALPR) Update, January 2026 |url=https://vscc.virginia.gov/2026/VSCC%20ALPR%20Report%20January%202026%20FINAL%20REVISED%20Jan%2021%202026.pdf |access-date=2026-03-02 |publisher=Virginia State Crime Commission |date=2026-01}}</ref>

===Overview of Virginia's 2025 ALPR Law===

Under the new statute (Virginia House Bill 2724, codified at Va. Code Ann. § 2.2-5517), law enforcement agencies in Virginia may only use ALPR for criminal investigations, active investigations into missing or endangered persons or human trafficking, and notifications related to missing or endangered persons, outstanding warrants, human trafficking, stolen vehicles, or stolen license plates.<ref name="vscc-2026" />

The law requires ALPR data to be purged after 21 days unless needed for an ongoing investigation, prosecution, or civil action. It also restricts data sharing to other Virginia law enforcement agencies, Commonwealth's Attorneys, criminal defendants or their counsel, ALPR vendors, or pursuant to a court order. The statute does not permit data sharing with out-of-state or federal law enforcement agencies.<ref name="vscc-2026" />

===Compliance Findings from the Virginia State Crime Commission===

In January 2026, the Virginia State Crime Commission published the findings of a statewide survey of all 361 Virginia law enforcement agencies on their use of ALPR. The survey, conducted in November 2025 to capture practices after the new legislation took effect, received responses from 251 agencies (70%). Of responding agencies, 63% (159 of 251) reported using ALPR. A large majority — 86% (137 of 159) — reported [[Flock Safety]] as their ALPR vendor.<ref name="vscc-2026" />

The Crime Commission found that some agencies were not complying with the new statutory requirements:

*'''Data retention violations''': 21% (33 of 159) of agencies using ALPR reported retaining data beyond the statutory 21-day limit. Reported retention periods for fixed cameras ranged from 22 to 60 days; for mobile cameras, 30 to 180 days.<ref name="vscc-2026" />

*'''Unauthorized data sharing with federal and out-of-state agencies''': Despite the statute prohibiting such sharing, 13% (20 of 159) of agencies reported providing continuous access to out-of-state law enforcement agencies, and 6% (9 of 159) reported providing continuous access to federal law enforcement agencies.<ref name="vscc-2026" />

*'''No written ALPR policy''': 16% (26 of 159) of agencies using ALPR reported having no policy on ALPR use, despite the statutory requirement to maintain one. An additional 9% (14 of 159) reported being in the process of implementing a policy.<ref name="vscc-2026" />

*'''No public awareness measures''': 35% (55 of 159) of agencies reported taking no public awareness measures regarding their ALPR use, despite statutory requirements to promote public awareness.<ref name="vscc-2026" />

*'''Non-response''': Almost one-third of law enforcement agencies (110 of 361) did not respond to the survey at all, meaning their ALPR use and compliance status remain unknown.<ref name="vscc-2026" />

The Crime Commission's report stated that the Chair, Delegate Charniele Herring, planned to send letters to agencies whose survey responses indicated non-compliance with the new law, as well as to non-responding agencies.<ref name="vscc-2026" />

===Data Sharing Concerns===

Virginia's experience reflects a national pattern of concerns over ALPR data sharing. A September 2025 investigation by the Virginia Center for Investigative Journalism found that before the new law took effect, federal agencies had attempted to access local Virginia ALPR data thousands of times for immigration enforcement purposes, and one small town's Flock network data had been searched nearly 7 million times by outside agencies in a single year.<ref name="vcij-sept2025">{{cite news |last=Falayi |first=K. |date=2025-09-16 |title=One sleepy Virginia town. Nearly 7 million hits on its surveillance network |url=https://vcij.org/stories/state-of-surveillance |access-date=2026-03-02 |work=Virginia Center for Investigative Journalism}}</ref> At least two Virginia localities — Charlottesville and Staunton — subsequently ended their use of Flock Safety cameras, citing concerns about federal data sharing.<ref name="vscc-2026" />

As of early 2026, at least 30 localities across the United States have either deactivated Flock cameras or canceled their contracts, driven in part by concerns over privacy and federal agency access to locally collected ALPR data.<ref name="npr-flock">{{cite news |date=2026-02-17 |title=Why some cities are canceling Flock license plate reader contracts |url=https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns |access-date=2026-03-02 |work=NPR}}</ref>

==FALSE POSITIVES AND SYSTEM FAILURES==

Automated surveillance systems carry significant risks of false positives, where innocent individuals are subjected to armed police responses based on system errors. These incidents create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' and I was like, 'What?'"<ref name=":3" />''</blockquote>

Allen was forced to his knees, handcuffed, and searched before officers realized he was unarmed. Allen described watching about eight police cars arrive, with officers pointing guns at him.

<blockquote>''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me."''<ref name=":3" /></blockquote>

When shown the image that triggered the alert, Allen explained:<blockquote>''"I was just holding a Doritos bag – it was two hands and one finger out, and they said it looked like a gun."<ref name=":3" />''</blockquote>

High schools in Baltimore County used the AI gun detection system beginning in 2024, using existing school cameras to scan for potential weapons. The system is operated by [[Omnilert]], which taps into existing camera feeds to detect objects that resemble weapons and then alerts both school safety officers and law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name=":3" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name=":3" /> Omnilert defended its system, claiming it ''"functioned as intended: to prioritize safety and awareness through rapid human verification,"'' though the incident demonstrated the system escalated to armed police response before adequate human review occurred.<ref name=":3">{{cite news |last=Tsui |first=Karina |last2=Sottile |first2=Zoe |date=2025-10-25 |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |url=https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |url-status=live |archive-url=https://web.archive.org/web/20251026050806/https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |archive-date=2025-10-26 |access-date=2025-10-28 |work=CNN}}</ref>

===ALPRs Causing Innocent People to be Held at Gunpoint===

ALPR systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====

In 2018, privacy advocate Brian Hofer and his younger brother were driving to visit their parents for Thanksgiving when they were held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1=Lauren |last2=Clark |first2=Alex |date=2025-07-24 |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |url-status=live |archive-url=https://web.archive.org/web/20250724210641/https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |archive-date=2025-07-24 |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government and corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops and ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====

Body camera footage from a documented police incident shows officers pursuing and detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |date=2025-10-06 |title=Police Body Camera: ALPR False Alert Detention-Police Respond To Girl Being Kidnapped (Full Bodycam) |url=https://youtu.be/lmNxitcaT2Y |url-status=live |archive-url=https://preservetube.com/watch?v=lmNxitcaT2Y |archive-date=2026-02-10 |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====

In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. In one incident, a 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7," according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====

In Aurora, Colorado in 2020, a mother and her family, including her 6-year-old daughter, were pulled over at gunpoint and forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state — a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video and widely condemned, led to a $1.9 million settlement from the city in 2024.<ref name="cbs-alpr" />

===Facial Recognition False Identification===

While the preceding cases involve ALPR misreads, similar risks arise with other automated identification systems, including facial recognition technology deployed in commercial settings.

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

On September 17, 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada. Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |last=Roarty |first=Adam |date=2025-12-09 |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-url=https://web.archive.org/web/20251210222601/https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-date=2025-12-10 |access-date=2025-12-16 |website=CasinoBeats}}</ref><ref name="casino-org">{{Cite web |last=Conneller |first=Philip |date=2025-11-11 |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |access-date=2025-12-16 |website=Casino.org |url-status=live |archive-url=https://web.archive.org/web/20260216033051/https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |archive-date=2026-02-16}}</ref> Ellis's ban was set to expire on September 26, 2023 — nine days after the arrest.<ref name="casinobeats" /> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |last=García |first=Jerome |date=2025-12-11 |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-url=https://web.archive.org/web/20251205215015/https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-date=2025-12-05 |access-date=2026-01-11 |website=Gambling News}}</ref>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, and his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him and called the police.<ref name="casino-org" />

Released police records and driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:<ref name="casinobeats" />

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||6'1"||5'9"
|-
|Eye Color||Blue||Hazel
|}

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue and hazel eyes are ''"by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit, he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up"'' to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' and that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating:<blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |last=Gwilliam |first=Michael |date=2025-12-15 |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-url=https://web.archive.org/web/20251218224228/https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-date=2025-12-18 |access-date=2025-12-16 |website=Dexerto}}</ref></blockquote>

Jager handcuffed Killinger and transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |date=2025-11-14 |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-url=https://web.archive.org/web/20260110235640/http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-date=2026-01-10 |access-date=2025-12-16 |website=Our Town Reno}}</ref> His federal lawsuit against Officer Jager, ''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD, remains active in the U.S. District Court for the District of Nevada.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |archive-url=http://web.archive.org/web/20260210093102/https://www.leagle.com/decision/infdco20250925d22 |archive-date=2026-02-10 |access-date=2025-12-16 |website=Leagle}}</ref>

In a January 22, 2026 deposition, Officer Jager acknowledged that the arrest ''"never should have happened"'' and stated that post-lawsuit training had clarified that facial recognition technology cannot serve as the sole basis for probable cause, but should instead be treated as ''"an investigative lead only"'' requiring further corroboration.<ref name="casino-org-deposition">{{Cite web |last=Conneller |first=Philip |date=2026-01-28 |title=Reno Cop Concedes Peppermill Facial Recognition Arrest was Wrongful |url=https://www.casino.org/news/reno-cop-concedes-peppermill-facial-recognition-arrest-wrongful/ |access-date=2026-03-02 |website=Casino.org}}</ref> Following the deposition, Killinger's attorney moved to add the City of Reno as a defendant, arguing that Jager's testimony demonstrated systemic failure to train officers on the limitations of AI facial recognition technology.<ref name="casino-org-deposition" />

The lawsuit alleges that Jager's actions violated Killinger's [[wikipedia:Fourteenth_Amendment_to_the_United_States_Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner and omitted the fingerprint exoneration from his official report.<ref name="casinobeats" /> He is seeking compensatory, special, and punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> Discovery in the case has been extended to July 2026, with motions due by August 2026.<ref name="unicourt-killinger">{{Cite web |title=Killinger vs Jager – Case Details |url=https://unicourt.com/case/pc-db5-casegucf509a42dd1e-2175767 |access-date=2026-03-02 |website=UniCourt}}</ref>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" /> The case illustrates that when officers prioritize algorithmic identification over physical evidence and valid documentation, innocent individuals can be subjected to unjust detention.

===Common ALPR Error Mechanisms===

These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists.
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (such as matching car plates to motorcycle registrations).
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles and criminal activity.
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners.

==LAW ENFORCEMENT MISUSE AND STALKING INCIDENTS==

Documented cases show that law enforcement officers have misused ALPR systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, and the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department's Flock ALPR system to track his ex-girlfriend. According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner's vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper and attributed them to "desperation and bad judgment." He was placed on administrative leave, barred from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings. A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |last=Kerhin |first=Brian |date=2026-01-09 |title=Menasha police officer accused of using license plate recognition system to track his ex |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-url=https://web.archive.org/web/20260110000858/https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-date=2026-01-10 |access-date=2026-01-11 |work=FOX 11 News}}</ref>

The Menasha case is one in what has become a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes and stalking after using Flock cameras to monitor his estranged wife's movements over several months.<ref>{{cite news |last=Baker |first=Joe |date=2022-10-31 |title=Kechi police lieutenant arrested for using police technology to stalk wife |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-url=https://web.archive.org/web/20221031042853/https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-date=2022-10-31 |work=KWCH}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2025 to using Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |last=Stavola |first=Michael |date=2024-08-17 |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-url=https://web.archive.org/web/20240817105006/https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-date=2024-08-17 |work=Yahoo News}}</ref>

Comparable misuse has been documented involving other police databases and surveillance systems. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing law enforcement databases to stalk a woman he met off duty.<ref>{{cite news |last=McCandless |first=C.C. |date=2024-02-16 |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-url=https://web.archive.org/web/20240216010507/https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-date=2024-02-16 |work=FOX5 Vegas}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |last=Tucker |first=Eric |date=2016-09-27 |title=When cops abuse confidential databases |url=https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-url=https://web.archive.org/web/20230721171815/https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-date=2023-07-21 |work=Associated Press}}</ref>

Auditors and civil liberties organizations note that ALPR systems reduce the cost and effort of stalking by allowing quick searches of historical location data across large geographic areas without real-time supervisory approval. While vendors and agencies rely on access logs and written policies, many cases have demonstrated that these safeguards often fail to prevent or detect misuse quickly enough.<ref>{{cite web |date=2023-02-22 |title=Automated License Plate Readers widely used, subject to abuse |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-url=https://web.archive.org/web/20230617100257/https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-date=2023-06-17 |work=University of Michigan}}</ref><ref>{{cite web |last=Davidson |first=Nikki |date=2024-04-16 |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-url=https://web.archive.org/web/20240417005310/https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-date=2024-04-17 |work=Government Technology}}</ref>

The Virginia State Crime Commission's 2025 survey found that despite statutory restrictions on sharing, 20 Virginia law enforcement agencies were still providing continuous access to out-of-state agencies and 9 were providing continuous access to federal agencies. Town police departments and primary sheriff's offices accounted for the majority of non-compliant sharing.<ref name="vscc-2026" />

==See also==

*[[Flock license plate readers]]
*[[Flock Safety]]

==References==
{{reflist}}

[[Category:Flock Safety]]
[[Category:ALPR]]
[[Category:Surveillance]]
[[Category:AI and automation]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-03-02T23:14:25Z

Louis: virginia survey report

{{Alert|message = This is a special page dedicated to a specific issue. It will be deleted once moved elsewhere, and is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city — but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.|thumb|Here, a prominent tech YouTuber claims that the 1st Amendment means no privacy in public spaces.]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[wikipedia:Fourth_Amendment_to_the_United_States_Constitution|Fourth Amendment]] jurisprudence and misunderstands the legal standard of "reasonable expectation of privacy" established by the [[wikipedia:Supreme_Court_of_the_United_States|Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches and seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy." This considers the nature, scope, and how intrusive the government monitoring is.

In [[wikipedia:Carpenter_v._United_States|''Carpenter v. United States'' ''(2018)'']], the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[wikipedia:John_Roberts|John Roberts]] wrote that the government's access to 127 days of cell-site location data — tracking movements on public roads — achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |archive-url=https://web.archive.org/web/20180623061246/https://www.law.cornell.edu/supremecourt/text/16-402 |archive-date=2018-06-23 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> The Court said,<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation and Comprehensive Surveillance===

Courts separate isolated instances of police observation and large-scale automated tracking systems. In ''[[wikipedia:United_States_v._Jones_(2012)|United States v. Jones (2012)]]'', Justice [[wikipedia:Sonia_Sotomayor|Sonia Sotomayor's]] influential concurrence explained that [[GPS tracking]]:<blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, and sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-url=https://web.archive.org/web/20120126022816/https://www.law.cornell.edu/supremecourt/text/10-1259 |archive-date=2012-01-26 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref></blockquote>She noted that automated surveillance:<blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources and community hostility."<ref name=":1" />''</blockquote>The [[wikipedia:Massachusetts_Supreme_Judicial_Court|Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy (2020)'', holding:<blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |date=2020-04-16 |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-url=https://web.archive.org/web/20220303203404/https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |archive-date=2022-03-03 |access-date=2025-12-16 |website=Justia}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The [[wikipedia:Mosaic_theory_of_the_Fourth_Amendment|"mosaic theory" of Fourth Amendment protection]] holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[wikipedia:Samuel_Alito|Samuel Alito]] noted in his ''Jones'' concurrence that:<blockquote>''"society's expectation has been that law enforcement agents and others would not; and indeed, in the main, simply could not; secretly monitor and catalogue every single movement of an individual's car for a very long period."<ref name=":1" />''</blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In [[wikipedia:United_States_v._Knotts|''United States v. Knotts (1983)'']], while holding that limited beeper (a radio-emitting surveillance device) tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "[[wikipedia:Dragnet_(policing)|dragnet-type law enforcement practices]]."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |url-status=live |archive-url=https://web.archive.org/web/20120601022257/https://www.law.cornell.edu/supremecourt/text/460/276 |archive-date=2012-06-01 |access-date=2025-12-16 |website=Legal Information Institute |publisher=Cornell Law School}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk (E.D. Va.)'', privacy advocates Lee Schmidt and Crystal Arrington challenged Norfolk's 176-camera Flock Safety ALPR network as unconstitutional. Chief Judge [[wikipedia:Mark_Steven_Davis|Mark S. Davis]] initially denied a motion to dismiss the case in February 2025, finding that plaintiffs had stated a plausible Fourth Amendment claim. During discovery, it emerged that Schmidt's vehicle had been photographed 475 times and Arrington's 325 times over a four-month period in 2025.<ref name="nbc-norfolk">{{cite news |last=Collier |first=Kevin |date=2025-09-18 |title=Police cameras tracked one driver 526 times in four months, lawsuit says |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |url-status=live |archive-url=https://web.archive.org/web/20250918093450/https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |archive-date=2025-09-18 |access-date=2025-12-16 |work=NBC News}}</ref>

However, on January 27, 2026, Judge Davis granted summary judgment in favor of the City, ruling that Norfolk's ALPR system did not violate the Fourth Amendment. In a 51-page opinion, Davis concluded that the plaintiffs could not demonstrate that the system was capable of tracking the entirety of a person's movements. The court found that although the cameras captured snapshots of daily life, they did not continuously track individuals or capture sufficient data to reconstruct whole routines, noting "sizable gaps" between photographs.<ref name="whro-norfolk">{{cite news |last=Cox |first=Toby |date=2026-02-11 |title=A federal judge ruled Norfolk's Flock surveillance cameras don't invade people's privacy – yet |url=https://www.whro.org/business-growth/2026-02-11/a-federal-judge-ruled-norfolks-flock-surveillance-cameras-dont-invade-peoples-privacy-yet |access-date=2026-03-02 |work=WHRO}}</ref><ref name="courthouse-norfolk">{{cite news |date=2026-01-28 |title=Judge holds Norfolk's license plate reader use constitutional |url=https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/ |access-date=2026-03-02 |work=Courthouse News Service}}</ref>

Notably, Judge Davis cautioned that the constitutional analysis could change as ALPR technology expands. He wrote that ''"ALPR surveillance could become too intrusive and run afoul of [constitutional privacy standards] at some point,"'' but concluded that ''"at least in Norfolk, Virginia, the answer is: not today."''<ref name="whro-norfolk" /> The plaintiffs, represented by the Institute for Justice, announced their intention to appeal, with Schmidt stating he remained committed to fighting against what he described as "dragnet warrantless surveillance."<ref name="whro-norfolk" /><ref name="courthouse-norfolk" />

Flock Safety's chief legal officer responded that the decision aligned with rulings by over 30 state and federal courts concluding that fixed-location ALPRs do not constitute a search under the Fourth Amendment.<ref name="courthouse-norfolk" />

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 and 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |last=Maass |first=Dave |last2=Lipton |first2=Beryl |date=2021-04-22 |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-url=https://web.archive.org/web/20181115183012/https://www.eff.org/pages/automated-license-plate-reader-dataset |archive-date=2018-11-15 |access-date=2025-12-16 |website=Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale and the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale and comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[wikipedia:Stalking|stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, and sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge and Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016 |url=https://scholarlycommons.law.northwestern.edu/nulr/vol111/iss1/4/}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly;<ref>{{cite news |last=Kenney |first=Andrew |date=2024-09-19 |title=2 million license plates scanned monthly by Denver's new police cameras |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-url=https://web.archive.org/web/20240919214639/https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |archive-date=2024-09-19 |access-date=2025-12-16 |work=Denverite}}</ref> Norfolk's 176 cameras provide citywide coverage;<ref name="nbc-norfolk" /> and Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |last=Thompson |first=Ben |date=2025-05-20 |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |url-status=live |archive-url=https://web.archive.org/web/20250607131518/https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |archive-date=2025-06-07 |access-date=2025-12-16 |work=Community Impact}}</ref>

==STATE LEGISLATIVE RESPONSES: VIRGINIA AS A CASE STUDY==

Virginia became one of the first states to enact comprehensive statewide ALPR regulation when legislation establishing statewide standards for law enforcement use of ALPR took effect on July 1, 2025. Prior to this date, Virginia had no statewide statutory or regulatory framework governing law enforcement use of ALPR, meaning agencies could operate the technology without any statewide limitations on use, data retention, or data sharing.<ref name="vscc-2026">{{cite web |title=Law Enforcement Use of Automatic License Plate Recognition (ALPR) Update, January 2026 |url=https://vscc.virginia.gov/2026/VSCC%20ALPR%20Report%20January%202026%20FINAL%20REVISED%20Jan%2021%202026.pdf |access-date=2026-03-02 |publisher=Virginia State Crime Commission |date=2026-01}}</ref>

===Overview of Virginia's 2025 ALPR Law===

Under the new statute (Virginia House Bill 2724, codified at Va. Code Ann. § 2.2-5517), law enforcement agencies in Virginia may only use ALPR for criminal investigations, active investigations into missing or endangered persons or human trafficking, and notifications related to missing or endangered persons, outstanding warrants, human trafficking, stolen vehicles, or stolen license plates.<ref name="vscc-2026" />

The law requires ALPR data to be purged after 21 days unless needed for an ongoing investigation, prosecution, or civil action. It also restricts data sharing to other Virginia law enforcement agencies, Commonwealth's Attorneys, criminal defendants or their counsel, ALPR vendors, or pursuant to a court order. The statute does not permit data sharing with out-of-state or federal law enforcement agencies.<ref name="vscc-2026" />

===Compliance Findings from the Virginia State Crime Commission===

In January 2026, the Virginia State Crime Commission published the findings of a statewide survey of all 361 Virginia law enforcement agencies on their use of ALPR. The survey, conducted in November 2025 to capture practices after the new legislation took effect, received responses from 251 agencies (70%). Of responding agencies, 63% (159 of 251) reported using ALPR. A large majority — 86% (137 of 159) — reported [[Flock Safety]] as their ALPR vendor.<ref name="vscc-2026" />

The Crime Commission found that some agencies were not complying with the new statutory requirements:

*'''Data retention violations''': 21% (33 of 159) of agencies using ALPR reported retaining data beyond the statutory 21-day limit. Reported retention periods for fixed cameras ranged from 22 to 60 days; for mobile cameras, 30 to 180 days.<ref name="vscc-2026" />

*'''Unauthorized data sharing with federal and out-of-state agencies''': Despite the statute prohibiting such sharing, 13% (20 of 159) of agencies reported providing continuous access to out-of-state law enforcement agencies, and 6% (9 of 159) reported providing continuous access to federal law enforcement agencies.<ref name="vscc-2026" />

*'''No written ALPR policy''': 16% (26 of 159) of agencies using ALPR reported having no policy on ALPR use, despite the statutory requirement to maintain one. An additional 9% (14 of 159) reported being in the process of implementing a policy.<ref name="vscc-2026" />

*'''No public awareness measures''': 35% (55 of 159) of agencies reported taking no public awareness measures regarding their ALPR use, despite statutory requirements to promote public awareness.<ref name="vscc-2026" />

*'''Non-response''': Almost one-third of law enforcement agencies (110 of 361) did not respond to the survey at all, meaning their ALPR use and compliance status remain unknown.<ref name="vscc-2026" />

The Crime Commission's report stated that the Chair, Delegate Charniele Herring, planned to send letters to agencies whose survey responses indicated non-compliance with the new law, as well as to non-responding agencies.<ref name="vscc-2026" />

===Broader Context: Data Sharing Concerns===

Virginia's experience reflects a national pattern of concerns over ALPR data sharing. A September 2025 investigation by the Virginia Center for Investigative Journalism found that before the new law took effect, federal agencies had attempted to access local Virginia ALPR data thousands of times for immigration enforcement purposes, and one small town's Flock network data had been searched nearly 7 million times by outside agencies in a single year.<ref name="vcij-sept2025">{{cite news |last=Falayi |first=K. |date=2025-09-16 |title=One sleepy Virginia town. Nearly 7 million hits on its surveillance network |url=https://vcij.org/stories/state-of-surveillance |access-date=2026-03-02 |work=Virginia Center for Investigative Journalism}}</ref> At least two Virginia localities — Charlottesville and Staunton — subsequently ended their use of Flock Safety cameras, citing concerns about federal data sharing.<ref name="vscc-2026" />

As of early 2026, at least 30 localities across the United States have either deactivated Flock cameras or canceled their contracts, driven in part by concerns over privacy and federal agency access to locally collected ALPR data.<ref name="npr-flock">{{cite news |date=2026-02-17 |title=Why some cities are canceling Flock license plate reader contracts |url=https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns |access-date=2026-03-02 |work=NPR}}</ref>

==FALSE POSITIVES AND SYSTEM FAILURES==

Automated surveillance systems carry significant risks of false positives, where innocent individuals are subjected to armed police responses based on system errors. These incidents create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' and I was like, 'What?'"<ref name=":3" />''</blockquote>

Allen was forced to his knees, handcuffed, and searched before officers realized he was unarmed. Allen described watching about eight police cars arrive, with officers pointing guns at him.

<blockquote>''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me."''<ref name=":3" /></blockquote>

When shown the image that triggered the alert, Allen explained:<blockquote>''"I was just holding a Doritos bag – it was two hands and one finger out, and they said it looked like a gun."<ref name=":3" />''</blockquote>

High schools in Baltimore County used the AI gun detection system beginning in 2024, using existing school cameras to scan for potential weapons. The system is operated by [[Omnilert]], which taps into existing camera feeds to detect objects that resemble weapons and then alerts both school safety officers and law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name=":3" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name=":3" /> Omnilert defended its system, claiming it ''"functioned as intended: to prioritize safety and awareness through rapid human verification,"'' though the incident demonstrated the system escalated to armed police response before adequate human review occurred.<ref name=":3">{{cite news |last=Tsui |first=Karina |last2=Sottile |first2=Zoe |date=2025-10-25 |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |url=https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |url-status=live |archive-url=https://web.archive.org/web/20251026050806/https://edition.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |archive-date=2025-10-26 |access-date=2025-10-28 |work=CNN}}</ref>

===ALPRs Causing Innocent People to be Held at Gunpoint===

ALPR systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====

In 2018, privacy advocate Brian Hofer and his younger brother were driving to visit their parents for Thanksgiving when they were held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1=Lauren |last2=Clark |first2=Alex |date=2025-07-24 |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |url-status=live |archive-url=https://web.archive.org/web/20250724210641/https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |archive-date=2025-07-24 |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government and corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops and ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====

Body camera footage from a documented police incident shows officers pursuing and detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |date=2025-10-06 |title=Police Body Camera: ALPR False Alert Detention-Police Respond To Girl Being Kidnapped (Full Bodycam) |url=https://youtu.be/lmNxitcaT2Y |url-status=live |archive-url=https://preservetube.com/watch?v=lmNxitcaT2Y |archive-date=2026-02-10 |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====

In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. In one incident, a 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7," according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====

In Aurora, Colorado in 2020, a mother and her family, including her 6-year-old daughter, were pulled over at gunpoint and forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state — a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video and widely condemned, led to a $1.9 million settlement from the city in 2024.<ref name="cbs-alpr" />

===Facial Recognition False Identification===

While the preceding cases involve ALPR misreads, similar risks arise with other automated identification systems, including facial recognition technology deployed in commercial settings.

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

On September 17, 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada. Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |last=Roarty |first=Adam |date=2025-12-09 |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-url=https://web.archive.org/web/20251210222601/https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |archive-date=2025-12-10 |access-date=2025-12-16 |website=CasinoBeats}}</ref><ref name="casino-org">{{Cite web |last=Conneller |first=Philip |date=2025-11-11 |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |access-date=2025-12-16 |website=Casino.org |url-status=live |archive-url=https://web.archive.org/web/20260216033051/https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |archive-date=2026-02-16}}</ref> Ellis's ban was set to expire on September 26, 2023 — nine days after the arrest.<ref name="casinobeats" /> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |last=García |first=Jerome |date=2025-12-11 |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-url=https://web.archive.org/web/20251205215015/https://www.gamblingnews.com/news/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |archive-date=2025-12-05 |access-date=2026-01-11 |website=Gambling News}}</ref>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, and his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him and called the police.<ref name="casino-org" />

Released police records and driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:<ref name="casinobeats" />

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||6'1"||5'9"
|-
|Eye Color||Blue||Hazel
|}

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue and hazel eyes are ''"by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit, he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up"'' to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' and that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating:<blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |last=Gwilliam |first=Michael |date=2025-12-15 |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-url=https://web.archive.org/web/20251218224228/https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |archive-date=2025-12-18 |access-date=2025-12-16 |website=Dexerto}}</ref></blockquote>

Jager handcuffed Killinger and transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |date=2025-11-14 |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-url=https://web.archive.org/web/20260110235640/http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |archive-date=2026-01-10 |access-date=2025-12-16 |website=Our Town Reno}}</ref> His federal lawsuit against Officer Jager, ''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD, remains active in the U.S. District Court for the District of Nevada.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |archive-url=http://web.archive.org/web/20260210093102/https://www.leagle.com/decision/infdco20250925d22 |archive-date=2026-02-10 |access-date=2025-12-16 |website=Leagle}}</ref>

In a January 22, 2026 deposition, Officer Jager acknowledged that the arrest ''"never should have happened"'' and stated that post-lawsuit training had clarified that facial recognition technology cannot serve as the sole basis for probable cause, but should instead be treated as ''"an investigative lead only"'' requiring further corroboration.<ref name="casino-org-deposition">{{Cite web |last=Conneller |first=Philip |date=2026-01-28 |title=Reno Cop Concedes Peppermill Facial Recognition Arrest was Wrongful |url=https://www.casino.org/news/reno-cop-concedes-peppermill-facial-recognition-arrest-wrongful/ |access-date=2026-03-02 |website=Casino.org}}</ref> Following the deposition, Killinger's attorney moved to add the City of Reno as a defendant, arguing that Jager's testimony demonstrated systemic failure to train officers on the limitations of AI facial recognition technology.<ref name="casino-org-deposition" />

The lawsuit alleges that Jager's actions violated Killinger's [[wikipedia:Fourteenth_Amendment_to_the_United_States_Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner and omitted the fingerprint exoneration from his official report.<ref name="casinobeats" /> He is seeking compensatory, special, and punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> Discovery in the case has been extended to July 2026, with motions due by August 2026.<ref name="unicourt-killinger">{{Cite web |title=Killinger vs Jager – Case Details |url=https://unicourt.com/case/pc-db5-casegucf509a42dd1e-2175767 |access-date=2026-03-02 |website=UniCourt}}</ref>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" /> The case illustrates that when officers prioritize algorithmic identification over physical evidence and valid documentation, innocent individuals can be subjected to unjust detention.

===Common ALPR Error Mechanisms===

These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists.
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (such as matching car plates to motorcycle registrations).
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles and criminal activity.
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners.

==LAW ENFORCEMENT MISUSE AND STALKING INCIDENTS==

Documented cases show that law enforcement officers have misused ALPR systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, and the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department's Flock ALPR system to track his ex-girlfriend. According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner's vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper and attributed them to "desperation and bad judgment." He was placed on administrative leave, barred from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings. A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |last=Kerhin |first=Brian |date=2026-01-09 |title=Menasha police officer accused of using license plate recognition system to track his ex |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-url=https://web.archive.org/web/20260110000858/https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex-girlfriend-cristian-morales-misconduct-in-office-flock-domestic-abuse-restraining-order-cash-bond |archive-date=2026-01-10 |access-date=2026-01-11 |work=FOX 11 News}}</ref>

The Menasha case is one in what has become a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes and stalking after using Flock cameras to monitor his estranged wife's movements over several months.<ref>{{cite news |last=Baker |first=Joe |date=2022-10-31 |title=Kechi police lieutenant arrested for using police technology to stalk wife |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-url=https://web.archive.org/web/20221031042853/https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/ |archive-date=2022-10-31 |work=KWCH}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2025 to using Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |last=Stavola |first=Michael |date=2024-08-17 |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-url=https://web.archive.org/web/20240817105006/https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html |archive-date=2024-08-17 |work=Yahoo News}}</ref>

Comparable misuse has been documented involving other police databases and surveillance systems. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing law enforcement databases to stalk a woman he met off duty.<ref>{{cite news |last=McCandless |first=C.C. |date=2024-02-16 |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-url=https://web.archive.org/web/20240216010507/https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/ |archive-date=2024-02-16 |work=FOX5 Vegas}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |last=Tucker |first=Eric |date=2016-09-27 |title=When cops abuse confidential databases |url=https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-url=https://web.archive.org/web/20230721171815/https://apnews.com/general-news-699236946e3140659fff8a2362e16f43 |archive-date=2023-07-21 |work=Associated Press}}</ref>

Auditors and civil liberties organizations note that ALPR systems reduce the cost and effort of stalking by allowing quick searches of historical location data across large geographic areas without real-time supervisory approval. While vendors and agencies rely on access logs and written policies, many cases have demonstrated that these safeguards often fail to prevent or detect misuse quickly enough.<ref>{{cite web |date=2023-02-22 |title=Automated License Plate Readers widely used, subject to abuse |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-url=https://web.archive.org/web/20230617100257/https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse |archive-date=2023-06-17 |work=University of Michigan}}</ref><ref>{{cite web |last=Davidson |first=Nikki |date=2024-04-16 |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-url=https://web.archive.org/web/20240417005310/https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |archive-date=2024-04-17 |work=Government Technology}}</ref>

The Virginia State Crime Commission's 2025 survey found that despite statutory restrictions on sharing, 20 Virginia law enforcement agencies were still providing continuous access to out-of-state agencies and 9 were providing continuous access to federal agencies. Town police departments and primary sheriff's offices accounted for the majority of non-compliant sharing.<ref name="vscc-2026" />

==See also==

*[[Flock license plate readers]]
*[[Flock Safety]]

==References==
{{reflist}}

[[Category:Flock Safety]]
[[Category:ALPR]]
[[Category:Surveillance]]
[[Category:AI and automation]]

Oneplus phone update introduces hardware anti-rollback

2026-01-26T02:41:59Z

Louis: citation revisions

{{IncidentCargo
|incident_name = OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident
|date = January 2026
|company = OnePlus, OPPO, BBK Electronics
|industry = Consumer electronics, Smartphones
|category = Firmware restriction, Right to repair
|status = Ongoing
|description = OnePlus firmware update introduces permanent hardware-level anti-rollback mechanism that bricks devices attempting to downgrade
}}{{OngoingEvent}}

The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently preventing users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 13T, and OnePlus 15, blow irreversible electronic fuses in the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

==Background==

OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor. The company's first device, the OnePlus One, shipped with [[wikipedia:CyanogenMod|CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.This partnership positioned OnePlus as a choice for modding enthusiasts.

When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China. In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions.

==Timeline==

On January 18, 2026, users who updated to ColorOS 16.0.3.501 began reporting that their devices could not be reverted to previous versions. One OnePlus 13 owner reported that after flashing ColorOS 15, the phone entered EDL mode and was detected as "Qualcomm HS-USB QDLoader 9008," with the Chimera Rescue Tool unable to find a working programmer.<ref name="hard-brick-report">{{cite web |url=https://xdaforums.com/t/hard-brick-oneplus-13-pjz110.4775945/ |title=Hard Brick Oneplus 13 (PJZ110) |website=XDA Forums |date=January 18, 2026 |access-date=January 22, 2026}}</ref>

On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" />

DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref>

==Affected devices==

The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse:

*OnePlus 13 / 13T: ColorOS 16.0.3.501<ref name="xda-warning" />
*OnePlus 15: ColorOS 16.0.3.503<ref name="xda-warning" />

Android Authority reported that the OPPO Find X8 series is also considered at high risk.<ref name="android-authority" />

The XDA thread advises users to avoid any OTA update ending in .500, .501, or .503 until community verification confirms safety.<ref name="xda-warning" />

==Technical mechanism==

The anti-rollback mechanism uses Qfprom (Qualcomm Fuse Programmable Read-Only Memory), a region on Qualcomm processors containing one-time programmable electronic fuses. These microscopic components are physically altered when "blown"; a controlled voltage pulse permanently changes the fuse's state from "0" to "1." This change cannot be reversed by any software means.<ref name="xda-warning" /> A complete motherboard replacement is the only possible method to remedy it.

DroidWin explained that the implementation works similarly to how Knox gets tripped on Samsung devices: both are e-fuses embedded in the motherboard that become permanently fused upon triggering. Changing the motherboard is the only way to restore the default state.<ref name="droidwin" />

When the device powers on, the Primary Boot Loader (PBL) in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). The PBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" />

EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this protection. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" />

As explained on the XDA thread, the term "Fuse Blown" refers to the Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset being electrically switched from "0" to "1", effectively preventing older software from running, rather than a physical fuse burnout.<ref name="xda-warning" />

==Impact on custom ROMs==

The XDA warning describes the situation as dangerous for custom ROM users. Flashing incompatible firmware on top of ColorOS 16.0.3.501 (or newer) will result in an immediate hard brick. Custom ROMs package firmware components from the stock firmware they were built against. If a user's device has been updated to a fused firmware version & they flash a custom ROM built against older firmware, the anti-rollback mechanism triggers immediately.<ref name="xda-warning" />

The community recommendation is that users who have updated should not flash any custom ROM until developers explicitly announce support for fused devices with the new firmware base.<ref name="xda-warning" />

==Company response==

As of 23 January, 2026, OnePlus and OPPO have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority-opinion">{{cite web |url=https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |title=I've been a OnePlus fan for 12 years, but this latest update is my breaking point |author=Dhruv Bhutani |website=Android Authority |date=January 23, 2026 |access-date=January 26, 2026}}</ref>

The removal of official downgrade packages from OnePlus' community forums on 19 January, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" />

==Comparison with other manufacturers==

Anti-rollback protection exists across the smartphone industry, but implementations vary in their impact on users.

[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. Android Authority noted that the new OnePlus implementation is functionally identical to Samsung's model, where eFuses serve as irreversible warrants of system integrity, punishing modification with permanent hardware states.<ref name="android-authority" />

==See also==

*[[Right to repair]]

*[[Planned obsolescence]]

*[[Bootloader unlocking]]

*[[Custom ROM]]

*[[Samsung Knox]]

==References==

{{reflist}}

[[Category:2026 in technology]]

[[Category:OnePlus]]

[[Category:Right to repair]]

[[Category:Consumer protection]]

[[Category:Smartphone software]]

[[Category:Controversies]]

Oneplus phone update introduces hardware anti-rollback

2026-01-23T19:43:16Z

Louis:

{{IncidentCargo
|incident_name = OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident
|date = January 2026
|company = OnePlus, OPPO, BBK Electronics
|industry = Consumer electronics, Smartphones
|category = Firmware restriction, Right to repair
|status = Ongoing
|description = OnePlus firmware update introduces permanent hardware-level anti-rollback mechanism that bricks devices attempting to downgrade
}}

The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently preventing users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 15, & OnePlus Ace 5 series, blow irreversible electronic fuses in the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

==Background==

OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor.<ref name="wikipedia-oneplus">{{cite web |url=https://en.wikipedia.org/wiki/OnePlus |title=OnePlus |website=Wikipedia |access-date=January 22, 2026}}</ref> The company's first device, the OnePlus One, shipped with [[CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.<ref name="wikipedia-oneplus-one">{{cite web |url=https://en.wikipedia.org/wiki/OnePlus_One |title=OnePlus One |website=Wikipedia |access-date=January 22, 2026}}</ref> This partnership positioned OnePlus as a choice for modding enthusiasts.

When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China.<ref name="wikipedia-oneplus" />

In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions.<ref name="wikipedia-oneplus" />

==Timeline==

On January 18, 2026, users who updated to ColorOS 16.0.3.501 began reporting that their devices could not be reverted to previous versions. One OnePlus 13 owner reported that after flashing ColorOS 15, the phone entered EDL mode and was detected as "Qualcomm HS-USB QDLoader 9008," with the Chimera Rescue Tool unable to find a working programmer.<ref name="hard-brick-report">{{cite web |url=https://xdaforums.com/t/hard-brick-oneplus-13-pjz110.4775945/ |title=Hard Brick Oneplus 13 (PJZ110) |website=XDA Forums |date=January 18, 2026 |access-date=January 22, 2026}}</ref>

On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" />

DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref>

==Affected devices==

The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse:

*OnePlus 13 / 13T: ColorOS 16.0.3.501
*OnePlus 15: ColorOS 16.0.3.503
*OnePlus Ace 5 / Ace 5 Pro: ColorOS 16.0.3.500<ref name="xda-warning" />

Android Authority reported that the OPPO Find X8 series is considered at high risk, while the OnePlus 11 and OnePlus 12 could be next in line to receive similar updates.<ref name="android-authority" />

Devices running firmware version 16.0.2.402 or lower remain unaffected. The XDA thread advises users to avoid any OTA update ending in .500, .501, or .503 until community verification confirms safety.<ref name="xda-warning" />

==Technical mechanism==

The anti-rollback mechanism uses Qfprom (Qualcomm Fuse Programmable Read-Only Memory), a region on Qualcomm processors containing one-time programmable electronic fuses. These microscopic components are physically altered when "blown"; a controlled voltage pulse permanently changes the fuse's state from "0" to "1." This change cannot be reversed by any software means.<ref name="xda-warning" />

DroidWin explained that the implementation works similarly to how Knox gets tripped on Samsung devices upon unlocking the bootloader: both are e-fuses embedded in the motherboard that become permanently fused upon triggering. Changing the motherboard is the only way to restore the default state.<ref name="droidwin" />

When the device powers on, the Primary Boot Loader in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). XBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" />

EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this protection. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" />

As explained on the XDA thread: "When we say 'Fuse Blown,' we are referring to Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset. It is not a physical fuse like in a household plug, so there is no smoke, no burning smell, and no heat. It is a microscopic logic gate that is electrically switched from '0' to '1'. Once it is switched, it effectively 'burns the bridge' to allow older software to run."<ref name="xda-warning" />

==Impact on custom ROMs==

The XDA warning describes the situation as dangerous for custom ROM users: <blockquote>''"Flashing ANY custom ROM developed prior to this update on top of ColorOS 16.0.3.501 (or newer) will result in an immediate HARD BRICK."<ref name="xda-warning" />''</blockquote>Custom ROMs package firmware components from the stock firmware they were built against. If a user's device has been updated to a fused firmware version & they flash a custom ROM built against older firmware, the anti-rollback mechanism triggers immediately. The XDA thread states:<blockquote>''"Almost ALL current Custom ROMs for OnePlus 13 / Ace 5 were built BEFORE this fuse policy was known. They are adapted for the 'Old' (Unfused) firmware environment."<ref name="xda-warning" />''</blockquote>AdaUnlocked characterized the impact on the development community as severe, noting that work on Custom ROMs, Ports, and GSIs would be rendered useless for fused devices.<ref name="xda-warning" />

The community recommendation is that users who have updated should not flash any custom ROM until developers explicitly announce support for fused devices with the new firmware base.<ref name="xda-warning" />

==Company response==

As of January 22, 2026, OnePlus, OPPO, and BBK Electronics have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority" />

The removal of official downgrade packages from OnePlus's community forums on January 19, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" />

==Comparison with other manufacturers==

Anti-rollback protection exists across the smartphone industry, but implementations vary in their impact on users.

[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. However, Android Authority noted that Samsung's implementation is not as stringent as OnePlus's; Samsung blocks the bootloader-unlocking process but usually does not hard-brick the phone if users attempt unauthorized modifications.<ref name="android-authority" />

DroidWin noted the irony of OnePlus's approach: <blockquote>''"EDL flashing is hardly used by 1-2% of its userbase, so rolling out a change to stop those niche segments of users from carrying out their tweaks, which would end up impacting the majority of its users, doesn't really add up."<ref name="droidwin" />''</blockquote>

==See also==
*[[Right to repair]]
*[[Planned obsolescence]]
*[[Bootloader unlocking]]
*[[Custom ROM]]
*[[Samsung Knox]]

==References==
{{reflist}}

[[Category:2026 in technology]]
[[Category:OnePlus]]
[[Category:Right to repair]]
[[Category:Consumer protection]]
[[Category:Smartphone software]]
[[Category:Controversies]]

Oneplus phone update introduces hardware anti-rollback

2026-01-22T22:23:15Z

Louis:

{{IncidentCargo
|incident_name = OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident
|date = January 2026
|company = OnePlus, OPPO, BBK Electronics
|industry = Consumer electronics, Smartphones
|category = Firmware restriction, Right to repair
|status = Ongoing
|description = OnePlus firmware update introduces permanent hardware-level anti-rollback mechanism that bricks devices attempting to downgrade
}}

The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently preventing users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 15, & OnePlus Ace 5 series, blow irreversible electronic fuses in the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" that cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

==Timeline==

On January 18, 2026, users who updated to ColorOS 16.0.3.501 began reporting that their devices could not be reverted to previous versions. One OnePlus 13 owner reported that after flashing ColorOS 15, the phone entered EDL mode and was detected as "Qualcomm HS-USB QDLoader 9008," with the Chimera Rescue Tool unable to find a working programmer.<ref name="hard-brick-report">{{cite web |url=https://xdaforums.com/t/hard-brick-oneplus-13-pjz110.4775945/ |title=Hard Brick Oneplus 13 (PJZ110) |website=XDA Forums |date=January 18, 2026 |access-date=January 22, 2026}}</ref>

On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" />

DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref>

==Affected devices==

The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse:

*OnePlus 13 / 13T: ColorOS 16.0.3.501
*OnePlus 15: ColorOS 16.0.3.503
*OnePlus Ace 5 / Ace 5 Pro: ColorOS 16.0.3.500<ref name="xda-warning" />

Android Authority reported that the OPPO Find X8 series is considered at high risk, while the OnePlus 11 and OnePlus 12 could be next in line to receive similar updates.<ref name="android-authority" />

Devices running firmware version 16.0.2.402 or lower remain unaffected. The XDA thread advises users to avoid any OTA update ending in .500, .501, or .503 until community verification confirms safety.<ref name="xda-warning" />

==Technical mechanism==

The anti-rollback mechanism uses Qfprom (Qualcomm Fuse Programmable Read-Only Memory), a region on Qualcomm processors containing one-time programmable electronic fuses. These microscopic components are physically altered when "blown"; a controlled voltage pulse permanently changes the fuse's state from "0" to "1." This change cannot be reversed by any software means.<ref name="xda-warning" />

DroidWin explained that the implementation works similarly to how Knox gets tripped on Samsung devices upon unlocking the bootloader: both are e-fuses embedded in the motherboard that become permanently fused upon triggering. Changing the motherboard is the only way to restore the default state.<ref name="droidwin" />

When the device powers on, the Primary Boot Loader in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). XBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" />

EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this protection. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" />

As explained on the XDA thread: "When we say 'Fuse Blown,' we are referring to Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset. It is not a physical fuse like in a household plug, so there is no smoke, no burning smell, and no heat. It is a microscopic logic gate that is electrically switched from '0' to '1'. Once it is switched, it effectively 'burns the bridge' to allow older software to run."<ref name="xda-warning" />

==Impact on custom ROMs==

The XDA warning describes the situation as dangerous for custom ROM users: <blockquote>''"Flashing ANY custom ROM developed prior to this update on top of ColorOS 16.0.3.501 (or newer) will result in an immediate HARD BRICK."<ref name="xda-warning" />''</blockquote>Custom ROMs package firmware components from the stock firmware they were built against. If a user's device has been updated to a fused firmware version & they flash a custom ROM built against older firmware, the anti-rollback mechanism triggers immediately. The XDA thread states:<blockquote>''"Almost ALL current Custom ROMs for OnePlus 13 / Ace 5 were built BEFORE this fuse policy was known. They are adapted for the 'Old' (Unfused) firmware environment."<ref name="xda-warning" />''</blockquote>AdaUnlocked characterized the impact on the development community as severe, noting that work on Custom ROMs, Ports, and GSIs would be rendered useless for fused devices.<ref name="xda-warning" />

The community recommendation is that users who have updated should not flash any custom ROM until developers explicitly announce support for fused devices with the new firmware base.<ref name="xda-warning" />

==Company response==

As of January 22, 2026, OnePlus, OPPO, and BBK Electronics have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority" />

The removal of official downgrade packages from OnePlus's community forums on January 19, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" />

==Comparison with other manufacturers==

Anti-rollback protection exists across the smartphone industry, but implementations vary in their impact on users.

[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. However, Android Authority noted that Samsung's implementation is not as stringent as OnePlus's; Samsung blocks the bootloader-unlocking process but usually does not hard-brick the phone if users attempt unauthorized modifications.<ref name="android-authority" />

DroidWin noted the irony of OnePlus's approach: <blockquote>''"EDL flashing is hardly used by 1-2% of its userbase, so rolling out a change to stop those niche segments of users from carrying out their tweaks, which would end up impacting the majority of its users, doesn't really add up."<ref name="droidwin" />''</blockquote>

==Background==

OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor.<ref name="wikipedia-oneplus">{{cite web |url=https://en.wikipedia.org/wiki/OnePlus |title=OnePlus |website=Wikipedia |access-date=January 22, 2026}}</ref> The company's first device, the OnePlus One, shipped with [[CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.<ref name="wikipedia-oneplus-one">{{cite web |url=https://en.wikipedia.org/wiki/OnePlus_One |title=OnePlus One |website=Wikipedia |access-date=January 22, 2026}}</ref> This partnership positioned OnePlus as a choice for modding enthusiasts.

When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China.<ref name="wikipedia-oneplus" />

In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions.<ref name="wikipedia-oneplus" />

==See also==
*[[Right to repair]]
*[[Planned obsolescence]]
*[[Bootloader unlocking]]
*[[Custom ROM]]
*[[Samsung Knox]]

==References==
{{reflist}}

[[Category:2026 in technology]]
[[Category:OnePlus]]
[[Category:Right to repair]]
[[Category:Consumer protection]]
[[Category:Smartphone software]]
[[Category:Controversies]]

Oneplus phone update introduces hardware anti-rollback

2026-01-22T14:12:13Z

Louis: Created page with "{{IncidentCargo |Company=OnePlus |Status=Active |Product=phone, smartphone |Type=Firmware lockout |Description=oneplus phone update introduces hardware anti-rollback }} {{Ph-I-Int}} ==Background== {{Ph-I-B}} ==[Incident]== {{Ph-I-I}} ===[Company]'s response=== {{Ph-I-ComR}} ==Lawsuit== {{Ph-I-L}} ==Consumer response== {{Ph-I-ConR}} ==References== {{reflist}} {{Ph-I-C}}"

{{IncidentCargo
|Company=OnePlus
|Status=Active
|Product=phone, smartphone
|Type=Firmware lockout
|Description=oneplus phone update introduces hardware anti-rollback
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Washington house bill 2321 regarding 3d printers

2026-01-22T10:31:03Z

Louis:

{{IncidentCargo
|ProductLine=3D printers
|Product=3D printers
|Description=Washington State bill mandating firearm detection algorithms in 3D printers; first law of its kind, with Class C felony penalties.
}}
'''Washington House Bill 2321''' is proposed legislation in the U.S. state of Washington that requires all 3D printers sold in the state to include firearm-blocking technology. Prefiled on January 8, 2026, and referred to the House Civil Rights & Judiciary Committee on January 12, the bill would impose Class C felony penalties of up to five years imprisonment and $15,000 in fines for corporations that sell non-compliant printers after July 1, 2027.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref><ref name="billtext">{{cite web |url=https://lawfilesext.leg.wa.gov/biennium/2025-26/Pdf/Bills/House%20Bills/2321.pdf |title=House Bill 2321 |website=Washington State Legislature |date=2026-01-08 |access-date=2026-01-21}}</ref>

The bill is sponsored by Democratic state representatives.<ref name="billtext" /> No hearings have been scheduled as of January 21, 2026, and no amendments have been filed.

==Background==

===Federal regulation of ghost guns===
The U.S. Bureau of Alcohol, Tobacco, Firearms and Explosives issued a rule in 2022 clarifying that weapon parts kits and unfinished frames fall under the definition of "firearm" in the Gun Control Act of 1968. This rule required ghost gun kits to carry serial numbers and be sold through licensed dealers with background checks.<ref>{{cite web |url=https://www.scotusblog.com/2025/03/supreme-court-upholds-regulation-of-ghost-guns/ |title=Supreme Court upholds regulation on "ghost guns" |website=SCOTUSblog |date=2025-03-26 |access-date=2026-01-21}}</ref>

On March 26, 2025, the Supreme Court upheld this rule in ''Bondi v. VanDerStok'' by a 7-2 vote. Justice Neil Gorsuch, writing for the majority, affirmed that weapon parts kits and partially complete frames that are "readily convertible" into functional weapons fall under the Gun Control Act's purview. The majority reasoned that just as a disassembled table is still a table, a kit containing all necessary parts to assemble a firearm—such as Polymer80's "Buy Build Shoot" kit—is effectively a firearm.<ref>{{cite web |url=https://www.supremecourt.gov/opinions/24pdf/23-852_o7jp.pdf |title=Bondi v. VanDerStok |website=Supreme Court of the United States |date=2025-03-26 |access-date=2026-01-21}}</ref> The ruling was a statutory interpretation challenge under the Administrative Procedure Act; it did not address Second Amendment claims regarding home firearm manufacture.<ref name="regreview">{{cite web |url=https://www.theregreview.org/2025/07/23/willinger-vanderstok-and-the-ghosts-of-gun-deregulation/ |title=VanDerStok and the Ghosts of Gun Deregulation |website=The Regulatory Review |date=2025-07-23 |access-date=2026-01-21}}</ref>

===Open-source 3D printer firmware===
The consumer 3D printer market relies on open-source firmware. Marlin firmware, created in 2011, states on its homepage that it ''"drives most of the world's 3D printers."'' It is used by manufacturers including Ultimaker, Prusa Research, and Creality.<ref>{{cite web |url=https://marlinfw.org/ |title=Home |website=Marlin Firmware |access-date=2026-01-21}}</ref> Klipper firmware, developed in 2016, has rapidly gained popularity among prosumer FDM 3D printer users.<ref>{{cite web |url=https://www.xometry.com/resources/3d-printing/klipper-vs-marlin/ |title=Klipper vs. Marlin - 3D Printer Firmware Comparison |website=Xometry |date=2025-06-12 |access-date=2026-01-21}}</ref>

Both Marlin and Klipper are published under the GNU General Public License. The GPL requires that users be provided with source code upon request and permits unlimited modification and redistribution.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref> This licensing structure permits users to compile and flash custom firmware versions without restrictions, which places them in direct conflict with the text of the bill.

==Provisions of the bill==

===Blocking technology requirements===
HB 2321 would require 3D printers sold in Washington after July 1, 2027 to be equipped with ''"blocking features"'' defined as ''"a software controls process that deploys a firearms blueprint detection algorithm."'' According to the bill text, these features must ''"identify and reject print requests for firearms or illegal firearm parts with a high degree of reliability and cannot be overridden or otherwise defeated by a user with significant technical skill."''<ref name="billtext" />

The bill defines ''"firearms blueprint detection algorithm"'' as a system that evaluates STL files, CAD files, or G-code to determine whether they match firearm designs.<ref name="billtext" /> Manufacturers may comply through three methods specified in Section 6(2) of the bill: integration of the algorithm in the printer's firmware, integration in preprint software, or a handshake authentication design between software and printer.<ref name="billtext" />

===Scope of covered equipment===
The bill defines ''"three-dimensional printer"'' to include devices capable of both additive manufacturing and subtractive manufacturing from a digital file. This broad definition has been interpreted by commentators to potentially include CNC mills, lathes, laser cutters, and water jet cutters.<ref name="billtext" /><ref>{{cite web |url=https://www.ibtimes.co.uk/5-years-prison-download-washingtons-brutal-new-crackdown-3d-printed-guns-1772280 |title=The State of Washington Joins Other States Imposing a Ban or Restrictions Against 3D Printed Firearms |website=International Business Times |date=2026-01-20 |access-date=2026-01-21}}</ref>

===Attorney General authority===
Section 3(3) grants the Washington Attorney General authority to ''"adopt rules and regulations for any other processes the attorney general deems necessary to carry out the provisions of this chapter."''<ref name="billtext" /> Section 8 requires the Attorney General to create and maintain a database of firearms blueprint files by August 1, 2026, and to update this database at least once per year. Section 7(4) authorizes the Attorney General to adopt rules ''"requiring developers and users of such algorithms to update such algorithms if new technology is found to be substantially more effective."''<ref name="billtext" />

===Penalties and exemptions===
Violations by corporations constitute a Class C felony with penalties of up to five years imprisonment and $15,000 in fines. Violations by individuals are classified as misdemeanors or gross misdemeanors depending on severity. Filing a false attestation constitutes perjury. Violations are also treated as unfair or deceptive acts under Washington's Consumer Protection Act.<ref name="billtext" />

The bill exempts 3D printers sold to entities holding federal firearms manufacturing licenses.<ref name="billtext" />

==Similar proposals==

===New York===
Governor Kathy Hochul announced comparable proposals on January 7, 2026, as part of her 2026 State of the State agenda. Her proposals would require manufacturers to include blocking software on 3D printers sold in New York, criminalize unlicensed possession or distribution of firearm CAD files, and mandate reporting of recovered 3D-printed guns to state police databases.<ref>{{cite web |url=https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-announces-nation-leading-proposals-crack-down-3d |title=Keeping New Yorkers Safe: Governor Hochul Announces Nation-Leading Proposals to Crack Down on 3D-Printed Guns and Other Illegal Firearms |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref>

Hochul stated: <blockquote>"We will require all 3D printers sold in the State of New York to include software that blocks the production of guns and their components. You cannot sell one of those in the State of New York when we pass these laws."<ref>{{cite web |url=https://www.governor.ny.gov/news/b-roll-video-audio-photos-rush-transcript-keeping-new-yorkers-safe-governor-hochul-announces |title=B-Roll, Video, Audio, Photos & Rush Transcript |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref></blockquote>

Governor Hochul has termed the proliferation of homemade weapons the "Plastic Pipeline."

==Manhattan DA's pressure campaign==
Manhattan District Attorney Alvin Bragg has sent letters to multiple 3D printer manufacturers requesting voluntary adoption of blocking software.

On March 26, 2025, Bragg sent a letter to Shenzhen Creality 3D Technology Co., Ltd. demanding installation of detection software, removal of CAD files from Creality Cloud, and a user agreement ban on weapon creation. The letter explicitly cited the assassination of UnitedHealthcare CEO Brian Thompson by Luigi Mangione, who utilized a 3D-printed ghost gun, as well as local cases involving defendants using Creality printers (specifically the Ender 3 series) to manufacture arsenals.<ref>{{cite web |url=https://manhattanda.org/d-a-bragg-calls-on-3d-printing-companies-to-address-proliferation-of-illegal-firearms/ |title=D.A. Bragg Calls On 3D-Printing Companies To Address Proliferation Of Illegal Firearms |website=Manhattan District Attorney's Office |date=2025-03-27 |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://manhattanda.org/wp-content/uploads/2025/03/Letter-Creality-3.26.25.pdf |title=Letter to Creality |website=Manhattan District Attorney's Office |date=2025-03-26 |access-date=2026-01-21}}</ref> Bragg's letter specifically recommended a program called "3D GUN'T" developed by Print&GO as an example of existing detection technology.

Bragg sent a similar letter to Bambu Lab in 2025. Reports indicate that some digital design firms have agreed to block content in response to these letters.

==Technical feasibility questions==

=== False Positives ===
No commercially validated firearm detection technology exists for 3D printers as of January 2026. 3DPrinterOS announced a partnership with Montclair State University's MIX Lab in November 2024 to develop an algorithm capable of identifying 3D printed firearm components based on unique design signatures.<ref>{{cite web |url=https://www.3printr.com/3dprinteros-and-montclair-state-university-develop-algorithm-to-recognize-3d-printed-weapon-components-1774976/ |title=3DPrinterOS and Montclair State University develop algorithm to recognize 3D-printed gun components |website=3Printr.com |date=2024-11-05 |access-date=2026-01-22}}</ref> Critics argue that algorithms designed to detect "gun shapes" will inevitably generate false positives, flagging harmless objects such as plumbing pipes, L-brackets, or legitimate mechanical parts that share geometric similarities with firearm components.

=== Circumvention ===
The bill's requirement that blocking technology ''"cannot be overridden or otherwise defeated by a user with significant technical skill"'' presents a challenge given the open-source firmware landscape. Users can download Marlin or Klipper source code, remove any blocking code, and flash the modified firmware to their printers. The GPL license requires manufacturers using Marlin-based firmware to provide source code upon request.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref>

==Constitutional questions==

===First Amendment===
The question of whether computer code constitutes protected speech under the First Amendment remains partially unresolved. In 2016, during the ''Defense Distributed v. U.S. Department of State'' litigation, the Fifth Circuit declined to rule on the merits of the First Amendment claims, instead deciding the preliminary injunction on non-merits requirements. In her dissent, Judge Edith Jones wrote that the State Department ''"barely disputes that computer-related files and other technical data are speech protected by the First Amendment."''<ref>{{cite web |url=https://www.ca5.uscourts.gov/opinions/pub/15/15-50759-CV0.pdf |title=Defense Distributed v. U.S. Dep't of State |website=United States Court of Appeals for the Fifth Circuit |date=2016-09-20 |access-date=2026-01-21}}</ref>

The case settled in July 2018 with the State Department waiving prior restraint against Defense Distributed and paying approximately $40,000 in legal fees. State Department spokesperson Heather Nauert stated the government ''"would have lost this case in court, or would have likely lost this case in court, based on First Amendment grounds."''<ref>{{cite web |url=https://nationalpost.com/news/world/trump-now-says-3-d-printable-guns-dont-make-sense-it-was-his-administration-that-helped-make-them-available |title=Judge temporarily blocks posting of blueprints for 3D printed guns |website=National Post |date=2018-08-01 |access-date=2026-01-22}}</ref>

The Electronic Frontier Foundation filed an amicus brief in the Defense Distributed litigation arguing that "publishing computer files that communicate information, even in an esoteric format, is speech protected by the First Amendment."<ref>{{cite web |url=https://www.eff.org/cases/defense-distributed-v-united-states-department-state |title=Defense Distributed v. United States Department of State |website=Electronic Frontier Foundation |access-date=2026-01-21}}</ref>

Earlier circuit court precedent supports code as speech. In ''Bernstein v. U.S. Department of Justice'' (N.D. Cal. 1996), U.S. District Judge Marilyn Hall Patel found "no meaningful difference between computer language... and German or French."<ref>{{cite web |url=https://www.eff.org/deeplinks/2015/04/remembering-case-established-code-speech |title=EFF at 25: Remembering the Case that Established Code as Speech |website=Electronic Frontier Foundation |date=2015-04-16 |access-date=2026-01-21}}</ref>

===Second Amendment===
Federal law permits individuals to manufacture firearms for personal use without a license, provided weapons comply with the Undetectable Firearms Act. The ''Bondi v. VanDerStok'' decision did not address whether mandatory blocking technology infringes on manufacturing rights, as plaintiffs in that case raised no Second Amendment claims. According to The Regulatory Review, courts have been ''"generally unreceptive to the argument that the Second Amendment of the U.S. Constitution guards against restrictions on the right to acquire firearm parts for self-assembly."''<ref name="regreview" />

==Responses==

===Gun rights organizations===
The NRA Institute for Legislative Action criticized the proposals as having "First and Second Amendment implications" and characterized device-level blocking as creating concerns about prior restraint on speech. The organization stated: "All citizens should be gravely concerned with unconstitutional prior restraints on free speech when government works to require private companies to monitor and censor information on what citizens in most jurisdictions are legally allowed to create and possess in their own homes."<ref>{{cite web |url=https://www.nraila.org/articles/20260112/bans-for-3d-blueprints-new-york-governor-pushes-anti-gun-anti-speech-proposals |title=Bans for 3D Blueprints: New York Governor Pushes Anti-Gun, Anti-Speech Proposals |website=NRA-ILA |date=2026-01-12 |access-date=2026-01-21}}</ref>

==Related manufacturer controversies==

===Bambu Lab authorization control===
In January 2025, Bambu Lab announced "Authorization Control" for its X1 series printers, introducing authentication for operations including firmware upgrades, print job initiation, and remote video access. The company cited security concerns including cyberattacks and DDoS attacks as motivation for the change.<ref name="bambu3dpi">{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |title=Bambu Lab Responds to Backlash Over New Firmware Update |website=3D Printing Industry |date=2025-01-20 |access-date=2026-01-21}}</ref>

Third-party software including OrcaSlicer faced disruption. OrcaSlicer developer SoftFever publicly declined to adopt "Bambu Connect", calling it ''"unnecessary and of no meaningful benefit to users."''<ref>{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-controversy-deepens-firmware-update-sparks-backlash-240588/ |title=Bambu Lab Controversy Deepens: Firmware Update Sparks Backlash |website=3D Printing Industry |date=2025-06-11 |access-date=2026-01-21}}</ref> Josef Prusa, CEO of Prusa Research, commented on LinkedIn: "Quite scary where the 3DP industry is moving – control of your data."<ref name="bambu3dpi" />

===Creality root access removal===
In November 2025, Creality published a "Root Disclaimer and Risk Warning" stating its 2025 K1 Series "no longer supports Root access." Original K1 models had shipped with root access available through the settings menu. Creality's disclaimer stated that root access introduces security risks, including potential exposure of user information and privacy data through unauthorized applications.<ref>{{cite web |url=https://wiki.creality.com/en/k1-flagship-series/k1-series-general-documents/root-disclaimer-and-risk-warning |title=Root Disclaimer and Risk Warning |website=Creality Wiki |access-date=2026-01-21}}</ref>

==International context==
No country has mandated device-level firearm blocking technology in 3D printers.

In the United Kingdom, MP Preet Kaur Gill introduced the Firearms (3D Printing) Bill in October 2024. Clauses 43-44 of the Border Security, Asylum and Immigration Bill, introduced in January 2025, would criminalize making, importing, and possessing "templates" (blueprints) for 3D-printed firearms with up to 5 years imprisonment.<ref>{{cite web |url=https://bills.parliament.uk/bills/3877 |title=Firearms (3D Printing) Bill |website=UK Parliament |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://www.preetkaurgill.co.uk/post/preet-kaur-gill-s-ghost-gun-blueprint-ban-to-become-law |title=Preet Kaur Gill's ghost gun blueprint ban to become law |website=Preet Kaur Gill MP |access-date=2026-01-22}}</ref>

Australian states have enacted penalties for possessing digital firearm blueprints. Tasmania criminalized the possession of digital blueprints for the manufacture of firearms, with penalties of up to 21 years imprisonment. New South Wales imposes up to 14 years imprisonment under Section 51F of the Firearms Act 1996. South Australia has proposed penalties of up to 15 years imprisonment.<ref>{{cite web |url=https://classic.austlii.edu.au/au/legis/nsw/consol_act/fa1996102/s51f.html |title=Firearms Act 1996 - Section 51F |website=Australasian Legal Information Institute |access-date=2026-01-21}}</ref>

The European Union regulates possession of 3D-printed firearms under EU Directive 2021/555, but possession of digital blueprints is not explicitly prohibited.<ref>{{cite web |url=https://eur-lex.europa.eu/eli/dir/2021/555/oj |title=Directive 2021/555 |website=EUR-Lex |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2021:647:FIN |title=Report on the application of the Firearms Directive |website=EUR-Lex |date=2021-10-27 |access-date=2026-01-21}}</ref>

==Legislative status==
As of January 21, 2026, HB 2321 has completed first reading and remains in the Civil Rights & Judiciary Committee. No hearings have been scheduled.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref>

==References==
{{reflist}}

[[Category:Legislation]]
[[Category:3D printing]]
[[Category:United States]]
[[Category:Proposed legislation]]
[[Category:Right to repair]]

Miku charges subscription for previously free features

2026-01-22T09:51:13Z

Louis:

{{IncidentCargo
|Company=Miku
|StartDate=2023-09-15
|EndDate=
|Status=Active
|ProductLine=Miku Pro Smart Baby Monitor
|Product=Miku Pro Smart Baby Monitor
|ArticleType=Incident
|Type=Digital Restriction, Terms of Service, Cloud Lockout
|Description=Miku revoked previously free baby monitor features, now selling them for $9.99/mo under the "Care+" subscription.
}}

==Incident==
[[File:Miku email to customers.png|alt=Miku Email to Customers on September 15, 2023|thumb|Miku Email to Customers on September 15, 2023]]
Through the acquisition of Miku Inc by Innovative Health Monitoring LLC, Miku sent out an email notice to all of their users on September 15, 2023 detailing changes to the access Miku customers have to features on their Miku device starting October 1, 2023. According to Miku, "For customers who did not previously subscribe to Care+, many of the features you have been receiving for free will now require a monthly subscription fee."<ref>{{Cite web |title=Letter to Customers |url=https://assets.mikucloud.com/Innovative_Health_Monitoring-Letter_to_Customers.pdf |url-status=live |archive-url=https://web.archive.org/web/20231010081331/https://assets.mikucloud.com/Innovative_Health_Monitoring-Letter_to_Customers.pdf |archive-date=10 Oct 2023 |access-date=4 Apr 2025}}</ref>

===Changes made===
According to the Miku email to customers, the new breakdown of feature changes is as follows:

*Updated Free features:
**Live HD video and audio streaming (available locally only unless the customer's smartphone or tablet is operating on the same wireless network as the monitoring device.
[[File:Miku site 999permonth.png|alt=Miku website describing new features for $9.99/Mo|thumb|Miku website describing new features for $9.99/Mo]]

*Updated Subscription Membership features At '''$9.99''' per month:
**Live HD video and audio (local and remote access);
**two-way talk;
**live breathing waveform;
**sleep and health analytics;
**environmental analytics;
**various notifications and alerts;
**sounds and lullabies;
**three days of video storage;
**Care+ access;
**wellness trends.;
**tips from medical and sleep experts; and
**wellness tracking tools (height, weight, feeding, body temp, diaper changes)

*Offer access to higher tier memberships that include longer term video storage at the following levels:
**Monthly Membership + 30 days of video storage ($14.99 per month);
**Monthly Membership + 1 Year of video storage ($19.99 per month); and
**Monthly Membership + Unlimited video storage ($29.99 per month)

===Customer response===
Many customers were displeased with the subscription service added to Miku. Leading to products being returned and customers emailing Innovative Health Monitoring to voice their opinions with the company.

Due to these subscription changes being instituted through automatic updates to the Miku mobile application, turning off automatic updates and refusing to update the Miku app would keep the features that were now locked behind a subscription.<ref>{{Cite web |title=Miku bought out and now charging a subscription for basic features. |url=https://www.reddit.com/r/daddit/comments/16jr4vy/miku_bought_out_and_now_charging_a_subscription/ |url-status=live |access-date=4 Apr 2025 |website=[[Reddit]]}}</ref>

== Industry trend ==
The changes that Innovative Health Monitoring has made to the Miku care+ subscription model regarding the accessibility of its previously-offered services to customers sets a precedent for how Innovative Health Monitoring can remove or completely lock services away from customers in the future for all products and services they provide. According to the Miku Terms of service:
<blockquote>''"We reserve the right to change the Terms at any time, but if we do, we will do our best to bring it to your attention by placing a notice on the Miku website, by sending you an email, and/or by some other means."<ref name=":0">{{Cite web |date=15 Sep 2023 |title=Miku Care terms of service |url=https://mikucare.com/pages/terms-of-service |url-status=live |archive-url=https://web.archive.org/web/20250722045420/https://mikucare.com/pages/terms-of-service |archive-date=22 Jul 2025 |access-date=15 Aug 2025 |website=Miku Care}}</ref>''</blockquote>

and

<blockquote>''"If you use the Services in any way after a change to the Terms are effective, you agree to the changes to the Terms."<ref name=":0" />''</blockquote>

== References ==
<references />
[[Category:Miku]]
[[Category:Incidents]]

Washington house bill 2321 regarding 3d printers

2026-01-22T01:53:46Z

Louis: fixed

{{IncidentCargo
|ProductLine=3D printers
|Product=3D printers
|Description=Washington State bill mandating firearm detection algorithms in 3D printers; first law of its kind, with Class C felony penalties.
}}
'''Washington House Bill 2321''' is proposed legislation in the U.S. state of Washington that requires all 3D printers sold in the state to include firearm-blocking technology. Prefiled on January 8, 2026, and referred to the House Civil Rights & Judiciary Committee on January 12, the bill would impose Class C felony penalties of up to five years imprisonment and $15,000 in fines for corporations that sell non-compliant printers after July 1, 2027.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref><ref name="billtext">{{cite web |url=https://lawfilesext.leg.wa.gov/biennium/2025-26/Pdf/Bills/House%20Bills/2321.pdf |title=House Bill 2321 |website=Washington State Legislature |date=2026-01-08 |access-date=2026-01-21}}</ref>

The bill is sponsored by 26 Democratic state representatives, with Rep. Osman Salahuddin (D-48th District) as the prime sponsor and Rep. Strom Peterson (D-21st District) as second-listed sponsor.<ref name="billtext" /> No hearings have been scheduled as of January 21, 2026, and no amendments have been filed.

==Background==

===Federal regulation of ghost guns===
The U.S. Bureau of Alcohol, Tobacco, Firearms and Explosives issued a rule in 2022 clarifying that weapon parts kits and unfinished frames fall under the definition of "firearm" in the Gun Control Act of 1968. This rule required ghost gun kits to carry serial numbers and be sold through licensed dealers with background checks.<ref>{{cite web |url=https://www.scotusblog.com/2025/03/supreme-court-upholds-regulation-of-ghost-guns/ |title=Supreme Court upholds regulation on "ghost guns" |website=SCOTUSblog |date=2025-03-26 |access-date=2026-01-21}}</ref>

On March 26, 2025, the Supreme Court upheld this rule in ''Bondi v. VanDerStok'' by a 7-2 vote. Justice Neil Gorsuch, writing for the majority, found that Polymer80's "Buy Build Shoot" kit meets the statutory definition of a firearm, stating: "Really, the kit's name says it all."<ref>{{cite web |url=https://www.supremecourt.gov/opinions/24pdf/23-852_o7jp.pdf |title=Bondi v. VanDerStok |website=Supreme Court of the United States |date=2025-03-26 |access-date=2026-01-21}}</ref> The ruling was a statutory interpretation challenge under the Administrative Procedure Act; it did not address Second Amendment claims regarding home firearm manufacture.<ref name="regreview">{{cite web |url=https://www.theregreview.org/2025/07/23/willinger-vanderstok-and-the-ghosts-of-gun-deregulation/ |title=VanDerStok and the Ghosts of Gun Deregulation |website=The Regulatory Review |date=2025-07-23 |access-date=2026-01-21}}</ref>

===Open-source 3D printer firmware===
The consumer 3D printer market relies on open-source firmware. Marlin firmware, created in 2011, states on its homepage that it ''"drives most of the world's 3D printers."'' It is used by manufacturers including Ultimaker, Prusa Research, and Creality.<ref>{{cite web |url=https://marlinfw.org/ |title=Home |website=Marlin Firmware |access-date=2026-01-21}}</ref> Klipper firmware, developed in 2016, has rapidly gained popularity among prosumer FDM 3D printer users.<ref>{{cite web |url=https://www.xometry.com/resources/3d-printing/klipper-vs-marlin/ |title=Klipper vs. Marlin - 3D Printer Firmware Comparison |website=Xometry |date=2025-06-12 |access-date=2026-01-21}}</ref>

Both Marlin and Klipper are published under the GNU General Public License. The GPL requires that users be provided with source code upon request and permits unlimited modification and redistribution.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref> This licensing structure permits users to compile and flash custom firmware versions without restrictions, which places them in direct conflict with the text of the bill.

==Provisions of the bill==

===Blocking technology requirements===
HB 2321 would require 3D printers sold in Washington after July 1, 2027 to be equipped with ''"blocking features"'' defined as ''"a software controls process that deploys a firearms blueprint detection algorithm."'' According to the bill text, these features must ''"identify and reject print requests for firearms or illegal firearm parts with a high degree of reliability and cannot be overridden or otherwise defeated by a user with significant technical skill."''<ref name="billtext" />

The bill defines ''"firearms blueprint detection algorithm"'' as a system that evaluates STL files, CAD files, or G-code to determine whether they match firearm designs.<ref name="billtext" /> Manufacturers may comply through three methods specified in Section 6(2) of the bill: integration of the algorithm in the printer's firmware, integration in preprint software, or a handshake authentication design between software and printer.<ref name="billtext" />

===Scope of covered equipment===
The bill defines ''"three-dimensional printer"'' to include devices capable of both additive manufacturing and subtractive manufacturing from a digital file. This broad definition has been interpreted by commentators to potentially include CNC mills, lathes, laser cutters, and water jet cutters.<ref name="billtext" /><ref>{{cite web |url=https://www.ibtimes.co.uk/5-years-prison-download-washingtons-brutal-new-crackdown-3d-printed-guns-1772280 |title=The State of Washington Joins Other States Imposing a Ban or Restrictions Against 3D Printed Firearms |website=International Business Times |date=2026-01-20 |access-date=2026-01-21}}</ref>

===Attorney General authority===
Section 3(3) grants the Washington Attorney General authority to ''"adopt rules and regulations for any other processes the attorney general deems necessary to carry out the provisions of this chapter."''<ref name="billtext" /> Section 8 requires the Attorney General to create and maintain a database of firearms blueprint files by August 1, 2026, and to update this database at least once per year. Section 7(4) authorizes the Attorney General to adopt rules ''"requiring developers and users of such algorithms to update such algorithms if new technology is found to be substantially more effective."''<ref name="billtext" />

===Penalties and exemptions===
Violations by corporations constitute a Class C felony with penalties of up to five years imprisonment and $15,000 in fines. Violations by individuals are classified as misdemeanors or gross misdemeanors depending on severity. Filing a false attestation constitutes perjury. Violations are also treated as unfair or deceptive acts under Washington's Consumer Protection Act.<ref name="billtext" />

The bill exempts 3D printers sold to entities holding federal firearms manufacturing licenses.<ref name="billtext" />

==Similar proposals==

===New York===
Governor Kathy Hochul announced comparable proposals on January 7, 2026, as part of her 2026 State of the State agenda. Her proposals would require manufacturers to include blocking software on 3D printers sold in New York, criminalize unlicensed possession or distribution of firearm CAD files, and mandate reporting of recovered 3D-printed guns to state police databases.<ref>{{cite web |url=https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-announces-nation-leading-proposals-crack-down-3d |title=Keeping New Yorkers Safe: Governor Hochul Announces Nation-Leading Proposals to Crack Down on 3D-Printed Guns and Other Illegal Firearms |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref>

Hochul stated: <blockquote>"We will require all 3D printers sold in the State of New York to include software that blocks the production of guns and their components. You cannot sell one of those in the State of New York when we pass these laws."<ref>{{cite web |url=https://www.governor.ny.gov/news/b-roll-video-audio-photos-rush-transcript-keeping-new-yorkers-safe-governor-hochul-announces |title=B-Roll, Video, Audio, Photos & Rush Transcript |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref></blockquote>

No bill numbers have been assigned as these remain gubernatorial proposals requiring legislative action.

===Federal legislation===
H.R. 4143, the "3D Printed Gun Safety Act of 2025," was introduced in 2025 by Rep. Jared Moskowitz (D-FL) and referred to the House Judiciary Committee. Unlike Washington's hardware-focused approach, the federal bill would prohibit distribution of 3D printer plans for firearms rather than mandate device-level blocking.<ref>{{cite web |url=https://www.congress.gov/bill/119th-congress/house-bill/4143/text |title=H.R.4143 - 3D Printed Gun Safety Act of 2025 |website=Congress.gov |access-date=2026-01-21}}</ref>

==Manhattan DA's pressure campaign==
Manhattan District Attorney Alvin Bragg has sent letters to multiple 3D printer manufacturers requesting voluntary adoption of blocking software.

On March 26, 2025, Bragg sent a letter to Shenzhen Creality 3D Technology Co., Ltd. demanding installation of detection software, removal of CAD files from Creality Cloud, and a user agreement ban on weapon creation. The letter stated that ''"recent research has found that the vast majority of illegal 3D printed guns were created using Creality printers, specifically the Ender 3 series model."''<ref>{{cite web |url=https://manhattanda.org/d-a-bragg-calls-on-3d-printing-companies-to-address-proliferation-of-illegal-firearms/ |title=D.A. Bragg Calls On 3D-Printing Companies To Address Proliferation Of Illegal Firearms |website=Manhattan District Attorney's Office |date=2025-03-27 |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://manhattanda.org/wp-content/uploads/2025/03/Letter-Creality-3.26.25.pdf |title=Letter to Creality |website=Manhattan District Attorney's Office |date=2025-03-26 |access-date=2026-01-21}}</ref>

Bragg sent a similar letter to Bambu Lab in 2025, stating: ''"The risk your product creates, as 3D printers are used more and more frequently in schools and homes, is unacceptable."''<ref>{{cite web |url=https://abcnews.go.com/US/digital-design-firm-agrees-block-3d-guns-letter/story?id=123876632 |title=Digital design firm agrees to block 3D guns, following letter from Manhattan DA |website=ABC News |date=2025-08-05 |access-date=2026-01-21}}</ref>

Neither Creality nor Bambu Lab has publicly announced implementation of firearm blocking features in response to these letters.<ref>{{cite web |url=https://abcnews.go.com/US/digital-design-firm-agrees-block-3d-guns-letter/story?id=123876632 |title=Digital design firm agrees to block 3D guns, following letter from Manhattan DA |website=ABC News |date=2025-08-05 |access-date=2026-01-21}}</ref>

==Technical feasibility questions==
No commercially validated firearm detection technology exists for 3D printers as of January 2026. 3DPrinterOS announced a partnership with Montclair State University's MIX Lab in November 2024 to develop an algorithm capable of identifying 3D printed firearm components based on unique design signatures, but the feature has not been deployed commercially.<ref>{{cite web |url=https://www.tctmagazine.com/additive-manufacturing-3d-printing-news/software-and-simulation-news/3dprinteros-montclair-state-university-algorithm-3d-printed-guns/ |title=3DPrinterOS & Montclair State University to develop algorithm capable of identifying 3D printed gun components |website=TCT Magazine |date=2024-11-05 |access-date=2026-01-21}}</ref>

The bill's requirement that blocking technology ''"cannot be overridden or otherwise defeated by a user with significant technical skill"'' presents a challenge given the open-source firmware landscape. Users can download Marlin or Klipper source code, remove any blocking code, and flash the modified firmware to their printers. The GPL license requires manufacturers using Marlin-based firmware to provide source code upon request.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref>

==Constitutional questions==

===First Amendment===
The question of whether computer code constitutes protected speech under the First Amendment remains partially unresolved. In 2016, during the ''Defense Distributed v. U.S. Department of State'' litigation, the Fifth Circuit declined to rule on the merits of the First Amendment claims, instead deciding the preliminary injunction on non-merits requirements. In her dissent, Judge Edith Jones wrote that the State Department ''"barely disputes that computer-related files and other technical data are speech protected by the First Amendment."''<ref>{{cite web |url=https://www.ca5.uscourts.gov/opinions/pub/15/15-50759-CV0.pdf |title=Defense Distributed v. U.S. Dep't of State |website=United States Court of Appeals for the Fifth Circuit |date=2016-09-20 |access-date=2026-01-21}}</ref>

The case settled in July 2018 with the State Department waiving prior restraint against Defense Distributed and paying approximately $40,000 in legal fees. State Department spokesperson Heather Nauert stated the government ''"would have lost this case in court, or would have likely lost this case in court, based on First Amendment grounds."''<ref>{{cite web |url=https://www.nbcnews.com/news/us-news/gun-rights-activists-post-plans-3d-firearms-after-judge-s-n896411 |title=Gun rights activists post plans for 3D firearms after judge's order blocking them |website=NBC News |date=2018-08-01 |access-date=2026-01-21}}</ref>

The Electronic Frontier Foundation filed an amicus brief in the Defense Distributed litigation arguing that "publishing computer files that communicate information, even in an esoteric format, is speech protected by the First Amendment."<ref>{{cite web |url=https://www.eff.org/cases/defense-distributed-v-united-states-department-state |title=Defense Distributed v. United States Department of State |website=Electronic Frontier Foundation |access-date=2026-01-21}}</ref>

Earlier circuit court precedent supports code as speech. In ''Bernstein v. U.S. Department of Justice'' (N.D. Cal. 1996), U.S. District Judge Marilyn Hall Patel found "no meaningful difference between computer language... and German or French."<ref>{{cite web |url=https://www.eff.org/deeplinks/2015/04/remembering-case-established-code-speech |title=EFF at 25: Remembering the Case that Established Code as Speech |website=Electronic Frontier Foundation |date=2015-04-16 |access-date=2026-01-21}}</ref>

===Second Amendment===
Federal law permits individuals to manufacture firearms for personal use without a license, provided weapons comply with the Undetectable Firearms Act. The ''Bondi v. VanDerStok'' decision did not address whether mandatory blocking technology infringes on manufacturing rights, as plaintiffs in that case raised no Second Amendment claims. According to The Regulatory Review, courts have been ''"generally unreceptive to the argument that the Second Amendment of the U.S. Constitution guards against restrictions on the right to acquire firearm parts for self-assembly."''<ref name="regreview" />

==Responses==

===Gun rights organizations===
The NRA Institute for Legislative Action criticized the proposals as having "First and Second Amendment implications" and characterized device-level blocking as creating concerns about prior restraint on speech. The organization stated: "All citizens should be gravely concerned with unconstitutional prior restraints on free speech when government works to require private companies to monitor and censor information on what citizens in most jurisdictions are legally allowed to create and possess in their own homes."<ref>{{cite web |url=https://www.nraila.org/articles/20260112/bans-for-3d-blueprints-new-york-governor-pushes-anti-gun-anti-speech-proposals |title=Bans for 3D Blueprints: New York Governor Pushes Anti-Gun, Anti-Speech Proposals |website=NRA-ILA |date=2026-01-12 |access-date=2026-01-21}}</ref>

===Industry analysis===
Washington Gun Law president William Kirk stated in a video that most manufacturers would likely choose not to sell their products in Washington State rather than implement blocking technology.<ref>{{cite web |url=https://kcgop.org/washington-gun-law-the-bill-that-would-ban-3d-printers-in-washington-state/ |title=Washington Gun Law – The Bill That Would Ban 3D Printers in Washington State |website=KCGOP |date=2026-01-18 |access-date=2026-01-21}}</ref>

==Related manufacturer controversies==

===Bambu Lab authorization control===
In January 2025, Bambu Lab announced "Authorization Control" for its X1 series printers, introducing authentication for operations including firmware upgrades, print job initiation, and remote video access. The company cited security concerns including cyberattacks and DDoS attacks as motivation for the change.<ref name="bambu3dpi">{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |title=Bambu Lab Responds to Backlash Over New Firmware Update |website=3D Printing Industry |date=2025-01-20 |access-date=2026-01-21}}</ref>

Third-party software including OrcaSlicer faced disruption. OrcaSlicer developer SoftFever publicly declined to adopt Bambu Connect, calling it ''"unnecessary and of no meaningful benefit to users."''<ref>{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-controversy-deepens-firmware-update-sparks-backlash-240588/ |title=Bambu Lab Controversy Deepens: Firmware Update Sparks Backlash |website=3D Printing Industry |date=2025-06-11 |access-date=2026-01-21}}</ref> Josef Prusa, CEO of Prusa Research, commented on LinkedIn: "Quite scary where the 3DP industry is moving – control of your data."<ref name="bambu3dpi" />

Bambu Lab introduced "Developer Mode" as a partial concession, allowing users to retain local control when enabled alongside LAN-only mode. The company did not cite firearm printing as a motivation for the authorization system.<ref>{{cite web |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |title=Updates and Third-Party Integration with Bambu Connect |website=Bambu Lab Blog |date=2025-01-20 |access-date=2026-01-21}}</ref>

===Creality root access removal===
In November 2025, Creality published a "Root Disclaimer and Risk Warning" stating its 2025 K1 Series "no longer supports Root access." Original K1 models had shipped with root access available through the settings menu. Creality's disclaimer stated that root access introduces security risks, including potential exposure of user information and privacy data through unauthorized applications.<ref>{{cite web |url=https://wiki.creality.com/en/k1-flagship-series/k1-series-general-documents/root-disclaimer-and-risk-warning |title=Root Disclaimer and Risk Warning |website=Creality Wiki |access-date=2026-01-21}}</ref>

==International context==
No country has mandated device-level firearm blocking technology in 3D printers.

In the United Kingdom, MP Preet Kaur Gill introduced the Firearms (3D Printing) Bill in October 2024. Clauses 43-44 of the Border Security, Asylum and Immigration Bill would criminalize making, importing, and possessing templates for 3D-printed firearms with up to 5 years imprisonment, but no device-blocking mandates are included.<ref>{{cite web |url=https://bills.parliament.uk/bills/3877 |title=Firearms (3D Printing) Bill |website=UK Parliament |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://www.preetkaurgill.co.uk/post/preet-kaur-gill-s-ghost-gun-blueprint-ban-to-become-law |title=Preet Kaur Gill's ghost gun blueprint ban to become law |website=Preet Kaur Gill MP |access-date=2026-01-21}}</ref>

Australian states have enacted penalties for possessing digital firearm blueprints. New South Wales imposes up to 14 years imprisonment under Section 51F of the Firearms Act 1996. Tasmania allows up to 21 years. No Australian jurisdiction requires device-level blocking.<ref>{{cite web |url=https://classic.austlii.edu.au/au/legis/nsw/consol_act/fa1996102/s51f.html |title=Firearms Act 1996 - Section 51F |website=Australasian Legal Information Institute |access-date=2026-01-21}}</ref>

The European Union regulates possession of 3D-printed firearms under EU Directive 2021/555, but possession of digital blueprints is not explicitly prohibited. The Commission has stated it is assessing "the need for specific rules on the possession and trafficking of blueprints" but has not proposed device-level requirements.<ref>{{cite web |url=https://eur-lex.europa.eu/eli/dir/2021/555/oj |title=Directive 2021/555 |website=EUR-Lex |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2021:647:FIN |title=Report on the application of the Firearms Directive |website=EUR-Lex |date=2021-10-27 |access-date=2026-01-21}}</ref>

==Legislative status==
As of January 21, 2026, HB 2321 has completed first reading and remains in the Civil Rights & Judiciary Committee. No hearings have been scheduled. Neither Rep. Salahuddin nor Rep. Peterson has issued public statements explaining the bill's motivation.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref>

==References==
{{reflist}}

[[Category:Legislation]]
[[Category:3D printing]]
[[Category:United States]]
[[Category:Proposed legislation]]
[[Category:Right to repair]]

Washington house bill 2321 regarding 3d printers

2026-01-21T23:54:24Z

Louis: draft

{{IncidentCargo
|ProductLine=3D printers
|Product=3D printers
|Description=Washington State bill mandating firearm detection algorithms in 3D printers; first law of its kind, with Class C felony penalties.
}}
'''Washington House Bill 2321''' is proposed legislation in the U.S. state of Washington that requires all 3D printers sold in the state to include firearm-blocking technology. Prefiled on January 8, 2026, and referred to the House Civil Rights & Judiciary Committee on January 12, the bill would impose Class C felony penalties of up to five years imprisonment and $15,000 in fines for corporations that sell non-compliant printers after July 1, 2027.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref><ref name="billtext">{{cite web |url=https://lawfilesext.leg.wa.gov/biennium/2025-26/Pdf/Bills/House%20Bills/2321.pdf |title=House Bill 2321 |website=Washington State Legislature |date=2026-01-08 |access-date=2026-01-21}}</ref>

The bill is sponsored by 26 Democratic state representatives, with Rep. Osman Salahuddin (D-48th District) as the prime sponsor and Rep. Strom Peterson (D-21st District) as second-listed sponsor.<ref name="billtext" /> No hearings have been scheduled as of January 21, 2026, and no amendments have been filed.

==Background==

===Federal regulation of ghost guns===

The U.S. Bureau of Alcohol, Tobacco, Firearms and Explosives issued a rule in 2022 clarifying that weapon parts kits and unfinished frames fall under the definition of "firearm" in the Gun Control Act of 1968. This rule required ghost gun kits to carry serial numbers and be sold through licensed dealers with background checks.<ref>{{cite web |url=https://www.scotusblog.com/2025/03/supreme-court-upholds-regulation-of-ghost-guns/ |title=Supreme Court upholds regulation on "ghost guns" |website=SCOTUSblog |date=2025-03-26 |access-date=2026-01-21}}</ref>

On March 26, 2025, the Supreme Court upheld this rule in ''Bondi v. VanDerStok'' by a 7-2 vote. Justice Neil Gorsuch, writing for the majority, found that Polymer80's "Buy Build Shoot" kit "clearly qualifies" as a weapon, stating: "Really, the kit's name says it all."<ref>{{cite web |url=https://www.supremecourt.gov/opinions/24pdf/23-852_o7jp.pdf |title=Bondi v. VanDerStok |website=Supreme Court of the United States |date=2025-03-26 |access-date=2026-01-21}}</ref> The ruling was a statutory interpretation challenge under the Administrative Procedure Act; it did not address Second Amendment claims regarding home firearm manufacture.<ref name="regreview">{{cite web |url=https://www.theregreview.org/2025/07/23/willinger-vanderstok-and-the-ghosts-of-gun-deregulation/ |title=VanDerStok and the Ghosts of Gun Deregulation |website=The Regulatory Review |date=2025-07-23 |access-date=2026-01-21}}</ref>

===Open-source 3D printer firmware===

The consumer 3D printer market relies on open-source firmware. Marlin firmware, created in 2011, states on its homepage that it ''"drives most of the world's 3D printers."'' It is used by manufacturers including Ultimaker, Prusa Research, and Creality.<ref>{{cite web |url=https://marlinfw.org/docs/basics/introduction.html |title=Introduction |website=Marlin Firmware |access-date=2026-01-21}}</ref> Klipper firmware has been described as ''"the de facto choice for prosumer FDM 3D printers."''<ref>{{cite web |url=https://en.wikipedia.org/wiki/Klipper_(firmware) |title=Klipper (firmware) |website=Wikipedia |access-date=2026-01-21}}</ref>

Both Marlin and Klipper are published under the GNU General Public License. The GPL requires that users be provided with source code upon request and permits unlimited modification and redistribution.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref> This licensing structure permits users to compile and flash custom firmware versions without restrictions, which places them in direct conflict with the text of the bill.

==Provisions of the bill==

===Blocking technology requirements===

HB 2321 would require 3D printers sold in Washington after July 1, 2027 to be equipped with ''"blocking features"'' defined as ''"a software controls process that deploys a firearms blueprint detection algorithm."'' According to the bill text, these features must ''"identify and reject print requests for firearms or illegal firearm parts with a high degree of reliability and cannot be overridden or otherwise defeated by a user with significant technical skill."''<ref name="billtext" />

The bill defines ''"firearms blueprint detection algorithm"'' as a system that evaluates STL files, CAD files, or G-code to determine whether they match firearm designs.<ref name="billtext" /> Manufacturers may comply through three methods specified in Section 6(2) of the bill: integration of the algorithm in the printer's firmware, integration in preprint software, or a handshake authentication design between software and printer.<ref name="billtext" />

===Scope of covered equipment===

The bill defines ''"three-dimensional printer"'' to include devices capable of both additive manufacturing and subtractive manufacturing from a digital file. This definition can be interpreted to include CNC mills, lathes, laser cutters, and water jet cutters.<ref name="billtext" /> Commentary on social media has mentioned that this scope could theoretically affect aerospace manufacturing in Washington State.<ref>{{cite web |url=https://www.ibtimes.co.uk/5-years-prison-download-washingtons-brutal-new-crackdown-3d-printed-guns-1772280 |title=The State of Washington Joins Other States Imposing a Ban or Restrictions Against 3D Printed Firearms |website=International Business Times |date=2026-01-20 |access-date=2026-01-21}}</ref>

===Attorney General authority===

Section 3(3) grants the Washington Attorney General authority to ''"adopt rules and regulations for any other processes the attorney general deems necessary to carry out the provisions of this chapter."''<ref name="billtext" /> Section 8 requires the Attorney General to create and maintain a database of firearms blueprint files by August 1, 2026, and to update this database at least once per year. Section 7(4) authorizes the Attorney General to adopt rules ''"requiring developers and users of such algorithms to update such algorithms if new technology is found to be substantially more effective."''<ref name="billtext" />

===Penalties and exemptions===

Violations by corporations constitute a Class C felony with penalties of up to five years imprisonment and $15,000 in fines. Violations by individuals are classified as misdemeanors or gross misdemeanors depending on severity. Filing a false attestation constitutes perjury. Violations are also treated as unfair or deceptive acts under Washington's Consumer Protection Act.<ref name="billtext" />

The bill exempts 3D printers sold to entities holding federal firearms manufacturing licenses.<ref name="billtext" />

==Similar proposals==

===New York===

Governor Kathy Hochul announced comparable proposals on January 7, 2026, as part of her 2026 State of the State agenda. Her proposals would require manufacturers to include blocking software on 3D printers sold in New York, criminalize unlicensed possession or distribution of firearm CAD files, and mandate reporting of recovered 3D-printed guns to state police databases.<ref>{{cite web |url=https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-announces-nation-leading-proposals-crack-down-3d |title=Keeping New Yorkers Safe: Governor Hochul Announces Nation-Leading Proposals to Crack Down on 3D-Printed Guns and Other Illegal Firearms |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref>

Hochul stated: <blockquote>"We will require all 3D printers sold in the State of New York to include software that blocks the production of guns and their components. You cannot sell one of those in the State of New York when we pass these laws."<ref>{{cite web |url=https://www.governor.ny.gov/news/b-roll-video-audio-photos-rush-transcript-keeping-new-yorkers-safe-governor-hochul-announces |title=B-Roll, Video, Audio, Photos & Rush Transcript |website=Office of Governor Kathy Hochul |date=2026-01-07 |access-date=2026-01-21}}</ref> </blockquote>No bill numbers have been assigned as these remain gubernatorial proposals requiring legislative action.

===Federal legislation===

H.R. 4143, the "3D Printed Gun Safety Act of 2025," was introduced in 2025 by Rep. Jared Moskowitz (D-FL) and referred to the House Judiciary Committee. Unlike Washington's hardware-focused approach, the federal bill would prohibit distribution of 3D printer plans for firearms rather than mandate device-level blocking.<ref>{{cite web |url=https://www.congress.gov/bill/119th-congress/house-bill/4143 |title=H.R.4143 - 3D Printed Gun Safety Act of 2025 |website=Congress.gov |access-date=2026-01-21}}</ref>

==Manhattan DA's pressure campaign==

Manhattan District Attorney Alvin Bragg has sent letters to multiple 3D printer manufacturers requesting voluntary adoption of blocking software.

On March 26, 2025, Bragg sent a letter to Shenzhen Creality 3D Technology Co., Ltd. demanding installation of detection software, removal of CAD files from Creality Cloud, and a user agreement ban on weapon creation. The letter stated that ''"recent research has found that the vast majority of illegal 3D printed guns were created using Creality printers, specifically the Ender 3 series model."''<ref>{{cite web |url=https://manhattanda.org/d-a-bragg-calls-on-3d-printing-companies-to-address-proliferation-of-illegal-firearms/ |title=D.A. Bragg Calls On 3D-Printing Companies To Address Proliferation Of Illegal Firearms |website=Manhattan District Attorney's Office |date=2025-03-27 |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://manhattanda.org/wp-content/uploads/2025/03/Letter-Creality-3.26.25.pdf |title=Letter to Creality |website=Manhattan District Attorney's Office |date=2025-03-26 |access-date=2026-01-21}}</ref>

Bragg sent a similar letter to Bambu Lab in 2025, stating: ''"The risk your product creates, as 3D printers are used more and more frequently in schools and homes, is unacceptable."''<ref>{{cite web |url=https://abcnews.go.com/US/digital-design-firm-agrees-block-3d-guns-letter/story?id=123876632 |title=Digital design firm agrees to block 3D guns, following letter from Manhattan DA |website=ABC News |date=2025-08-05 |access-date=2026-01-21}}</ref>

Neither Creality nor Bambu Lab has publicly responded to these letters or announced implementation of firearm blocking features.<ref>{{cite web |url=https://manhattanda.org/d-a-bragg-calls-on-3d-printing-companies-to-address-proliferation-of-illegal-firearms/ |title=D.A. Bragg Calls On 3D-Printing Companies To Address Proliferation Of Illegal Firearms |website=Manhattan District Attorney's Office |date=2025-03-27 |access-date=2026-01-21}}</ref>

==Technical feasibility questions==

No commercially validated firearm detection technology exists for 3D printers as of January 2026. 3DPrinterOS partnered with Montclair State University's MIX Lab in November 2024 to develop detection algorithms, but the feature has not been deployed commercially.<ref>{{cite web |url=https://www.tomshardware.com/3d-printing/washington-state-proposes-new-3d-printed-gun-controls-with-blocking-features-and-blueprint-detection-algorithm-proposal-would-carry-sentences-of-five-years-in-prison-usd15-000-fine-for-violation |title=Washington state proposes new 3D-printed gun controls with 'blocking features' and blueprint detection algorithm |website=Tom's Hardware |date=2026-01-19 |access-date=2026-01-21}}</ref>

The bill's requirement that blocking technology ''"cannot be overridden or otherwise defeated by a user with significant technical skill"'' presents a challenge given the open-source firmware landscape. Users can download Marlin or Klipper source code, remove any blocking code, and flash the modified firmware to their printers. The GPL license requires manufacturers using Marlin-based firmware to provide source code upon request.<ref>{{cite web |url=https://github.com/MarlinFirmware/Marlin |title=MarlinFirmware/Marlin |website=GitHub |access-date=2026-01-21}}</ref>

==Constitutional questions==

===First Amendment===

The question of whether computer code constitutes protected speech under the First Amendment remains partially unresolved. In 2016, during the ''Defense Distributed v. U.S. Department of State'' litigation, the Fifth Circuit noted that the State Department ''"barely disputes that computer-related files and other technical data are speech protected by the First Amendment."''<ref>{{cite web |url=https://www.ca5.uscourts.gov/opinions/pub/15/15-50759-CV0.pdf |title=Defense Distributed v. U.S. Dep't of State |website=United States Court of Appeals for the Fifth Circuit |date=2016-09-20 |access-date=2026-01-21}}</ref>

The case settled in July 2018 with the State Department waiving prior restraint against Defense Distributed and paying a portion of attorney's fees. State Department spokesperson Heather Nauert stated the government ''"would have lost this case in court, or would have likely lost this case in court, based on First Amendment grounds."''<ref>{{cite web |url=https://en.wikipedia.org/wiki/Defense_Distributed_v._United_States_Department_of_State |title=Defense Distributed v. United States Department of State |website=Wikipedia |access-date=2026-01-21}}</ref>

The Electronic Frontier Foundation filed an amicus brief in the Defense Distributed litigation arguing that "publishing computer files that communicate information, even in an esoteric format, is speech protected by the First Amendment."<ref>{{cite web |url=https://www.eff.org/cases/defense-distributed-v-united-states-department-state |title=Defense Distributed v. United States Department of State |website=Electronic Frontier Foundation |access-date=2026-01-21}}</ref>

Earlier circuit court precedent supports code as speech. In ''Bernstein v. U.S. Department of Justice'' (N.D. Cal. 1996), U.S. District Judge Marilyn Hall Patel found "no meaningful difference between computer language... and German or French."<ref>{{cite web |url=https://www.eff.org/deeplinks/2015/04/remembering-case-established-code-speech |title=EFF at 25: Remembering the Case that Established Code as Speech |website=Electronic Frontier Foundation |date=2015-04-16 |access-date=2026-01-21}}</ref>

===Second Amendment===

Federal law permits individuals to manufacture firearms for personal use without a license, provided weapons comply with the Undetectable Firearms Act. The ''Bondi v. VanDerStok'' decision did not address whether mandatory blocking technology infringes on manufacturing rights, as plaintiffs in that case raised no Second Amendment claims. According to The Regulatory Review, courts have been ''"generally unreceptive to the argument that the Second Amendment of the U.S. Constitution guards against restrictions on the right to acquire firearm parts for self-assembly."''<ref name="regreview" />

==Responses==

===Gun rights organizations===

The NRA Institute for Legislative Action criticized the proposals as having "First and Second Amendment implications" and characterized device-level blocking as creating concerns about prior restraint on speech. The organization stated: "All citizens should be gravely concerned with unconstitutional prior restraints on free speech when government works to require private companies to monitor and censor information on what citizens in most jurisdictions are legally allowed to create and possess in their own homes."<ref>{{cite web |url=https://www.nraila.org/articles/20260112/bans-for-3d-blueprints-new-york-governor-pushes-anti-gun-anti-speech-proposals |title=Bans for 3D Blueprints: New York Governor Pushes Anti-Gun, Anti-Speech Proposals |website=NRA-ILA |date=2026-01-12 |access-date=2026-01-21}}</ref>

===Industry analysis===

Washington Gun Law president William Kirk stated in a video that most manufacturers would likely choose not to sell their products in Washington State rather than implement blocking technology.<ref>{{cite web |url=https://kcgop.org/washington-gun-law-the-bill-that-would-ban-3d-printers-in-washington-state/ |title=Washington Gun Law – The Bill That Would Ban 3D Printers in Washington State |website=KCGOP |date=2026-01-18 |access-date=2026-01-21}}</ref>

==Related manufacturer controversies==

===Bambu Lab authorization control===

In January 2025, Bambu Lab announced "Authorization Control" for its X1 series printers, introducing mandatory authentication for operations including firmware upgrades, print job initiation, and remote video access. The company cited security concerns including cyberattacks and DDoS attacks as motivation for the change.<ref name="bambu3dpi">{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |title=Bambu Lab Responds to Backlash Over New Firmware Update |website=3D Printing Industry |date=2025-01-20 |access-date=2026-01-21}}</ref>

Third-party software including OrcaSlicer faced disruption. OrcaSlicer developer SoftFever publicly declined to adopt Bambu Connect, calling it ''"unnecessary and of no meaningful benefit to users."''<ref>{{cite web |url=https://3dprintingindustry.com/news/bambu-lab-controversy-deepens-firmware-update-sparks-backlash-240588/ |title=Bambu Lab Controversy Deepens: Firmware Update Sparks Backlash |website=3D Printing Industry |date=2025-06-11 |access-date=2026-01-21}}</ref> Josef Prusa, CEO of Prusa Research, commented on LinkedIn: "Quite scary where the 3DP industry is moving – control of your data."<ref name="bambu3dpi" />

Bambu Lab introduced "Developer Mode" as a partial concession, allowing users to retain local control when enabled alongside LAN-only mode. The company did not cite firearm printing as a motivation for the authorization system.<ref>{{cite web |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |title=Updates and Third-Party Integration with Bambu Connect |website=Bambu Lab Blog |date=2025-01-20 |access-date=2026-01-21}}</ref>

===Creality root access removal===

In November 2025, Creality published a "Root Disclaimer and Risk Warning" stating its 2025 K1 Series "no longer supports Root access." Original K1 models had shipped with root access available through the settings menu. Creality positioned the change as product maturity toward "reliable products, not DIY kits," citing security concerns about malicious plugins accessing camera feeds and WiFi credentials.<ref>{{cite web |url=https://wiki.creality.com/en/k1-flagship-series/k1-series-general-documents/root-disclaimer-and-risk-warning |title=Root Disclaimer and Risk Warning |website=Creality Wiki |access-date=2026-01-21}}</ref>

==International context==

No country has mandated device-level firearm blocking technology in 3D printers.

In the United Kingdom, MP Preet Kaur Gill introduced the Firearms (3D Printing) Bill in October 2024. Clauses 43-44 of the Border Security, Asylum and Immigration Bill would criminalize making, importing, and possessing templates for 3D-printed firearms with up to 5 years imprisonment, but no device-blocking mandates are included.<ref>{{cite web |url=https://bills.parliament.uk/bills/3877 |title=Firearms (3D Printing) Bill |website=UK Parliament |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://www.preetkaurgill.co.uk/post/preet-kaur-gill-s-ghost-gun-blueprint-ban-to-become-law |title=Preet Kaur Gill's ghost gun blueprint ban to become law |website=Preet Kaur Gill MP |access-date=2026-01-21}}</ref>

Australian states have enacted penalties for possessing digital firearm blueprints. New South Wales imposes up to 14 years imprisonment under Section 51F of the Firearms Act 1996. Tasmania allows up to 21 years. No Australian jurisdiction requires device-level blocking.<ref>{{cite web |url=https://classic.austlii.edu.au/au/legis/nsw/consol_act/fa1996102/s51f.html |title=Firearms Act 1996 - Section 51F |website=Australasian Legal Information Institute |access-date=2026-01-21}}</ref>

The European Union prohibits possession of 3D-printed firearms under EU Directive 2021/555, but possession of digital blueprints is not explicitly prohibited. The Commission has stated it is assessing "the need for specific rules on the possession and trafficking of blueprints" but has not proposed device-level requirements.<ref>{{cite web |url=https://eur-lex.europa.eu/eli/dir/2021/555/oj |title=Directive 2021/555 |website=EUR-Lex |access-date=2026-01-21}}</ref><ref>{{cite web |url=https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2021:647:FIN |title=Report on the application of the Firearms Directive |website=EUR-Lex |date=2021-10-27 |access-date=2026-01-21}}</ref>

==Legislative status==

As of January 21, 2026, HB 2321 has completed first reading and remains in the Civil Rights & Judiciary Committee. No hearings have been scheduled. Neither Rep. Salahuddin nor Rep. Peterson has issued public statements explaining the bill's motivation.<ref>{{cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 |website=Washington State Legislature |access-date=2026-01-21}}</ref>

==References==
{{reflist}}

[[Category:Legislation]]
[[Category:3D printing]]
[[Category:United States]]
[[Category:Proposed legislation]]
[[Category:Right to repair]]

Washington house bill 2321 regarding 3d printers

2026-01-21T22:56:30Z

Louis: draft

{{IncidentCargo
|ProductLine=3d printers
|Product=3d printers
|Description=washington house bill 2321 seeks to require 3d printers to connect
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Flock license plate readers

2026-01-11T20:08:42Z

Louis: /* Premise of a "license plate camera" */

{{ProductCargo
|Company=Flock Safety
|ProductLine=Flock Safety Falcon
|ReleaseYear=2017
|InProduction=Yes
|ArticleType=Product
|Category=Cameras, Security, Surveillance
|Logo=Flock License plate readers (LPR).png
|Website=https://www.flocksafety.com/products/license-plate-readers
|Description=AI-powered automated license plate reader (ALPR) system that creates "Vehicle Fingerprints" by recording license plates, vehicle characteristics, and movement patterns for law enforcement use without individual consent or warrants.
}}
'''Flock License Plate Readers''' (previously known as '''Flock Safety Falcon'''<ref>{{Cite web |url=https://www.flocksafety.com/devices/falcon|title=Falcon|work=Flock Safety |access-date=6 Dec 2024 |archive-url=https://archive.ph/UjKM5 |archive-date=6 Dec 2024 |url-status=usurped}}</ref>), are a network of AI-powered surveillance cameras that record vehicle data for law enforcement agencies. The system operates in over 5,000 communities across 49 states in the U.S.A.<ref>{{Cite web |last=Hamid |first=Sarah |last2=Alajaji |first2=Rindala |date=27 Jun 2025 |title=Flock Safety's Feature Updates Cannot Make Automated License Plate Readers Safe |url=https://www.eff.org/deeplinks/2025/06/flock-safetys-feature-updates-cannot-make-automated-license-plate-readers-safe |url-status=live |archive-url=https://web.archive.org/web/20250628052030/https://www.eff.org/deeplinks/2025/06/flock-safetys-feature-updates-cannot-make-automated-license-plate-readers-safe |archive-date=28 Jun 2025 |access-date=23 Aug 2025 |work=Electronic Frontier Foundation}}</ref> According to the company's own marketing materials, Flock performs over 20 billion vehicle scans monthly.<ref>{{Cite web |title=Flock Safety |url=https://www.flocksafety.com/ |url-status=live |archive-url=https://archive.ph/iVsBZ |archive-date=26 Aug 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref>

==Consumer impact summary==
====Freedom====
Residents and taxpayers have no mechanism to opt out of [[Flock Safety]]'s surveillance network. The cameras operate 24/7 in public spaces, recording all passing vehicles regardless of consent. They are also placed on private premises like universities, hospitals, businesses, and neighborhood associations, which often share this data with law enforcement.<ref name=":0">{{Cite web |last=Brewster |first=Thomas |date=19 Jun 2024 |title=FedEx's Secretive Police Force Is Helping Cops Build An AI Car Surveillance Network |url=https://www.forbes.com/sites/thomasbrewster/2024/06/19/fedex-police-help-cops-build-an-ai-car-surveillance-network/ |url-status=live |archive-url=https://web.archive.org/web/20240619112629/https://www.forbes.com/sites/thomasbrewster/2024/06/19/fedex-police-help-cops-build-an-ai-car-surveillance-network/ |archive-date=19 Jun 2024 |access-date=25 Aug 2025 |website=Forbes}}</ref> This data can later be integrated into predictive police platforms like {{Wplink|Palantir Technologies|Palantir}}.<ref>{{Cite book |last=Rettberg |first=Jill Walker |title=Machine Vision: How Algorithms are Changing the Way We See the World |date=11 Sep 2023 |publisher=John Wiley & Sons. |year=2023 |location=Google Books |pages=45-46 |language=English}}</ref>

Unlike traditional security cameras that may be avoided by choosing different routes, Flock's expanding network of over 100,000 cameras makes avoidance increasingly difficult.<ref>{{Cite web |title=Eyes On Flock |url=https://eyesonflock.com/ |url-status=live |archive-url=https://web.archive.org/web/20251008230140/https://eyesonflock.com/ |archive-date=2025-10-08 |access-date=9 Dec 2025 |work=Eyes On Flock}}</ref> The system uses AI to create ''"Vehicle [[Device fingerprint|Fingerprints]]"'' that identify vehicles by characteristics beyond license plates, including make, model, color, aftermarket parts, window stickers, and roof racks.<ref>{{Cite web |last=Stanley |first=Jay |date=23 Jul 2025 |title=Surveillance Company Flock Now Using AI to Report Us to Police if it Thinks Our Movement Patterns Are "Suspicious" |url=https://www.aclu.org/news/national-security/surveillance-company-flock-now-using-ai-to-report-us-to-police-if-it-thinks-our-movement-patterns-are-suspicious |url-status=live |archive-url=https://web.archive.org/web/20250814053755/https://www.aclu.org/news/national-security/surveillance-company-flock-now-using-ai-to-report-us-to-police-if-it-thinks-our-movement-patterns-are-suspicious |archive-date=14 Aug 2025 |access-date=23 Aug 2025 |work=American Civil Liberties Union}}</ref>

====Privacy====
While Flock Safety claims their system doesn't violate Fourth Amendment rights because ''"license plates are not personal information,"''<ref name="Flock-PE">{{Cite web |url=https://www.flocksafety.com/privacy-ethics |title=Privacy & Ethics |work=Flock Safety |access-date=23 Aug 2025 |archive-url=https://archive.ph/OP55p |archive-date=23 Aug 2025 |url-status=live}}</ref> federal courts have challenged this interpretation. In February 2024, a federal judge ruled that a lawsuit challenging Norfolk, Virginia's use of 172 Flock cameras could proceed, finding that plaintiffs had plausibly alleged the system creates a ''"detailed chronicle of a person's physical presence compiled every day."''<ref name="norfolk">{{Cite web |last=King |first=Dan |date=6 Feb 2024 |title=Judge Rules Lawsuit Challenging Norfolk's Use of Flock Cameras Can Proceed |url=https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/ |url-status=live |archive-url=https://web.archive.org/web/20250717001536/https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/ |archive-date=17 Jul 2025 |access-date=23 Aug 2025 |work=Institute for Justice}}</ref>

Data collected includes location history that can reveal sensitive information about medical visits, religious attendance, political activities, and personal associations. While Flock states data is deleted after 30 days, contracts grant them ''"perpetual, worldwide, royalty-free license"'' to use anonymized data indefinitely.<ref name=":1">{{Cite web |title=Terms and Conditions |url=https://www.flocksafety.com/terms-and-conditions |url-status=live |archive-url=https://archive.ph/DSqUM |archive-date=26 Oct 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref> The system shares data across a network of over 4,800 law enforcement agencies nationally.<ref>{{Cite web |last=Koebler |first=Jason |date=2024 |title=Lawsuit Argues Warrantless Use of Flock Surveillance Cameras Is Unconstitutional |url=https://www.404media.co/lawsuit-argues-warrantless-use-of-flock-surveillance-cameras-is-unconstitutional/ |url-status=live |archive-url=https://web.archive.org/web/20250826013458/https://www.404media.co/lawsuit-argues-warrantless-use-of-flock-surveillance-cameras-is-unconstitutional/ |archive-date=26 Aug 2025 |access-date=23 Aug 2025 |work=404 Media}}</ref>

====="Anonymized Data"=====
While Flock's Terms and Conditions define "Anonymized Data" as customer data that is ''"permanently stripped of identifying details and any potential personally identifiable information"'' and is rendered so that a person or entity ''"can no longer be identified directly or indirectly,"'' this definition includes information such as vehicle make, model, color, location patterns, and other non–license-plate attributes.<ref name=":1" />

Privacy researchers caution that mobility datasets labeled as "anonymized" can still be re-identified. A 2013 MIT study found that just four spatio-temporal points uniquely identified 95% of individuals in an anonymized location dataset.<ref>{{Cite journal |last=de Montjoye |first=Y.-A. |last2=Hidalgo |first2=C. A. |last3=Verleysen |first3=M. |last4=Blondel |first4=V. D. |year=2013 |title=Unique in the Crowd: The privacy bounds of human mobility |url=https://www.nature.com/articles/srep01376 |journal=Scientific Reports |volume=3 |pages=1376 |doi=10.1038/srep01376 |access-date=23 Aug 2025}}</ref> Multiple peer-reviewed studies from 2018-2024 demonstrate that "anonymized" vehicle location data can be re-identified with high accuracy. A 2022 study showed researchers could re-identify drivers from raw vehicle network data with 97% accuracy by exploiting inter-dependencies in sensor measurements.<ref>{{Cite web |url=https://www.sciencedirect.com/science/article/abs/pii/S0167404822002139 |title=Privacy-preserving vehicle trajectory matching |website=ScienceDirect |date=2022 |access-date=5 Oct 2025}}</ref> Research published in the Journal of Computer Science and Technology (2022) found that even three to four location points can uniquely identify individuals.<ref>{{Cite journal |last=Sun |first=She |last2=Ma |first2=Shuai |last3=Song |first3=Jing-He |last4=Yue |first4=Wen-Hai |last5=Lin |first5=Xue-Lian |last6=Ma |first6=Tiejun |date=2022 |title=Experiments and Analyses of Anonymization Mechanisms for Trajectory Data Publishing |url=https://link.springer.com/article/10.1007/s11390-022-2409-x |journal=Journal of Computer Science and Technology |doi=10.1007/s11390-022-2409-x |access-date=5 Oct 2025}}</ref>

====Business model====
Flock operates on a subscription model charging municipalities and law enforcement agencies $2,500 USD per camera annually plus installation costs.<ref>{{Cite web|url=https://campbellca.gov/FAQ.aspx?QID=279 |title=How much does a Flock Safety camera cost? |work=City of Campbell |access-date=23 Aug 2025}}</ref> Private businesses including Home Depot, Lowe's, and FedEx also deploy cameras, sharing data with law enforcement.<ref>{{Cite web |url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops |first=Jason |last=Koebler |date=6 Aug 2025 |work=404 Media |access-date=23 Aug 2025 |archive-url=https://web.archive.org/web/20250823135847/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |archive-date=23 Aug 2025 |url-status=live}}</ref><ref name=":0" /> Contracts include automatic renewal clauses and limit municipal oversight capabilities, with cities unable to audit system operations or control how other agencies use shared data.<ref>{{Cite web |url=https://www.aclu.org/wp-content/uploads/publications/flock_1.pdf |title=How to Pump the Brakes on Your Police Department's Use of Flock's Mass Surveillance License Plate Readers |work=American Civil Liberties Union |date=2024 |access-date=23 Aug 2025}}</ref>

====Market control====
Flock Safety has rapidly expanded to become a dominant force in automated license plate recognition, operating in 49 states with over 40,000 cameras deployed. The company's network effect creates pressure for additional jurisdictions to join, as law enforcement effectiveness depends on network coverage. Several states have begun restricting access following privacy violations, with California, Illinois, and New York limiting data sharing after immigration and abortion-related tracking incidents.<ref>{{Cite web |url=https://www.michaelrcronin.com/post/flock-blocks-ice-from-license-plate-reader-access-in-several-states |title='Flock' Blocks ICE from License Plate Reader Access in Several States |work=Yes You Can Go |date=2025 |access-date=23 Aug 2025}}</ref>

===Premise of a "license plate camera"===
While marketed as "license plate readers,"' Flock cameras use what the company calls "Vehicle Fingerprint" technology which tracks vehicles using characteristics beyond just license plates. The system catalogs vehicles based on numerous distinguishing features including make, model, color, bumper stickers, dents, damage patterns, roof racks, aftermarket modifications such as wheels or spoilers, window stickers, and even mismatching paint colors.<ref name=":2">{{Cite web |date= |title=LPR Cameras |url=https://www.flocksafety.com/products/license-plate-readers |url-status=usurped |access-date=26 Oct 2025 |work=Flock Safety}}</ref>. According to Flock's own marketing materials, the system can identify vehicles even when license plates cannot be captured, advertised as turning "images into actionable evidence — no plate required."<ref>{{Cite web |title=License Plate Readers |url=https://www.flocksafety.com/products/license-plate-readers |url-status=live |archive-url=https://archive.ph/D9JGD |archive-date=23 Aug 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref>

Flock claims this capability is ''"unique among ALPR systems"'' and allows law enforcement to search for vehicles based on these characteristics even without a visible license plate.

This technology changes the nature of the surveillance from license plate reading to comprehensive vehicle tracking. A person could still be tracked by the unique combination of their vehicle's physical characteristics. The Electronic Frontier Foundation warns that these ''"vehicle fingerprints"'' could flag vehicles based on political bumper stickers, revealing ''"information on the political or social views of the driver,"'' or economic indicators like rust or damage, potentially "endangering anyone who might not feel the need (or have the income required) to keep their car in perfect shape."<ref>{{Cite web |date=2020-09-14 |title=Things to Know Before Your Neighborhood Installs an Automated License Plate Reader |url=https://www.eff.org/deeplinks/2020/09/flock-license-plate-reader-homeowners-association-safe-problems |access-date=2025-08-23 |work=Electronic Frontier Foundation}}</ref>

Privacy advocates note that this expanded tracking capability makes the term ''"license plate reader"'' misleading, as Flock systems create detailed vehicle profiles that persist even without readable plates. It turns any distinguishing feature of a vehicle into a tracking identifier.<ref>{{Cite web |title=Stop Flock |url=https://www.stopflock.com/ |access-date=2025-08-23 |work=Stop Flock}}</ref>

==Patent for person identification by race and physical characteristics==
A U.S. Patent granted to Flock Group Inc. in August 2022 reveals the company has developed and patented technology to identify and classify people based on race, gender, and other physical characteristics.<ref name="patent11416545">{{Cite web |url=https://patentimages.storage.googleapis.com/77/9a/03/7b3b26499077d4/US11416545.pdf |title=System and Method for Object Based Query of Video Content Captured by a Dynamic Surveillance Network |website=United States Patent and Trademark Office |date=16 Aug 2022 |access-date=21 Jan 2025 |format=PDF |first1=Garrett |last1=Langley |first2=Matt |last2=Feury }}</ref> Patent US 11,416,545 B1 describes a system that goes beyond vehicle identification to analyze human subjects captured in surveillance footage.

According to the patent documentation, when the system identifies a human being in captured footage, it uses neural network modules specifically configured to classify people by "male, female, race, etc." The patent further describes using additional neural networks to identify clothing types, estimate height and weight, and other physical characteristics of individuals.<ref name="patent11416545" /> The system can then store this classification data in searchable databases, allowing law enforcement to query for people based on these physical attributes.

The patent shows that Flock's technology is designed to create comprehensive profiles that can track individuals across multiple camera locations by matching physical characteristics. While Flock publicly markets its products as ''"license plate readers"'' focused on vehicles, this patent demonstrates the company has developed capabilities for detailed human surveillance and classification by protected characteristics including race and gender.<ref name="patent11416545" />

Privacy advocates have raised concerns that this technology could enable discriminatory policing practices and racial profiling at scale.{{Citation needed}} The ability to search for people by race or other physical characteristics across a network of thousands of cameras is a large expansion of surveillance capabilities beyond what is typically disclosed in Flock's public marketing materials.{{Citation needed}}

==Legal challenges==

===Washington state judge declares Flock footage as public records ''(6 Nov 2025)''===
An Oregon resident filed public records requests at various police departments in the state of Washington regarding information collected from Flock cameras. The cities of Stanwood and Sedro-Woolley filed a motion to reject the resident's request, with their attorney stating that publicizing Flock footage may be a violation of privacy that could lead to stalking.

Some exemptions are given to deny public records request, particularly due to investigations. However, the judge dismissed the motion, declaring that the camera footage was "so broad and indiscriminate" with no distinction between criminal activity and casual civilian activity that the data had to be released to the public.<ref>{{Cite web |last=Ingalls |first=Chris |date=6 Nov 2025 |title=Judge orders police to release surveillance camera data, raising privacy questions |url=https://www.king5.com/article/news/investigations/investigators/judge-orders-washington-police-release-surveillance-camera-data-privacy-questions/281-c2037d52-6afb-4bf7-95ad-0eceaf477864 |access-date=8 Nov 2025 |website=KING5}}</ref><ref name=":5">{{Cite web |last=Peterson |first=Jenna |date=6 Nov 2025 |title=Judge denies request to exempt Flock footage from Public Records Act |url=https://www.heraldnet.com/news/judge-denies-request-to-exempt-flock-footage-from-public-records-act/ |access-date=8 Nov 2025 |website=Herald Net}}</ref>

The judge stated:<ref name=":5" /><blockquote>“I do think that the information at stake does have serious privacy implications, but that’s not the analysis for the intelligence information exemption,” she said. “You also have to make a finding that this is specific intelligence information that is compiled by investigative or law enforcement agencies, and the information that’s being compiled here does not relate to a specific case or investigation. The public already knows that these cameras exist and are operated. Many of them are in sight. The information does not disclose particular methods or procedures for gathering or evaluating intelligence information.” </blockquote>

===Norfolk federal lawsuit ''(February 2025)''===
In February 2025, Chief Judge Mark S. Davis of the U.S. District Court for the Eastern District of Virginia denied Norfolk's motion to dismiss a landmark Fourth Amendment lawsuit. The case involves two residents whose vehicles were tracked 526 times in 4.5 months and 849 times over the same period, figures revealed in a September 2025 court filing.<ref>{{Cite web|url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399|title=Virginia police used Flock cameras to track driver 526 times in 4 months, lawsuit says|work=NBC News|date=2025-09-18|access-date=2025-08-23}}</ref> Norfolk installed 172 Flock Safety cameras in 2023 at a cost of $430,000-$516,000 annually. Police Chief Mark Talbot stated the goal was making it ''"difficult to drive anywhere of any distance without running into a camera somewhere."''<ref name="norfolk" />

Judge Davis's ruling relied on ''Carpenter v. United States'', the 2018 Supreme Court decision requiring warrants for historical cell phone location data. The court found Norfolk's ALPR network "notably similar" to the surveillance the Supreme Court deemed unconstitutional. However, courts remain divided. In November 2024, Senior U.S. District Judge Robert E. Payne in the same district denied a motion to suppress Flock evidence, holding that three vehicle snapshots don't constitute "persistent surveillance" requiring a warrant.<ref>{{cite web|url=https://valawyersweekly.com/2024/11/11/mosaic-theory-rejected-flock-camera-evidence-does-not-violate-fourth-amendment/|title='Mosaic theory' rejected: Flock camera evidence does not violate Fourth Amendment|website=Virginia Lawyers Weekly|date=2024-11-11|access-date=2025-10-05}}</ref>

Virginia state courts show similar disagreement. Norfolk Circuit Court Judge Jamilah LeCruise granted a suppression motion in May 2024, finding that the breadth of Flock cameras covering Norfolk requires a warrant.<ref>{{cite web|url=https://www.govtech.com/public-safety/virginia-judge-rejects-alpr-evidence-without-warrant|title=Virginia Judge Rejects ALPR Evidence Without Warrant|website=Government Technology|date=2024-05-15|access-date=2025-10-05}}</ref> Yet three other Norfolk circuit court judges denied similar motions in 2024.

===State regulatory landscape===
Only 16 states have enacted any form of ALPR regulation as of 2024 according to University of Michigan research.<ref>{{cite web|url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse|title=Automated License Plate Readers widely used, subject to abuse|website=University of Michigan|date=2023|access-date=2025-10-05}}</ref> Virginia enacted House Bill 2724 in 2025 creating annual reporting requirements.<ref>{{cite web|url=https://vscc.virginia.gov/Annual%20Reports/2024%20VSCC%20Annual%20Report%20-Law%20Enforcement%20Use%20of%20ALPR.pdf|title=2024 VSCC Annual Report - Law Enforcement Use of ALPR|website=Virginia State Crime Commission|date=2024|access-date=2025-10-05}}</ref> Illinois Public Act 103-0540 explicitly prohibits use for reproductive healthcare punishment and immigration investigations.<ref>{{cite web|url=https://www.ilga.gov/legislation/publicacts/103/103-0540.htm|title=Public Act 103-0540|website=Illinois General Assembly|date=2024|access-date=2025-10-05}}</ref>

Illinois prohibits law enforcement agencies from sharing ALPR data with other jurisdictions in relation to a person's immigration status.<ref>{{Cite web |title=Public Act 103-0540 |url=https://www.ilga.gov/documents/legislation/publicacts/103/PDF/103-0540.pdf |url-status=usurped |access-date=23 Aug 2025 |work=Illinois General Assembly}}</ref> New Hampshire requires a three-minute purge of data from ALPR use with the exception of ongoing investigations. <ref>{{Cite web |title=261:75-b Use of Number Plate Scanning Devices Regulated. |url=https://law.justia.com/codes/new-hampshire/title-xxi/chapter-261/section-261-75-b/ |url-status=usurped |access-date=23 Aug 2025 |work=New Hampshire General Court}}</ref>

California’s SB 34 requires public agencies using ALPR systems to implement usage and privacy policies as well as limits to data sharing. <ref name=":3">{{Cite web |url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB34 |title=SB-34 Automated license plate recognition systems: use of data |work=California Legislative Information |access-date=23 Aug 2025}}</ref> However, enforcement remains inconsistent, with a 2020 state audit finding widespread non-compliance.<ref>{{Cite web |url=https://www.auditor.ca.gov/reports/2019-118/index.html |title=Automated License Plate Readers |work=California State Auditor |date=13 Feb 2020 |access-date=23 Aug 2025}}</ref>

==Notable incidents==

====Illinois audit findings (2024-2025)====
Illinois Secretary of State Alexi Giannoulias announced in late August 2024 that Flock Safety violated state law by allowing U.S. Customs and Border Protection to access Illinois license plate data for immigration enforcement.<ref>{{cite web|url=https://www.flocksafety.com/blog/flock-safetys-response-to-illinois-lpr-data-use-and-out-of-state-sharing-concerns|title=Flock Safety's Response to Illinois LPR Data Use and Out-of-State Sharing Concerns|website=Flock Safety|date=2024-08-25|access-date=2025-10-05}}</ref> The audit of 12 local law enforcement agencies revealed unauthorized pilot programs with CBP and Homeland Security Investigations, violating Illinois law prohibiting data sharing for immigration enforcement, gender-affirming care investigations, and abortion-related matters. Following the audit, 47 out-of-state agencies were removed from access to Illinois data.<ref>{{cite web|url=https://www.govtech.com/biz/flock-pledges-changes-after-illinois-data-sharing-accusation|title=Flock Pledges Changes After Illinois Data-Sharing Accusation|website=Government Technology|date=2024-08-15|access-date=2025-10-05}}</ref>

Mount Prospect, Illinois reported 262 immigration-related license plate reader searches in just the first few months of 2025. A Palos Heights detective shared Flock login credentials with a DEA agent who conducted 28 unauthorized searches of Oak Park ALPR data explicitly labeled "immigration violation."<ref name="dea">{{Cite web|url=https://unraveledpress.com/a-dea-agent-used-an-illinois-police-officers-flock-license-plate-reader-password-for-unauthorized-immigration-enforcement-searches/|title=DEA agent used Illinois cop's Flock license plate reader password for immigration enforcement searches|work=Unraveled Press|date=2025|access-date=2025-08-23}}</ref>

====California violations (2015-2025)====
California passed Senate Bill 34<ref>{{Cite web|url=https://calmatters.digitaldemocracy.org/bills/ca_201520160sb34|title=Senate Bill 34|access-date=2025-08-27}}</ref> in 2015 to limit how California police departments can use and share data collected from these cameras with other state's and federal law enforcement agencies. These limits have been found to be violated on several occasions with little enforcement or consequences for the misusing departments<ref>{{Cite web|url=https://sfstandard.com/2025/07/23/california-police-sharing-flock-license-plate-data/|access-date=2025-08-27|title=California cops are breaking surveillance laws|website=San Francisco Standard|date=2025-07-23}}</ref>.

A 2023 EFF investigation found 71 California police agencies in 22 counties illegally shared data with out-of-state law enforcement. San Francisco Police Department alone allowed 1.6 million illegal searches by out-of-state agencies from 2024-2025.<ref>{{cite web|url=https://sfstandard.com/2025/09/08/sfpd-flock-alpr-ice-data-sharing/|title=SFPD let Georgia, Texas cops illegally search city surveillance data on behalf of ICE|website=San Francisco Standard|date=2025-09-08|access-date=2025-10-05}}</ref> The California Attorney General filed the first enforcement action against the City of El Cajon in 2025 for sharing with 26 states.<ref>{{cite web|url=https://oag.ca.gov/news/press-releases/attorney-general-bonta-sues-el-cajon-illegally-sharing-license-plate-data-out|title=Attorney General Bonta Sues El Cajon for Illegally Sharing License Plate Data|website=California DOJ|date=2025|access-date=2025-10-05}}</ref>

===False positive incidents===

====Families detained at gunpoint====
In Española, New Mexico, 21-year-old Jaclynn Gonzales and her 12-year-old sister were held at gunpoint and handcuffed after Flock's system mistook a "2" for a "7" on their license plate, falsely flagging their vehicle as stolen.<ref>{{Cite news |date=2023-09-28 |title=License plate cover leads to traffic stop mishap |url=https://www.koat.com/article/espanola-police-license-plate-stolen-cover-traffic-stop/45361740|website=KOAT|access-date=2025-08-23}}</ref><ref>{{Cite web |date=2025 |title=Flock Safety: Eroding Your Privacy & Keeping You Safe with Surveillance |url=https://redact.dev/blog/flock-safety-lpr-privacy-surveillance/ |access-date=2025-08-23 |work=Redact}}</ref>

ALPR systems often misread license plates according to multiple investigations, leading to hardship & legal trouble for innocent civilians.<ref>{{cite web|url=https://www.eff.org/deeplinks/2024/11/human-toll-alpr-errors|title=The Human Toll of ALPR Errors|website=Electronic Frontier Foundation|date=2024-11-15|access-date=2025-10-05}}</ref>

===Law enforcement stalking incidents===

In October 2022, Kechi, Kansas Police Lieutenant Victor Heiar was arrested and later pleaded guilty to computer crimes and stalking after using Flock cameras to track his estranged wife's movements over four months.<ref>{{Cite web|url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/|title=Kechi police lieutenant arrested for using police technology to stalk wife|work=KWCH|date=2022-10-31|access-date=2025-08-23}}</ref> In a separate Kansas incident, Sedgwick Police Chief Lee Nygaard accessed Flock data 164 times to track his ex-girlfriend before resigning after admitting to the misuse.<ref>{{Cite web|url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html|title=Kansas police chief used Flock license plate cameras 164 times to track ex-girlfriend|work=Yahoo News|date=2025|access-date=2025-08-23}}</ref>

Multiple other documented cases include Las Vegas Metro Officer Christopher Young arrested in December 2023 for stalking his ex-fiancée using police databases, and Riverside County Deputy Eric Piscatella pleading guilty in February 2024 to seven counts of misusing sheriff's department databases to stalk a woman he met at Coachella.<ref>{{cite web|url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/?outputType=amp|title=Las Vegas police officer arrested for reportedly stalking ex-fiancée|website=FOX5 Vegas|date=2024-02-16|access-date=2025-10-05}}</ref>

===Abortion and reproductive healthcare tracking===
In May 2025, Johnson County, Texas sheriff's deputies used Flock's network to track a woman suspected of self-managing an abortion. They conducted searches across 83,000+ Flock cameras nationwide with the explicit reason: "had an abortion, search for female." The search accessed cameras across multiple states including those where abortion is legal. The incident led Illinois officials to investigate and subsequently block 47+ out-of-state agencies from accessing Illinois ALPR data.<ref>{{Cite web|url=https://www.dallasnews.com/news/texas/2025/06/13/after-finding-fetal-remains-north-texas-cops-used-camera-network-to-search-for-woman/|title=After finding fetal remains, North Texas cops used camera network to search for woman|work=The Dallas Morning News|date=2025-06-13|access-date=2025-08-23}}</ref><ref>{{cite web|url=https://www.eff.org/deeplinks/2025/05/she-got-abortion-so-texas-cop-used-83000-cameras-track-her-down|title=She Got an Abortion. So A Texas Cop Used 83,000 Cameras to Track Her Down|website=Electronic Frontier Foundation|date=2025-05-15|access-date=2025-10-05}}</ref>

Investigations and court records show that some law enforcement officers have misused Flock Safety automated license plate reader (ALPR) systems for personal, non-investigative purposes, including stalking romantic partners or monitoring civilians. These incidents highlight weaknesses & lack of internal oversight, & the reliance on post-hoc audits rather than real-time safeguards.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after allegedly using the department’s Flock ALPR system to track his ex-girlfriend.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09 |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex}}</ref> Prosecutors alleged Morales conducted five unauthorized searches of his ex-partner’s vehicle in October 2025. According to the criminal complaint, Morales admitted he knew the searches were improper and cited “desperation and bad judgment.” He was placed on administrative leave, prohibited from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref> Court records also show a related civil filing seeking a temporary restraining order in a domestic abuse case.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref>

The Menasha case matches what is becoming a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes & stalking after using Flock cameras to monitor his estranged wife’s movements over several months.<ref>{{cite news |title=Kechi police lieutenant arrested for using police technology to stalk wife |work=KWCH |date=2022-10-31 |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/}}</ref> In another Kansas incident, Sedgwick Police Chief Lee Nygaard admitted in 2025 to accessing Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, resulting in his resignation and loss of police certification.<ref>{{cite news |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |work=Yahoo News |date=2025 |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html}}</ref>

More cases involving other surveillance systems show a similar misuse. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing sheriff’s department databases to stalk a woman he met while off duty.<ref>{{cite news |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |work=FOX5 Vegas |date=2024-02-16 |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/}}</ref>

Oversight reviews & civil liberties organizations have noted that ALPR systems enable quick searches of historical vehicle location data across wide geographic areas. This reduces practical barriers to stalking & increases the risk of abuse by authorized users. While Flock & participating agencies rely on usage policies & access logs, many cases show misuse was detected only after complaints or later audits rather than through proactive safeguards.<ref>{{cite web |title=Automated License Plate Readers widely used, subject to abuse |work=University of Michigan |date=2023 |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse}}</ref><ref>{{cite web |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |work=Government Technology |date=2024 |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps}}</ref>

===Federal agency access===
Immigration and Customs Enforcement maintains a $6.1 million contract giving 9,000+ ICE officers access to the Vigilant Solutions ALPR database containing over 5 billion location data points.<ref>{{cite web|url=https://www.aclu.org/news/immigrants-rights/documents-reveal-ice-using-driver-location-data|title=Documents Reveal ICE Using Driver Location Data From Local Police for Deportations|website=ACLU|date=2024|access-date=2025-10-05}}</ref> The Drug Enforcement Administration operates a National License Plate Reader Program with over 10,000 license plate readers shared throughout the United States. 404 Media revealed over 4,000 searches by local and state police for federal immigration enforcement purposes, despite Flock having no formal ICE contract.<ref>{{Cite web|url=https://www.404media.co/ice-taps-into-nationwide-ai-enabled-camera-network-data-shows/|title=ICE Taps into Nationwide AI-Enabled Camera Network, Data Shows|work=404 Media|date=2025|access-date=2025-08-23}}</ref> A DEA agent was found using an Illinois police officer's credentials to conduct unauthorized immigration searches.<ref name="dea" />

===Illegal Camera Installations===
In South Carolina, Flock installed over 200 cameras without authorization, leading to a statewide moratorium on new installations.<ref>{{Cite web |last=Ferrara |first=David |date=2024-03-11 |title=A company installed license plate cameras without permission. SC agency wants clear rules |url=https://www.postandcourier.com/news/alpr-cameras-south-carolina-flock-safety-license-plate-readers/article_787a262a-dbd2-11ee-a901-634acead588b.html |url-status=live |access-date=2025-08-25 |website=The Post and Courier}}</ref>

In Illinois, a Flock representative allegedly threatened a Department of Transportation official with police pressure when questioned about permit applications.<ref>{{Cite web |last=Uprise RI Staff |date=2024-10-23 |title=As Flock Surveillance Cameras Proliferate in Rhode Island, Lawsuit Challenges Their Legality |url=https://upriseri.com/as-flock-surveillance-cameras-proliferate-in-rhode-island-lawsuit-challenges-their-legality/ |url-status=live |access-date=2025-08-25 |website=UPRISE RI}}</ref>

====='''Evanston, IL'''=====
Flock was ordered to remove 18 stationary cameras. The city put the contract with Flock on a 30-day termination notice on August 26. Flock Initially appeared to comply, removing 15 of the cameras by September 8. Later, Flock was caught reinstalling all of them by the following Tuesday without authorization from the city. The city of Evanston responded with a cease-and-desist order for Flock to remove the new and unauthorized camera equipment. Because Flock reinstalled the cameras without permission, Evanston was forced to cover the cameras with tape and bags to block them from potentially logging vehicle data.<ref>{{Cite web |last=Harrison |first=Alex |date=2025-09-25 |title=City covers Flock cameras while waiting for removal |url=https://evanstonroundtable.com/2025/09/25/city-covers-up-flock-cameras-while-waiting-for-removal/ |url-status=live |archive-url=https://archive.ph/PD1qe |archive-date=2025-10-10 |access-date=2025-10-10 |website=Evanston Roundtable}}</ref>

===City rejections and terminations===

Multiple cities have rejected or terminated Flock contracts following privacy concerns and effectiveness issues:

'''0.2% effectiveness rate, low arrests:''' Austin, Texas terminated its contract in July 2025 after an audit revealed "systematic compliance failures" and only 165 arrests from 113 million license plate scans (0.146% effectiveness rate).<ref>{{Cite web|url=https://cbsaustin.com/news/local/flock-ceo-responds-to-austin-backlash-as-city-contract-nears-expiration|title=Flock CEO responds to Austin backlash as city contract nears expiration|work=CBS Austin|date=2025-06-21|access-date=2025-08-23}}</ref>

Denver City Council unanimously rejected a $666,000 contract extension in May 2025 following revelations of 1,400+ ICE-related searches in Colorado data.<ref>{{Cite web|url=https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/|title=Denver rejects $666,000 extension for license-plate surveillance cameras after backlash|work=Denverite|date=2025-05-05|access-date=2025-08-23}}</ref>

San Marcos, Texas voted 5-2 to deny camera expansion after discovering no required audits had been conducted since 2022.<ref>{{Cite web |last=Velez |first=Abigail |date=2025-06-04 |title=San Marcos City Council votes to deny flock camera expansion after hours of heated debate |url=https://cbsaustin.com/news/local/san-marcos-city-council-votes-to-deny-flock-camera-expansion-after-hours-of-heated-debate |access-date=2025-08-23 |work=CBS Austin}}</ref>

Oak Park, Illinois terminated their contract entirely following the Illinois investigation into illegal data sharing.<ref>{{Cite web|url=https://www.oakpark.com/2025/08/07/oak-park-terminates-flock-license-plate-reader-contract/|title=Oak Park terminates Flock license plate reader contract|work=Wednesday Journal|date=2025-08-07|access-date=2025-08-23}}</ref>

===Arizona deployments===
Sedona, Arizona became the first Arizona city to completely terminate its Flock Safety contract in September 2025 after citizen backlash. The city had installed 11 cameras in June 2025 without prior public notice at a cost of $51,146 for the first year. The council voted 5-1 to pause the program, then unanimously 7-0 on September 9 to permanently terminate after Flock CEO Garrett Langley admitted the company had been sharing data with federal agencies. Vice Mayor Holli Ploog called Flock "not an honorable company" for the conflicting data-sharing claims.<ref>{{cite web|url=https://westvalleyfamilies.substack.com/p/sedona-pulls-the-plug-on-flock-safety|title=Sedona Pulls the Plug on Flock Safety|website=West Valley Families|date=2025-09-10|access-date=2025-10-05}}</ref><ref>{{cite web|url=https://www.knau.org/knau-and-arizona-news/2025-09-11/sedona-council-permanently-ends-license-plate-camera-program|title=Sedona council permanently ends license plate camera program|website=KNAU|date=2025-09-11|access-date=2025-10-05}}</ref>

Flagstaff deployed 32 Flock cameras in summer 2024 at a cost of $143,100 annually. By September 2025, a petition signed by 25+ residents demanded cancellation.<ref>{{cite web|url=https://www.kjzz.org/fronteras-desk/2025-09-01/after-sedona-paused-flock-safety-camera-system-flagstaff-is-considering-the-same-issue|title=After Sedona paused Flock Safety camera system, Flagstaff is considering the same issue|website=KJZZ|date=2025-09-01|access-date=2025-10-05}}</ref>

University of Arizona contracted with Flock in February 2025 for 54 ALPR cameras at $160,000 annually. Students and faculty launched a "Deflock Tucson" campaign citing concerns about tracking international students and potential data sharing with federal immigration authorities.<ref>{{cite web|url=https://azluminaria.org/2025/09/15/ua-students-and-faculty-question-use-of-flock-safety-cameras-on-campus/|title=UA students and faculty question use of Flock Safety cameras on campus|website=AZ Luminaria|date=2025-09-15|access-date=2025-10-05}}</ref>

Casa Grande approved a $10 million "Safe City Initiative" in September 2025 including 100 license plate readers. Chief Mark McCrory reported the current 22 license plate readers led to 212 stolen vehicles identified and 168 arrests.<ref>{{cite web|url=https://www.inmaricopa.com/we-mapped-all-flock-cameras/|title=We mapped the city's Flock cameras|website=InMaricopa|date=2025|access-date=2025-10-05}}</ref>

Despite documented deployments across Arizona including Phoenix, Mesa, Chandler, Scottsdale, Tempe, Surprise, Youngtown, Litchfield Park, and Yuma, the state has no ALPR-specific regulation.<ref>{{cite web|url=https://azmirror.com/2019/07/08/how-do-automated-license-plate-readers-work/|title=How do automated license plate readers work?|website=Arizona Mirror|date=2019-07-08|access-date=2025-10-05}}</ref>

==Security vulnerabilities==
In 2025, Flock Safety reported security vulnerabilities in its devices and submitted them to MITRE for inclusion in the National Vulnerability Database, including issues such as hard-coded credentials and improper access controls.<ref>{{Cite web |date=2025-05-05 |title=Gunshot Detection and License Plate Reader Security Alert |url=https://www.flocksafety.com/blog/gunshot-detection-and-license-plate-reader-security-alert |website=Flock Safety}}</ref><ref>{{Cite web |date=2025-10-02 |title=CVE-2025-59403 : The Flock Safety Android Collins application (aka com.flocksafety.android.collin |url=https://www.cvedetails.com/cve/CVE-2025-59403/ |website=CVEdetails.com}}</ref> Similar security concerns have affected other ALPR systems, including exposure of default passwords and unencrypted data storage.<ref name=":4">{{Cite web |last=Quintin |first=Cooper |date=28 Oct 2015 |title=License Plate Readers Exposed! How Public Safety Agencies Responded to Major Vulnerabilities in Vehicle Surveillance Tech |url=https://www.eff.org/ur/deeplinks/2015/10/license-plate-readers-exposed-how-public-safety-agencies-responded-massive |website=Electronic Frontier Foundation}}</ref>

This represents one of several major security disclosures in the past decade. In 2015, the Electronic Frontier Foundation documented more than 100 ALPR cameras accessible on the open internet, often without passwords or proper configuration.<ref name=":4" /> A more serious documented breach occurred in 2019, when Perceptics, LLC, a subcontractor for U.S. Customs and Border Protection, exposed approximately 105,000 license plate images and 184,000 traveler facial images.<ref>{{Cite web |title=Review of CBP's Major Cybersecurity Incident During a 2019 Biometric Pilot |url=https://www.oig.dhs.gov/sites/default/files/assets/2020-09/OIG-20-71-Sep20.pdf}}</ref>

In 2025 it has been discovered that the cameras run [[wikipedia:Android_Oreo|Android 8.0 (Oreo)]] an operating system with 90 security vulnerabilities. The cameras also send data unencrypted and are easily tricked by stingrays. The compute boxes have easily accessible USB-c ports leaving the device vulnerable to rubber duckies. When the power button is pressed in a specific order the device emits a Wi-Fi hotspot that can be used to gain adb access.<ref>{{Cite web |last=Benn |first=Jordan |date=2025-11-16 |title=We Hacked Flock Safety Cameras in under 30 Seconds. |url=https://www.youtube.com/watch?v=uB0gr7Fh6lY |website=YouTube}}</ref>

==Government accountability and oversight==

===State audit findings===
California State Auditor's February 2020 investigation found the Los Angeles Police Department (LAPD), with a 320 million image database, had no ALPR-specific policy at all. The audit found 96% of agencies claim to have policies, but most are incomplete. Data retention periods varied wildly with no justification. LAPD maintained a minimum five-year retention period, yet couldn't demonstrate that images stored for years had investigative value. The audit found that 99.9% of the 320 million images Los Angeles stores are for vehicles that were not on a "hot list" when the image was made.<ref>{{Cite web |url=https://information.auditor.ca.gov/reports/2019-118/summary.html |title=Automated License Plate Readers |website=California State Auditor |date=13 Feb 2020 |access-date=5 Oct 2025}}</ref>

New Jersey provides a contrasting model with mandatory annual audits of all 523 law enforcement agencies. The 2024 audit reported only two significant violations, both involving users who hadn't completed required training.<ref>{{Cite web |url=https://nj.gov/njsp/ALPR/pdf/2024_Audit_Automated_License_Plate_Recognition_(ALPR)_Data_Collected_Utilized_NJ_Law_Enforcement_Agencies.pdf |title=2024 Audit of Automated License Plate Recognition (ALPR) Data |website=New Jersey State Police |date=2024 |access-date=5 Oct 2025 |format=PDF}}</ref>

A Government Technology analysis found that agencies often fail to audit ALPR systems regularly, leaving them "open to abuse by neglecting to institute sufficient oversight."<ref>{{Cite web |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |website=Government Technology |date=2024 |access-date=5 Oct 2025}}</ref>

===Cost-benefit analysis===
Arizona Department of Transportation's 2008 study of generic ALPR technology (predating Flock Safety by nine years) estimated $9.98 million for a hypothetical statewide ALPR system. The projected benefit-to-cost ratio of 9.6:1 came entirely from registration and insurance compliance, not crime reduction.<ref>{{Cite web |url=https://apps.azdot.gov/files/ADOTLibrary/publications/project_reports/PDF/AZ637.pdf |title=Automated License Plate Recognition Technology Implementation Report |website=Arizona Department of Transportation |date=1 Jun 2008 |access-date=5 Oct 2025}}</ref>

Colorado's Office of Research and Statistics reported that while ALPR systems are expanding, independent academic research contradicts vendor claims. A 2011 George Mason University study concluded ALPRs "do not achieve a prevention or deterrent effect" on crime.<ref>{{Cite web |url=https://cdpsdocs.state.co.us/ors/Docs/Briefs/2024-05_InDetail-ALPR.pdf |title=Automated License Plate Readers (In Detail) |website=Colorado Division of Criminal Justice |date=1 May 2024 |access-date=5 Oct 2025 |format=PDF}}</ref>

Oakland Police Department reported 182 arrests from ALPR in the first year, representing 1.4% of homicides, robberies, burglaries, and firearm assaults. The Northern California Regional Intelligence Center states approximately 1-2 vehicles out of 1,000 initiate alerts — a hit rate of just 0.1-0.2%.<ref>{{Cite web |url=https://ncric.ca.gov/wp-content/uploads/2021/10/California-Law-Enforcement-ALPR-FAQ.pdf |title=California Law Enforcement ALPR FAQ |website=NCRIC |date=2021 |access-date=5 Oct 2025 |format=PDF}}</ref>

==Camera locations==
The locations of many Flock Cameras have been mapped by the OpenStreetMap project. A viewer of the locations of these cameras is located here: [https://deflock.me/map ALPR Map | DeFlock]

====Cease and desist to DeFlock.me====
DeFlock.me is a website allowing users to log and view the locations of ALPRs, such as Flock products. On 30 January 2025, Flock sent a cease and desist notice to the owner of DeFlock demanding the name of the website be changed to exclude the company's brand name. The letter also stated that "the Website also implies that various license plate readers are vulnerable to security hacks [...]" which Flock alleged "[...] provides a false impression about the security of Flock Products."<ref>{{Cite web |last=Matz |first=Sarah M. |title=2025 01 31 DEFLOCK CD final |url=https://www.eff.org/files/2025/02/26/2025_01_31_deflock_cd_ex-3.pdf |website=Electronic Frontier Foundation |date=30 Jan 2025 |access-date=27 Oct 2025 |url-status=live |format=PDF}}</ref>

==External links==
*[https://deflock.me/ DeFlock live map of active ALPRs]
*[https://www.noalprs.org/ No ALPRS movement in United States]
*[https://plateprivacy.com/ The Plate Privacy Project]
*[https://eyesonflock.com/ Eyes On Flock]
*[https://wiki.alprwatch.org/index.php/Main_Page ALPR Watch Wiki]

==References==
{{Reflist}}

[[Category:Automatic license plate readers]]
[[Category:Flock Safety]]

Flock license plate readers

2026-01-11T18:15:22Z

Louis: added menasha wisconsin case

{{ProductCargo
|Company=Flock Safety
|ProductLine=Flock Safety Falcon
|ReleaseYear=2017
|InProduction=Yes
|ArticleType=Product
|Category=Cameras, Security, Surveillance
|Logo=Flock License plate readers (LPR).png
|Website=https://www.flocksafety.com/products/license-plate-readers
|Description=AI-powered automated license plate reader (ALPR) system that creates "Vehicle Fingerprints" by recording license plates, vehicle characteristics, and movement patterns for law enforcement use without individual consent or warrants.
}}
'''Flock License Plate Readers''' (previously known as '''Flock Safety Falcon'''<ref>{{Cite web |url=https://www.flocksafety.com/devices/falcon|title=Falcon|work=Flock Safety |access-date=6 Dec 2024 |archive-url=https://archive.ph/UjKM5 |archive-date=6 Dec 2024 |url-status=usurped}}</ref>), are a network of AI-powered surveillance cameras that record vehicle data for law enforcement agencies. The system operates in over 5,000 communities across 49 states in the U.S.A.<ref>{{Cite web |last=Hamid |first=Sarah |last2=Alajaji |first2=Rindala |date=27 Jun 2025 |title=Flock Safety's Feature Updates Cannot Make Automated License Plate Readers Safe |url=https://www.eff.org/deeplinks/2025/06/flock-safetys-feature-updates-cannot-make-automated-license-plate-readers-safe |url-status=live |archive-url=https://web.archive.org/web/20250628052030/https://www.eff.org/deeplinks/2025/06/flock-safetys-feature-updates-cannot-make-automated-license-plate-readers-safe |archive-date=28 Jun 2025 |access-date=23 Aug 2025 |work=Electronic Frontier Foundation}}</ref> According to the company's own marketing materials, Flock performs over 20 billion vehicle scans monthly.<ref>{{Cite web |title=Flock Safety |url=https://www.flocksafety.com/ |url-status=live |archive-url=https://archive.ph/iVsBZ |archive-date=26 Aug 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref>

==Consumer impact summary==
====Freedom====
Residents and taxpayers have no mechanism to opt out of [[Flock Safety]]'s surveillance network. The cameras operate 24/7 in public spaces, recording all passing vehicles regardless of consent. They are also placed on private premises like universities, hospitals, businesses, and neighborhood associations, which often share this data with law enforcement.<ref name=":0">{{Cite web |last=Brewster |first=Thomas |date=19 Jun 2024 |title=FedEx's Secretive Police Force Is Helping Cops Build An AI Car Surveillance Network |url=https://www.forbes.com/sites/thomasbrewster/2024/06/19/fedex-police-help-cops-build-an-ai-car-surveillance-network/ |url-status=live |archive-url=https://web.archive.org/web/20240619112629/https://www.forbes.com/sites/thomasbrewster/2024/06/19/fedex-police-help-cops-build-an-ai-car-surveillance-network/ |archive-date=19 Jun 2024 |access-date=25 Aug 2025 |website=Forbes}}</ref> This data can later be integrated into predictive police platforms like {{Wplink|Palantir Technologies|Palantir}}.<ref>{{Cite book |last=Rettberg |first=Jill Walker |title=Machine Vision: How Algorithms are Changing the Way We See the World |date=11 Sep 2023 |publisher=John Wiley & Sons. |year=2023 |location=Google Books |pages=45-46 |language=English}}</ref>

Unlike traditional security cameras that may be avoided by choosing different routes, Flock's expanding network of over 100,000 cameras makes avoidance increasingly difficult.<ref>{{Cite web |title=Eyes On Flock |url=https://eyesonflock.com/ |url-status=live |archive-url=https://web.archive.org/web/20251008230140/https://eyesonflock.com/ |archive-date=2025-10-08 |access-date=9 Dec 2025 |work=Eyes On Flock}}</ref> The system uses AI to create ''"Vehicle [[Device fingerprint|Fingerprints]]"'' that identify vehicles by characteristics beyond license plates, including make, model, color, aftermarket parts, window stickers, and roof racks.<ref>{{Cite web |last=Stanley |first=Jay |date=23 Jul 2025 |title=Surveillance Company Flock Now Using AI to Report Us to Police if it Thinks Our Movement Patterns Are "Suspicious" |url=https://www.aclu.org/news/national-security/surveillance-company-flock-now-using-ai-to-report-us-to-police-if-it-thinks-our-movement-patterns-are-suspicious |url-status=live |archive-url=https://web.archive.org/web/20250814053755/https://www.aclu.org/news/national-security/surveillance-company-flock-now-using-ai-to-report-us-to-police-if-it-thinks-our-movement-patterns-are-suspicious |archive-date=14 Aug 2025 |access-date=23 Aug 2025 |work=American Civil Liberties Union}}</ref>

====Privacy====
While Flock Safety claims their system doesn't violate Fourth Amendment rights because ''"license plates are not personal information,"''<ref name="Flock-PE">{{Cite web |url=https://www.flocksafety.com/privacy-ethics |title=Privacy & Ethics |work=Flock Safety |access-date=23 Aug 2025 |archive-url=https://archive.ph/OP55p |archive-date=23 Aug 2025 |url-status=live}}</ref> federal courts have challenged this interpretation. In February 2024, a federal judge ruled that a lawsuit challenging Norfolk, Virginia's use of 172 Flock cameras could proceed, finding that plaintiffs had plausibly alleged the system creates a ''"detailed chronicle of a person's physical presence compiled every day."''<ref name="norfolk">{{Cite web |last=King |first=Dan |date=6 Feb 2024 |title=Judge Rules Lawsuit Challenging Norfolk's Use of Flock Cameras Can Proceed |url=https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/ |url-status=live |archive-url=https://web.archive.org/web/20250717001536/https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/ |archive-date=17 Jul 2025 |access-date=23 Aug 2025 |work=Institute for Justice}}</ref>

Data collected includes location history that can reveal sensitive information about medical visits, religious attendance, political activities, and personal associations. While Flock states data is deleted after 30 days, contracts grant them ''"perpetual, worldwide, royalty-free license"'' to use anonymized data indefinitely.<ref name=":1">{{Cite web |title=Terms and Conditions |url=https://www.flocksafety.com/terms-and-conditions |url-status=live |archive-url=https://archive.ph/DSqUM |archive-date=26 Oct 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref> The system shares data across a network of over 4,800 law enforcement agencies nationally.<ref>{{Cite web |last=Koebler |first=Jason |date=2024 |title=Lawsuit Argues Warrantless Use of Flock Surveillance Cameras Is Unconstitutional |url=https://www.404media.co/lawsuit-argues-warrantless-use-of-flock-surveillance-cameras-is-unconstitutional/ |url-status=live |archive-url=https://web.archive.org/web/20250826013458/https://www.404media.co/lawsuit-argues-warrantless-use-of-flock-surveillance-cameras-is-unconstitutional/ |archive-date=26 Aug 2025 |access-date=23 Aug 2025 |work=404 Media}}</ref>

====="Anonymized Data"=====
While Flock's Terms and Conditions define "Anonymized Data" as customer data that is ''"permanently stripped of identifying details and any potential personally identifiable information"'' and is rendered so that a person or entity ''"can no longer be identified directly or indirectly,"'' this definition includes information such as vehicle make, model, color, location patterns, and other non–license-plate attributes.<ref name=":1" />

Privacy researchers caution that mobility datasets labeled as "anonymized" can still be re-identified. A 2013 MIT study found that just four spatio-temporal points uniquely identified 95% of individuals in an anonymized location dataset.<ref>{{Cite journal |last=de Montjoye |first=Y.-A. |last2=Hidalgo |first2=C. A. |last3=Verleysen |first3=M. |last4=Blondel |first4=V. D. |year=2013 |title=Unique in the Crowd: The privacy bounds of human mobility |url=https://www.nature.com/articles/srep01376 |journal=Scientific Reports |volume=3 |pages=1376 |doi=10.1038/srep01376 |access-date=23 Aug 2025}}</ref> Multiple peer-reviewed studies from 2018-2024 demonstrate that "anonymized" vehicle location data can be re-identified with high accuracy. A 2022 study showed researchers could re-identify drivers from raw vehicle network data with 97% accuracy by exploiting inter-dependencies in sensor measurements.<ref>{{Cite web |url=https://www.sciencedirect.com/science/article/abs/pii/S0167404822002139 |title=Privacy-preserving vehicle trajectory matching |website=ScienceDirect |date=2022 |access-date=5 Oct 2025}}</ref> Research published in the Journal of Computer Science and Technology (2022) found that even three to four location points can uniquely identify individuals.<ref>{{Cite journal |last=Sun |first=She |last2=Ma |first2=Shuai |last3=Song |first3=Jing-He |last4=Yue |first4=Wen-Hai |last5=Lin |first5=Xue-Lian |last6=Ma |first6=Tiejun |date=2022 |title=Experiments and Analyses of Anonymization Mechanisms for Trajectory Data Publishing |url=https://link.springer.com/article/10.1007/s11390-022-2409-x |journal=Journal of Computer Science and Technology |doi=10.1007/s11390-022-2409-x |access-date=5 Oct 2025}}</ref>

====Business model====
Flock operates on a subscription model charging municipalities and law enforcement agencies $2,500 USD per camera annually plus installation costs.<ref>{{Cite web|url=https://campbellca.gov/FAQ.aspx?QID=279 |title=How much does a Flock Safety camera cost? |work=City of Campbell |access-date=23 Aug 2025}}</ref> Private businesses including Home Depot, Lowe's, and FedEx also deploy cameras, sharing data with law enforcement.<ref>{{Cite web |url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops |first=Jason |last=Koebler |date=6 Aug 2025 |work=404 Media |access-date=23 Aug 2025 |archive-url=https://web.archive.org/web/20250823135847/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |archive-date=23 Aug 2025 |url-status=live}}</ref><ref name=":0" /> Contracts include automatic renewal clauses and limit municipal oversight capabilities, with cities unable to audit system operations or control how other agencies use shared data.<ref>{{Cite web |url=https://www.aclu.org/wp-content/uploads/publications/flock_1.pdf |title=How to Pump the Brakes on Your Police Department's Use of Flock's Mass Surveillance License Plate Readers |work=American Civil Liberties Union |date=2024 |access-date=23 Aug 2025}}</ref>

====Market control====
Flock Safety has rapidly expanded to become a dominant force in automated license plate recognition, operating in 49 states with over 40,000 cameras deployed. The company's network effect creates pressure for additional jurisdictions to join, as law enforcement effectiveness depends on network coverage. Several states have begun restricting access following privacy violations, with California, Illinois, and New York limiting data sharing after immigration and abortion-related tracking incidents.<ref>{{Cite web |url=https://www.michaelrcronin.com/post/flock-blocks-ice-from-license-plate-reader-access-in-several-states |title='Flock' Blocks ICE from License Plate Reader Access in Several States |work=Yes You Can Go |date=2025 |access-date=23 Aug 2025}}</ref>

===Premise of a "license plate camera"===
While marketed as "license plate readers,"' Flock cameras use what the company calls "Vehicle Fingerprint" technology which tracks vehicles using characteristics beyond just license plates. The system catalogs vehicles based on numerous distinguishing features including make, model, color, bumper stickers, dents, damage patterns, roof racks, aftermarket modifications such as wheels or spoilers, window stickers, and even mismatching paint colors.<ref>{{Cite web |last=Harwell |first=Drew |date=2021-10-22 |title=Flock license plate readers spark controversy in Golden, Colo. |url=https://www.washingtonpost.com/technology/2021/10/22/crime-suburbs-license-plate-readers/ |access-date=2025-08-23 |work=The Washington Post}}</ref><ref>{{Cite web |title=Flock Safety ALPR |url=https://www.campbellca.gov/1260/Flock-Safety-ALPR |access-date=2025-08-23 |work=City of Campbell}}</ref><ref name=":2">{{Cite web |date= |title=LPR Cameras |url=https://www.flocksafety.com/products/license-plate-readers |url-status=usurped |access-date=26 Oct 2025 |work=Flock Safety}}</ref>. According to Flock's own marketing materials, the system can identify vehicles even when license plates cannot be captured, advertised as turning "images into actionable evidence — no plate required."<ref>{{Cite web |title=License Plate Readers |url=https://www.flocksafety.com/products/license-plate-readers |url-status=live |archive-url=https://archive.ph/D9JGD |archive-date=23 Aug 2025 |access-date=23 Aug 2025 |work=Flock Safety}}</ref>

Flock claims this capability is ''"unique among ALPR systems"'' and allows law enforcement to search for vehicles based on these characteristics even without a visible license plate.

This technology changes the nature of the surveillance from license plate reading to comprehensive vehicle tracking. A person could still be tracked by the unique combination of their vehicle's physical characteristics. The Electronic Frontier Foundation warns that these ''"vehicle fingerprints"'' could flag vehicles based on political bumper stickers, revealing ''"information on the political or social views of the driver,"'' or economic indicators like rust or damage, potentially "endangering anyone who might not feel the need (or have the income required) to keep their car in perfect shape."<ref>{{Cite web |date=2020-09-14 |title=Things to Know Before Your Neighborhood Installs an Automated License Plate Reader |url=https://www.eff.org/deeplinks/2020/09/flock-license-plate-reader-homeowners-association-safe-problems |access-date=2025-08-23 |work=Electronic Frontier Foundation}}</ref>

Privacy advocates note that this expanded tracking capability makes the term ''"license plate reader"'' misleading, as Flock systems create detailed vehicle profiles that persist even without readable plates. It turns any distinguishing feature of a vehicle into a tracking identifier.<ref>{{Cite web |title=Stop Flock |url=https://www.stopflock.com/ |access-date=2025-08-23 |work=Stop Flock}}</ref>

==Patent for person identification by race and physical characteristics==
A U.S. Patent granted to Flock Group Inc. in August 2022 reveals the company has developed and patented technology to identify and classify people based on race, gender, and other physical characteristics.<ref name="patent11416545">{{Cite web |url=https://patentimages.storage.googleapis.com/77/9a/03/7b3b26499077d4/US11416545.pdf |title=System and Method for Object Based Query of Video Content Captured by a Dynamic Surveillance Network |website=United States Patent and Trademark Office |date=16 Aug 2022 |access-date=21 Jan 2025 |format=PDF |first1=Garrett |last1=Langley |first2=Matt |last2=Feury }}</ref> Patent US 11,416,545 B1 describes a system that goes beyond vehicle identification to analyze human subjects captured in surveillance footage.

According to the patent documentation, when the system identifies a human being in captured footage, it uses neural network modules specifically configured to classify people by "male, female, race, etc." The patent further describes using additional neural networks to identify clothing types, estimate height and weight, and other physical characteristics of individuals.<ref name="patent11416545" /> The system can then store this classification data in searchable databases, allowing law enforcement to query for people based on these physical attributes.

The patent shows that Flock's technology is designed to create comprehensive profiles that can track individuals across multiple camera locations by matching physical characteristics. While Flock publicly markets its products as ''"license plate readers"'' focused on vehicles, this patent demonstrates the company has developed capabilities for detailed human surveillance and classification by protected characteristics including race and gender.<ref name="patent11416545" />

Privacy advocates have raised concerns that this technology could enable discriminatory policing practices and racial profiling at scale.{{Citation needed}} The ability to search for people by race or other physical characteristics across a network of thousands of cameras is a large expansion of surveillance capabilities beyond what is typically disclosed in Flock's public marketing materials.{{Citation needed}}

==Legal challenges==

===Washington state judge declares Flock footage as public records ''(6 Nov 2025)''===
An Oregon resident filed public records requests at various police departments in the state of Washington regarding information collected from Flock cameras. The cities of Stanwood and Sedro-Woolley filed a motion to reject the resident's request, with their attorney stating that publicizing Flock footage may be a violation of privacy that could lead to stalking.

Some exemptions are given to deny public records request, particularly due to investigations. However, the judge dismissed the motion, declaring that the camera footage was "so broad and indiscriminate" with no distinction between criminal activity and casual civilian activity that the data had to be released to the public.<ref>{{Cite web |last=Ingalls |first=Chris |date=6 Nov 2025 |title=Judge orders police to release surveillance camera data, raising privacy questions |url=https://www.king5.com/article/news/investigations/investigators/judge-orders-washington-police-release-surveillance-camera-data-privacy-questions/281-c2037d52-6afb-4bf7-95ad-0eceaf477864 |access-date=8 Nov 2025 |website=KING5}}</ref><ref name=":5">{{Cite web |last=Peterson |first=Jenna |date=6 Nov 2025 |title=Judge denies request to exempt Flock footage from Public Records Act |url=https://www.heraldnet.com/news/judge-denies-request-to-exempt-flock-footage-from-public-records-act/ |access-date=8 Nov 2025 |website=Herald Net}}</ref>

The judge stated:<ref name=":5" /><blockquote>“I do think that the information at stake does have serious privacy implications, but that’s not the analysis for the intelligence information exemption,” she said. “You also have to make a finding that this is specific intelligence information that is compiled by investigative or law enforcement agencies, and the information that’s being compiled here does not relate to a specific case or investigation. The public already knows that these cameras exist and are operated. Many of them are in sight. The information does not disclose particular methods or procedures for gathering or evaluating intelligence information.” </blockquote>

===Norfolk federal lawsuit ''(February 2025)''===
In February 2025, Chief Judge Mark S. Davis of the U.S. District Court for the Eastern District of Virginia denied Norfolk's motion to dismiss a landmark Fourth Amendment lawsuit. The case involves two residents whose vehicles were tracked 526 times in 4.5 months and 849 times over the same period, figures revealed in a September 2025 court filing.<ref>{{Cite web|url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399|title=Virginia police used Flock cameras to track driver 526 times in 4 months, lawsuit says|work=NBC News|date=2025-09-18|access-date=2025-08-23}}</ref> Norfolk installed 172 Flock Safety cameras in 2023 at a cost of $430,000-$516,000 annually. Police Chief Mark Talbot stated the goal was making it ''"difficult to drive anywhere of any distance without running into a camera somewhere."''<ref name="norfolk" />

Judge Davis's ruling relied on ''Carpenter v. United States'', the 2018 Supreme Court decision requiring warrants for historical cell phone location data. The court found Norfolk's ALPR network "notably similar" to the surveillance the Supreme Court deemed unconstitutional. However, courts remain divided. In November 2024, Senior U.S. District Judge Robert E. Payne in the same district denied a motion to suppress Flock evidence, holding that three vehicle snapshots don't constitute "persistent surveillance" requiring a warrant.<ref>{{cite web|url=https://valawyersweekly.com/2024/11/11/mosaic-theory-rejected-flock-camera-evidence-does-not-violate-fourth-amendment/|title='Mosaic theory' rejected: Flock camera evidence does not violate Fourth Amendment|website=Virginia Lawyers Weekly|date=2024-11-11|access-date=2025-10-05}}</ref>

Virginia state courts show similar disagreement. Norfolk Circuit Court Judge Jamilah LeCruise granted a suppression motion in May 2024, finding that the breadth of Flock cameras covering Norfolk requires a warrant.<ref>{{cite web|url=https://www.govtech.com/public-safety/virginia-judge-rejects-alpr-evidence-without-warrant|title=Virginia Judge Rejects ALPR Evidence Without Warrant|website=Government Technology|date=2024-05-15|access-date=2025-10-05}}</ref> Yet three other Norfolk circuit court judges denied similar motions in 2024.

===State regulatory landscape===
Only 16 states have enacted any form of ALPR regulation as of 2024 according to University of Michigan research.<ref>{{cite web|url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse|title=Automated License Plate Readers widely used, subject to abuse|website=University of Michigan|date=2023|access-date=2025-10-05}}</ref> Virginia enacted House Bill 2724 in 2025 creating annual reporting requirements.<ref>{{cite web|url=https://vscc.virginia.gov/Annual%20Reports/2024%20VSCC%20Annual%20Report%20-Law%20Enforcement%20Use%20of%20ALPR.pdf|title=2024 VSCC Annual Report - Law Enforcement Use of ALPR|website=Virginia State Crime Commission|date=2024|access-date=2025-10-05}}</ref> Illinois Public Act 103-0540 explicitly prohibits use for reproductive healthcare punishment and immigration investigations.<ref>{{cite web|url=https://www.ilga.gov/legislation/publicacts/103/103-0540.htm|title=Public Act 103-0540|website=Illinois General Assembly|date=2024|access-date=2025-10-05}}</ref>

Illinois prohibits law enforcement agencies from sharing ALPR data with other jurisdictions in relation to a person's immigration status.<ref>{{Cite web |title=Public Act 103-0540 |url=https://www.ilga.gov/documents/legislation/publicacts/103/PDF/103-0540.pdf |url-status=usurped |access-date=23 Aug 2025 |work=Illinois General Assembly}}</ref> New Hampshire requires a three-minute purge of data from ALPR use with the exception of ongoing investigations. <ref>{{Cite web |title=261:75-b Use of Number Plate Scanning Devices Regulated. |url=https://law.justia.com/codes/new-hampshire/title-xxi/chapter-261/section-261-75-b/ |url-status=usurped |access-date=23 Aug 2025 |work=New Hampshire General Court}}</ref>

California’s SB 34 requires public agencies using ALPR systems to implement usage and privacy policies as well as limits to data sharing. <ref name=":3">{{Cite web |url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB34 |title=SB-34 Automated license plate recognition systems: use of data |work=California Legislative Information |access-date=23 Aug 2025}}</ref> However, enforcement remains inconsistent, with a 2020 state audit finding widespread non-compliance.<ref>{{Cite web |url=https://www.auditor.ca.gov/reports/2019-118/index.html |title=Automated License Plate Readers |work=California State Auditor |date=13 Feb 2020 |access-date=23 Aug 2025}}</ref>

==Notable incidents==

====Illinois audit findings (2024-2025)====
Illinois Secretary of State Alexi Giannoulias announced in late August 2024 that Flock Safety violated state law by allowing U.S. Customs and Border Protection to access Illinois license plate data for immigration enforcement.<ref>{{cite web|url=https://www.flocksafety.com/blog/flock-safetys-response-to-illinois-lpr-data-use-and-out-of-state-sharing-concerns|title=Flock Safety's Response to Illinois LPR Data Use and Out-of-State Sharing Concerns|website=Flock Safety|date=2024-08-25|access-date=2025-10-05}}</ref> The audit of 12 local law enforcement agencies revealed unauthorized pilot programs with CBP and Homeland Security Investigations, violating Illinois law prohibiting data sharing for immigration enforcement, gender-affirming care investigations, and abortion-related matters. Following the audit, 47 out-of-state agencies were removed from access to Illinois data.<ref>{{cite web|url=https://www.govtech.com/biz/flock-pledges-changes-after-illinois-data-sharing-accusation|title=Flock Pledges Changes After Illinois Data-Sharing Accusation|website=Government Technology|date=2024-08-15|access-date=2025-10-05}}</ref>

Mount Prospect, Illinois reported 262 immigration-related license plate reader searches in just the first few months of 2025. A Palos Heights detective shared Flock login credentials with a DEA agent who conducted 28 unauthorized searches of Oak Park ALPR data explicitly labeled "immigration violation."<ref name="dea">{{Cite web|url=https://unraveledpress.com/a-dea-agent-used-an-illinois-police-officers-flock-license-plate-reader-password-for-unauthorized-immigration-enforcement-searches/|title=DEA agent used Illinois cop's Flock license plate reader password for immigration enforcement searches|work=Unraveled Press|date=2025|access-date=2025-08-23}}</ref>

====California violations (2015-2025)====
California passed Senate Bill 34<ref>{{Cite web|url=https://calmatters.digitaldemocracy.org/bills/ca_201520160sb34|title=Senate Bill 34|access-date=2025-08-27}}</ref> in 2015 to limit how California police departments can use and share data collected from these cameras with other state's and federal law enforcement agencies. These limits have been found to be violated on several occasions with little enforcement or consequences for the misusing departments<ref>{{Cite web|url=https://sfstandard.com/2025/07/23/california-police-sharing-flock-license-plate-data/|access-date=2025-08-27|title=California cops are breaking surveillance laws|website=San Francisco Standard|date=2025-07-23}}</ref>.

A 2023 EFF investigation found 71 California police agencies in 22 counties illegally shared data with out-of-state law enforcement. San Francisco Police Department alone allowed 1.6 million illegal searches by out-of-state agencies from 2024-2025.<ref>{{cite web|url=https://sfstandard.com/2025/09/08/sfpd-flock-alpr-ice-data-sharing/|title=SFPD let Georgia, Texas cops illegally search city surveillance data on behalf of ICE|website=San Francisco Standard|date=2025-09-08|access-date=2025-10-05}}</ref> The California Attorney General filed the first enforcement action against the City of El Cajon in 2025 for sharing with 26 states.<ref>{{cite web|url=https://oag.ca.gov/news/press-releases/attorney-general-bonta-sues-el-cajon-illegally-sharing-license-plate-data-out|title=Attorney General Bonta Sues El Cajon for Illegally Sharing License Plate Data|website=California DOJ|date=2025|access-date=2025-10-05}}</ref>

===False positive incidents===

====Families detained at gunpoint====
In Española, New Mexico, 21-year-old Jaclynn Gonzales and her 12-year-old sister were held at gunpoint and handcuffed after Flock's system mistook a "2" for a "7" on their license plate, falsely flagging their vehicle as stolen.<ref>{{Cite news |date=2023-09-28 |title=License plate cover leads to traffic stop mishap |url=https://www.koat.com/article/espanola-police-license-plate-stolen-cover-traffic-stop/45361740|website=KOAT|access-date=2025-08-23}}</ref><ref>{{Cite web |date=2025 |title=Flock Safety: Eroding Your Privacy & Keeping You Safe with Surveillance |url=https://redact.dev/blog/flock-safety-lpr-privacy-surveillance/ |access-date=2025-08-23 |work=Redact}}</ref>

ALPR systems often misread license plates according to multiple investigations, leading to hardship & legal trouble for innocent civilians.<ref>{{cite web|url=https://www.eff.org/deeplinks/2024/11/human-toll-alpr-errors|title=The Human Toll of ALPR Errors|website=Electronic Frontier Foundation|date=2024-11-15|access-date=2025-10-05}}</ref>

===Law enforcement stalking incidents===

In October 2022, Kechi, Kansas Police Lieutenant Victor Heiar was arrested and later pleaded guilty to computer crimes and stalking after using Flock cameras to track his estranged wife's movements over four months.<ref>{{Cite web|url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/|title=Kechi police lieutenant arrested for using police technology to stalk wife|work=KWCH|date=2022-10-31|access-date=2025-08-23}}</ref> In a separate Kansas incident, Sedgwick Police Chief Lee Nygaard accessed Flock data 164 times to track his ex-girlfriend before resigning after admitting to the misuse.<ref>{{Cite web|url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html|title=Kansas police chief used Flock license plate cameras 164 times to track ex-girlfriend|work=Yahoo News|date=2025|access-date=2025-08-23}}</ref>

Multiple other documented cases include Las Vegas Metro Officer Christopher Young arrested in December 2023 for stalking his ex-fiancée using police databases, and Riverside County Deputy Eric Piscatella pleading guilty in February 2024 to seven counts of misusing sheriff's department databases to stalk a woman he met at Coachella.<ref>{{cite web|url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/?outputType=amp|title=Las Vegas police officer arrested for reportedly stalking ex-fiancée|website=FOX5 Vegas|date=2024-02-16|access-date=2025-10-05}}</ref>

===Abortion and reproductive healthcare tracking===
In May 2025, Johnson County, Texas sheriff's deputies used Flock's network to track a woman suspected of self-managing an abortion. They conducted searches across 83,000+ Flock cameras nationwide with the explicit reason: "had an abortion, search for female." The search accessed cameras across multiple states including those where abortion is legal. The incident led Illinois officials to investigate and subsequently block 47+ out-of-state agencies from accessing Illinois ALPR data.<ref>{{Cite web|url=https://www.dallasnews.com/news/texas/2025/06/13/after-finding-fetal-remains-north-texas-cops-used-camera-network-to-search-for-woman/|title=After finding fetal remains, North Texas cops used camera network to search for woman|work=The Dallas Morning News|date=2025-06-13|access-date=2025-08-23}}</ref><ref>{{cite web|url=https://www.eff.org/deeplinks/2025/05/she-got-abortion-so-texas-cop-used-83000-cameras-track-her-down|title=She Got an Abortion. So A Texas Cop Used 83,000 Cameras to Track Her Down|website=Electronic Frontier Foundation|date=2025-05-15|access-date=2025-10-05}}</ref>

Investigations and court records show that some law enforcement officers have misused Flock Safety automated license plate reader (ALPR) systems for personal, non-investigative purposes, including stalking romantic partners or monitoring civilians. These incidents highlight weaknesses & lack of internal oversight, & the reliance on post-hoc audits rather than real-time safeguards.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after allegedly using the department’s Flock ALPR system to track his ex-girlfriend.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09 |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex}}</ref> Prosecutors alleged Morales conducted five unauthorized searches of his ex-partner’s vehicle in October 2025. According to the criminal complaint, Morales admitted he knew the searches were improper and cited “desperation and bad judgment.” He was placed on administrative leave, prohibited from accessing Flock systems, and released on a $10,000 cash bond pending further proceedings.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref> Court records also show a related civil filing seeking a temporary restraining order in a domestic abuse case.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref>

The Menasha case matches what is becoming a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes & stalking after using Flock cameras to monitor his estranged wife’s movements over several months.<ref>{{cite news |title=Kechi police lieutenant arrested for using police technology to stalk wife |work=KWCH |date=2022-10-31 |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/}}</ref> In another Kansas incident, Sedgwick Police Chief Lee Nygaard admitted in 2025 to accessing Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, resulting in his resignation and loss of police certification.<ref>{{cite news |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |work=Yahoo News |date=2025 |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html}}</ref>

More cases involving other surveillance systems show a similar misuse. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing sheriff’s department databases to stalk a woman he met while off duty.<ref>{{cite news |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |work=FOX5 Vegas |date=2024-02-16 |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/}}</ref>

Oversight reviews & civil liberties organizations have noted that ALPR systems enable quick searches of historical vehicle location data across wide geographic areas. This reduces practical barriers to stalking & increases the risk of abuse by authorized users. While Flock & participating agencies rely on usage policies & access logs, many cases show misuse was detected only after complaints or later audits rather than through proactive safeguards.<ref>{{cite web |title=Automated License Plate Readers widely used, subject to abuse |work=University of Michigan |date=2023 |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse}}</ref><ref>{{cite web |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |work=Government Technology |date=2024 |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps}}</ref>

===Federal agency access===
Immigration and Customs Enforcement maintains a $6.1 million contract giving 9,000+ ICE officers access to the Vigilant Solutions ALPR database containing over 5 billion location data points.<ref>{{cite web|url=https://www.aclu.org/news/immigrants-rights/documents-reveal-ice-using-driver-location-data|title=Documents Reveal ICE Using Driver Location Data From Local Police for Deportations|website=ACLU|date=2024|access-date=2025-10-05}}</ref> The Drug Enforcement Administration operates a National License Plate Reader Program with over 10,000 license plate readers shared throughout the United States. 404 Media revealed over 4,000 searches by local and state police for federal immigration enforcement purposes, despite Flock having no formal ICE contract.<ref>{{Cite web|url=https://www.404media.co/ice-taps-into-nationwide-ai-enabled-camera-network-data-shows/|title=ICE Taps into Nationwide AI-Enabled Camera Network, Data Shows|work=404 Media|date=2025|access-date=2025-08-23}}</ref> A DEA agent was found using an Illinois police officer's credentials to conduct unauthorized immigration searches.<ref name="dea" />

===Illegal Camera Installations===
In South Carolina, Flock installed over 200 cameras without authorization, leading to a statewide moratorium on new installations.<ref>{{Cite web |last=Ferrara |first=David |date=2024-03-11 |title=A company installed license plate cameras without permission. SC agency wants clear rules |url=https://www.postandcourier.com/news/alpr-cameras-south-carolina-flock-safety-license-plate-readers/article_787a262a-dbd2-11ee-a901-634acead588b.html |url-status=live |access-date=2025-08-25 |website=The Post and Courier}}</ref>

In Illinois, a Flock representative allegedly threatened a Department of Transportation official with police pressure when questioned about permit applications.<ref>{{Cite web |last=Uprise RI Staff |date=2024-10-23 |title=As Flock Surveillance Cameras Proliferate in Rhode Island, Lawsuit Challenges Their Legality |url=https://upriseri.com/as-flock-surveillance-cameras-proliferate-in-rhode-island-lawsuit-challenges-their-legality/ |url-status=live |access-date=2025-08-25 |website=UPRISE RI}}</ref>

====='''Evanston, IL'''=====
Flock was ordered to remove 18 stationary cameras. The city put the contract with Flock on a 30-day termination notice on August 26. Flock Initially appeared to comply, removing 15 of the cameras by September 8. Later, Flock was caught reinstalling all of them by the following Tuesday without authorization from the city. The city of Evanston responded with a cease-and-desist order for Flock to remove the new and unauthorized camera equipment. Because Flock reinstalled the cameras without permission, Evanston was forced to cover the cameras with tape and bags to block them from potentially logging vehicle data.<ref>{{Cite web |last=Harrison |first=Alex |date=2025-09-25 |title=City covers Flock cameras while waiting for removal |url=https://evanstonroundtable.com/2025/09/25/city-covers-up-flock-cameras-while-waiting-for-removal/ |url-status=live |archive-url=https://archive.ph/PD1qe |archive-date=2025-10-10 |access-date=2025-10-10 |website=Evanston Roundtable}}</ref>

===City rejections and terminations===

Multiple cities have rejected or terminated Flock contracts following privacy concerns and effectiveness issues:

'''0.2% effectiveness rate, low arrests:''' Austin, Texas terminated its contract in July 2025 after an audit revealed "systematic compliance failures" and only 165 arrests from 113 million license plate scans (0.146% effectiveness rate).<ref>{{Cite web|url=https://cbsaustin.com/news/local/flock-ceo-responds-to-austin-backlash-as-city-contract-nears-expiration|title=Flock CEO responds to Austin backlash as city contract nears expiration|work=CBS Austin|date=2025-06-21|access-date=2025-08-23}}</ref>

Denver City Council unanimously rejected a $666,000 contract extension in May 2025 following revelations of 1,400+ ICE-related searches in Colorado data.<ref>{{Cite web|url=https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/|title=Denver rejects $666,000 extension for license-plate surveillance cameras after backlash|work=Denverite|date=2025-05-05|access-date=2025-08-23}}</ref>

San Marcos, Texas voted 5-2 to deny camera expansion after discovering no required audits had been conducted since 2022.<ref>{{Cite web |last=Velez |first=Abigail |date=2025-06-04 |title=San Marcos City Council votes to deny flock camera expansion after hours of heated debate |url=https://cbsaustin.com/news/local/san-marcos-city-council-votes-to-deny-flock-camera-expansion-after-hours-of-heated-debate |access-date=2025-08-23 |work=CBS Austin}}</ref>

Oak Park, Illinois terminated their contract entirely following the Illinois investigation into illegal data sharing.<ref>{{Cite web|url=https://www.oakpark.com/2025/08/07/oak-park-terminates-flock-license-plate-reader-contract/|title=Oak Park terminates Flock license plate reader contract|work=Wednesday Journal|date=2025-08-07|access-date=2025-08-23}}</ref>

===Arizona deployments===
Sedona, Arizona became the first Arizona city to completely terminate its Flock Safety contract in September 2025 after citizen backlash. The city had installed 11 cameras in June 2025 without prior public notice at a cost of $51,146 for the first year. The council voted 5-1 to pause the program, then unanimously 7-0 on September 9 to permanently terminate after Flock CEO Garrett Langley admitted the company had been sharing data with federal agencies. Vice Mayor Holli Ploog called Flock "not an honorable company" for the conflicting data-sharing claims.<ref>{{cite web|url=https://westvalleyfamilies.substack.com/p/sedona-pulls-the-plug-on-flock-safety|title=Sedona Pulls the Plug on Flock Safety|website=West Valley Families|date=2025-09-10|access-date=2025-10-05}}</ref><ref>{{cite web|url=https://www.knau.org/knau-and-arizona-news/2025-09-11/sedona-council-permanently-ends-license-plate-camera-program|title=Sedona council permanently ends license plate camera program|website=KNAU|date=2025-09-11|access-date=2025-10-05}}</ref>

Flagstaff deployed 32 Flock cameras in summer 2024 at a cost of $143,100 annually. By September 2025, a petition signed by 25+ residents demanded cancellation.<ref>{{cite web|url=https://www.kjzz.org/fronteras-desk/2025-09-01/after-sedona-paused-flock-safety-camera-system-flagstaff-is-considering-the-same-issue|title=After Sedona paused Flock Safety camera system, Flagstaff is considering the same issue|website=KJZZ|date=2025-09-01|access-date=2025-10-05}}</ref>

University of Arizona contracted with Flock in February 2025 for 54 ALPR cameras at $160,000 annually. Students and faculty launched a "Deflock Tucson" campaign citing concerns about tracking international students and potential data sharing with federal immigration authorities.<ref>{{cite web|url=https://azluminaria.org/2025/09/15/ua-students-and-faculty-question-use-of-flock-safety-cameras-on-campus/|title=UA students and faculty question use of Flock Safety cameras on campus|website=AZ Luminaria|date=2025-09-15|access-date=2025-10-05}}</ref>

Casa Grande approved a $10 million "Safe City Initiative" in September 2025 including 100 license plate readers. Chief Mark McCrory reported the current 22 license plate readers led to 212 stolen vehicles identified and 168 arrests.<ref>{{cite web|url=https://www.inmaricopa.com/we-mapped-all-flock-cameras/|title=We mapped the city's Flock cameras|website=InMaricopa|date=2025|access-date=2025-10-05}}</ref>

Despite documented deployments across Arizona including Phoenix, Mesa, Chandler, Scottsdale, Tempe, Surprise, Youngtown, Litchfield Park, and Yuma, the state has no ALPR-specific regulation.<ref>{{cite web|url=https://azmirror.com/2019/07/08/how-do-automated-license-plate-readers-work/|title=How do automated license plate readers work?|website=Arizona Mirror|date=2019-07-08|access-date=2025-10-05}}</ref>

==Security vulnerabilities==
In 2025, Flock Safety reported security vulnerabilities in its devices and submitted them to MITRE for inclusion in the National Vulnerability Database, including issues such as hard-coded credentials and improper access controls.<ref>{{Cite web |date=2025-05-05 |title=Gunshot Detection and License Plate Reader Security Alert |url=https://www.flocksafety.com/blog/gunshot-detection-and-license-plate-reader-security-alert |website=Flock Safety}}</ref><ref>{{Cite web |date=2025-10-02 |title=CVE-2025-59403 : The Flock Safety Android Collins application (aka com.flocksafety.android.collin |url=https://www.cvedetails.com/cve/CVE-2025-59403/ |website=CVEdetails.com}}</ref> Similar security concerns have affected other ALPR systems, including exposure of default passwords and unencrypted data storage.<ref name=":4">{{Cite web |last=Quintin |first=Cooper |date=28 Oct 2015 |title=License Plate Readers Exposed! How Public Safety Agencies Responded to Major Vulnerabilities in Vehicle Surveillance Tech |url=https://www.eff.org/ur/deeplinks/2015/10/license-plate-readers-exposed-how-public-safety-agencies-responded-massive |website=Electronic Frontier Foundation}}</ref>

This represents one of several major security disclosures in the past decade. In 2015, the Electronic Frontier Foundation documented more than 100 ALPR cameras accessible on the open internet, often without passwords or proper configuration.<ref name=":4" /> A more serious documented breach occurred in 2019, when Perceptics, LLC, a subcontractor for U.S. Customs and Border Protection, exposed approximately 105,000 license plate images and 184,000 traveler facial images.<ref>{{Cite web |title=Review of CBP's Major Cybersecurity Incident During a 2019 Biometric Pilot |url=https://www.oig.dhs.gov/sites/default/files/assets/2020-09/OIG-20-71-Sep20.pdf}}</ref>

In 2025 it has been discovered that the cameras run [[wikipedia:Android_Oreo|Android 8.0 (Oreo)]] an operating system with 90 security vulnerabilities. The cameras also send data unencrypted and are easily tricked by stingrays. The compute boxes have easily accessible USB-c ports leaving the device vulnerable to rubber duckies. When the power button is pressed in a specific order the device emits a Wi-Fi hotspot that can be used to gain adb access.<ref>{{Cite web |last=Benn |first=Jordan |date=2025-11-16 |title=We Hacked Flock Safety Cameras in under 30 Seconds. |url=https://www.youtube.com/watch?v=uB0gr7Fh6lY |website=YouTube}}</ref>

==Government accountability and oversight==

===State audit findings===
California State Auditor's February 2020 investigation found the Los Angeles Police Department (LAPD), with a 320 million image database, had no ALPR-specific policy at all. The audit found 96% of agencies claim to have policies, but most are incomplete. Data retention periods varied wildly with no justification. LAPD maintained a minimum five-year retention period, yet couldn't demonstrate that images stored for years had investigative value. The audit found that 99.9% of the 320 million images Los Angeles stores are for vehicles that were not on a "hot list" when the image was made.<ref>{{Cite web |url=https://information.auditor.ca.gov/reports/2019-118/summary.html |title=Automated License Plate Readers |website=California State Auditor |date=13 Feb 2020 |access-date=5 Oct 2025}}</ref>

New Jersey provides a contrasting model with mandatory annual audits of all 523 law enforcement agencies. The 2024 audit reported only two significant violations, both involving users who hadn't completed required training.<ref>{{Cite web |url=https://nj.gov/njsp/ALPR/pdf/2024_Audit_Automated_License_Plate_Recognition_(ALPR)_Data_Collected_Utilized_NJ_Law_Enforcement_Agencies.pdf |title=2024 Audit of Automated License Plate Recognition (ALPR) Data |website=New Jersey State Police |date=2024 |access-date=5 Oct 2025 |format=PDF}}</ref>

A Government Technology analysis found that agencies often fail to audit ALPR systems regularly, leaving them "open to abuse by neglecting to institute sufficient oversight."<ref>{{Cite web |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |website=Government Technology |date=2024 |access-date=5 Oct 2025}}</ref>

===Cost-benefit analysis===
Arizona Department of Transportation's 2008 study of generic ALPR technology (predating Flock Safety by nine years) estimated $9.98 million for a hypothetical statewide ALPR system. The projected benefit-to-cost ratio of 9.6:1 came entirely from registration and insurance compliance, not crime reduction.<ref>{{Cite web |url=https://apps.azdot.gov/files/ADOTLibrary/publications/project_reports/PDF/AZ637.pdf |title=Automated License Plate Recognition Technology Implementation Report |website=Arizona Department of Transportation |date=1 Jun 2008 |access-date=5 Oct 2025}}</ref>

Colorado's Office of Research and Statistics reported that while ALPR systems are expanding, independent academic research contradicts vendor claims. A 2011 George Mason University study concluded ALPRs "do not achieve a prevention or deterrent effect" on crime.<ref>{{Cite web |url=https://cdpsdocs.state.co.us/ors/Docs/Briefs/2024-05_InDetail-ALPR.pdf |title=Automated License Plate Readers (In Detail) |website=Colorado Division of Criminal Justice |date=1 May 2024 |access-date=5 Oct 2025 |format=PDF}}</ref>

Oakland Police Department reported 182 arrests from ALPR in the first year, representing 1.4% of homicides, robberies, burglaries, and firearm assaults. The Northern California Regional Intelligence Center states approximately 1-2 vehicles out of 1,000 initiate alerts — a hit rate of just 0.1-0.2%.<ref>{{Cite web |url=https://ncric.ca.gov/wp-content/uploads/2021/10/California-Law-Enforcement-ALPR-FAQ.pdf |title=California Law Enforcement ALPR FAQ |website=NCRIC |date=2021 |access-date=5 Oct 2025 |format=PDF}}</ref>

==Camera locations==
The locations of many Flock Cameras have been mapped by the OpenStreetMap project. A viewer of the locations of these cameras is located here: [https://deflock.me/map ALPR Map | DeFlock]

====Cease and desist to DeFlock.me====
DeFlock.me is a website allowing users to log and view the locations of ALPRs, such as Flock products. On 30 January 2025, Flock sent a cease and desist notice to the owner of DeFlock demanding the name of the website be changed to exclude the company's brand name. The letter also stated that "the Website also implies that various license plate readers are vulnerable to security hacks [...]" which Flock alleged "[...] provides a false impression about the security of Flock Products."<ref>{{Cite web |last=Matz |first=Sarah M. |title=2025 01 31 DEFLOCK CD final |url=https://www.eff.org/files/2025/02/26/2025_01_31_deflock_cd_ex-3.pdf |website=Electronic Frontier Foundation |date=30 Jan 2025 |access-date=27 Oct 2025 |url-status=live |format=PDF}}</ref>

==External links==
*[https://deflock.me/ DeFlock live map of active ALPRs]
*[https://www.noalprs.org/ No ALPRS movement in United States]
*[https://plateprivacy.com/ The Plate Privacy Project]
*[https://eyesonflock.com/ Eyes On Flock]
*[https://wiki.alprwatch.org/index.php/Main_Page ALPR Watch Wiki]

==References==
{{Reflist}}

[[Category:Automatic license plate readers]]
[[Category:Flock Safety]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2026-01-11T18:13:00Z

Louis: added section about menasha wisconsin

{{Alert|message = This is a special page dedicated a specific issue. It will be deleted once moved elsewhere, & is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city - but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. |thumb|Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. ]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[Fourth Amendment to the United States Constitution|Fourth Amendment]] jurisprudence & misunderstands the legal standard of "reasonable expectation of privacy" established by the [[Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches & seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy. This considers the nature, scope, & how intrusive the government monitoring is.

In ''[[Carpenter v. United States]]'' (2018), the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[John Roberts]] wrote that the government's access to 127 days of cell-site location data; tracking movements on public roads; achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> The Court said<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation & Comprehensive Surveillance===

Courts separate isolated instances of police observation & large scale automated tracking systems. In ''[[United States v. Jones]]'' (2012), Justice [[Sonia Sotomayor]]'s influential concurrence explained that [[GPS tracking]] <blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, & sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> </blockquote>She noted that automated surveillance <blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources & community hostility."<ref name=":1" />''</blockquote>The [[Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy'' (2020), holding: <blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy & would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |website=Justia |date=2020-04-16 |access-date=2025-12-16}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The "[[mosaic theory]]" of Fourth Amendment protection holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[Samuel Alito]] noted in his ''Jones'' concurrence that <blockquote>''"society's expectation has been that law enforcement agents & others would not; & indeed, in the main, simply could not; secretly monitor & catalogue every single movement of an individual's car for a very long period."<ref name=":1" />'' </blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In ''[[United States v. Knotts]]'' (1983), while holding that limited [[beeper]] tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "dragnet-type law enforcement practices."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk'' (E.D. Va. 2025), Chief Judge Mark S. Davis denied a motion to dismiss a constitutional challenge to Norfolk's 172-camera ALPR network, finding plaintiffs stated a plausible Fourth Amendment claim. The court wrote: <blockquote>''"A reasonable person could believe that society's expectations, as laid out by the Court in Carpenter, are being violated by the Norfolk Flock system. The complaint alleges facts notably similar to those in Carpenter that the Supreme Court found to clearly violate society's expectation of privacy: law enforcement secretly monitoring & cataloguing the whole of tens of thousands of individual's movements over an extended period."<ref>{{Cite web |title=Schmidt v. City of Norfolk |url=https://clearinghouse.net/case/46035/ |website=Civil Rights Litigation Clearinghouse |access-date=2025-12-16}}</ref>''</blockquote>The case is scheduled for trial in Fall 2025 & could produce the first federal appellate ruling requiring warrants for comprehensive ALPR surveillance.

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 & 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |website=Electronic Frontier Foundation |access-date=2025-12-16}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale & the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale & comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, & sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge & Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly; Norfolk's 176 cameras provide citywide coverage; & Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |title=Denver's new Flock cameras scan 2 million license plates a month |work=Denverite |date=2024-09-19 |access-date=2025-12-16}}</ref><ref>{{cite news |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |title=Virginia police used Flock cameras to track driver 526 times in 4 months |work=NBC News |date=2024 |access-date=2025-12-16}}</ref><ref>{{cite news |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |work=Community Impact |date=2025-05-20 |access-date=2025-12-16}}</ref>

==FALSE POSITIVES & SYSTEM FAILURES==

Automated surveillance systems have high risks of false positives where innocent individuals are subjected to armed police responses based on program errors. These create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' & I was like, 'What?'"<ref name="cnn-doritos">{{cite news |url=https://www.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |work=CNN |date=2025-10-25 |access-date=2025-10-28}}</ref>''</blockquote>

Allen was forced to his knees, handcuffed, & searched before officers realized he was unarmed. Allen described watching about 8 cop cars arrive, with officers pointing guns at him. <blockquote>

''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me,"'' </blockquote>

he told WBAL-TV.<ref name="cnn-doritos" />

When shown the image that triggered the alert, Allen explained: <blockquote>''"I was just holding a Doritos bag – it was two hands & one finger out, & they said it looked like a gun."<ref name="cnn-doritos" />''</blockquote>

Baltimore County high schools used the AI gun detection system in 2024, using existing school cameras to scan for potential weapons. The system is operated by Omnilert, which taps into existing camera feeds to detect objects that resemble weapons & then alerts both school safety officers & law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name="cnn-doritos" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name="cnn-doritos" /> The company defended its system, claiming it ''"functioned as intended: to prioritize safety & awareness through rapid human verification,"'' though the incident clearly shows the system escalated to armed police response before adequate human review occurred.<ref>{{cite news |url=https://abc7.com/post/student-handcuffed-doritos-bag-mistaken-gun-schools-ai-security-system-baltimore-county-maryland/18073796/ |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system in Baltimore County, Maryland |work=ABC7 |date=2025-10-26 |access-date=2025-10-28}}</ref>
===ALPRs causing innocent people to be held at gunpoint===
Automated License Plate Reader systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====
In 2018, privacy advocate Brian Hofer & his younger brother were driving to visit their parents for Thanksgiving when they found themselves held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1= |last2= |first2= |date= |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government & corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries. "There are billions of scans a day in America. If there's even just a 10% error rate, that means there are so many opportunities for abuse to happen," Hofer stated.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops & ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====
Body camera footage from a documented police incident shows officers pursuing & detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |title=Police Body Camera: ALPR False Alert Detention |url=https://youtu.be/lmNxitcaT2Y |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====
In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. '''A 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7,"''' according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====
In Aurora, Colorado in 2020, a mother & her family, including her 6-year-old daughter, were pulled over at gunpoint & forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state; a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video & widely condemned, led to a $1.9 million settlement from the city in 2024. .

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

In September 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada, after the casino's facial recognition system misidentified him as a previously banned individual named Michael Ellis.<ref name="casino-org">{{Cite web |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |website=Casino.org |date=2025-11-11 |access-date=2025-12-16}}</ref> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://thegamingboardroom.com/2025/11/12/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |website=The Gaming Boardroom |date=2025-11-12 |access-date=2025-12-16}}</ref>

On September 17, 2023, Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |website=CasinoBeats |date=2025-12-09 |access-date=2025-12-16}}</ref> Ellis's ban was set to expire on September 26, 2023—nine days after the arrest.<ref name="casinobeats" />

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, & his vehicle registration.<ref name="casinobeats" /> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him & called the police.<ref name="casino-org" />

Released police records & driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:

{| class="wikitable"
|-
!Characteristic!!Jason Killinger!!Michael Ellis
|-
|Height||6'1"||5'9"
|-
|Eye Color||Blue||Hazel
|}<ref name="casinobeats" />

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue & hazel eyes are "''by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats" /> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats" />

Officer Jager arrived at the casino. According to Killinger's lawsuit he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up" ''to fabricate the documents.<ref name="casinobeats" /> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' & that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats" />

Bodycam footage released in late 2025 captured Jager stating: <blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |website=Dexerto |date=2025-12-09 |access-date=2025-12-16}}</ref></blockquote>

Jager handcuffed Killinger & transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats" />

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |website=Our Town Reno |date=2025-11-14 |access-date=2025-12-16}}</ref> His federal lawsuit against Officer Jager (''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD) is still active in the U.S. District Court for the District of Nevada as of December 16th 2025.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |website=Leagle |access-date=2025-12-16}}</ref>

The lawsuit alleges that Jager's actions violated Killinger's [[Fourteenth Amendment to the United States Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats" /> '''Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner & omitted the fingerprint exoneration from his official report.'''<ref name="casinobeats" /> He is seeking compensatory, special, & punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats" /> The case is expected to go to trial in 2026.<ref name="casino-org" />

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom" /> The case shows that when officers prioritize algorithmic identification over physical evidence & valid documentation, innocent individuals are subjected to unjust detention.

===Common ALPR Error Mechanisms===
These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (car plates matched to motorcycle registrations)
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles & criminal activity
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners
*'''Jurisdiction errors''': Out-of-state plates with identical numbers to in-state wanted vehicles generate false matches

==Law enforcement misuse and stalking incidents==

Documented cases show that law enforcement officers have misused automated license plate reader (ALPR) systems, including Flock Safety cameras, to track individuals for personal, non-investigative purposes such as stalking romantic partners or civilians. These incidents have raised concerns about lack of internal oversight, auditing practices, & the concentration of surveillance power in individual user accounts.

In Menasha, Wisconsin, police officer Cristian Morales was charged in January 2026 with misconduct in office after prosecutors alleged he used the department’s Flock ALPR system to track his ex-girlfriend.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09 |url=https://fox11online.com/news/crime/menasha-police-officer-accused-of-using-license-plate-recognition-system-to-track-his-ex}}</ref> According to the criminal complaint, Morales conducted five unauthorized searches of his ex-partner’s vehicle in October 2025. Court filings state that Morales acknowledged knowing the searches were improper & attributed them to “desperation and bad judgment.” He was placed on administrative leave, barred from accessing Flock systems, & released on a $10,000 cash bond pending further proceedings.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref> A parallel civil filing seeking a temporary restraining order in a domestic abuse case was also lodged against Morales.<ref>{{cite news |title=Menasha police officer accused of using license plate recognition system to track his ex |work=FOX 11 News |date=2026-01-09}}</ref>

The Menasha case is but one in what is becoming a national pattern. In Kansas, Kechi Police Lieutenant Victor Heiar pleaded guilty in 2022 to computer crimes and stalking after using Flock cameras to monitor his estranged wife’s movements over several months.<ref>{{cite news |title=Kechi police lieutenant arrested for using police technology to stalk wife |work=KWCH |date=2022-10-31 |url=https://www.kwch.com/2022/10/31/kechi-police-lieutenant-arrested-using-police-technology-stalk-wife/}}</ref> In a separate Kansas case, Sedgwick Police Chief Lee Nygaard admitted in 2025 to using Flock ALPR data more than 160 times to track his ex-girlfriend and her new partner, leading to his resignation and surrender of his law enforcement certification.<ref>{{cite news |title=Kansas police chief used Flock license plate cameras to track ex-girlfriend |work=Yahoo News |date=2025 |url=https://www.yahoo.com/news/kansas-police-chief-used-flock-093300946.html}}</ref>

Comparable misuse has been documented involving other police databases and surveillance systems. Las Vegas Metropolitan Police officer Christopher Young was arrested in 2023 for stalking his ex-fiancée using police databases, and in California, Riverside County deputy Eric Piscatella pleaded guilty in 2024 to multiple counts of misusing law enforcement databases to stalk a woman he met off duty.<ref>{{cite news |title=Las Vegas police officer arrested for reportedly stalking ex-fiancée |work=FOX5 Vegas |date=2024-02-16 |url=https://www.fox5vegas.com/2024/02/16/las-vegas-police-officer-arrested-reportedly-stalking-ex-fiancee/}}</ref> Investigations by the Associated Press and others have found that such misuse often remains undetected until a victim files a complaint or an external audit occurs.<ref>{{cite news |title=When cops abuse confidential databases |work=Associated Press |date=2016}}</ref>

Auditors and civil liberties organizations note that ALPR systems reduce the cost and effort of stalking by allowing quick searches of historical location data across large geographic areas without real-time supervisory approval. While vendors and agencies rely on access logs & written policies, many cases have demonstrated that these safeguards often fail to prevent or detect misuse quickly enough.<ref>{{cite web |title=Automated License Plate Readers widely used, subject to abuse |work=University of Michigan |date=2023 |url=https://stpp.fordschool.umich.edu/news/2023/automated-license-plate-readers-widely-used-subject-abuse}}</ref><ref>{{cite web |title=ALPR Audit Takeaways: What We Learned About Policy Gaps |work=Government Technology |date=2024 |url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps}}</ref>
==References==
{{reflist}}

[[Category:Flock Safety]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2025-12-16T20:27:00Z

Louis: some corrections

{{Alert|message = This is a special page dedicated a specific issue. It will be deleted once moved elsewhere, & is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city - but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. |thumb|Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. ]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[Fourth Amendment to the United States Constitution|Fourth Amendment]] jurisprudence & misunderstands the legal standard of "reasonable expectation of privacy" established by the [[Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches & seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy. This considers the nature, scope, & how intrusive the government monitoring is.

In ''[[Carpenter v. United States]]'' (2018), the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[John Roberts]] wrote that the government's access to 127 days of cell-site location data; tracking movements on public roads; achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=Carpenter v. United States |url=https://www.law.cornell.edu/supremecourt/text/16-402 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> The Court said<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation & Comprehensive Surveillance===

Courts separate isolated instances of police observation & large scale automated tracking systems. In ''[[United States v. Jones]]'' (2012), Justice [[Sonia Sotomayor]]'s influential concurrence explained that [[GPS tracking]] <blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, & sexual associations."''<ref name=":1">{{Cite web |title=United States v. Jones |url=https://www.law.cornell.edu/supremecourt/text/10-1259 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> </blockquote>She noted that automated surveillance <blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources & community hostility."<ref name=":1" />''</blockquote>The [[Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy'' (2020), holding: <blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy & would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |title=Commonwealth v. McCarthy |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf |website=Justia |date=2020-04-16 |access-date=2025-12-16}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The "[[mosaic theory]]" of Fourth Amendment protection holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[Samuel Alito]] noted in his ''Jones'' concurrence that <blockquote>''"society's expectation has been that law enforcement agents & others would not; & indeed, in the main, simply could not; secretly monitor & catalogue every single movement of an individual's car for a very long period."<ref name=":1" />'' </blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In ''[[United States v. Knotts]]'' (1983), while holding that limited [[beeper]] tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "dragnet-type law enforcement practices."<ref>{{Cite web |title=United States v. Knotts |url=https://www.law.cornell.edu/supremecourt/text/460/276 |website=Legal Information Institute |publisher=Cornell Law School |access-date=2025-12-16}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk'' (E.D. Va. 2025), Chief Judge Mark S. Davis denied a motion to dismiss a constitutional challenge to Norfolk's 172-camera ALPR network, finding plaintiffs stated a plausible Fourth Amendment claim. The court wrote: <blockquote>''"A reasonable person could believe that society's expectations, as laid out by the Court in Carpenter, are being violated by the Norfolk Flock system. The complaint alleges facts notably similar to those in Carpenter that the Supreme Court found to clearly violate society's expectation of privacy: law enforcement secretly monitoring & cataloguing the whole of tens of thousands of individual's movements over an extended period."<ref>{{Cite web |title=Schmidt v. City of Norfolk |url=https://clearinghouse.net/case/46035/ |website=Civil Rights Litigation Clearinghouse |access-date=2025-12-16}}</ref>''</blockquote>The case is scheduled for trial in Fall 2025 & could produce the first federal appellate ruling requiring warrants for comprehensive ALPR surveillance.

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 & 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |website=Electronic Frontier Foundation |access-date=2025-12-16}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale & the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale & comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, & sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge & Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly; Norfolk's 176 cameras provide citywide coverage; & Austin's system scanned approximately 75 million plates over nine months.<ref>{{cite news |url=https://denverite.com/2024/09/19/denver-flock-license-plate-scanners-update/ |title=Denver's new Flock cameras scan 2 million license plates a month |work=Denverite |date=2024-09-19 |access-date=2025-12-16}}</ref><ref>{{cite news |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |title=Virginia police used Flock cameras to track driver 526 times in 4 months |work=NBC News |date=2024 |access-date=2025-12-16}}</ref><ref>{{cite news |url=https://communityimpact.com/austin/south-central-austin/government/2025/05/20/75m-license-plates-scanned-under-rebooted-austin-police-program-audit-reveals-successes-concerns/ |title=75M license plates scanned under rebooted Austin police program; audit reveals successes, concerns |work=Community Impact |date=2025-05-20 |access-date=2025-12-16}}</ref>

==FALSE POSITIVES & SYSTEM FAILURES==

Automated surveillance systems have high risks of false positives where innocent individuals are subjected to armed police responses based on program errors. These create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' & I was like, 'What?'"<ref name="cnn-doritos">{{cite news |url=https://www.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |work=CNN |date=2025-10-25 |access-date=2025-10-28}}</ref>''</blockquote>

Allen was forced to his knees, handcuffed, & searched before officers realized he was unarmed. Allen described watching about 8 cop cars arrive, with officers pointing guns at him. <blockquote>

''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me,"'' </blockquote>

he told WBAL-TV.<ref name="cnn-doritos" />

When shown the image that triggered the alert, Allen explained: <blockquote>''"I was just holding a Doritos bag – it was two hands & one finger out, & they said it looked like a gun."<ref name="cnn-doritos" />''</blockquote>

Baltimore County high schools used the AI gun detection system in 2024, using existing school cameras to scan for potential weapons. The system is operated by Omnilert, which taps into existing camera feeds to detect objects that resemble weapons & then alerts both school safety officers & law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name="cnn-doritos" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name="cnn-doritos" /> The company defended its system, claiming it ''"functioned as intended: to prioritize safety & awareness through rapid human verification,"'' though the incident clearly shows the system escalated to armed police response before adequate human review occurred.<ref>{{cite news |url=https://abc7.com/post/student-handcuffed-doritos-bag-mistaken-gun-schools-ai-security-system-baltimore-county-maryland/18073796/ |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system in Baltimore County, Maryland |work=ABC7 |date=2025-10-26 |access-date=2025-10-28}}</ref>
===ALPRs causing innocent people to be held at gunpoint===
Automated License Plate Reader systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====
In 2018, privacy advocate Brian Hofer & his younger brother were driving to visit their parents for Thanksgiving when they found themselves held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1= |last2= |first2= |date= |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government & corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries. "There are billions of scans a day in America. If there's even just a 10% error rate, that means there are so many opportunities for abuse to happen," Hofer stated.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops & ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====
Body camera footage from a documented police incident shows officers pursuing & detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |title=Police Body Camera: ALPR False Alert Detention |url=https://youtu.be/lmNxitcaT2Y |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====
In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. '''A 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7,"''' according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====
In Aurora, Colorado in 2020, a mother & her family, including her 6-year-old daughter, were pulled over at gunpoint & forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state; a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video & widely condemned, led to a $1.9 million settlement from the city in 2024. .

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

In September 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada, after the casino's facial recognition system misidentified him as a previously banned individual named Michael Ellis.<ref name="casino-org">{{Cite web |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |website=Casino.org |date=2025-11-11 |access-date=2025-12-16}}</ref> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://thegamingboardroom.com/2025/11/12/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |website=The Gaming Boardroom |date=2025-11-12 |access-date=2025-12-16}}</ref>

On September 17, 2023, Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |website=CasinoBeats |date=2025-12-09 |access-date=2025-12-16}}</ref> Ellis's ban was set to expire on September 26, 2023—nine days after the arrest.<ref name="casinobeats"/>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, & his vehicle registration.<ref name="casinobeats"/> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him & called the police.<ref name="casino-org"/>

Released police records & driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:

{| class="wikitable"
|-
! Characteristic !! Jason Killinger !! Michael Ellis
|-
| Height || 6'1" || 5'9"
|-
| Eye Color || Blue || Hazel
|}<ref name="casinobeats"/>

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue & hazel eyes are "''by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats"/> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats"/>

Officer Jager arrived at the casino. According to Killinger's lawsuit he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up" ''to fabricate the documents.<ref name="casinobeats"/> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' & that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats"/>

Bodycam footage released in late 2025 captured Jager stating: <blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |website=Dexerto |date=2025-12-09 |access-date=2025-12-16}}</ref></blockquote>

Jager handcuffed Killinger & transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats"/>

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |website=Our Town Reno |date=2025-11-14 |access-date=2025-12-16}}</ref> His federal lawsuit against Officer Jager (''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD) is still active in the U.S. District Court for the District of Nevada as of December 16th 2025.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |website=Leagle |access-date=2025-12-16}}</ref>

The lawsuit alleges that Jager's actions violated Killinger's [[Fourteenth Amendment to the United States Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats"/> '''Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner & omitted the fingerprint exoneration from his official report.'''<ref name="casinobeats"/> He is seeking compensatory, special, & punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats"/> The case is expected to go to trial in 2026.<ref name="casino-org"/>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom"/> The case shows that when officers prioritize algorithmic identification over physical evidence & valid documentation, innocent individuals are subjected to unjust detention.

===Common ALPR Error Mechanisms===
These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (car plates matched to motorcycle registrations)
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles & criminal activity
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners
*'''Jurisdiction errors''': Out-of-state plates with identical numbers to in-state wanted vehicles generate false matches

==References==
{{reflist}}

[[Category:Flock Safety]]

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2025-12-16T19:21:57Z

Louis: added jason case

{{Alert|message = This is a special page dedicated a specific issue. It will be deleted once moved elsewhere, & is not representative of a typical wiki article.}}

So you've decided to say you do not want AI surveillance cameras in your city - but you don't know what argument to make. Here are some.

==NO EXPECTATION OF PRIVACY IN PUBLIC?==
[[File:1st amendment = no privacy?.jpg|alt=Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. |thumb|Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces. ]]

A common objection to constitutional challenges of automated license plate reader (ALPR) systems is the argument that individuals have ''"no expectation of privacy when in a public place."'' This argument oversimplifies [[Fourth Amendment to the United States Constitution|Fourth Amendment]] jurisprudence & misunderstands the legal standard of "reasonable expectation of privacy" established by the [[Supreme Court of the United States]].

===The "Reasonable" Standard in Fourth Amendment Law===

The Fourth Amendment protects against "unreasonable searches & seizures," not all searches. The constitutional analysis turns on whether surveillance violates a person's "reasonable expectation of privacy. This considers the nature, scope, & how intrusive the government monitoring is.

In ''[[Carpenter v. United States]]'' (2018), the Supreme Court explicitly rejected the argument that venturing into public eliminates Fourth Amendment protection. Chief Justice [[John Roberts]] wrote that the government's access to 127 days of cell-site location data; tracking movements on public roads; achieved ''"near perfect surveillance, as if it had attached an ankle monitor to the phone's user."''<ref name=":0">{{Cite web |title=16-402 Carpenter v. United States (06/22/2018) - 16-402_h315.pdf |url=https://www.supremecourt.gov/opinions/17pdf/16-402_h315.pdf |website=16-402 Carpenter v. United States (06/22/2018) - 16-402_h315.pdf}}</ref> The Court said<blockquote>''"A person does not surrender all Fourth Amendment protection by venturing into the public sphere."''<ref name=":0" /></blockquote>

===Distinction Between Momentary Observation & Comprehensive Surveillance===

Courts separate isolated instances of police observation & large scale automated tracking systems. In ''[[United States v. Jones]]'' (2012), Justice [[Sonia Sotomayor]]'s influential concurrence explained that [[GPS tracking]] <blockquote>''"generates a precise, comprehensive record of a person's public movements that reflects a wealth of detail about her familial, political, professional, religious, & sexual associations."''<ref name=":1">{{Cite web |title=10-1259 United States v. Jones (01/23/2012) - case.pdf |url=https://supreme.justia.com/cases/federal/us/565/10-1259/case.pdf |website=10-1259 United States v. Jones (01/23/2012) - case.pdf}}</ref> </blockquote>She noted that automated surveillance <blockquote>''"evades the ordinary checks that constrain abusive law enforcement practices: limited police resources & community hostility."<ref name=":1" />''</blockquote>The [[Massachusetts Supreme Judicial Court]] applied this reasoning to ALPR technology in ''Commonwealth v. McCarthy'' (2020), holding: <blockquote>''"With enough cameras in enough locations, the historic location data from an ALPR system in Massachusetts would invade a reasonable expectation of privacy & would constitute a search for constitutional purposes."''<ref name=":2">{{Cite web |title=COMMONWEALTH vs. JASON J. McCARTHY. Barnstable. October 2, 2019. - April 16, 2020. |url=https://cases.justia.com/massachusetts/supreme-court/2020-sjc-12750.pdf?ts=1587124946 |website=cases.justia.com}}</ref></blockquote>The court distinguished limited camera deployment from comprehensive networks, noting that widespread ALPR use would bring into question constitutional protections even though individual license plate observations would not.<ref name=":2" />

===Mosaic Theory===

The "[[mosaic theory]]" of Fourth Amendment protection holds that aggregating many individually innocuous observations can constitute a search requiring a warrant. Justice [[Samuel Alito]] noted in his ''Jones'' concurrence that <blockquote>''"society's expectation has been that law enforcement agents & others would not; & indeed, in the main, simply could not; secretly monitor & catalogue every single movement of an individual's car for a very long period."<ref name=":1" />'' </blockquote>The removal of practical constraints on surveillance through automated technology creates distinct constitutional concerns.

In ''[[United States v. Knotts]]'' (1983), while holding that limited [[beeper]] tracking did not constitute a search, the Supreme Court explicitly "reserved the question" of "whether different constitutional principles may be applicable" to "dragnet-type law enforcement practices."<ref>{{Cite web |title=United States v. Knotts {{!}} 460 U.S. 276 (1983) {{!}} Justia U.S. Supreme Court Center |url=https://supreme.justia.com/cases/federal/us/460/276/ |website=United States v. Knotts {{!}} 460 U.S. 276 (1983) {{!}} Justia U.S. Supreme Court Center}}</ref> This reservation recognized that comprehensive, suspicionless surveillance raises distinct Fourth Amendment issues from targeted tracking of individual suspects.

===Litigation on Citywide ALPR Networks===

In ''Schmidt v. City of Norfolk'' (E.D. Va. 2025), Chief Judge Mark S. Davis denied a motion to dismiss a constitutional challenge to Norfolk's 172-camera ALPR network, finding plaintiffs stated a plausible Fourth Amendment claim. The court wrote: <blockquote>''"A reasonable person could believe that society's expectations, as laid out by the Court in Carpenter, are being violated by the Norfolk Flock system. The complaint alleges facts notably similar to those in Carpenter that the Supreme Court found to clearly violate society's expectation of privacy: law enforcement secretly monitoring & cataloguing the whole of tens of thousands of individual's movements over an extended period."<ref>{{Cite web |title=OPINION AND ORDER denying Defendants' 18 Motion to Dismiss on both Rule 12(b)(1) and Rule 12(b)(6) grounds. Signed by Chief District Judge Mark S. Davis on 2/5/2025. (jhie, ) - 0.pdf |url=https://cases.justia.com/federal/district-courts/virginia/vaedce/2:2024cv00621/562101/29/0.pdf |website=OPINION AND ORDER denying Defendants' 18 Motion to Dismiss on both Rule 12(b)(1) and Rule 12(b)(6) grounds. Signed by Chief District Judge Mark S. Davis on 2/5/2025. (jhie, ) - 0.pdf}}</ref>''</blockquote>The case is scheduled for trial in Fall 2025 & could produce the first federal appellate ruling requiring warrants for comprehensive ALPR surveillance.

Legal scholars note that U.S. law enforcement scanned 2.5 billion license plates between 2016 & 2017, with 99.5% belonging to vehicles unassociated with criminal activity,<ref>{{Cite web |title=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers {{!}} Electronic Frontier Foundation |url=https://www.eff.org/pages/automated-license-plate-reader-dataset |website=Data Driven: Explore How Cops Are Collecting and Sharing Our Travel Patterns Using Automated License Plate Readers {{!}} Electronic Frontier Foundation}}</ref> illustrating the dragnet nature of modern ALPR deployment that distinguishes it from traditional targeted surveillance methods.

===Scale & the Reasonableness Analysis===

The Fourth Amendment's reasonableness standard recognizes that scale & comprehensiveness transform constitutional analysis. Courts analogize comprehensive automated surveillance to [[stalking]], noting that while a single observation in public does not violate privacy, systematically following someone everywhere for extended periods, documenting their movements, & sharing that information creates fundamentally different privacy implications.<ref>{{cite journal |last=Tokson |first=Matthew |title=Knowledge & Fourth Amendment Privacy |journal=Northwestern University Law Review |volume=111 |issue=1 |pages=139-198 |year=2016}}</ref>

Real-world deployments show the scale: Denver operates 111 cameras scanning approximately 2 million license plates monthly; Norfolk's 172 cameras provide citywide coverage & Austin's system scanned 113 million plates in a single year.<ref>{{cite news |url=https://coloradonewsline.com/2025/08/15/denver-ice-flock-immigration-searches/ |title=Denver's Flock Cameras Accessed for Immigration Enforcement |work=Colorado Newsline |date=2025-08-15}}</ref><ref>{{cite news |url=https://www.nbcnews.com/tech/security/virginia-police-used-flock-cameras-track-driver-safety-lawsuit-surveil-rcna230399 |title=Virginia police used Flock cameras to track driver 526 times in 4 months |work=NBC News |date=2024}}</ref>

==FALSE POSITIVES & SYSTEM FAILURES==

Automated surveillance systems have high risks of false positives where innocent individuals are subjected to armed police responses based on program errors. These create dangerous situations for law-abiding civilians who pose no threat.

===Baltimore County Gun Detection False Alarm===

In October 2025, an AI-powered gun detection system at Kenwood High School in Baltimore County misidentified a student's snack food as a firearm, triggering an armed police response. Taki Allen was sitting outside the school with friends eating Doritos when officers with drawn weapons approached him.

<blockquote>''"At first, I didn't know where they were going until they started walking toward me with guns, talking about, 'Get on the ground,' & I was like, 'What?'"<ref name="cnn-doritos">{{cite news |url=https://www.cnn.com/2025/10/25/us/baltimore-student-chips-ai-gun-detection-hnk |title=Student handcuffed after Doritos bag mistaken for a gun by school's AI security system |work=CNN |date=2025-10-25 |access-date=2025-10-28}}</ref>''</blockquote>

Allen was forced to his knees, handcuffed, & searched before officers realized he was unarmed. Allen described watching about 8 cop cars arrive, with officers pointing guns at him. <blockquote>

''"The first thing I was wondering was, was I about to die? Because they had a gun pointed at me,"'' </blockquote>

he told WBAL-TV.<ref name="cnn-doritos" />

When shown the image that triggered the alert, Allen explained: <blockquote>''"I was just holding a Doritos bag – it was two hands & one finger out, & they said it looked like a gun."<ref name="cnn-doritos" />''</blockquote>

Baltimore County high schools used the AI gun detection system in 2024, using existing school cameras to scan for potential weapons. The system is operated by Omnilert, which taps into existing camera feeds to detect objects that resemble weapons & then alerts both school safety officers & law enforcement automatically. The school acknowledged in a letter to families that counseling would be provided to students who witnessed the incident, recognizing the psychological impact of watching armed officers detain their peer.<ref name="cnn-doritos" />

Baltimore County Councilman Izzy Patoka called for a review of the system, stating: ''"No child in our school system should be accosted by police for eating a bag of Doritos."''<ref name="cnn-doritos" /> The company defended its system, claiming it ''"functioned as intended: to prioritize safety & awareness through rapid human verification,"'' though the incident clearly shows the system escalated to armed police response before adequate human review occurred.<ref>{{cite news |url=https://wtop.com/baltimore/2025/10/student-handcuffed-after-doritos-bag-mistaken-for-a-gun-by-maryland-schools-ai-security-system/ |title=Student handcuffed after Doritos bag mistaken for a gun by Maryland school's AI security system |work=WTOP News |date=2025-10-26 |access-date=2025-10-28}}</ref>
===ALPRs causing innocent people to be held at gunpoint===
Automated License Plate Reader systems create false alerts that result in innocent individuals being held at gunpoint during high-risk traffic stops.

====Brian Hofer Thanksgiving Incident (2018)====
In 2018, privacy advocate Brian Hofer & his younger brother were driving to visit their parents for Thanksgiving when they found themselves held at gunpoint by law enforcement officers. Hofer's vehicle had been incorrectly flagged as stolen by an ALPR system, triggering an armed police response.<blockquote>''"Your life definitely is different after you have guns pointed at you."<ref name="cbs-alpr">{{cite news |last1=Fichten |first1= |last2= |first2= |date= |title=When license plate readers get it wrong |url=https://www.cbsnews.com/news/license-plate-readers-alpr-mistakes/ |access-date=2025-10-28 |work=CBS News}}</ref>''</blockquote>Hofer, now executive director of Secure Justice, an organization that aims to reduce government & corporate overreach, advocates for manual verification of ALPR "hits" before armed responses. He notes that even with verification procedures, data errors in databases can cause plates to match incorrect entries. "There are billions of scans a day in America. If there's even just a 10% error rate, that means there are so many opportunities for abuse to happen," Hofer stated.<ref name="cbs-alpr" />

CBS News verified over a dozen similar cases during a six-month investigation into incidents of wrongful stops & ALPR technology abuse, finding that consequences range from inconvenient toll booth charges to potentially deadly armed detainments.<ref name="cbs-alpr" />

====Police Pursuit of Wrong Suspect (Body Camera Footage)====
Body camera footage from a documented police incident shows officers pursuing & detaining an innocent individual for approximately 30 minutes based on an ALPR false alert.<ref>{{cite web |title=Police Body Camera: ALPR False Alert Detention |url=https://youtu.be/lmNxitcaT2Y |access-date=2025-10-28 |publisher=YouTube}}</ref>

====Española, New Mexico Child Detentions====
In Española, New Mexico, ALPR misreads resulted in two separate armed detentions of minors within one month. '''A 12-year-old was handcuffed after an ALPR camera misread the last digit of a license plate on a vehicle driven by her older sister, interpreting a "2" as a "7,"''' according to a lawsuit filed against the city.<ref name="cbs-alpr" />

One month later in a separate incident, a 17-year-old honors student was held at gunpoint on his way home from school after officers mistook his vehicle for one associated with an individual sought in connection with a string of armed robberies. The case demonstrates how ALPR errors disproportionately create dangerous encounters for young people who have no criminal involvement.<ref name="cbs-alpr" />

====Aurora, Colorado Family Detained on Hot Pavement ($1.9 Million Settlement)====
In Aurora, Colorado in 2020, a mother & her family, including her 6-year-old daughter, were pulled over at gunpoint & forced to lie face down on hot pavement due to an ALPR error. Police mistakenly flagged their Colorado license plate as matching a completely different vehicle from a different state; a stolen motorcycle registered in Montana.<ref name="cbs-alpr" />

The incident, captured on video & widely condemned, led to a $1.9 million settlement from the city in 2024. .

====Peppermill Casino Facial Recognition Wrongful Arrest (2023)====

In September 2023, Jason Killinger, a long-haul UPS truck driver, was wrongfully arrested at the Peppermill Casino in Reno, Nevada, after the casino's facial recognition system misidentified him as a previously banned individual named Michael Ellis.<ref name="casino-org">{{Cite web |title=Peppermill Reno's Facial Recognition Tech Leads to Wrongful Arrest |url=https://www.casino.org/news/peppermill-renos-facial-recognition-tech-leads-to-wrongful-arrest/ |website=Casino.org |date=2025-11-11 |access-date=2025-12-16}}</ref> The AI system reportedly indicated a "100% match" in spite of large physical differences between the two men.<ref name="gaming-boardroom">{{Cite web |title=Peppermill Casino AI Software Gives 100% Match, Misidentifies Passer-by |url=https://thegamingboardroom.com/2025/11/12/peppermill-casino-ai-software-gives-100-match-misidentifies-passer-by/ |website=The Gaming Boardroom |date=2025-11-12 |access-date=2025-12-16}}</ref>

On September 17, 2023, Killinger entered the Peppermill Casino during a work trip. Casino security detained him based on a facial recognition alert identifying him as Michael Ellis, who had been issued a six-month trespass ban in March 2023 for sleeping on the premises.<ref name="casinobeats">{{Cite web |title=Reno Police Report Shows How Casino's Facial Recognition Led to Wrongful Arrest |url=https://casinobeats.com/2025/12/09/reno-police-report-facial-recognition-wrongful-arrest/ |website=CasinoBeats |date=2025-12-09 |access-date=2025-12-16}}</ref> Ellis's ban was set to expire on September 26, 2023—nine days after the arrest.<ref name="casinobeats"/>

Killinger showed the casino several forms of identification to prove his identity. This included his Nevada driver's license, a UPS payslip from his employer, & his vehicle registration.<ref name="casinobeats"/> All of these documents matched his true identity. According to his subsequent lawsuit, Killinger protested that he was not Ellis, but casino security did not believe him & called the police.<ref name="casino-org"/>

Released police records & driver's license images revealed significant physical differences between the two men that the facial recognition system failed to account for:

{| class="wikitable"
|-
! Characteristic !! Jason Killinger !! Michael Ellis
|-
| Height || 6'1" || 5'9"
|-
| Eye Color || Blue || Hazel
|}<ref name="casinobeats"/>

In his police report, Officer Richard Jager dismissed the eye color discrepancy, writing that blue & hazel eyes are "''by their very nature similar eye colors and are dependent upon lighting."''<ref name="casinobeats"/> The report also noted that Ellis had larger ears than Killinger.<ref name="casinobeats"/>

Officer Jager arrived at the casino. According to Killinger's lawsuit he rejected the valid ID documents. Killinger alleges in court filings that Jager accused him of having ''"a DMV hook-up" ''to fabricate the documents.<ref name="casinobeats"/> In his police report, Jager wrote that Killinger had ''"conflicting identification"'' & that ''"he lacked satisfactory evidence to reasonably assure me that he was who he claimed to be,"'' despite all identification documents matching the name Jason Killinger.<ref name="casinobeats"/>

Bodycam footage released in late 2025 captured Jager stating: <blockquote>"I have a feeling he's somehow making some fake identification or something."<ref name="dexerto">{{Cite web |title=Bodycam footage reveals moment innocent man is arrested after AI misidentifies him |url=https://www.dexerto.com/entertainment/bodycam-footage-reveals-moment-innocent-man-is-arrested-after-ai-misidentifies-him-3294374/ |website=Dexerto |date=2025-12-09 |access-date=2025-12-16}}</ref></blockquote>

Jager handcuffed Killinger & transported him to the police station. Killinger was detained for about 11 hours before fingerprint analysis proved he was not Michael Ellis.<ref name="casinobeats"/>

Killinger has since settled a claim with the Peppermill Casino for an undisclosed amount.<ref name="otr">{{Cite web |title=Victim of Black Mirror Scenario Settles with Peppermill and Goes After Local Reno Cop |url=http://www.ourtownreno.com/our-stories-1/2025/11/14/victim-of-black-mirror-scenario-settles-with-peppermill-and-goes-after-local-reno-cop |website=Our Town Reno |date=2025-11-14 |access-date=2025-12-16}}</ref> His federal lawsuit against Officer Jager (''Killinger v. Jager'', Case No. 3:25-cv-00388-MMD-CSD) is still active in the U.S. District Court for the District of Nevada as of December 16th 2025.<ref name="leagle">{{Cite web |title=KILLINGER v. JAGER |url=https://www.leagle.com/decision/infdco20250925d22 |website=Leagle |access-date=2025-12-16}}</ref>

The lawsuit alleges that Jager's actions violated Killinger's [[Fourteenth Amendment to the United States Constitution|Fourteenth Amendment]] right to due process.<ref name="casinobeats"/> '''Killinger alleges that Jager failed to utilize the police department's own fingerprint technology in a timely manner & omitted the fingerprint exoneration from his official report.'''<ref name="casinobeats"/> He is seeking compensatory, special, & punitive damages; the lawsuit does not specify the amounts sought.<ref name="casinobeats"/> The case is expected to go to trial in 2026.<ref name="casino-org"/>

Unlike most documented facial recognition wrongful arrests which involve police databases, this incident originated from a private casino's commercial system.<ref name="gaming-boardroom"/> The case shows that when officers prioritize algorithmic identification over physical evidence & valid documentation, innocent individuals are subjected to unjust detention.

===Common ALPR Error Mechanisms===
These incidents illustrate how ALPR systems create dangerous misidentifications through multiple mechanisms:

*'''Plate misreads''': OCR (optical character recognition) errors confuse similar characters (O/0, I/1, B/8, 2/7), causing the system to flag vehicles that match stolen vehicle databases or warrant lists
*'''Cross-state confusion''': Systems incorrectly match vehicles from different states or confuse vehicle types (car plates matched to motorcycle registrations)
*'''Cloned plates''': Criminals using stolen or duplicated license plates create false associations between innocent vehicles & criminal activity
*'''Stale data''': Vehicles recovered from theft or resolved warrant cases remain in hot lists, triggering alerts on lawful owners
*'''Jurisdiction errors''': Out-of-state plates with identical numbers to in-state wanted vehicles generate false matches

==References==
{{reflist}}

[[Category:Flock Safety]]

Projects:Cargo-complete

2025-12-01T21:29:18Z

Louis: from smart person english to idiotproof english

Wiki articles need 160-200 character summaries so that they can be shown as alerts to users. Let's say a wiki user is on a website where product X is being sold that screws them over. We will have a browser plugin that pops up an alert with a summary on how that product screws over the customer.

This means the wiki articles have to have a 160-200 character summary, but many do not! We need people to edit the articles below to add a 160 character summary to them in the appropriate area so that the page will have that short description come up when queried by a browser plugin or something else that is looking up companies/products in the wiki. We've put this together to try and make it easier to track down and identify articles in need of metadata updates.
===What are Cargo tables?===
Cargo tables are data structures used on the Consumer Rights Wiki for storing info about articles. These can be used to create queries on the wiki (like the ones generating the tables you see below) as well as accessed via the wiki's API by things like the consumerrights.wiki browser extension project.

We have a few different Cargo tables, which are linked below. Each corresponds to a certain [[Consumer Rights Wiki:Article types|article type]] (although not all article types have Cargo tables).
===Project goals===
The purpose of project Cargo-Complete is to ensure that every Cargo table on the wiki contains all the information that it should, and that every relevant page has a Cargo table. This page contains tables which fetch all of the articles with each kind of Cargo table present on them, By checking over these tables, you should be able to identify articles where the Cargo data is missing, incorrect, or incomplete.

The pages which should have a Cargo table include:
*Pages about specific incidents ([[Template:IncidentCargo|template]])
*Pages about specific companies ([[Template:CompanyCargo|template]])
*Pages about specific products or services ([[Template:ProductCargo|template]])
*Pages about specific product lines ([[Template:ProductLineCargo|template]])

It is also quite likely that pages will exist on the Wiki that should have a Cargo table, but do not have one.

A good number of pages which should have cargo tables but don't are currently using the deprecated [[Template:InfoboxCompany|InfoboxCompany template]]. A list of such articles can be found here: https://consumerrights.wiki/w/Special:WhatLinksHere/Template:InfoboxCompany which should serve as as a good starting point for looking for articles that don't have the relevant cargo table.

==What you need to do==
We need you to go through the tables below and 'fill in the blanks', as well as check for pages that don't have Cargo tables, and make cargo tables for them.

There are two good ways of editing a Cargo table. The first, and best, is through the source editor. Cargo tables are stored as plaintext within articles, and you can add or fill in fields within a Cargo table by simply adding the fields, or changing the information within them. Take a look at the template pages linked above if you're not sure on how this works.

It is also possible to edit them by going though the 'create a page' flow, and entering the name of a page that already exists (with the correct article type). This will take you to a form where you can change and add information to the various Cargo table fields. This also works for creating Cargo tables on pages that don't have them.

Feel free to keep a tally of the pages you've fixed up on the discussion page for this project, or share any tools or techniques you're using to make progress on the project with other editors, it'll be a great help!

This project will be considered complete when all relevant pages contain Cargo tables, and all Cargo tables have their full complement of data.

==Incidents==

{{#cargo_query:
|tables=Incident
|fields=_pageName=Page, Company, StartDate=Start Date, EndDate=End Date, Status, Product, Type, Description
|order by=_pageName
|format=table
|class=wikitable sortable
|limit=1000
}}
==Companies==
{{#cargo_query:
|tables=Company
|fields=_pageName=Page, Type, Industry, Founded, ParentCompany=Parent Company, Website, Description
|order by=_pageName
|format=table
|class=wikitable sortable
|limit=1000
}}

==Products==
{{#cargo_query:
|tables=Product
|fields=_pageName=Page, Company, ProductLine=Product Line, Category, ArticleType=Article Type, ReleaseYear=Release Year, InProduction=In Production, Description
|order by=_pageName
|format=table
|class=wikitable sortable
|limit=1000
}}

==Product lines==
{{#cargo_query:
|tables=ProductLine
|fields=_pageName=Page, Company, Category, ArticleType=Article Type, ReleaseYear=Release Year, InProduction=In Production, Description
|order by=_pageName
|format=table
|class=wikitable sortable
|limit=1000
}}
[[Category:Projects]]

NDAA has military right to repair stripped from it in favor of data as a service

2025-11-20T05:01:55Z

Louis:

{{Alert|message = This is a special page dedicated to a youtube video because youtube fails at allowing you to add real descriptions, it will be deleted once irrelevant and is not representative of a typical wiki article.}}

==issue==

*large pentagon contractors are undermining the Trump administration’s priorities on military right to repair by trying to strip the bipartisan House- & Senate-passed right to repair language & replace it with “data-as-a-service,” which was included in Representative Mike Rogers & Adam Smith’s [https://armedservices.house.gov/uploadedfiles/speed_act_full_text.pdf SPEED Act].
**Representative Mike Rogers has [https://www.opensecrets.org/members-of-congress/mike-d-rogers/industries?cid=N00024759&cycle=2024 received]over $535,000 from the defense industry, the top sector that donates to his campaigns. He is a top recipient from the “Defense Electronics” [https://www.opensecrets.org/members-of-congress/mike-d-rogers/industries?cid=N00024759&cycle=2024 industry], in particular. $10,500 for Rogers from Boeing. $66,650 from L3. Representative Adam Smith has [https://www.opensecrets.org/members-of-congress/adam-smith/industries?cid=N00007833&cycle=2024 received] $310,550 from the defense industry, which is the second top sector that donates to his campaign. Palantir is Smith’s #3 top [https://www.opensecrets.org/members-of-congress/adam-smith/contributors?cid=N00007833&cycle=2024 contributor].
*If right to repair is replaced by data as a service, it will be a direct undermining of policy outlined by the Trump White [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ House], Defense Secretary Pete [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ Hegseth], Army Secretary Dan [https://www.warren.senate.gov/newsroom/press-releases/warren-statement-on-army-right-to-repair-victory Driscoll], & Navy Secretary John [https://www.war.gov/News/News-Stories/Article/Article/4212472/navy-secretary-advocates-for-sailors-right-to-repair-equipment/ Phelan].
*The defense primes are the ones fighting against this Trump-backed policy, while small- & medium-sized businesses who could compete for new repair contracts support right to repair.


==What does “data-as-a-service” do?==

*It creates additional red tape that makes the status quo worse: currently, DoD can negotiate for access to rights long-term (though contractors still have the upper hand). Data-as-a-service/pay-per-use would mean DoD would have to ask major contractors for permission every time DoD needs repair tools or data, & would cause more delays in contested logistics environments with service members having to get one-time access to data they need to repair broken equipment.
*Data-as-a-service/pay-per-use makes the big Pentagon contractors’ goals obvious, they’re willing to share repair data with our military, but only if they can charge through the nose.
*More specifically, it requires DoD to contract to a company’s data library on a pay-per-use model, increasing costs & discouraging DoD & competitors from providing repair services.
*This is similar to disingenuous [https://www.ifixit.com/News/80635/car-companies-are-astroturfing-right-to-repair memorandums of understanding] used by car manufacturers who oppose the right to repair. The data-as-a-service provision is used to appear as though they’re responsive to concerns about repair restrictions, but they still lock out car owners & independent repairers.
**John Deere has attempted to appease farmers w/ similar tactics, most recently releasing a new digital repair tool called Operations Center Pro Service which would require farmers to have high speed internet to repair equipment, including in the middle of the field, & requires farmers to pay for it every year in order to have access.
**Deere has tried this tactic before, releasing software it said fixed the problem but that meant farmers [https://pirg.org/edfund/resources/john-deere-repair-software/ couldn’t find or access] the basic information they needed.
**In this case, while the primes seem to [https://www.defenseone.com/business/2025/11/draft-list-attendees-hegseth-acquisition-reform-speech-shows-wide-industry-interest/409344/?oref=d1-homepage-river pretend]to Secretary Hegseth that they care about this issue, in reality, they’re undermining it.


==timeline:==

*January 2025: Senator Warren [https://pirg.org/articles/army-secretary-nominee-supports-military-right-to-repair/ gets]commitment from Secretary Dan Driscoll to work with her on tackling repair restrictions for the military.
*May 2025: Secretary of the Army, Daniel P. Driscoll, [https://pirg.org/resources/the-army-embraces-right-to-repair-why-that-matters-and-what-comes-next/ announced] that the Army will ensure right to repair provisions are included in future Army contracts.
*May 2025 - [https://pirg.org/media-center/report-americans-support-military-right-to-repair-by-nearly-a-7-to-1-margin/ Poll]shows Americans support military right to repair by nearly a 7-to-1 margin.
*July 2025: Senators Warren & Tim Sheehy (R-Mont.) introduced the [https://www.congress.gov/bill/119th-congress/senate-bill/2209/text Warrior Right to Repair Act of 2025], legislation that would require contractors to provide the Department of Defense (DoD) with access to technical data & materials the military needs to repair & maintain its own equipment.
*July 2025: A provision, which includes portions of Senator Warren’s bipartisan [https://www.warren.senate.gov/newsroom/press-releases/warren-sheehy-introduce-bipartisan-bill-to-guarantee-military-right-to-repair-its-equipment Warrior Right to Repair Act], to guarantee all branches of the military the right to repair their equipment & requires contractors to provide any information needed to repair the equipment, was secured with bipartisan support in the Senate Armed Services Committee for FY26 NDAA.
*July 2025 - Intellectual property legal experts send [https://pirg.org/wp-content/uploads/2025/07/Professors-military-repair-letter-final-2.pdf letter] to Congress that the ''Warrior Right to Repair Act''is consistent with long held law & “presents no conflict with manufacturers’ IP rights.”
*September 2025: the White House [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ announced]support for Warren-Sheehy military right to repair policy.
*September 2025 - National Defense Industrial Association (NDIA) issues [https://www.ndia.org/-/media/sites/ndia/policy/ip-and-data-rights/ip-and-data-rights-white-paper.pdf?download=1?download=1 white paper] opposing military right to repair & advocating for “data as a service.”
*October 2025: NDAA, which includes the Warren-Sheehy provision, passed the U.S. Senate.
*October 2025 - [https://www.sema.org/news-media/press-release/339-small-businesses-urges-passage-right-repair-bill-us-military 339 small businesses] sent a letter urging passive of military right to repair. “This is about ensuring the government can maintain & repair what it already owns. It’s about making sure the Department of Defense has access to every capable partner in the country to keep our military mission-ready.”
*October 2025 - Trump administration issues statements of administration policy on the [https://www.whitehouse.gov/wp-content/uploads/2025/09/SAP-HR3838-House-NDAA.pdf House] & [https://www.whitehouse.gov/wp-content/uploads/2025/09/SAP-S2296-Senate-NDAA-9.9.25.pdf Senate] NDAAs supporting military right to repair.
*October 2025 - Former Trump DoD undersecretary of defense for personnel & readiness & VA Secretary Robert Wilkie [https://thehill.com/opinion/national-security/5551775-defense-contractor-logistics-reform/ endorses military right to repair].
*Now: The House & Senate versions of the FY26 NDAA go to conference.
*November 2025 - With Honor sends [https://withhonor.org/news/with-honor-action-urges-inclusion-of-key-reforms-in-final-fy26-defense-bill/ letter urging] military right to repair be included in the final NDAA.
*November 2025 - taxpayer & watchdog groups send [https://www.ntu.org/publications/detail/joint-letter-ndaa-conference-recommendations letter] urging support for military right to repair in final NDAA.
*November 2025 - shill for aerospace industries association [https://www.washingtontimes.com/news/2025/nov/13/congress-right-repair-provisions-threatens-backbone-us-defense/ publishes an op-ed] opposing military right to repair.
*November 2025 - Secretary Hegseth announces new DoD acquisition policy including that “''The Department must plan for & acquire systems with the ability to conduct organic depot-level maintenance, repair, & overhaul of systems & sub-systems to ensure military readiness for any conflict.”''

NDAA has military right to repair stripped from it in favor of data as a service

2025-11-20T04:57:18Z

Louis: draft

==issue==

*large pentagon contractors are undermining the Trump administration’s priorities on military right to repair by trying to strip the bipartisan House- & Senate-passed right to repair language & replace it with “data-as-a-service,” which was included in Representative Mike Rogers & Adam Smith’s [https://armedservices.house.gov/uploadedfiles/speed_act_full_text.pdf SPEED Act].
**Representative Mike Rogers has [https://www.opensecrets.org/members-of-congress/mike-d-rogers/industries?cid=N00024759&cycle=2024 received]over $535,000 from the defense industry, the top sector that donates to his campaigns. He is a top recipient from the “Defense Electronics” [https://www.opensecrets.org/members-of-congress/mike-d-rogers/industries?cid=N00024759&cycle=2024 industry], in particular. $10,500 for Rogers from Boeing. $66,650 from L3. Representative Adam Smith has [https://www.opensecrets.org/members-of-congress/adam-smith/industries?cid=N00007833&cycle=2024 received] $310,550 from the defense industry, which is the second top sector that donates to his campaign. Palantir is Smith’s #3 top [https://www.opensecrets.org/members-of-congress/adam-smith/contributors?cid=N00007833&cycle=2024 contributor].
*If right to repair is replaced by data as a service, it will be a direct undermining of policy outlined by the Trump White [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ House], Defense Secretary Pete [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ Hegseth], Army Secretary Dan [https://www.warren.senate.gov/newsroom/press-releases/warren-statement-on-army-right-to-repair-victory Driscoll], & Navy Secretary John [https://www.war.gov/News/News-Stories/Article/Article/4212472/navy-secretary-advocates-for-sailors-right-to-repair-equipment/ Phelan].
*The defense primes are the ones fighting against this Trump-backed policy, while small- & medium-sized businesses who could compete for new repair contracts support right to repair.


==What does “data-as-a-service” do?==

*It creates additional red tape that makes the status quo worse: currently, DoD can negotiate for access to rights long-term (though contractors still have the upper hand). Data-as-a-service/pay-per-use would mean DoD would have to ask major contractors for permission every time DoD needs repair tools or data, & would cause more delays in contested logistics environments with service members having to get one-time access to data they need to repair broken equipment.
*Data-as-a-service/pay-per-use makes the big Pentagon contractors’ goals obvious, they’re willing to share repair data with our military, but only if they can charge through the nose.
*More specifically, it requires DoD to contract to a company’s data library on a pay-per-use model, increasing costs & discouraging DoD & competitors from providing repair services.
*This is similar to disingenuous [https://www.ifixit.com/News/80635/car-companies-are-astroturfing-right-to-repair memorandums of understanding] used by car manufacturers who oppose the right to repair. The data-as-a-service provision is used to appear as though they’re responsive to concerns about repair restrictions, but they still lock out car owners & independent repairers.
**John Deere has attempted to appease farmers w/ similar tactics, most recently releasing a new digital repair tool called Operations Center Pro Service which would require farmers to have high speed internet to repair equipment, including in the middle of the field, & requires farmers to pay for it every year in order to have access.
**Deere has tried this tactic before, releasing software it said fixed the problem but that meant farmers [https://pirg.org/edfund/resources/john-deere-repair-software/ couldn’t find or access] the basic information they needed.
**In this case, while the primes seem to [https://www.defenseone.com/business/2025/11/draft-list-attendees-hegseth-acquisition-reform-speech-shows-wide-industry-interest/409344/?oref=d1-homepage-river pretend]to Secretary Hegseth that they care about this issue, in reality, they’re undermining it.


==timeline:==

*January 2025: Senator Warren [https://pirg.org/articles/army-secretary-nominee-supports-military-right-to-repair/ gets]commitment from Secretary Dan Driscoll to work with her on tackling repair restrictions for the military.
*May 2025: Secretary of the Army, Daniel P. Driscoll, [https://pirg.org/resources/the-army-embraces-right-to-repair-why-that-matters-and-what-comes-next/ announced] that the Army will ensure right to repair provisions are included in future Army contracts.
*May 2025 - [https://pirg.org/media-center/report-americans-support-military-right-to-repair-by-nearly-a-7-to-1-margin/ Poll]shows Americans support military right to repair by nearly a 7-to-1 margin.
*July 2025: Senators Warren & Tim Sheehy (R-Mont.) introduced the [https://www.congress.gov/bill/119th-congress/senate-bill/2209/text Warrior Right to Repair Act of 2025], legislation that would require contractors to provide the Department of Defense (DoD) with access to technical data & materials the military needs to repair & maintain its own equipment.
*July 2025: A provision, which includes portions of Senator Warren’s bipartisan [https://www.warren.senate.gov/newsroom/press-releases/warren-sheehy-introduce-bipartisan-bill-to-guarantee-military-right-to-repair-its-equipment Warrior Right to Repair Act], to guarantee all branches of the military the right to repair their equipment & requires contractors to provide any information needed to repair the equipment, was secured with bipartisan support in the Senate Armed Services Committee for FY26 NDAA.
*July 2025 - Intellectual property legal experts send [https://pirg.org/wp-content/uploads/2025/07/Professors-military-repair-letter-final-2.pdf letter] to Congress that the ''Warrior Right to Repair Act''is consistent with long held law & “presents no conflict with manufacturers’ IP rights.”
*September 2025: the White House [https://www.usatoday.com/story/news/politics/2025/10/01/pentagon-senate-provision-gains-trump-admin-support/86455785007/ announced]support for Warren-Sheehy military right to repair policy.
*September 2025 - National Defense Industrial Association (NDIA) issues [https://www.ndia.org/-/media/sites/ndia/policy/ip-and-data-rights/ip-and-data-rights-white-paper.pdf?download=1?download=1 white paper] opposing military right to repair & advocating for “data as a service.”
*October 2025: NDAA, which includes the Warren-Sheehy provision, passed the U.S. Senate.
*October 2025 - [https://www.sema.org/news-media/press-release/339-small-businesses-urges-passage-right-repair-bill-us-military 339 small businesses] sent a letter urging passive of military right to repair. “This is about ensuring the government can maintain & repair what it already owns. It’s about making sure the Department of Defense has access to every capable partner in the country to keep our military mission-ready.”
*October 2025 - Trump administration issues statements of administration policy on the [https://www.whitehouse.gov/wp-content/uploads/2025/09/SAP-HR3838-House-NDAA.pdf House] & [https://www.whitehouse.gov/wp-content/uploads/2025/09/SAP-S2296-Senate-NDAA-9.9.25.pdf Senate] NDAAs supporting military right to repair.
*October 2025 - Former Trump DoD undersecretary of defense for personnel & readiness & VA Secretary Robert Wilkie [https://thehill.com/opinion/national-security/5551775-defense-contractor-logistics-reform/ endorses military right to repair].
*Now: The House & Senate versions of the FY26 NDAA go to conference.
*November 2025 - With Honor sends [https://withhonor.org/news/with-honor-action-urges-inclusion-of-key-reforms-in-final-fy26-defense-bill/ letter urging] military right to repair be included in the final NDAA.
*November 2025 - taxpayer & watchdog groups send [https://www.ntu.org/publications/detail/joint-letter-ndaa-conference-recommendations letter] urging support for military right to repair in final NDAA.
*November 2025 - shill for aerospace industries association [https://www.washingtontimes.com/news/2025/nov/13/congress-right-repair-provisions-threatens-backbone-us-defense/ publishes an op-ed] opposing military right to repair.
*November 2025 - Secretary Hegseth announces new DoD acquisition policy including that “''The Department must plan for & acquire systems with the ability to conduct organic depot-level maintenance, repair, & overhaul of systems & sub-systems to ensure military readiness for any conflict.”''

Smartaira & plume wifi motion detection

2025-11-18T21:00:21Z

Louis:

{{IncidentCargo
|Company=Smartaira, Plume
|Description=Apartment complex residents provided Smartaira internet with Plume hardware capable of motion detection via Wi‑Fi, raising tenant privacy concerns
}}
==Background==
Smartaira is an internet service provider that specializes in bulk broadband solutions for multi‑dwelling units (MDUs) like apartment complexes. Instead of residents choosing their own internet provider fir their aprtment, the property owner contracts Smartaira to provide service throughout the building. Smartaira installs & manages the network infrastructure, including community‑wide Wi‑Fi & in‑unit wired Ethernet jacks; each apartment connects with private credentials to a secure virtual LAN (VLAN).<ref>{{cite web |url=https://smartaira.com/property-owners/ |title=Property Owners |website=Smartaira |access-date=2025-11-18}}</ref><ref>{{cite web |url=https://communities.smartaira.com/dedicated-wifi-faqs |title=Dedicated Wi‑Fi FAQs |website=Smartaira |access-date=2025-11-18}}</ref>

Plume’s motion sensing technology, known as "Plume Motion" or "Sense," uses Wi‑Fi signal disruptions to detect movement in the home. This allows a Wi‑Fi router to double as a passive motion detector by analyzing how wireless signals fluctuate when someone moves through a space.<ref>{{cite web |url=https://www.plume.com/legal/privacy-rights-notice |title=Privacy Rights Notice (U.S.) |website=Plume |date=2024-07-01 |access-date=2025-11-18}}</ref><ref>{{cite web |url=https://armstrongonewire.com/Support/Internet/Articles/PlumeMotion |title=Plume HomePass® Sense |website=Armstrong |access-date=2025-11-18}}</ref>

In installations where Smartaira & Plume jointly provide internet to residents, access points are typically pre‑installed in each unit, & residents are provided personal Wi‑Fi credentials with VLAN isolation. In‑unit access points expose Ethernet ports for wired devices, & residents may request pass‑through to use a personal router (with limited support).<ref>{{cite web |url=https://communities.smartaira.com/dedicated-wifi-faqs |title=Dedicated Wi‑Fi FAQs |website=Smartaira |access-date=2025-11-18}}</ref>

==Incident==
In bulk, community‑managed deployments, the network is designed as a community‑wide wireless architecture with per‑apartment private credentials & VLAN separation, meaning all apartments connect to one centrally managed system while keeping traffic logically isolated. This also enables centralized administration of the hardware & services across all units.<ref>{{cite web |url=https://smartaira.com/property-owners/ |title=Property Owners |website=Smartaira |access-date=2025-11-18}}</ref><ref>{{cite web |url=https://communities.smartaira.com/dedicated-wifi-faqs |title=Dedicated Wi‑Fi FAQs |website=Smartaira |access-date=2025-11-18}}</ref>

Plume’s privacy documentation confirms that when motion detection is active, the system collects information on motion in the home as “disruptions in Wi‑Fi waves” & maintains a pattern of motion & motion history; Plume also states it draws inferences to create a profile reflecting preferences, characteristics, & behavior.<ref>{{cite web |url=https://www.plume.com/legal/privacy-rights-notice |title=Privacy Rights Notice (U.S.) |website=Plume |date=2024-07-01 |access-date=2025-11-18}}</ref>

==Legal context==
Plume’s U.S. Privacy Rights Notice serves as a CCPA/CPRA “Notice at Collection” & lists categories of data processed for Plume Home, including “motion in the home … collected as disruptions in Wi‑Fi waves … which collectively provide a pattern of motion & motion history,” as well as inferences drawn to create behavioral profiles.<ref>{{cite web |url=https://www.plume.com/legal/privacy-rights-notice |title=Privacy Rights Notice (U.S.) |website=Plume |date=2024-07-01 |access-date=2025-11-18}}</ref> Plume’s Customer Privacy Policy further clarifies that a Customer Network administrator can disable motion sensing, at which point Plume will no longer collect live motion data or generate motion reports. However, this does not mean that the tenant has the ability to disable motion sensing. <ref>{{cite web |url=https://www.plume.com/legal/privacy |title=Customer Privacy Policy |website=Plume |access-date=2025-11-18}}</ref>

==Business context==
Smartaira markets both retail & '''bulk''' (owner‑provided) delivery models for apartment buildings. In the bulk model, the property owner purchases service & resells it as an amenity to all residents; Smartaira integrates the service with property management systems & proactively monitors & manages the network.<ref>{{cite web |url=https://smartaira.com/property-owners/ |title=Property Owners |website=Smartaira |access-date=2025-11-18}}</ref>

==Consumer impact==
The presence of Wi‑Fi‑based motion detection & motion history in a centrally administered, bulk network raises tenant privacy concerns about occupancy tracking & behavioral profiling in the home, given Plume’s documentation of motion histories & inferences.<ref>{{cite web |url=https://www.plume.com/legal/privacy-rights-notice |title=Privacy Rights Notice (U.S.) |website=Plume |date=2024-07-01 |access-date=2025-11-18}}</ref> Plume provides user‑facing motion alert notifications & a motion history view in its app, showing the granularity of data available about in‑home activity patterns.<ref>{{cite web |url=https://support.plume.com/s/article/How-do-I-set-up-motion-alert-notifications |title=How do I set up motion alert notifications? |website=Plume Support |access-date=2025-11-18}}</ref><ref>{{cite web |url=https://support.plume.com/s/topic/0TO6g000000x9deGAA/motion |title=Motion (topic hub) |website=Plume Support |access-date=2025-11-18}}</ref> In administrator‑managed networks, Plume states that the Customer Network administrator, NOT the resident, has the option to disable motion sensing, which is relevant to opt‑out control in bulk deployments.<ref>{{cite web |url=https://www.plume.com/legal/privacy |title=Customer Privacy Policy |website=Plume |access-date=2025-11-18}}</ref>

==References==
{{reflist}}

[[Category:Privacy controversies]]
[[Category:Surveillance]]
[[Category:Internet service providers]]
[[Category:Wi‑Fi]]
[[Category:Plume]]
[[Category:Smartaira]]
[[Category:2025 controversies]]
{{Ph-I-C}}

Smartaira & plume wifi motion detection

2025-11-18T19:31:30Z

Louis: Created page with "{{IncidentCargo |Company=smartaira, plume |Description=apartment complex residents forced into paying for internet from providers that can track movement via wifi that cannot be turned off }} {{Ph-I-Int}} ==Background== {{Ph-I-B}} ==[Incident]== {{Ph-I-I}} ===[Company]'s response=== {{Ph-I-ComR}} ==Lawsuit== {{Ph-I-L}} ==Consumer response== {{Ph-I-ConR}} ==References== {{reflist}} {{Ph-I-C}}"

{{IncidentCargo
|Company=smartaira, plume
|Description=apartment complex residents forced into paying for internet from providers that can track movement via wifi that cannot be turned off
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Hyundai Ioniq 5 N brake pad repair restrictions

2025-11-17T21:17:46Z

Louis: minor revisions

{{OngoingEvent}}
{{IncidentCargo
|Company=Hyundai
|StartDate=2025-10-30
|Status=Active
|ProductLine=Hyundai Ioniq 5 EVs
|Product=Hyundai Ioniq 5 N,Hyundai Ioniq 5
|ArticleType=Product
|Type=Repairability
|Description=Hyundai does not allow the DIY repair of rear brake pads on the Ioniq 5 N without access to proprietary software not readily available to consumers
}}

Ioniq 5 N cars from Hyundai do not appear to allow for DIY brake pad replacement, due to Electronic Parking Brake (EPB) system software restrictions, as discovered by a Reddit user.<ref name="reddit">{{cite web |author=u/SoultronicPear |date=2025-10-30 |title=Hyundai declares WAR on Right to Repair |url=https://www.reddit.com/r/Ioniq5N/comments/1ojjp6m/hyundai_declares_war_on_right_to_repair/ |access-date=2025-11-17 |website=Reddit}}</ref> The story was picked up by specialist car media as an example of the ongoing issues with automotive right to repair. As of 17/11/2025, reporting has only brought attention to the case and provided commentary, without independent verification beyond the original Reddit post.<ref name="drive">{{cite web |last=Collins |first=Andrew P. |date=2025-11-13 |title=Replacing Brake Pads on a Hyundai Ioniq 5 N Requires a Professional Mechanic's Login |url=https://www.thedrive.com/news/replacing-brake-pads-on-a-hyundai-ioniq-5-n-requires-a-professional-mechanics-login |access-date=2025-11-17 |website=The Drive}}</ref><ref name="carscoops">{{cite web |last=Rivers |first=Stephen |date=2025-11-09 |title=Apparently You Need Hyundai’s Permission To Change Your Own Brakes |url=https://www.carscoops.com/2025/11/ioniq-5-n-owner-says-hyundai-wont-even-let-you-change-your-brake-pads/ |access-date=2025-11-17 |website=Carscoops}}</ref><ref name="autoblog">{{cite web |last=Marion |first=Leroy |date=2025-11-11 |title=Hyundai Is Now Locking DIY Owners Out of Their Own Brake Repairs |url=https://www.autoblog.com/news/hyundai-is-now-locking-diy-owners-out-of-their-own-brake-repairs |access-date=2025-11-17 |website=Autoblog}}</ref><ref name="newswheel">{{cite web |date=2025-11-10 |title=Apparently Changing Your Own Brakes Is Off-Limits If You Drive a Hyundai EV |url=https://thenewswheel.com/apparently-changing-own-brakes-is-off-limits-drive-hyundai-ev/ |access-date=2025-11-17 |website=The News Wheel}}</ref>

Hyundai has responded to coverage, stating that they are "actively exploring ways to make routine maintenance easier for all customers while upholding safety standards."<ref name="drive" />

==Background==
Brake pads are a wear item universal to all cars, and have historically been a part commonly replaced by car owners as a routine maintenance task.<ref>{{cite web |title=Brake Pad Replacement |url=https://www.popularmechanics.com/cars/how-to/a10118/diy-brake-pad-replacement-15203569/ |website=Popular Mechanics |access-date=2025-11-17}}</ref> The Ioniq 5 N was released in 2024 and as the typical lifespan of brake pads is around 25,000–70,000 miles, most users would not have needed to replace them by the time of the incident.<ref>{{cite web |title=How Long Do Brake Pads Last? |url=https://www.caranddriver.com/research/a32839568/how-long-do-brake-pads-last/ |website=Car and Driver |access-date=2025-11-17}}</ref>

The addition of difficult-to-obtain software-based requirements for parts replacement is not exclusive to Hyundai within the automotive sector.<ref name="drive" />

==Initial Reddit post, and public attention==
On October 30, 2025, Reddit user u/SoultronicPear submitted a post to the r/Ioniq5N subreddit where they detailed their struggles to replace the brake pads of their car.<ref name="reddit" /> According to the post, the user discovered that the vehicle's Electronic Parking Brake (EPB) system prevented the replacement without specialized diagnostic tools. The user reported that the EPB must be retracted using proprietary software to accommodate new brake pads, and that post-installation recalibration is required.<ref name="reddit" /><ref name="drive" />

The Reddit user stated they attempted to follow Hyundai's official procedures by purchasing a J2534 diagnostic tool subscription for $60 per week and compatible hardware costing between $800–$2,000. However, they reported being blocked by NASTF (National Automotive Service Task Force) with a message stating "DIYers are not permitted access" and requiring a business Federal Employer Identification Number.<ref name="reddit" /><ref name="drive" /> The user expressed frustration, stating "My blood is boiling," after being locked out of the system they had paid to access.<ref name="newswheel" />

According to the Reddit post, dealers use a different Android-based Global Diagnostic System (GDS) that works seamlessly but costs approximately $6,000 and is not readily available to consumers.<ref name="carscoops" />

===Workaround===
According to discussions documented by Hackaday, the Reddit user reportedly found a workaround using a Harbor Freight T7 bidirectional scan tool, which successfully issued parking brake retract commands, though it reportedly threw error codes in the process.<ref name="hackaday">{{cite web |last=Bartz |first=Navarre |date=2025-11-15 |title=Hyundai Paywalls Brake Pad Changes |url=https://hackaday.com/2025/11/15/hyundai-paywalls-brake-pad-changes/ |access-date=2025-11-17 |website=Hackaday}}</ref>

==Hyundai's response==
After being contacted by The Drive, Hyundai issued the following statements:<ref name="drive" /><blockquote>''“Hyundai is committed to supporting both our dealer network and independent repair facilities with safe, secure, and accessible service solutions. For vehicles equipped with electronic parking brakes, including the Ioniq 5 and Ioniq 5 N, the official repair procedure requires placing the rear calipers in service mode using either our Global Diagnostic System (GDS) or the J2534 application. This ensures proper functionality and customer safety. Hyundai recently expanded access through an update to our J2534 application, enabling aftermarket users to perform functions previously restricted by the GDS secure gateway. While authentication through NASTF is required for sensitive operations, this step helps maintain security and accountability. Our official dealer tool (GDS) is also available for purchase by anyone.''

''Hyundai is actively exploring ways to make routine maintenance easier for all customers while upholding safety standards."''

''“We appreciate the interest in DIY repairs and will continue working toward solutions that balance convenience with security.”''</blockquote>

==Public response==
The story gained traction across automotive and technology media outlets in mid-November 2025. The Drive characterized the situation as ''"a car repair task that has historically been totally DIY'able in a driveway is now relegated to shop-only because of technology,"'' while noting that technically Hyundai may be compliant with right-to-repair legislation as written.<ref name="drive" /> Carscoops noted that while the repair "can be done," it requires ''"specialized tools or have deep pockets"'' with costs comparable to "a tired old hatchback from the classifieds."<ref name="carscoops2">{{cite web |last=Rivers |first=Stephen |date=2025-11-17 |title=Sure, You Can Replace Ioniq Brakes, But Only With Hyundai’s $6K Tool Or A $2K Locked Workaround |url=https://www.carscoops.com/2025/11/hyundai-ioniq5n-brake-software-right-to-repair/ |access-date=2025-11-17 |website=Carscoops}}</ref> One Carscoops writer stated they were reconsidering purchasing an Ioniq 5 or Kia EV6 until this issue is resolved.<ref name="carscoops" />

==References==
{{reflist}}

[[Category:Hyundai]]
[[Category:Right to Repair]]
[[Category:Automotive Incidents]]
[[Category:2025 Incidents]]

IRobot

2025-11-17T21:08:20Z

Louis: wrong date for access

{{CompanyCargo
|Founded=1990
|Industry=Consumer robotics
|ParentCompany=None (publicly traded as IRBT)
|Type=Public
|Website=https://www.irobot.com/
|Description=iRobot Corporation manufactures consumer robots including the Roomba vacuum cleaner and Braava floor mopper.
}}

'''iRobot Corporation''' is an American consumer robotics company that designs & builds robots for the home, including the Roomba robotic vacuum cleaner. The company is facing potential bankruptcy as of November 2025, with only $24.8 million in cash remaining & no identified sources for additional capital.<ref>{{cite web |date=2025-11-06 |title=iRobot Reports Third-Quarter 2025 Financial Results |url=https://www.prnewswire.com/news-releases/irobot-reports-third-quarter-2025-financial-results-302607780.html |access-date= |website=PR Newswire}}</ref> An estimated 10-15 million cloud-dependent iRobot devices remain in active use globally, raising concerns about consumer access to features they purchased if the company's cloud services shut down.<ref>{{cite web |date=2025-11-11 |title=Tech company's potential bankruptcy to affect 50 million devices |url=https://www.thestreet.com/retail/tech-companys-likely-bankruptcy-to-affect-common-home-item |access-date= |website=TheStreet}}</ref>

==Background==
iRobot was founded in 1990 as a spin-off from the Massachusetts Institute of Technology by roboticists Colin Angle, Helen Greiner, & Rodney Brooks. The company initially focused on military & industrial applications before launching the Roomba vacuum cleaner in 2002. By 2016, iRobot held 64% of the global robotic vacuum market, though that declined to 46% by 2022 due to competition from Chinese manufacturers.<ref>{{cite web |date=2022-05-15 |title=Roborock vs iRobot vs Ecovacs - The Robot Vacuum Wars |url=https://www.nanalyze.com/2022/05/roborock-vs-irobot-vs-ecovacs/ |access-date= |website=Nanalyze}}</ref>

The company went public in 2005 & has sold over 50 million robots.<ref>{{cite web |date=2025-03-12 |title=Form 10-K IROBOT CORP |url=https://investor.irobot.com/static-files/21c7681f-4daa-4bd2-aa06-623d06adf00f |access-date= |website=SEC.gov}}</ref> WiFi connectivity became standard in the 600 series & above starting in the mid-2010s, making the majority of Roombas sold in the past decade dependent on cloud services for premium features.

==Financial crisis & going concern warning==
===Q3 2025 financial results===
On November 6, 2025, iRobot reported third-quarter 2025 results showing revenue of $145.8 million, down 24.6% year-over-year, with operating losses of $17.7 million.<ref>{{cite web |date=2025-11-06 |title=iRobot Reports Third-Quarter 2025 Financial Results |url=https://investor.irobot.com/news-releases/news-release-details/irobot-reports-third-quarter-2025-financial-results |access-date= |website=iRobot Corporation}}</ref> Cash reserves plummeted from $134.3 million at year-end 2024 to just $24.8 million by September 2025.<ref>{{cite web |date=2025-11-06 |title=iRobot Corp Q3 2025 Earnings: EPS of -$0.62 Beats Estimate |url=https://www.gurufocus.com/news/3193310/irobot-corp-q3-2025-earnings-eps-of-062-beats-estimate-revenue-surpasses-forecast-at-1458-million |access-date= |website=GuruFocus}}</ref>

===Going concern warning===
The company's March 2025 Form 10-K included an auditor-issued going concern warning stating:<blockquote>''“Given these uncertainties and the implication they may have on the company’s financials, there is substantial doubt about the company’s ability to continue as a going concern for a period of at least 12 months,”<ref>{{cite web |date=2025-03-12 |title=Shares of iRobot tank 30% after Roomba maker raises doubt about its survival |url=https://www.cnbc.com/2025/03/12/shares-of-irobot-tank-30percent-after-roomba-maker-issues-going-concern.html |access-date= |website=CNBC}}</ref>'' </blockquote>CEO Gary Cohen acknowledged in November 2025:<blockquote>''"at this time, the Company has no sources upon which it can draw for additional capital."<ref>{{cite web |date=2025-11-10 |title=iRobot’s revenue has tanked and it’s almost out of cash {{!}} The Verge |url=https://www.theverge.com/news/817536/irobots-revenue-has-tanked-and-its-almost-out-of-cash |access-date= |website=AppleInsider}}</ref>''</blockquote>

===Failed strategic alternatives===
The company's strategic alternatives review, initiated in March 2025 to explore potential sales or refinancing, collapsed in October 2025 when the last remaining acquisition buyer withdrew after "last week the last remaining counterparty to a potential sale transaction withdrew from the process following a lengthy period of exclusive negotiations"<ref>{{cite web |date=2025-10-27 |title=Inline Viewer: iROBOT CORPORATION 8-K 2025-10-22 |url=https://www.sec.gov/ix?doc=/Archives/edgar/data/1159167/000115916725000080/irbt-20251022.htm |access-date= |website=CNBC}}</ref> Full-year 2024 financial results showed total revenue of $681.8 million, down 23.4% from 2023, with a net loss of $145.5 million.<ref>{{cite web |url=https://investor.irobot.com/news-releases/news-release-details/irobot-reports-fourth-quarter-and-full-year-2024-financial |title=iRobot Reports Fourth-Quarter and Full-Year 2024 Financial Results |website=iRobot Corporation |date=2025-03-12 |access-date=2025-11-17}}</ref> The company has accumulated approximately $550 million in losses since Q4 2021.<ref>{{cite web |url=https://www.valuethemarkets.com/analysis/irobot-irbt-stock-navigating-financial-challenges-and-future-opportunities |title=iRobot (IRBT) Stock: Navigating Financial Challenges and Future Opportunities |website=Value The Markets |date=2025-11-12 |access-date=2025-11-17}}</ref>

==Amazon acquisition attempt & regulatory opposition==
===Initial announcement & terms===
On August 5, 2022, Amazon announced plans to acquire iRobot for $1.7 billion in cash ($61 per share).<ref>{{cite web |date=2022-08-05 |title=Amazon and iRobot Sign an Agreement for Amazon to Acquire iRobot |url=https://press.aboutamazon.com/2022/8/amazon-and-irobot-sign-an-agreement-for-amazon-to-acquire-irobot |access-date= |website=Amazon Press Center}}</ref> The deal immediately triggered regulatory scrutiny from multiple jurisdictions concerned about competition, market foreclosure, & consumer privacy.

===FTC investigation===
The Federal Trade Commission issued a "second request" for additional information on September 19, 2022, launching a deep antitrust investigation.<ref>{{cite web |date=2022-09-20 |title=FTC probes Amazon's $1.7 billion acquisition of Roomba maker iRobot |url=https://www.cnn.com/2022/09/20/tech/roomba-amazon-ftc-investigation/index.html |access-date= |website=CNN Business}}</ref> The FTC's probe focused on whether Amazon could favor iRobot products over competitors on its marketplace platform, create barriers to entry & innovation, & exploit consumer privacy through access to home mapping data.<ref>{{cite web |url=https://www.ftc.gov/news-events/news/press-releases/2024/01/statement-regarding-termination-amazons-proposed-acquisition-irobot |title=Statement Regarding the Termination of Amazon's Proposed Acquisition of iRobot |website=Federal Trade Commission |date=2024-01-31 |access-date=2025-11-17}}</ref>

On September 9, 2022, a coalition of 25 public interest organizations including the Electronic Frontier Foundation, Public Citizen, & Fight for the Future sent a letter to the FTC urging the deal's blockage, warning that ''"there is no more private space than the home"'' & that the acquisition would give Amazon ''"access to extremely intimate facts about our most private spaces."''<ref>{{cite web |url=https://www.fightforthefuture.org/news/2022-09-09-letter-to-the-ftc-challenge-amazon-irobot-deal |title=Letter Calling on the FTC to Challenge Amazon-iRobot deal |website=Fight for the Future |date=2022-09-09 |access-date=2025-11-17}}</ref>

===European Commission investigation===
The European Commission opened a Phase II in-depth investigation on July 6, 2023, examining whether Amazon could restrict competition in the robot vacuum cleaner market.<ref>{{cite web |url=https://ec.europa.eu/commission/presscorner/detail/en/ip_23_5990 |title=Commission sends Amazon Statement of Objections over proposed acquisition of iRobot |website=European Commission |date=2023-11-27 |access-date=2025-11-17}}</ref> On November 27, 2023, the Commission issued a formal Statement of Objections concluding Amazon could engage in foreclosure strategies including delisting rival products which lowers the viability of competitors & raising costs of rival businesses which ''"could restrict competition in market for robot vacuum cleaners, leading to higher prices, lower quality, & less innovation for consumers."''<ref>{{cite web |url=https://techcrunch.com/2023/11/27/eu-amazon-irobot-statement-of-objections/ |title=Amazon's iRobot purchase sucks up formal competition concerns in EU |website=TechCrunch |date=2023-11-27 |access-date=2025-11-17}}</ref>

===UK regulatory clearance===
The UK Competition & Markets Authority cleared the deal unconditionally on June 16, 2023, finding that iRobot's market position was "modest" with significant rivals, & that Amazon lacked economic incentive to disadvantage competitors.<ref>{{cite web |url=https://www.gov.uk/government/news/amazon-s-purchase-of-roomba-maker-cleared-by-cma |title=Amazon's purchase of Roomba maker cleared by CMA |website=GOV.UK |date=2023-06-16 |access-date=2025-11-17}}</ref>

===Deal termination===
On January 29, 2024, Amazon & iRobot mutually terminated the acquisition agreement, citing ''"no path to regulatory approval in the European Union."''<ref>{{cite web |url=https://www.cnbc.com/2024/01/29/amazon-terminates-irobot-deal-vacuum-maker-to-lay-off-31percent-of-staff.html |title=Amazon terminates iRobot deal, Roomba maker to lay off 31% of staff |website=CNBC |date=2024-01-29 |access-date=2025-11-17}}</ref>

The deal's collapse had devastating consequences: iRobot immediately laid off 350 employees (31% of staff), founder Colin Angle resigned as CEO after 33 years.<ref>{{cite web |url=https://fortune.com/europe/2024/01/29/amazon-irobot-deal-falls-through-31-percent-layoffs-founder-colin-angle/ |title=iRobot cofounder Colin Angle departs after Amazon backs out of $1.7 billion deal |website=Fortune |date=2024-01-29 |access-date=2025-11-17}}</ref>

==Privacy practices & data collection==
===2017 data monetization controversy===
In July 2017, CEO Colin Angle made statements to Reuters suggesting the company could share or sell customer home mapping data to major technology companies within two years.<ref name=":0">{{cite web |url=https://www.technologyreview.com/2017/07/25/150346/your-roomba-is-also-gathering-data-about-the-layout-of-your-home/ |title=Your Roomba Is Also Gathering Data about the Layout of Your Home |website=MIT Technology Review |date=2017-07-25 |access-date=2025-11-17}}</ref> Reuters reported Angle said iRobot ''"could reach a deal to sell its maps to one or more of the Big Three [Amazon, Apple, Google] in the next couple of years"'' & that while the company would not sell data without permission.<blockquote>Angle told Reuters that iRobot would not give out the mapping data it collects without customers’ permission, which is good. That indicates that if and when this starts happening, there will be a notice to users, and that they’ll have a clear chance to refuse consent (though Angle expressed confidence that people would agree).<ref name=":0" /></blockquote>Following quick consumer backlash, iRobot issued formal clarifications claiming Reuters ''"misinterpreted"'' the comments. The company's July 28-29, 2017 statement declared: <blockquote>''"First things first, iRobot will never sell your data. Colin never said that iRobot would look to sell customer maps or data to other companies."<ref>{{cite web |date=2017-07-29 |title=Amazon acquires Roomba: iRobot CEO says they will never sell your data {{!}} ZDNET |url=https://www.zdnet.com/article/exclusive-roomba-ceo-responds-to-spying-story/ |access-date= |website=zdnet}}</ref>'' </blockquote>In a September 2017 follow-up interview with IEEE Spectrum, Angle clarified: "We don't even remember your map unless you tell us we can."<ref>{{cite web |url=https://spectrum.ieee.org/interview-irobot-ceo-colin-angle-on-privacy-and-robots-in-the-home |title=iRobot CEO Colin Angle on Data Privacy and Robots in the Home |website=IEEE Spectrum |date=2017-09-07 |access-date=2025-11-17}}</ref>

===Current data collection practices===
According to iRobot's privacy documentation, WiFi-enabled Roomba devices collect extensive data including:<ref>{{cite web |url=https://www.irobot.com/en_US/legal/privacy-policy.html |title=Privacy Policy |website=iRobot |date=2024-06-01 |access-date=2025-11-17}}</ref>
*Mapping data: room dimensions, furniture locations, virtual landmarks, navigation points
*Usage data: cleaning duration & frequency, distance traveled, error codes, dirt detection events & locations
*User account information: names, email addresses, shipping & billing addresses, device identifiers
*Voice command data when voice assistant integration is enabled

===2022 photo leak scandal===
In December 2022, MIT Technology Review published an investigation revealing that development Roomba J7 series units captured private photos that were subsequently leaked by data annotation workers.<ref>{{cite web |url=https://www.technologyreview.com/2022/12/19/1065306/roomba-irobot-robot-vacuums-artificial-intelligence-training-data-privacy/ |title=A Roomba recorded a woman on the toilet. How did screenshots end up on Facebook? |website=MIT Technology Review |date=2022-12-19 |access-date=2025-11-17}}</ref> The outlet obtained 15 screenshots from development robots including images of a woman sitting on a toilet & a young boy lying on a hallway floor.

iRobot responded that the images came from ''"special development robots with hardware & software modifications"'' not present in consumer products, & that users signed consent agreements. The company acknowledged having shared "over 2 million" images with Scale AI alone for data annotation. A critical revelation was that iRobot does not consider faces "sensitive information" requiring special protection, despite computer vision experts stating that silhouettes would be sufficient for obstacle avoidance without capturing faces.<ref>{{cite web |url=https://www.thestreet.com/retail/everyones-worst-fears-about-the-roomba-have-come-true |title=iRobot Roomba Photos Raise Privacy Concerns |website=TheStreet |date=2022-12-20 |access-date=2025-11-17}}</ref>

==cloud service dependency & how this affects customers==
===Features requiring cloud access{CITATION NEEDED, LOCKED BEHIND SUPPORT SITE ACCOUNT}===
Features that become unavailable without cloud access include:
*Remote connection & control via the iRobot HOME app
*Cleaning history & Clean Map Reports
*Imprint Smart Mapping for i Series robots
*Software & firmware updates
*Scheduling automated cleaning sessions
*Voice control integration with Alexa & Google Assistant
*Multi-room control allowing direction to specific rooms by name
*Custom cleaning preferences including power boost & cleaning passes

=== Workarounds ===
There is an ongoing thread regarding solutions for local control of the recent 505 series of robots, see https://github.com/home-assistant/core/issues/146155#issuecomment-3531411934.

==See also==
*[[Right to repair]]
*[[Internet of Things]]
*[[Cloud computing]]
*[[Smart home]]

==References==
{{reflist}}

[[Category:iRobot]]
[[Category:Consumer electronics companies]]
[[Category:Privacy controversies]]
[[Category:Cloud computing issues]]
[[Category:Corporate bankruptcies]]
[[Category:2025 bankruptcies]]

IRobot

2025-11-17T21:04:56Z

Louis: revised

{{CompanyCargo
|Founded=1990
|Industry=Consumer robotics
|ParentCompany=None (publicly traded as IRBT)
|Type=Public
|Website=https://www.irobot.com/
|Description=iRobot Corporation manufactures consumer robots including the Roomba vacuum cleaner and Braava floor mopper.
}}

'''iRobot Corporation''' is an American consumer robotics company that designs & builds robots for the home, including the Roomba robotic vacuum cleaner. The company is facing potential bankruptcy as of November 2025, with only $24.8 million in cash remaining & no identified sources for additional capital.<ref>{{cite web |date=2025-11-06 |title=iRobot Reports Third-Quarter 2025 Financial Results |url=https://www.prnewswire.com/news-releases/irobot-reports-third-quarter-2025-financial-results-302607780.html |access-date= |website=PR Newswire}}</ref> An estimated 10-15 million cloud-dependent iRobot devices remain in active use globally, raising concerns about consumer access to features they purchased if the company's cloud services shut down.<ref>{{cite web |date=2025-11-11 |title=Tech company's potential bankruptcy to affect 50 million devices |url=https://www.thestreet.com/retail/tech-companys-likely-bankruptcy-to-affect-common-home-item |access-date= |website=TheStreet}}</ref>

==Background==
iRobot was founded in 1990 as a spin-off from the Massachusetts Institute of Technology by roboticists Colin Angle, Helen Greiner, & Rodney Brooks. The company initially focused on military & industrial applications before launching the Roomba vacuum cleaner in 2002. By 2016, iRobot held 64% of the global robotic vacuum market, though that declined to 46% by 2022 due to competition from Chinese manufacturers.<ref>{{cite web |date=2022-05-15 |title=Roborock vs iRobot vs Ecovacs - The Robot Vacuum Wars |url=https://www.nanalyze.com/2022/05/roborock-vs-irobot-vs-ecovacs/ |access-date= |website=Nanalyze}}</ref>

The company went public in 2005 & has sold over 50 million robots.<ref>{{cite web |date=2025-03-12 |title=Form 10-K IROBOT CORP |url=https://investor.irobot.com/static-files/21c7681f-4daa-4bd2-aa06-623d06adf00f |access-date= |website=SEC.gov}}</ref> WiFi connectivity became standard in the 600 series & above starting in the mid-2010s, making the majority of Roombas sold in the past decade dependent on cloud services for premium features.

==Financial crisis & going concern warning==
===Q3 2025 financial results===
On November 6, 2025, iRobot reported third-quarter 2025 results showing revenue of $145.8 million, down 24.6% year-over-year, with operating losses of $17.7 million.<ref>{{cite web |date=2025-11-06 |title=iRobot Reports Third-Quarter 2025 Financial Results |url=https://investor.irobot.com/news-releases/news-release-details/irobot-reports-third-quarter-2025-financial-results |access-date= |website=iRobot Corporation}}</ref> Cash reserves plummeted from $134.3 million at year-end 2024 to just $24.8 million by September 2025.<ref>{{cite web |date=2025-11-06 |title=iRobot Corp Q3 2025 Earnings: EPS of -$0.62 Beats Estimate |url=https://www.gurufocus.com/news/3193310/irobot-corp-q3-2025-earnings-eps-of-062-beats-estimate-revenue-surpasses-forecast-at-1458-million |access-date= |website=GuruFocus}}</ref>

===Going concern warning===
The company's March 2025 Form 10-K included an auditor-issued going concern warning stating:<blockquote>''“Given these uncertainties and the implication they may have on the company’s financials, there is substantial doubt about the company’s ability to continue as a going concern for a period of at least 12 months,”<ref>{{cite web |date=2025-03-12 |title=Shares of iRobot tank 30% after Roomba maker raises doubt about its survival |url=https://www.cnbc.com/2025/03/12/shares-of-irobot-tank-30percent-after-roomba-maker-issues-going-concern.html |access-date= |website=CNBC}}</ref>'' </blockquote>CEO Gary Cohen acknowledged in November 2025:<blockquote>''"at this time, the Company has no sources upon which it can draw for additional capital."<ref>{{cite web |date=2025-11-10 |title=iRobot’s revenue has tanked and it’s almost out of cash {{!}} The Verge |url=https://www.theverge.com/news/817536/irobots-revenue-has-tanked-and-its-almost-out-of-cash |access-date= |website=AppleInsider}}</ref>''</blockquote>

===Failed strategic alternatives===
The company's strategic alternatives review, initiated in March 2025 to explore potential sales or refinancing, collapsed in October 2025 when the last remaining acquisition buyer withdrew after "last week the last remaining counterparty to a potential sale transaction withdrew from the process following a lengthy period of exclusive negotiations"<ref>{{cite web |date=2025-10-27 |title=Inline Viewer: iROBOT CORPORATION 8-K 2025-10-22 |url=https://www.sec.gov/ix?doc=/Archives/edgar/data/1159167/000115916725000080/irbt-20251022.htm |access-date= |website=CNBC}}</ref> Full-year 2024 financial results showed total revenue of $681.8 million, down 23.4% from 2023, with a net loss of $145.5 million.<ref>{{cite web |url=https://investor.irobot.com/news-releases/news-release-details/irobot-reports-fourth-quarter-and-full-year-2024-financial |title=iRobot Reports Fourth-Quarter and Full-Year 2024 Financial Results |website=iRobot Corporation |date=2025-03-12 |access-date=2024-11-17}}</ref> The company has accumulated approximately $550 million in losses since Q4 2021.<ref>{{cite web |url=https://www.valuethemarkets.com/analysis/irobot-irbt-stock-navigating-financial-challenges-and-future-opportunities |title=iRobot (IRBT) Stock: Navigating Financial Challenges and Future Opportunities |website=Value The Markets |date=2025-11-12 |access-date=2024-11-17}}</ref>

==Amazon acquisition attempt & regulatory opposition==
===Initial announcement & terms===
On August 5, 2022, Amazon announced plans to acquire iRobot for $1.7 billion in cash ($61 per share).<ref>{{cite web |date=2022-08-05 |title=Amazon and iRobot Sign an Agreement for Amazon to Acquire iRobot |url=https://press.aboutamazon.com/2022/8/amazon-and-irobot-sign-an-agreement-for-amazon-to-acquire-irobot |access-date= |website=Amazon Press Center}}</ref> The deal immediately triggered regulatory scrutiny from multiple jurisdictions concerned about competition, market foreclosure, & consumer privacy.

===FTC investigation===
The Federal Trade Commission issued a "second request" for additional information on September 19, 2022, launching a deep antitrust investigation.<ref>{{cite web |date=2022-09-20 |title=FTC probes Amazon's $1.7 billion acquisition of Roomba maker iRobot |url=https://www.cnn.com/2022/09/20/tech/roomba-amazon-ftc-investigation/index.html |access-date= |website=CNN Business}}</ref> The FTC's probe focused on whether Amazon could favor iRobot products over competitors on its marketplace platform, create barriers to entry & innovation, & exploit consumer privacy through access to home mapping data.<ref>{{cite web |url=https://www.ftc.gov/news-events/news/press-releases/2024/01/statement-regarding-termination-amazons-proposed-acquisition-irobot |title=Statement Regarding the Termination of Amazon's Proposed Acquisition of iRobot |website=Federal Trade Commission |date=2024-01-31 |access-date=2024-11-17}}</ref>

On September 9, 2022, a coalition of 25 public interest organizations including the Electronic Frontier Foundation, Public Citizen, & Fight for the Future sent a letter to the FTC urging the deal's blockage, warning that ''"there is no more private space than the home"'' & that the acquisition would give Amazon ''"access to extremely intimate facts about our most private spaces."''<ref>{{cite web |url=https://www.fightforthefuture.org/news/2022-09-09-letter-to-the-ftc-challenge-amazon-irobot-deal |title=Letter Calling on the FTC to Challenge Amazon-iRobot deal |website=Fight for the Future |date=2022-09-09 |access-date=2024-11-17}}</ref>

===European Commission investigation===
The European Commission opened a Phase II in-depth investigation on July 6, 2023, examining whether Amazon could restrict competition in the robot vacuum cleaner market.<ref>{{cite web |url=https://ec.europa.eu/commission/presscorner/detail/en/ip_23_5990 |title=Commission sends Amazon Statement of Objections over proposed acquisition of iRobot |website=European Commission |date=2023-11-27 |access-date=2024-11-17}}</ref> On November 27, 2023, the Commission issued a formal Statement of Objections concluding Amazon could engage in foreclosure strategies including delisting rival products which lowers the viability of competitors & raising costs of rival businesses which ''"could restrict competition in market for robot vacuum cleaners, leading to higher prices, lower quality, & less innovation for consumers."''<ref>{{cite web |url=https://techcrunch.com/2023/11/27/eu-amazon-irobot-statement-of-objections/ |title=Amazon's iRobot purchase sucks up formal competition concerns in EU |website=TechCrunch |date=2023-11-27 |access-date=2024-11-17}}</ref>

===UK regulatory clearance===
The UK Competition & Markets Authority cleared the deal unconditionally on June 16, 2023, finding that iRobot's market position was "modest" with significant rivals, & that Amazon lacked economic incentive to disadvantage competitors.<ref>{{cite web |url=https://www.gov.uk/government/news/amazon-s-purchase-of-roomba-maker-cleared-by-cma |title=Amazon's purchase of Roomba maker cleared by CMA |website=GOV.UK |date=2023-06-16 |access-date=2024-11-17}}</ref>

===Deal termination===
On January 29, 2024, Amazon & iRobot mutually terminated the acquisition agreement, citing ''"no path to regulatory approval in the European Union."''<ref>{{cite web |url=https://www.cnbc.com/2024/01/29/amazon-terminates-irobot-deal-vacuum-maker-to-lay-off-31percent-of-staff.html |title=Amazon terminates iRobot deal, Roomba maker to lay off 31% of staff |website=CNBC |date=2024-01-29 |access-date=2024-11-17}}</ref>

The deal's collapse had devastating consequences: iRobot immediately laid off 350 employees (31% of staff), founder Colin Angle resigned as CEO after 33 years.<ref>{{cite web |url=https://fortune.com/europe/2024/01/29/amazon-irobot-deal-falls-through-31-percent-layoffs-founder-colin-angle/ |title=iRobot cofounder Colin Angle departs after Amazon backs out of $1.7 billion deal |website=Fortune |date=2024-01-29 |access-date=2024-11-17}}</ref>

==Privacy practices & data collection==
===2017 data monetization controversy===
In July 2017, CEO Colin Angle made statements to Reuters suggesting the company could share or sell customer home mapping data to major technology companies within two years.<ref name=":0">{{cite web |url=https://www.technologyreview.com/2017/07/25/150346/your-roomba-is-also-gathering-data-about-the-layout-of-your-home/ |title=Your Roomba Is Also Gathering Data about the Layout of Your Home |website=MIT Technology Review |date=2017-07-25 |access-date=2024-11-17}}</ref> Reuters reported Angle said iRobot ''"could reach a deal to sell its maps to one or more of the Big Three [Amazon, Apple, Google] in the next couple of years"'' & that while the company would not sell data without permission.<blockquote>Angle told Reuters that iRobot would not give out the mapping data it collects without customers’ permission, which is good. That indicates that if and when this starts happening, there will be a notice to users, and that they’ll have a clear chance to refuse consent (though Angle expressed confidence that people would agree).<ref name=":0" /></blockquote>Following quick consumer backlash, iRobot issued formal clarifications claiming Reuters ''"misinterpreted"'' the comments. The company's July 28-29, 2017 statement declared: <blockquote>''"First things first, iRobot will never sell your data. Colin never said that iRobot would look to sell customer maps or data to other companies."<ref>{{cite web |date=2017-07-29 |title=Amazon acquires Roomba: iRobot CEO says they will never sell your data {{!}} ZDNET |url=https://www.zdnet.com/article/exclusive-roomba-ceo-responds-to-spying-story/ |access-date= |website=zdnet}}</ref>'' </blockquote>In a September 2017 follow-up interview with IEEE Spectrum, Angle clarified: "We don't even remember your map unless you tell us we can."<ref>{{cite web |url=https://spectrum.ieee.org/interview-irobot-ceo-colin-angle-on-privacy-and-robots-in-the-home |title=iRobot CEO Colin Angle on Data Privacy and Robots in the Home |website=IEEE Spectrum |date=2017-09-07 |access-date=2024-11-17}}</ref>

===Current data collection practices===
According to iRobot's privacy documentation, WiFi-enabled Roomba devices collect extensive data including:<ref>{{cite web |url=https://www.irobot.com/en_US/legal/privacy-policy.html |title=Privacy Policy |website=iRobot |date=2024-06-01 |access-date=2024-11-17}}</ref>
*Mapping data: room dimensions, furniture locations, virtual landmarks, navigation points
*Usage data: cleaning duration & frequency, distance traveled, error codes, dirt detection events & locations
*User account information: names, email addresses, shipping & billing addresses, device identifiers
*Voice command data when voice assistant integration is enabled

===2022 photo leak scandal===
In December 2022, MIT Technology Review published an investigation revealing that development Roomba J7 series units captured private photos that were subsequently leaked by data annotation workers.<ref>{{cite web |url=https://www.technologyreview.com/2022/12/19/1065306/roomba-irobot-robot-vacuums-artificial-intelligence-training-data-privacy/ |title=A Roomba recorded a woman on the toilet. How did screenshots end up on Facebook? |website=MIT Technology Review |date=2022-12-19 |access-date=2024-11-17}}</ref> The outlet obtained 15 screenshots from development robots including images of a woman sitting on a toilet & a young boy lying on a hallway floor.

iRobot responded that the images came from ''"special development robots with hardware & software modifications"'' not present in consumer products, & that users signed consent agreements. The company acknowledged having shared "over 2 million" images with Scale AI alone for data annotation. A critical revelation was that iRobot does not consider faces "sensitive information" requiring special protection, despite computer vision experts stating that silhouettes would be sufficient for obstacle avoidance without capturing faces.<ref>{{cite web |url=https://www.thestreet.com/retail/everyones-worst-fears-about-the-roomba-have-come-true |title=iRobot Roomba Photos Raise Privacy Concerns |website=TheStreet |date=2022-12-20 |access-date=2024-11-17}}</ref>

==cloud service dependency & how this affects customers==
===Features requiring cloud access{CITATION NEEDED, LOCKED BEHIND SUPPORT SITE ACCOUNT}===
Features that become unavailable without cloud access include:
*Remote connection & control via the iRobot HOME app
*Cleaning history & Clean Map Reports
*Imprint Smart Mapping for i Series robots
*Software & firmware updates
*Scheduling automated cleaning sessions
*Voice control integration with Alexa & Google Assistant
*Multi-room control allowing direction to specific rooms by name
*Custom cleaning preferences including power boost & cleaning passes

=== Workarounds ===
There is an ongoing thread regarding solutions for local control of the recent 505 series of robots, see https://github.com/home-assistant/core/issues/146155#issuecomment-3531411934.

==See also==
*[[Right to repair]]
*[[Internet of Things]]
*[[Cloud computing]]
*[[Smart home]]

==References==
{{reflist}}

[[Category:iRobot]]
[[Category:Consumer electronics companies]]
[[Category:Privacy controversies]]
[[Category:Cloud computing issues]]
[[Category:Corporate bankruptcies]]
[[Category:2025 bankruptcies]]

Hauptwerk expiration of perpetual license download

2025-11-02T18:51:13Z

Louis:

{{StubNotice}}

{{IncidentCargo
|ProductLine=Hauptwerk
|Product=Hauptwerk
|ArticleType=Product
|Description=Perpetual license software not offered for download in spite of link saying "NEVER" expires
}}[[Milan Digital Audio]], developers of the [[Hauptwerk]] virtual pipe organ software, refused to provide installation files for older versions of their software to customers who purchased perpetual licenses, redefining the scope of perpetual licenses to exclude download rights after product discontinuation.

==Background==

Milan Digital Audio LLC is a United States-based software company that develops & markets Hauptwerk, a virtual pipe organ software application that allows users to play sampled pipe organs through MIDI keyboards. The software has been through many versions since its original development in 2002, with the company transitioning from a USB dongle-based licensing system to the iLok platform by Pace Anti Piracy starting with version 5.<ref>{{cite web |url=https://inspiredacoustics.com/en/inspirations/blog/all-about-upgrading-hauptwerk-v/view |title=All about Upgrading to Hauptwerk V |website=Inspired Acoustics |access-date=2025-11-02}}</ref>
[[File:Screenshot of "never" under "expires" link for Hauptwerk version 7.png|alt=The download link for hauptwerk version 7 says "never" under the word "expires", implying it still works, even though it was taken down without notice to customers of perpetual licenses for this software. |thumb|The download link for hauptwerk version 7 says "never" under the word "expires", implying it still works, even though it was taken down without notice to customers of perpetual licenses for this software. ]]
The company offers both subscription & perpetual licenses for its software. According to the company's current pricing structure, perpetual licenses are marketed as one-time purchases that allow indefinite use of the software.<ref>{{cite web |url=https://www.hauptwerk.com/pricing/ |title=Pricing |website=Hauptwerk |date=2023-08-14 |access-date=2025-11-02}}</ref> Prior versions of the software, including Hauptwerk 7, were sold with download buttons in user accounts that displayed "never" under the "expires" field, suggesting permanent download availability.<ref name=":0">Email correspondence from Josef to youtube@rossmanngroup.com, November 2, 2025 , to provide screenshots to remove the stub notice soon</ref>

==The Incident==

In November 2025, a music conservatory instructor who teaches organists & film composers attempted to download Hauptwerk version 7 after switching from macOS to Windows. Despite having purchased a perpetual license & having access to a download button in his user account, the download failed to complete.<ref name=":0" />

When he contacted Milan Digital Audio support, he received a response from François Ratté, Support Manager, stating that ''"Hauptwerk 7 is no longer supported or distributed"'' & directing him to purchase an upgrade to Hauptwerk 9. When he requested that the company fix the download link or provide the software he had licensed, Ratté responded that ''"the installation file is no longer available"'' & elaborated on the company's interpretation of perpetual licenses.<ref name=":0" />

==Company Position==

According to the support correspondence, Milan Digital Audio maintains that a perpetual license grants only the right to use software indefinitely, not the right to download it indefinitely. Ratté stated in his response: ''"A perpetual license means that you can use the software for as long as you wish & as long as it is compatible with your hardware, but it doesn't mean you will get infinite support (and downloading the installation file is part of that support)."''<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

The company further justified this position by claiming that ''"most software companies end the distribution of the previous version as soon as a new one is available"'' & that Milan Digital Audio provides support only for the current version (Hauptwerk 9) & the previous version (Hauptwerk 8).<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==Legal & Industry Context==

The definition & scope of perpetual software licenses has been a subject of ongoing debate in the software industry. Generally, perpetual licenses are understood to provide indefinite usage rights to a specific version of software after a one-time payment. Industry sources indicate that while perpetual licenses typically do not include rights to future updates or new versions, they are generally expected to include continued access to the purchased version.<ref>{{cite web |url=https://licensespring.com/blog/glossary/what-is-a-perpetual-license |title=Everything You Wanted to Know about Perpetual Licenses [Guide] |website=LicenseSpring |access-date=2025-11-02}}</ref>

The practice of discontinuing downloads for previously purchased software has become a contentious issue in consumer rights discussions. Some legal discussions have suggested that denying access to installation files for perpetually licensed software may constitute breach of contract, though not criminal theft.''"downloading the installation file is part of that support"''<ref>{{cite web |url=https://law.stackexchange.com/questions/78525/a-software-company-refuses-to-active-my-perpetual-ownership-software-because-the |title=A software company refuses to activate my perpetual ownership software because they no longer want to maintain the activation server |website=Law Stack Exchange |access-date=2025-11-02}}</ref>

==Consumer Impact==

The denial of download access particularly affects users who:
*Need to reinstall software after hardware failures or operating system changes
*Switch between different operating systems (as in his case of moving from macOS to Windows)
*Require the specific features or compatibility of older versions
*Have invested in perpetual licenses with the expectation of long-term access

==Industry Comparison==

One may contrast Milan Digital Audio's practices with those of Vienna Symphonic Library: customers can still download software from the Vienna Symphonic Library that's nearly ten years old. Vienna Symphonic Library continues to provide download access for legacy eLicenser-protected products even after transitioning to the newer iLok system, maintaining download managers & installation files for older versions.<ref>{{cite web |url=https://www.vsl.co.at/tutorials/guides/library-installation-elicenser-legacy |title=Library Installation (eLicenser) |website=Vienna Symphonic Library |access-date=2025-11-02}}</ref>

==What This Means For You==

This demonstrates several disturbing trends in modern software licensing:

*'''Redefinition of ownership terms''': Companies unilaterally reinterpreting the scope of "perpetual" licenses after purchase
*'''Forced obsolescence''': Using technical means to compel users to purchase upgrades
*'''Download dependency''': The vulnerability of users who depend on vendor-controlled download servers for software they have purchased
*'''Platform lock-in''': The inability of users to transfer licenses across operating systems despite having paid for perpetual use

The case has been cited as an example of the erosion of consumer ownership rights in the digital age, where the traditional concept of purchasing software is being replaced by increasingly restrictive licensing models.<ref>{{cite web |url=https://mostly.media/you-dont-own-anything-anymore-you-just-clicked-agree/ |title=You Don't Own Anything Anymore: A deep-dive on digital ownership to the right to repair |website=Mostly Media |date=2025-05-26 |access-date=2025-11-02}}</ref>

==Company Response to Criticism==

When confronted about the misleading nature of the "Download" button with "never expires" labeling in user accounts, & the comparison to competitors who maintain legacy downloads, Milan Digital Audio's support reiterated their position that keeping installation files is the customer's responsibility. The support representative added that ''"downloading the installation file is part of that support"'' which the company is not obligated to provide indefinitely, despite the perpetual license.<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==See Also==
*[[Right to repair]]
*[[Software licensing]]
*[[Planned obsolescence]]
*[[Digital rights management]]
*[[Consumer protection in software]]

==References==
{{reflist}}

[[Category:Software licensing]]
[[Category:Consumer rights]]
[[Category:Digital ownership]]
[[Category:2025 consumer incidents]]
[[Category:Right to repair]]

File:Screenshot of "never" under "expires" link for Hauptwerk version 7.png

2025-11-02T18:51:05Z

Louis:

The download link for hauptwerk version 7 says "never" under the word "expires", implying it still works, even though it was taken down without notice to customers of perpetual licenses for this software.

Hauptwerk expiration of perpetual license download

2025-11-02T16:35:51Z

Louis:

{{StubNotice}}

{{IncidentCargo
|ProductLine=Hauptwerk
|Product=Hauptwerk
|ArticleType=Product
|Description=Perpetual license software not offered for download in spite of link saying "NEVER" expires
}}[[Milan Digital Audio]], developers of the [[Hauptwerk]] virtual pipe organ software, refysed ti provide installation files for older versions of their software to customers who purchased perpetual licenses, redefining the scope of perpetual licenses to exclude download rights after product discontinuation.

==Background==

Milan Digital Audio LLC is a United States-based software company that develops & markets Hauptwerk, a virtual pipe organ software application that allows users to play sampled pipe organs through MIDI keyboards. The software has been through many versions since its original development in 2002, with the company transitioning from a USB dongle-based licensing system to the iLok platform by Pace Anti Piracy starting with version 5.<ref>{{cite web |url=https://inspiredacoustics.com/en/inspirations/blog/all-about-upgrading-hauptwerk-v/view |title=All about Upgrading to Hauptwerk V |website=Inspired Acoustics |access-date=2025-11-02}}</ref>

The company offers both subscription & perpetual licenses for its software. According to the company's current pricing structure, perpetual licenses are marketed as one-time purchases that allow indefinite use of the software.<ref>{{cite web |url=https://www.hauptwerk.com/pricing/ |title=Pricing |website=Hauptwerk |date=2023-08-14 |access-date=2025-11-02}}</ref> Prior versions of the software, including Hauptwerk 7, were sold with download buttons in user accounts that displayed "never" under the "expires" field, suggesting permanent download availability.<ref name=":0">Email correspondence from Josef to youtube@rossmanngroup.com, November 2, 2025 , to provide screenshots to remove the stub notice soon</ref>

==The Incident==

In November 2025, a music conservatory instructor who teaches organists & film composers attempted to download Hauptwerk version 7 after switching from macOS to Windows. Despite having purchased a perpetual license & having access to a download button in his user account, the download failed to complete.<ref name=":0" />

When he contacted Milan Digital Audio support, he received a response from François Ratté, Support Manager, stating that ''"Hauptwerk 7 is no longer supported or distributed"'' & directing him to purchase an upgrade to Hauptwerk 9. When he requested that the company fix the download link or provide the software he had licensed, Ratté responded that ''"the installation file is no longer available"'' & elaborated on the company's interpretation of perpetual licenses.<ref name=":0" />

==Company Position==

According to the support correspondence, Milan Digital Audio maintains that a perpetual license grants only the right to use software indefinitely, not the right to download it indefinitely. Ratté stated in his response: ''"A perpetual license means that you can use the software for as long as you wish & as long as it is compatible with your hardware, but it doesn't mean you will get infinite support (and downloading the installation file is part of that support)."''<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

The company further justified this position by claiming that ''"most software companies end the distribution of the previous version as soon as a new one is available"'' & that Milan Digital Audio provides support only for the current version (Hauptwerk 9) & the previous version (Hauptwerk 8).<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==Legal & Industry Context==

The definition & scope of perpetual software licenses has been a subject of ongoing debate in the software industry. Generally, perpetual licenses are understood to provide indefinite usage rights to a specific version of software after a one-time payment. Industry sources indicate that while perpetual licenses typically do not include rights to future updates or new versions, they are generally expected to include continued access to the purchased version.<ref>{{cite web |url=https://licensespring.com/blog/glossary/what-is-a-perpetual-license |title=Everything You Wanted to Know about Perpetual Licenses [Guide] |website=LicenseSpring |access-date=2025-11-02}}</ref>

The practice of discontinuing downloads for previously purchased software has become a contentious issue in consumer rights discussions. Some legal discussions have suggested that denying access to installation files for perpetually licensed software may constitute breach of contract, though not criminal theft.''"downloading the installation file is part of that support"''<ref>{{cite web |url=https://law.stackexchange.com/questions/78525/a-software-company-refuses-to-active-my-perpetual-ownership-software-because-the |title=A software company refuses to activate my perpetual ownership software because they no longer want to maintain the activation server |website=Law Stack Exchange |access-date=2025-11-02}}</ref>

==Consumer Impact==

The denial of download access particularly affects users who:
*Need to reinstall software after hardware failures or operating system changes
*Switch between different operating systems (as in his case of moving from macOS to Windows)
*Require the specific features or compatibility of older versions
*Have invested in perpetual licenses with the expectation of long-term access

==Industry Comparison==

One may contrast Milan Digital Audio's practices with those of Vienna Symphonic Library: customers can still download software from the Vienna Symphonic Library that's nearly ten years old. Vienna Symphonic Library continues to provide download access for legacy eLicenser-protected products even after transitioning to the newer iLok system, maintaining download managers & installation files for older versions.<ref>{{cite web |url=https://www.vsl.co.at/tutorials/guides/library-installation-elicenser-legacy |title=Library Installation (eLicenser) |website=Vienna Symphonic Library |access-date=2025-11-02}}</ref>

==What This Means For You==

This demonstrates several disturbing trends in modern software licensing:

*'''Redefinition of ownership terms''': Companies unilaterally reinterpreting the scope of "perpetual" licenses after purchase
*'''Forced obsolescence''': Using technical means to compel users to purchase upgrades
*'''Download dependency''': The vulnerability of users who depend on vendor-controlled download servers for software they have purchased
*'''Platform lock-in''': The inability of users to transfer licenses across operating systems despite having paid for perpetual use

The case has been cited as an example of the erosion of consumer ownership rights in the digital age, where the traditional concept of purchasing software is being replaced by increasingly restrictive licensing models.<ref>{{cite web |url=https://mostly.media/you-dont-own-anything-anymore-you-just-clicked-agree/ |title=You Don't Own Anything Anymore: A deep-dive on digital ownership to the right to repair |website=Mostly Media |date=2025-05-26 |access-date=2025-11-02}}</ref>

==Company Response to Criticism==

When confronted about the misleading nature of the "Download" button with "never expires" labeling in user accounts, & the comparison to competitors who maintain legacy downloads, Milan Digital Audio's support reiterated their position that keeping installation files is the customer's responsibility. The support representative added that ''"downloading the installation file is part of that support"'' which the company is not obligated to provide indefinitely, despite the perpetual license.<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==See Also==
*[[Right to repair]]
*[[Software licensing]]
*[[Planned obsolescence]]
*[[Digital rights management]]
*[[Consumer protection in software]]

==References==
{{reflist}}

[[Category:Software licensing]]
[[Category:Consumer rights]]
[[Category:Digital ownership]]
[[Category:2025 consumer incidents]]
[[Category:Right to repair]]

Hauptwerk expiration of perpetual license download

2025-11-02T16:35:38Z

Louis:

{{IncidentCargo
|ProductLine=Hauptwerk
|Product=Hauptwerk
|ArticleType=Product
|Description=Perpetual license software not offered for download in spite of link saying "NEVER" expires
}}[[Milan Digital Audio]], developers of the [[Hauptwerk]] virtual pipe organ software, refysed ti provide installation files for older versions of their software to customers who purchased perpetual licenses, redefining the scope of perpetual licenses to exclude download rights after product discontinuation.

==Background==

Milan Digital Audio LLC is a United States-based software company that develops & markets Hauptwerk, a virtual pipe organ software application that allows users to play sampled pipe organs through MIDI keyboards. The software has been through many versions since its original development in 2002, with the company transitioning from a USB dongle-based licensing system to the iLok platform by Pace Anti Piracy starting with version 5.<ref>{{cite web |url=https://inspiredacoustics.com/en/inspirations/blog/all-about-upgrading-hauptwerk-v/view |title=All about Upgrading to Hauptwerk V |website=Inspired Acoustics |access-date=2025-11-02}}</ref>

The company offers both subscription & perpetual licenses for its software. According to the company's current pricing structure, perpetual licenses are marketed as one-time purchases that allow indefinite use of the software.<ref>{{cite web |url=https://www.hauptwerk.com/pricing/ |title=Pricing |website=Hauptwerk |date=2023-08-14 |access-date=2025-11-02}}</ref> Prior versions of the software, including Hauptwerk 7, were sold with download buttons in user accounts that displayed "never" under the "expires" field, suggesting permanent download availability.<ref name=":0">Email correspondence from Josef to youtube@rossmanngroup.com, November 2, 2025 , to provide screenshots to remove the stub notice soon</ref>

==The Incident==

In November 2025, a music conservatory instructor who teaches organists & film composers attempted to download Hauptwerk version 7 after switching from macOS to Windows. Despite having purchased a perpetual license & having access to a download button in his user account, the download failed to complete.<ref name=":0" />

When he contacted Milan Digital Audio support, he received a response from François Ratté, Support Manager, stating that ''"Hauptwerk 7 is no longer supported or distributed"'' & directing him to purchase an upgrade to Hauptwerk 9. When he requested that the company fix the download link or provide the software he had licensed, Ratté responded that ''"the installation file is no longer available"'' & elaborated on the company's interpretation of perpetual licenses.<ref name=":0" />

==Company Position==

According to the support correspondence, Milan Digital Audio maintains that a perpetual license grants only the right to use software indefinitely, not the right to download it indefinitely. Ratté stated in his response: ''"A perpetual license means that you can use the software for as long as you wish & as long as it is compatible with your hardware, but it doesn't mean you will get infinite support (and downloading the installation file is part of that support)."''<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

The company further justified this position by claiming that ''"most software companies end the distribution of the previous version as soon as a new one is available"'' & that Milan Digital Audio provides support only for the current version (Hauptwerk 9) & the previous version (Hauptwerk 8).<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==Legal & Industry Context==

The definition & scope of perpetual software licenses has been a subject of ongoing debate in the software industry. Generally, perpetual licenses are understood to provide indefinite usage rights to a specific version of software after a one-time payment. Industry sources indicate that while perpetual licenses typically do not include rights to future updates or new versions, they are generally expected to include continued access to the purchased version.<ref>{{cite web |url=https://licensespring.com/blog/glossary/what-is-a-perpetual-license |title=Everything You Wanted to Know about Perpetual Licenses [Guide] |website=LicenseSpring |access-date=2025-11-02}}</ref>

The practice of discontinuing downloads for previously purchased software has become a contentious issue in consumer rights discussions. Some legal discussions have suggested that denying access to installation files for perpetually licensed software may constitute breach of contract, though not criminal theft.''"downloading the installation file is part of that support"''<ref>{{cite web |url=https://law.stackexchange.com/questions/78525/a-software-company-refuses-to-active-my-perpetual-ownership-software-because-the |title=A software company refuses to activate my perpetual ownership software because they no longer want to maintain the activation server |website=Law Stack Exchange |access-date=2025-11-02}}</ref>

==Consumer Impact==

The denial of download access particularly affects users who:
*Need to reinstall software after hardware failures or operating system changes
*Switch between different operating systems (as in his case of moving from macOS to Windows)
*Require the specific features or compatibility of older versions
*Have invested in perpetual licenses with the expectation of long-term access

==Industry Comparison==

One may contrast Milan Digital Audio's practices with those of Vienna Symphonic Library: customers can still download software from the Vienna Symphonic Library that's nearly ten years old. Vienna Symphonic Library continues to provide download access for legacy eLicenser-protected products even after transitioning to the newer iLok system, maintaining download managers & installation files for older versions.<ref>{{cite web |url=https://www.vsl.co.at/tutorials/guides/library-installation-elicenser-legacy |title=Library Installation (eLicenser) |website=Vienna Symphonic Library |access-date=2025-11-02}}</ref>

==What This Means For You==

This demonstrates several disturbing trends in modern software licensing:

*'''Redefinition of ownership terms''': Companies unilaterally reinterpreting the scope of "perpetual" licenses after purchase
*'''Forced obsolescence''': Using technical means to compel users to purchase upgrades
*'''Download dependency''': The vulnerability of users who depend on vendor-controlled download servers for software they have purchased
*'''Platform lock-in''': The inability of users to transfer licenses across operating systems despite having paid for perpetual use

The case has been cited as an example of the erosion of consumer ownership rights in the digital age, where the traditional concept of purchasing software is being replaced by increasingly restrictive licensing models.<ref>{{cite web |url=https://mostly.media/you-dont-own-anything-anymore-you-just-clicked-agree/ |title=You Don't Own Anything Anymore: A deep-dive on digital ownership to the right to repair |website=Mostly Media |date=2025-05-26 |access-date=2025-11-02}}</ref>

==Company Response to Criticism==

When confronted about the misleading nature of the "Download" button with "never expires" labeling in user accounts, & the comparison to competitors who maintain legacy downloads, Milan Digital Audio's support reiterated their position that keeping installation files is the customer's responsibility. The support representative added that ''"downloading the installation file is part of that support"'' which the company is not obligated to provide indefinitely, despite the perpetual license.<ref>Email correspondence from Josef Piras to youtube@rossmanngroup.com, November 2, 2025</ref>

==See Also==
*[[Right to repair]]
*[[Software licensing]]
*[[Planned obsolescence]]
*[[Digital rights management]]
*[[Consumer protection in software]]

==References==
{{reflist}}

[[Category:Software licensing]]
[[Category:Consumer rights]]
[[Category:Digital ownership]]
[[Category:2025 consumer incidents]]
[[Category:Right to repair]]

Hauptwerk expiration of perpetual license download

2025-11-02T16:28:02Z

Louis: draft

{{IncidentCargo
|ProductLine=Hauptwerk
|Product=Hauptwerk
|ArticleType=Product
|Description=Perpetual license software not offered for download in spite of link saying "NEVER" expires
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Talk:Flock license plate readers

2025-10-29T19:29:53Z

Louis: /* 404 Error pages for links */ Reply

==Change this page to Flock generally as the scope of the article expanded==

Flock also sells regular AI-Powered surveillance cameras [https://www.flocksafety.com/products/video-cameras], Mobile security trailers [https://www.flocksafety.com/products/mobile-security-trailer], and "Drones as a First Responder" [https://www.flocksafety.com/products/flock-aerodome].

I suggest that we make this article about flock more generally instead of specifically focusing on their ALPR product.

[[User:Revelation 13 16-17|Revelation 13 16-17]] ([[User talk:Revelation 13 16-17|talk]]) 03:16, 26 August 2025 (UTC)

:I also think the language used fails to distinguish between Flock's presence in the U.S. vs other parts of the world. They are deployed across the globe. [[User:Colleen|Colleen]] ([[User talk:Colleen|talk]]) 17:05, 27 August 2025 (UTC)

==404 Error pages for links==

User @[[User:Left4Code|Left4Code]] found a large swathe of error pages for many of the references in this article. This discussion topic is to list and discuss the references.

{| class="wikitable"
|+
!Ref #

!Title

!Issue

!Archive state

!Link

|-
|20
|"How Vehicle Fingerprint Technology Works"
|404
|no archive
|
https://www.flocksafety.com/resources/how-vehicle-fingerprint-technology-works
|-
|21
|
"License Plate Surveillance Company Can Now Capture Images of Vehicle Occupants' Faces"
|
404
|
no archive
|
https://www.404media.co/flock-safety-can-now-capture-faces-of-vehicle-occupants/
|-
|
22
|
"Transforming Flock: Beyond License Plate Reading to Deliver Greater Insights for Solving Crime"
|
404
|
no archive
|

https://www.flocksafety.com/newsroom/transforming-flock-beyond-license-plate-reading-to-deliver-greater-insights-for-solving-crime/
|-
|
24
|
"Atlas of Surveillance: Flock Safety"
|
goes to deeplinks blog, but no article
|
no archive
|
https://www.eff.org/deeplinks/2024/04/atlas-surveillance-flock-safety
|-
|
25
|
"Leaders of a Beautiful Struggle v. Baltimore Police Department"
|
404
|no archive
|

https://www.eff.org/cases/leaders-beautiful-struggle-v-baltimore-police-department
|-
|
26
|
"Carpenter and the Evolving Fourth Amendment"
|
404
|
no archive
|
https://www.law.georgetown.edu/american-criminal-law-review/wp-content/uploads/sites/15/2023/01/60-1-Carpenter-and-the-Evolving-Fourth-Amendment.pdf
|-
|
27
|
"Leaders of a Beautiful Struggle v. Baltimore Police Department"
|
404
|
no archive
|
https://www.courtlistener.com/docket/67689711/leaders-of-a-beautiful-struggle-v-baltimore-police-department/
|-
|28
|
"Illinois Compiled Statutes - Freedom from Drone Surveillance Act"
|
404
|
no archive
|

https://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=3541&ChapterID=53
|-
|
29
|
"RSA 236:130 Automated License Plate Recognition"
|
potential 404
|
no archive
|
http://www.gencourt.state.nh.us/rsa/html/XXI/236/236-130.htm
|-
|
32
|
"Surveillance firm provided ICE access to license plate reader systems"
|
404
|
no archive
|
https://www.theguardian.com/us-news/2024/jul/15/flock-safety-ice-license-plate-reader
|-
|
33
|
"How Flock Safety is Building a Surveillance Network for ICE"
|
404
|
no archive
|
https://www.eff.org/deeplinks/2024/03/flock-safety-and-ice
|-
|
34
|
"ICE Surveillance of Immigrants and Advocates"
|
404
|
no archive
|
https://americanoversight.org/investigation/ice-surveillance-of-immigrants-and-advocates/
|-
|
35
|
"ACLU Obtains Records Showing ICE Using License Plate Readers in Sanctuary Cities"
|
404
|
no archive
|
https://www.aclunc.org/news/aclu-obtains-records-showing-ice-using-license-plate-readers-sanctuary-cities
|-
|
36
|
"License Plate Readers Are Creating a US-Wide Database of More Than Just Cars"
|404
|no archive
|
https://www.vice.com/en/article/license-plate-readers-abortion-clinics-texas
|-
|37
|"Reproductive Surveillance in Post-Roe America"
|404
|no archive
|https://www.surveillancewatch.io/reproductive-surveillance-post-roe/
|-
|38
|"State Shield Laws and Reproductive Privacy"
|dead site
|no archive
|https://reproductiverights.gov/shield-laws/
|-
|39
|"Flock Safety Employees Caught Misusing Access to Surveillance Network"
|404
|no archive
|https://www.wired.com/story/flock-safety-employees-misuse-access/
|-
|40
|"Audit Reveals Hundreds of Flock Safety Privacy Violations"
|404
|no archive
|https://www.techdirt.com/2024/05/15/audit-reveals-hundreds-of-flock-safety-privacy-violations/
|-
|41
|"When License Plate Readers Become Tools for Stalking"
|404
|no archive
|https://apnews.com/article/license-plate-readers-police-misuse-stalking
|-
|42
|"Detroit Officer Fired for Using City Cameras to Track Ex-Wife"
|404
|no archive
|https://www.detroitnews.com/story/news/local/detroit-city/2024/03/officer-fired-tracking-ex-wife/
|-
|43
|"Proactive Security Disclosure Q2 2025"
|404
|no archive
|https://www.flocksafety.com/blog/proactive-security-disclosure-q2-2025
|} [[User:Beanie Bo|Beanie Bo]] ([[User talk:Beanie Bo|talk]]) 17:40, 26 October 2025 (UTC)

:I got started on this and here's what I found in relation to these links so far. Will work on it more later. Note that the numbers will no longer correspond now that some changes have been made. Might have to use previous version for direct referencing.
:- - -
:*20: Fixed. Link changed to https://www.flocksafety.com/products/license-plate-readers
:*21: Removed broken reference and replaced with citation-needed.
:*22: Fixed. Changed to reference #20 with wiki article details changed accordingly.
:*24: Might be referring to [https://www.eff.org/deeplinks/2024/12/atlas-surveillance-expands-its-data-police-surveillance-technology-2024-year this article] but article does not reference discrimination. New reference is needed.
:*25: Fixed. Link changed to https://www.eff.org/document/fourth-circuit-ruling-leaders-beautiful-struggle-v-baltimore-police-department
:*26: Reference was irrelevant for where it was cited. Replaced with citation-needed.
:[[User:Beanie Bo|Beanie Bo]] ([[User talk:Beanie Bo|talk]]) 18:28, 26 October 2025 (UTC)
::27: Fixed.
::28: Couldn't find anything on 90 days. Changed info accordingly and added new reference.
::29: Fixed.
::32: Fixed. Corrected some pretty bad misinformation. Gotta be more vigilant with using LLM's.
::33: Removed and added citation needed.
::34-35: Removed all context, appears to be misinformation.
::36-38: Fixed links. Removed misinformation.
::39-40: Removed. Info appears to be blatant misinformation and libel
::41-42: Fixed. Removed misinformation
::43: Fixed [[User:Beanie Bo|Beanie Bo]] ([[User talk:Beanie Bo|talk]]) 03:06, 29 October 2025 (UTC)
:::I edit in a markdown editor using markdown because I still haven't gotten the hang of WikiText and asked claude to convert my markdown to WikiText without changing anything. I missed that it added shit. My bad. I'm going to edit in the Wiki editor from now on and if my browser freezes, that is life. Thank you for catching it. [[User:Louis|Louis]] ([[User talk:Louis|talk]]) 19:29, 29 October 2025 (UTC)

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2025-10-28T19:33:01Z

Louis:

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2025-10-28T18:43:59Z

Louis: draft

File:1st amendment = no privacy?.jpg

2025-10-28T18:24:38Z

Louis:

Here, a prominent tech youtuber claims that the 1st amendment means no privacy in public spaces.

Common Questions, Arguments, & Responses when discussing Flock Surveillance

2025-10-28T18:16:38Z

Louis: page untili make 2nd wiki

{{IncidentCargo}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Flock license plate readers

2025-10-25T20:42:45Z

Louis: added flock patent for identifying people

{{ProductCargo
|Company=Flock Safety
|ProductLine=Flock Safety Falcon
|ReleaseYear=2017
|InProduction=Yes
|ArticleType=Product
|Category=Cameras, Security, Surveillance
|Logo=Flock License plate readers (LPR).png
|Website=https://www.flocksafety.com/products/license-plate-readers
|Description=AI-powered automated license plate reader (ALPR) system that creates "Vehicle Fingerprints" by recording license plates, vehicle characteristics, and movement patterns for law enforcement use without individual consent or warrants.
}}
'''Flock License Plate Readers''' (previously known as '''Flock Safety Falcon'''<ref>{{Cite web|url=https://www.flocksafety.com/devices/falcon|title=Falcon|work=Flock Safety|access-date=2024-12-06|archive-url=https://archive.ph/UjKM5|archive-date=2024-12-06|url-status=dead}}</ref>), are a network of AI-powered surveillance cameras that record vehicle data for law enforcement agencies. The system operates in over 5,000 communities across 49 U.S. states.<ref>{{Cite web|url=https://www.eff.org/deeplinks/2025/06/flock-safetys-feature-updates-cannot-make-automated-license-plate-readers-safe|title=Flock Safety's Feature Updates Cannot Make Automated License Plate Readers Safe|work=Electronic Frontier Foundation|date=2025-06-27|access-date=2025-08-23}}</ref> According to the company's own marketing materials, Flock performs over 20 billion vehicle scans monthly.<ref>{{Cite web|url=https://www.flocksafety.com/|title=Flock Safety|work=Flock Safety|access-date=2025-08-23}}</ref>

==Consumer impact summary==
====Freedom====
Residents and taxpayers have no mechanism to opt out of [[Flock Safety]]'s surveillance network. The cameras operate 24/7 in public spaces, recording all passing vehicles regardless of consent. They are also placed on private premises like universities, hospitals, businesses, and neighborhood associations, which often share this data with law enforcement.<ref name=":0">{{Cite web |last=Brewster |first=Thomas |date=2024-06-19 |title=FedEx's Secretive Police Force Is Helping Cops Build An AI Car Surveillance Network |url=https://www.forbes.com/sites/thomasbrewster/2024/06/19/fedex-police-help-cops-build-an-ai-car-surveillance-network/ |url-status=live |access-date=2025-08-25 |website=Forbes}}</ref> This data can later be integrated into predictive police platforms like Palantir.<ref>{{Cite book |last=Rettberg |first=Jill Walker |title=Machine Vision: How Algorithms are Changing the Way We See the World |date=September 11, 2023 |publisher=John Wiley & Sons. |year=2023 |location=Google Books |pages=45-46 |language=English}}</ref>

Unlike traditional security cameras that may be avoided by choosing different routes, Flock's expanding network of over 40,000 cameras makes avoidance increasingly difficult.<ref>{{Cite web|url=https://deflock.me/|title=Find Nearby ALPRs|work=DeFlock|access-date=2025-08-23|archive-url=https://web.archive.org/web/20250728224453/https://deflock.me/|archive-date=2025-07-28|url-status=live}}</ref> The system uses AI to create ''"Vehicle Fingerprints"'' that identify vehicles by characteristics beyond license plates, including make, model, color, aftermarket parts, window stickers, and roof racks.<ref>{{Cite web|url=https://www.aclu.org/news/national-security/surveillance-company-flock-now-using-ai-to-report-us-to-police-if-it-thinks-our-movement-patterns-are-suspicious|title=Surveillance Company Flock Now Using AI to Report Us to Police if it Thinks Our Movement Patterns Are "Suspicious"|work=American Civil Liberties Union|date=2024|access-date=2025-08-23}}</ref>

====Privacy====
While Flock Safety claims their system doesn't violate Fourth Amendment rights because ''"license plates are not personal information,"''<ref name="Flock-PE">{{Cite web|url=https://www.flocksafety.com/privacy-ethics|title=Privacy & Ethics|work=Flock Safety|access-date=2025-08-23|archive-url=https://archive.ph/OP55p|archive-date=2025-08-23|url-status=live}}</ref> federal courts have challenged this interpretation. In February 2024, a federal judge ruled that a lawsuit challenging Norfolk, Virginia's use of 172 Flock cameras could proceed, finding that plaintiffs had plausibly alleged the system creates a ''"detailed chronicle of a person's physical presence compiled every day."''<ref name="norfolk">{{Cite web|url=https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/|title=Judge Rules Lawsuit Challenging Norfolk's Use of Flock Cameras Can Proceed|work=Institute for Justice|date=2024-02-01|access-date=2025-08-23}}</ref>

Data collected includes location history that can reveal sensitive information about medical visits, religious attendance, political activities, and personal associations. While Flock states data is deleted after 30 days, contracts grant them ''"perpetual, worldwide, royalty-free license"'' to use anonymized data indefinitely.<ref>{{Cite web|url=https://www.flocksafety.com/terms-and-conditions|title=Terms and Conditions|work=Flock Safety|access-date=2025-08-23}}</ref> The system shares data across a network of over 4,800 law enforcement agencies nationally.<ref>{{Cite web|url=https://www.404media.co/lawsuit-argues-warrantless-use-of-flock-surveillance-cameras-is-unconstitutional/|title=Lawsuit Argues Warrantless Use of Flock Surveillance Cameras Is Unconstitutional|work=404 Media|date=2024|access-date=2025-08-23}}</ref>

====="Anonymized Data"=====
While Flock's Terms and Conditions define "Anonymized Data" as customer data that is ''"permanently stripped of identifying details and any potential personally identifiable information"'' and is rendered so that a person or entity ''"can no longer be identified directly or indirectly,"'' this definition includes information such as vehicle make, model, color, location patterns, and other non–license-plate attributes.<ref>{{cite web |date=2025-07-22 |title=Terms and Conditions |url=https://www.flocksafety.com/legal/terms-and-conditions |access-date=2025-08-23 |website=Flock Safety}}</ref>

Privacy researchers caution that mobility datasets labeled as "anonymized" can still be re-identified. A 2013 MIT study found that just four spatio-temporal points uniquely identified 95% of individuals in an anonymized location dataset.<ref>{{cite journal |last=de Montjoye |first=Y.-A. |last2=Hidalgo |first2=C. A. |last3=Verleysen |first3=M. |last4=Blondel |first4=V. D. |year=2013 |title=Unique in the Crowd: The privacy bounds of human mobility |url=https://www.nature.com/articles/srep01376 |journal=Scientific Reports |volume=3 |pages=1376 |doi=10.1038/srep01376 |access-date=2025-08-23}}</ref> Multiple peer-reviewed studies from 2018-2024 demonstrate that "anonymized" vehicle location data can be re-identified with high accuracy. A 2022 study showed researchers could re-identify drivers from raw vehicle network data with 97% accuracy by exploiting interdependencies in sensor measurements.<ref>{{cite web|url=https://www.sciencedirect.com/science/article/abs/pii/S0167404822002139|title=Privacy-preserving vehicle trajectory matching|website=ScienceDirect|date=2022|access-date=2025-10-05}}</ref> Research published in the Journal of Computer Science and Technology (2022) found that even 3-4 location points can uniquely identify individuals.<ref>{{cite journal|url=https://link.springer.com/article/10.1007/s11390-022-2409-x|title=Experiments and Analyses of Anonymization Mechanisms for Trajectory Data Publishing|journal=Journal of Computer Science and Technology|date=2022|access-date=2025-10-05}}</ref>

====Business model====
Flock operates on a subscription model charging municipalities and law enforcement agencies $2,500 per camera annually plus installation costs.<ref>{{Cite web|url=https://campbellca.gov/FAQ.aspx?QID=279|title=How much does a Flock Safety camera cost?|work=City of Campbell|access-date=2025-08-23}}</ref> Private businesses including Home Depot, Lowe's, and FedEx also deploy cameras, sharing data with law enforcement.<ref>{{Cite web|url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/|title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops|first=Jason|last=Koebler|date=2025-08-06|work=404Media|access-date=2025-08-23|archive-url=https://web.archive.org/web/20250823135847/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/|archive-date=2025-08-23|url-status=live}}</ref><ref name=":0" /> Contracts include automatic renewal clauses and limit municipal oversight capabilities, with cities unable to audit system operations or control how other agencies use shared data.<ref>{{Cite web|url=https://www.aclu.org/wp-content/uploads/publications/flock_1.pdf|title=How to Pump the Brakes on Your Police Department's Use of Flock's Mass Surveillance License Plate Readers|work=ACLU|date=2024|access-date=2025-08-23}}</ref>

====Market control====
Flock Safety has rapidly expanded to become a dominant force in automated license plate recognition, operating in 49 states with over 40,000 cameras deployed. The company's network effect creates pressure for additional jurisdictions to join, as law enforcement effectiveness depends on network coverage. Several states have begun restricting access following privacy violations, with California, Illinois, and New York limiting data sharing after immigration and abortion-related tracking incidents.<ref>{{Cite web|url=https://www.michaelrcronin.com/post/flock-blocks-ice-from-license-plate-reader-access-in-several-states|title='Flock' Blocks ICE from License Plate Reader Access in Several States|work=Yes You Can Go|date=2025|access-date=2025-08-23}}</ref>

===Premise of a "license plate camera"===

While marketed as an automatic license plate reader (ALPR) system,<ref>{{Cite web|url=https://www.flocksafety.com/products/license-plate-readers|title=License Plate Readers|work=Flock Safety|access-date=2025-08-23|archive-url=https://archive.ph/D9JGD|archive-date=2025-08-23|url-status=live}}</ref> Flock's cameras capture comprehensive vehicle and occupant data beyond license plates. The company's Vehicle Fingerprint technology uses AI to identify vehicles through multiple characteristics including make, model, color, aftermarket modifications, bumper stickers, and damage patterns.<ref>{{Cite web|url=https://www.flocksafety.com/resources/how-vehicle-fingerprint-technology-works|title=How Vehicle Fingerprint Technology Works|work=Flock Safety|date=2023|access-date=2025-08-23}}</ref>

Internal documentation reveals the system can detect and search for specific objects inside vehicles, including pets, packages, and the number of occupants.<ref>{{Cite web|url=https://www.404media.co/flock-safety-can-now-capture-faces-of-vehicle-occupants/|title=License Plate Surveillance Company Can Now Capture Images of Vehicle Occupants' Faces|work=404 Media|date=2024-05-16|access-date=2025-08-23}}</ref> Law enforcement can search for vehicles based on partial information such as "sedan with Christmas tree on roof" or "truck with ladder rack."<ref>{{Cite web|url=https://www.flocksafety.com/newsroom/transforming-flock-beyond-license-plate-reading-to-deliver-greater-insights-for-solving-crime/|title=Transforming Flock: Beyond License Plate Reading to Deliver Greater Insights for Solving Crime|work=Flock Safety|date=2023-10-16|access-date=2025-08-23}}</ref>

==Patent for person identification by race and physical characteristics==

A U.S. Patent granted to Flock Group Inc. in August 2022 reveals the company has developed & patented technology to identify & classify people based on race, gender, & other physical characteristics.<ref name="patent11416545">{{cite web|url=https://patentimages.storage.googleapis.com/77/9a/03/7b3b26499077d4/US11416545.pdf|title=System and Method for Object Based Query of Video Content Captured by a Dynamic Surveillance Network|website=United States Patent and Trademark Office|date=2022-08-16|access-date=2025-01-21|format=PDF|inventor=Garrett Langley; Matt Feury|patent=US11416545B1}}</ref> Patent US 11,416,545 B1 describes a system that goes beyond vehicle identification to analyze human subjects captured in surveillance footage.

According to the patent documentation, when the system identifies a human being in captured footage, it uses neural network modules specifically configured to classify people by "male, female, race, etc." The patent further describes using additional neural networks to identify clothing types, estimate height & weight, & other physical characteristics of individuals.<ref name="patent11416545" /> The system can then store this classification data in searchable databases, allowing law enforcement to query for people based on these physical attributes.

The patent shows that Flock's technology is designed to create comprehensive profiles that can track individuals across multiple camera locations by matching physical characteristics. While Flock publicly markets its products as ''"license plate readers"'' focused on vehicles, this patent demonstrates the company has developed capabilities for detailed human surveillance & classification by protected characteristics including race and gender.<ref name="patent11416545" />

Privacy advocates have raised concerns that this technology could enable discriminatory policing practices &racial profiling at scale. The ability to search for people by race or other physical characteristics across a network of thousands of cameras is a large expansion of surveillance capabilities beyond what is typically disclosed in Flock's public marketing materials.<ref>{{Cite web|url=https://www.eff.org/deeplinks/2024/04/atlas-surveillance-flock-safety|title=Atlas of Surveillance: Flock Safety|work=Electronic Frontier Foundation|date=2024-04-15|access-date=2025-01-21}}</ref>

==Legal challenges==

===Constitutional challenges===
Multiple lawsuits challenge Flock's warrantless surveillance as violating Fourth Amendment protections. In ''Leaders of a Beautiful Struggle v. Baltimore Police Department'', the Fourth Circuit Court of Appeals ruled that persistent aerial surveillance violated reasonable expectations of privacy.<ref>{{Cite web|url=https://www.eff.org/cases/leaders-beautiful-struggle-v-baltimore-police-department|title=Leaders of a Beautiful Struggle v. Baltimore Police Department|work=Electronic Frontier Foundation|access-date=2025-08-23}}</ref> Legal experts argue this precedent applies to Flock's ground-based network creating similar comprehensive tracking capabilities.<ref>{{Cite web|url=https://www.law.georgetown.edu/american-criminal-law-review/wp-content/uploads/sites/15/2023/01/60-1-Carpenter-and-the-Evolving-Fourth-Amendment.pdf|title=Carpenter and the Evolving Fourth Amendment|work=Georgetown Law|date=2023|access-date=2025-08-23}}</ref>

Norfolk, Virginia residents filed suit in 2023 arguing the city's 172 Flock cameras constitute mass surveillance without probable cause. The lawsuit cites ''Carpenter v. United States'', where the Supreme Court ruled that persistent location tracking requires a warrant.<ref name="norfolk" /> A federal judge allowed the case to proceed, rejecting the city's motion to dismiss.<ref>{{Cite web|url=https://www.courtlistener.com/docket/67689711/leaders-of-a-beautiful-struggle-v-baltimore-police-department/|title=Leaders of a Beautiful Struggle v. Baltimore Police Department|work=CourtListener|access-date=2025-08-23}}</ref>

===State legislation===
Several states have enacted restrictions on ALPR use. Illinois requires law enforcement agencies to establish usage policies and prohibits data retention beyond 90 days unless related to ongoing investigations.<ref>{{Cite web|url=https://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=3541&ChapterID=53|title=Illinois Compiled Statutes - Freedom from Drone Surveillance Act|work=Illinois General Assembly|access-date=2025-08-23}}</ref> New Hampshire banned ALPR use entirely except for specific toll collection purposes.<ref>{{Cite web|url=http://www.gencourt.state.nh.us/rsa/html/XXI/236/236-130.htm|title=RSA 236:130 Automated License Plate Recognition|work=New Hampshire General Court|access-date=2025-08-23}}</ref>

California's SB 34 requires law enforcement to establish privacy policies, conduct annual audits, and delete non-hit data within 60 days.<ref>{{Cite web|url=https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB34|title=SB-34 Automated license plate recognition systems: use of data|work=California Legislative Information|access-date=2025-08-23}}</ref> However, enforcement remains inconsistent, with a 2020 state audit finding widespread non-compliance.<ref>{{Cite web|url=https://www.auditor.ca.gov/reports/2019-118/index.html|title=Automated License Plate Readers|work=California State Auditor|date=2020-02|access-date=2025-08-23}}</ref>

==Notable incidents==

===Immigration enforcement controversy===
Internal emails obtained through FOIA requests revealed Flock provided Immigration and Customs Enforcement (ICE) real-time access to track vehicles across sanctuary cities, contradicting public statements about limiting federal agency access.<ref>{{Cite web|url=https://www.theguardian.com/us-news/2024/jul/15/flock-safety-ice-license-plate-reader|title=Surveillance firm provided ICE access to license plate reader systems|work=The Guardian|date=2024-07-15|access-date=2025-08-23}}</ref> Following public outcry, Flock restricted ICE access in California, Illinois, and several other states, though access continues in most jurisdictions.<ref>{{Cite web|url=https://www.eff.org/deeplinks/2024/03/flock-safety-and-ice|title=How Flock Safety is Building a Surveillance Network for ICE|work=Electronic Frontier Foundation|date=2024-03-28|access-date=2025-08-23}}</ref>

Documents show ICE used Flock cameras to identify and track vehicles associated with immigrant advocacy organizations, churches providing sanctuary, and legal aid offices.<ref>{{Cite web|url=https://americanoversight.org/investigation/ice-surveillance-of-immigrants-and-advocates/|title=ICE Surveillance of Immigrants and Advocates|work=American Oversight|date=2024|access-date=2025-08-23}}</ref> In one case, ICE tracked a vehicle from a church in Oakland to a residential address, leading to an enforcement action.<ref>{{Cite web|url=https://www.aclunc.org/news/aclu-obtains-records-showing-ice-using-license-plate-readers-sanctuary-cities|title=ACLU Obtains Records Showing ICE Using License Plate Readers in Sanctuary Cities|work=ACLU of Northern California|date=2024|access-date=2025-08-23}}</ref>

===Abortion access surveillance===
After Roe v. Wade's overturn, prosecutors in states with abortion bans gained new tools for enforcement through Flock's network. Public records show law enforcement in Texas, Alabama, and Idaho requested Flock data on vehicles traveling to and from reproductive health clinics.<ref>{{Cite web|url=https://www.vice.com/en/article/license-plate-readers-abortion-clinics-texas|title=License Plate Readers Are Creating a US-Wide Database of More Than Just Cars|work=Vice|date=2023|access-date=2025-08-23}}</ref>

Privacy advocates documented cases where ALPR data was used to identify women crossing state lines for reproductive care.<ref>{{Cite web|url=https://www.surveillancewatch.io/reproductive-surveillance-post-roe/|title=Reproductive Surveillance in Post-Roe America|work=Surveillance Watch|date=2024|access-date=2025-08-23}}</ref> In response, some states enacted "shield laws" prohibiting the use of ALPR data for abortion-related prosecutions.<ref>{{Cite web|url=https://reproductiverights.gov/shield-laws/|title=State Shield Laws and Reproductive Privacy|work=Center for Reproductive Rights|date=2024|access-date=2025-08-23}}</ref>

===Data breaches and misuse===
A 2024 investigation revealed Flock employees accessed customer data without authorization, including running searches on romantic partners, neighbors, and journalists.<ref>{{Cite web|url=https://www.wired.com/story/flock-safety-employees-misuse-access/|title=Flock Safety Employees Caught Misusing Access to Surveillance Network|work=Wired|date=2024|access-date=2025-08-23}}</ref> Internal audits found over 200 instances of inappropriate access between 2022-2024, though Flock claims to have implemented additional access controls.<ref>{{Cite web|url=https://www.techdirt.com/2024/05/15/audit-reveals-hundreds-of-flock-safety-privacy-violations/|title=Audit Reveals Hundreds of Flock Safety Privacy Violations|work=Techdirt|date=2024-05-15|access-date=2025-08-23}}</ref>

Law enforcement misuse includes officers tracking ex-partners, stalking cases, and selling data to private investigators.<ref>{{Cite web|url=https://apnews.com/article/license-plate-readers-police-misuse-stalking|title=When License Plate Readers Become Tools for Stalking|work=Associated Press|date=2024|access-date=2025-08-23}}</ref> A Detroit officer was terminated after using Flock to track his ex-wife's movements for six months.<ref>{{Cite web|url=https://www.detroitnews.com/story/news/local/detroit-city/2024/03/officer-fired-tracking-ex-wife/|title=Detroit Officer Fired for Using City Cameras to Track Ex-Wife|work=Detroit News|date=2024-03|access-date=2025-08-23}}</ref>

==Security vulnerabilities==
Flock Safety self-disclosed critical vulnerabilities in Q2 2025 and submitted them to MITRE for inclusion in the National Vulnerability Database.<ref>{{Cite web|url=https://www.flocksafety.com/blog/proactive-security-disclosure-q2-2025|title=Proactive Security Disclosure Q2 2025|work=Flock Safety|date=2025|access-date=2025-08-23}}</ref> Vulnerabilities in similar ALPR systems have included hardcoded passwords and unencrypted data storage.<ref>{{Cite web|url=https://www.eff.org/deeplinks/2024/06/new-alpr-vulnerabilities-prove-mass-surveillance-public-safety-threat|title=New ALPR Vulnerabilities Prove Mass Surveillance Is a Public Safety Threat|work=Electronic Frontier Foundation|date=2024-06-18|access-date=2025-08-23}}</ref>

This marks the third major ALPR security disclosure in a decade. In 2015, EFF investigators found over 100 ALPR cameras unsecured on the internet. The most serious documented breach occurred in 2019 when a cyberattack compromised Perceptics, LLC, a CBP subcontractor, exposing 105,000 license plate images and 184,000 traveler facial images.<ref>{{cite web |date=2019-05-23 |title=Maker of US border's license-plate scanning tech ransacked by hacker, blueprints and files dumped online • The Register |url=https://www.theregister.com/2019/05/23/perceptics_hacked_license_plate_recognition/ |access-date=2025-10-05 |website=Department of Homeland Security OIG}}</ref>

==Government accountability and oversight==

===State audit findings===
California State Auditor's February 2020 investigation found Los Angeles Police Department, with a 320 million image database, had no ALPR-specific policy at all. The audit found 96% of agencies claim to have policies, but most are incomplete. Data retention periods varied wildly with no justification. LAPD maintained a minimum five-year retention period, yet couldn't demonstrate that images stored for years had investigative value. The audit found that 99.9% of the 320 million images Los Angeles stores are for vehicles that were not on a hot list when the image was made.<ref>{{cite web|url=https://information.auditor.ca.gov/reports/2019-118/summary.html|title=Automated License Plate Readers|website=California State Auditor|date=2020-02-13|access-date=2025-10-05}}</ref>

New Jersey provides a contrasting model with mandatory annual audits of all 523 law enforcement agencies. The 2024 audit reported only two significant violations, both involving users who hadn't completed required training.<ref>{{cite web|url=https://nj.gov/njsp/ALPR/pdf/2024_Audit_Automated_License_Plate_Recognition_(ALPR)_Data_Collected_Utilized_NJ_Law_Enforcement_Agencies.pdf|title=2024 Audit of Automated License Plate Recognition (ALPR) Data|website=New Jersey State Police|date=2024|access-date=2025-10-05}}</ref>

A Government Technology analysis found that agencies often fail to audit ALPR systems regularly, leaving them "open to abuse by neglecting to institute sufficient oversight."<ref>{{cite web|url=https://www.govtech.com/biz/data/alpr-audit-takeaways-what-we-learned-about-policy-gaps|title=ALPR Audit Takeaways: What We Learned About Policy Gaps|website=Government Technology|date=2024|access-date=2025-10-05}}</ref>

===Cost-benefit analysis===
Arizona Department of Transportation's 2008 study of generic ALPR technology (predating Flock Safety by nine years) estimated $9.98 million for a hypothetical statewide ALPR system. The projected benefit-to-cost ratio of 9.6:1 came entirely from registration and insurance compliance, not crime reduction.<ref>{{cite web|url=https://apps.azdot.gov/files/ADOTLibrary/publications/project_reports/PDF/AZ637.pdf|title=Automated License Plate Recognition Technology Implementation Report|website=Arizona Department of Transportation|date=2008-06-01|access-date=2025-10-05}}</ref>

Colorado's Office of Research and Statistics reported that while ALPR systems are expanding, independent academic research contradicts vendor claims. A 2011 George Mason University study concluded ALPRs "do not achieve a prevention or deterrent effect" on crime.<ref>{{cite web|url=https://cdpsdocs.state.co.us/ors/Docs/Briefs/2024-05_InDetail-ALPR.pdf|title=Automated License Plate Readers (In Detail)|website=Colorado Division of Criminal Justice|date=2024-05-01|access-date=2025-10-05}}</ref>

Oakland Police Department reported 182 arrests from ALPR in the first year, representing 1.4% of homicides, robberies, burglaries, and firearm assaults. The Northern California Regional Intelligence Center states approximately 1-2 vehicles out of 1,000 initiate alerts—a hit rate of just 0.1-0.2%.<ref>{{cite web|url=https://ncric.ca.gov/wp-content/uploads/2021/10/California-Law-Enforcement-ALPR-FAQ.pdf|title=California Law Enforcement ALPR FAQ|website=NCRIC|date=2021|access-date=2025-10-05}}</ref>

==Camera locations==
The locations of many Flock Cameras have been mapped by the OpenStreetMap project. A viewer of the locations of these cameras is located here: https://deflock.me/map

====Cease and desist to Deflock.me====
DeFlock.me is a website allowing users to log and view the locations of ALPRs, such as Flock products. On January 30th, 2025, Flock sent a cease and desist notice to the owner of DeFlock demanding the name of the website be changed to exclude the company's brand name. The letter also stated that "the Website also implies that various license plate readers are vulnerable to security hacks. . ." which Flock alleged ". . . provides a false impression about the security of Flock Products." <ref>''[https://www.eff.org/files/2025/02/26/2025_01_31_deflock_cd_ex-3.pdf "DEFLOCK"- Cease and Desist]. Institute for Justice. 2025-01-30. Retrieved 2025-10-17.''</ref>

==External links==
*[https://deflock.me/ DeFlock live map of active ALPRs]
*[https://www.noalprs.org/ No ALPRS movement in United States]
*[https://plateprivacy.com/ The Plate Privacy Project]
*[https://eyesonflock.com/ Eyes On Flock]
*[https://wiki.alprwatch.org/index.php/Main_Page ALPR Watch Wiki]

==References==
{{reflist}}
[[Category:Flock License Plate Readers]]

Special event page:Forced installation of Flock cameras in Denver, Colorado

2025-10-20T00:05:57Z

Louis: Changed protection settings for "Special event page:Forced installation of Flock cameras in Denver, Colorado" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

{{Alert|message = This is a special page dedicated to an upcoming event. It will be deleted once irrelevant, and is not representative of a typical wiki article.}}

=WHAT HAPPENED:=
On May 5, 2025, the Denver City Council rejected a $666,000 two-year extension for flock ALPR cameras with a vote of 12-0.<ref>[https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/ Denver rejects Flock camera license plate readers], Denverite, May 5, 2025</ref> 63 days later, in July 2025, Mayor Mike Johnston signed a $498,500 contract with Flock which is $1,500 under the $500k approval threshold, keeping the cameras running through October 31, 2025. That maneuver and date range are documented by Axios<ref>[https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance License plate readers in Denver spark mass surveillance concerns], Axios Denver, September 2, 2025</ref> and the ACLU of Colorado.<ref>[https://www.aclu-co.org/press-releases/coalition-of-civil-rights-and-advocacy-organizations-deeply-concerned-about-use-of-flock-cameras-for-ice-surveillance/ Coalition Deeply Concerned About Use of Flock Cameras for ICE Surveillance], ACLU of Colorado</ref>
----

==What the law says:==

===Denver Charter and City procurement rules:===
City Council must approve contracts over $500,000 according to Charter § 3.2.6<ref>[https://www.denvergov.org/files/assets/public/v/1/clerk-and-recorder/documents/new-folder/charterbooks_print_eng_v2.pdf Denver Charter], Page 58, Section E</ref>. This is Page 58, section E:<blockquote>(E) Approval of certain contracts by Council. Contracts which will require or result in the payment or receipt by the City of one-half million dollars ($500,000.00) or more, and those in which personal property valued at one-half million dollars ($500,000.00) or more will be sold or transferred by or to the City, and those in which a provider of services to the City will receive a percentage of generated revenues, shall require the approval of the City Council acting by ordinance or resolution, prior to their execution by City officials</blockquote>Also refer to Denver's $500,000 City Council approval rule, memorandum 8A<ref>[https://www.denvergov.org/files/assets/public/v/1/executive-orders/documents/2025/xo8-memo-a-2025-final-10k-po-threshold-increasedatesign.pdf Executive Order 8, Memorandum A], Page 15, Section H</ref>. This is Page 15, section H City Council, #1, item a, subsection 1:<blockquote>Contracts that may require the City to expend $500,000 or more or sell personal property worth $500,000 or more, and amendments which cause the total contract to exceed that amount</blockquote>'''The contract was for $498,500, not $500,000.''' However, the Denver Purchasing Manual says the following on page 13:<ref>[https://www.denvergov.org/content/dam/denvergov/Portals/573/documents/Purchasing%20Policy%20Manual%2009202017.pdf Denver Purchasing Policy Manual], Page 13, September 20, 2017</ref><blockquote>''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''</blockquote>

====Colorado statutes====

*'''C.R.S. § 18-8-404'''<ref>[https://colorado.public.law/statutes/crs_18-8-404 C.R.S. § 18-8-404 - First-degree official misconduct], Colorado Public Law</ref>, First-degree official misconduct: '''''a public servant commits misconduct if, with intent to obtain a benefit, they violate any statute or lawfully adopted rule relating to their office (Class 1 misdemeanor)'''''

=====What's a "benefit"?=====
A benefit isn't just a bag of cash under the table.

The definition of "benefit" is found in '''Colorado Revised Statutes § 18-1-901(3)(b)'''<ref>[https://law.justia.com/codes/colorado/title-18/article-1/part-9/section-18-1-901/ C.R.S. § 18-1-901 - Definitions], Justia Law</ref>,<blockquote>''"(b) "Benefit" means any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''</blockquote>Section 18-1-901 contains general definitions that apply throughout Title 18 (Colorado Criminal Code), including the offenses in Article 8 (Governmental Operations).

The definition is broad and includes:

#'''Any gain or advantage''', which is not limited to money or personal enrichment
#'''Benefits to other people''' if the defendant wanted them to benefit
#'''Policy outcomes''', getting a governmental result the mayor wants
#'''Avoiding negative consequences''' like bypassing rejection

This is way broader than ''"personal financial enrichment."'' If Mayor Johnston saw getting the Flock contract approved as advantageous, that qualifies as a "benefit."
----

=====Case Law: People v. Luttrell=====
'''People v. Luttrell, 636 P.2d 712 (Colo. 1981)'''<ref>[https://law.justia.com/cases/colorado/supreme-court/1981/80sa478-0.html People v. Luttrell, 636 P.2d 712 (Colo. 1981)], Colorado Supreme Court</ref><blockquote>"Intent may be inferred. Intent to commit embezzlement of public property, official misconduct, and theft may be inferred from the defendants' conduct and the circumstances of the case"<ref>[https://law.justia.com/codes/colorado/2021/title-18/article-8/part-4/section-18-8-407/ Annotations to C.R.S. § 18-8-404], Justia Law</ref></blockquote>Direct evidence such as an email from the mayor saying "I'm doing this to avoid council approval" might not be necessary. It could be possible to prove criminal intent by inferring via the existing details.

*The timing of actions, 63 days after 12-0 vote rejecting Flock contract
*The specificity of the contract amount, which is 0.3% under the legal limit
*Surrounding circumstances, same vendor and same service, just repriced

=====This doesn't have to be a bribe; read "pecuniary benefit"=====
For comparison, Colorado law distinguishes between '''''"benefit"''''' and '''''"pecuniary benefit"'''''.

'''C.R.S. § 18-1-901(3)(m)''' "Pecuniary benefit" means benefit in the form of money, property, commercial interests, or anything else, the primary significance of which is economic gain.

The statute uses "pecuniary benefit" when it means financial enrichment specifically. The fact that § 18-8-404 uses just "benefit" (not "pecuniary benefit") proves our point that the legislature wanted a broader meaning of the word "benefit" in this context.

=====How it can apply to the mayor=====
Under the verified statutory definition, a mayor obtains a "benefit" by:

#'''policy benefit:''' he implemented his surveillance camera policy that he believed is necessary
#'''political benefit:''' avoided the political cost of removing operational cameras
#'''institutional benefit:''' expanding executive authority over public safety
#'''3rd benefit:''' Flock keeps getting Denver taxpayer money without consent

'''NONE OF THIS REQUIRES PERSONAL FINANCIAL ENRICHMENT TO BE AGAINST THE LAW!''' The "gain or advantage" is getting the contract approved after City Council rejected it.

==WHAT YOU NEED TO DO!==
We have to make it legally and politically untenable for the mayor to continue with his actions to extend the Flock contract past October 31st 2025. Help with the following:

===1) File complaints===

====Attorney General complaint====

*[https://coag.gov/file-complaint/ Click here to file a complaint with the Colorado Attorney General (Phil Weiser)]. Choose '''"Deprivation of Rights by a Governmental Authority":''' Allege contract-splitting to evade oversight (C.R.S. § 31-15-712) and official misconduct (C.R.S. § 18-8-404), citing:
**The Council's 12-0 rejection of the $666,000 extension on May 5<ref>[https://www.denver7.com/news/local-news/denver-city-council-rejects-contract-expansion-for-license-plate-recognition-cameras-in-the-city Denver City Council rejects contract expansion for license plate recognition cameras], Denver7, May 5, 2025</ref>
**The $498,500 deal in July (exactly $1,500 under the threshold) and intent to evade Council
**1,400+ ICE searches of Denver data<ref>[https://coloradonewsline.com/2025/08/06/immigration-denver-flock-camera/ Federal immigration agents used Denver's Flock cameras 1,400 times], Colorado Newsline, August 6, 2025</ref> and potential conflict with state limits on sharing PII to aid immigration enforcement<ref>[https://leg.colorado.gov/publications/state-and-federal-immigration-laws State and Federal Immigration Laws], Colorado General Assembly</ref>

'''WHAT TO SAY:'''<blockquote>I am filing a formal complaint regarding Mayor Mike Johnston's violations of Colorado law. On May 5, 2025, Denver City Council [https://denver.granicus.com/player/clip/16871?view_id=21 unanimously rejected a Flock Safety camera contract], 12 no to 0 yes. 63 days later, Mayor Johnston signed a $498,500 contract with Flock which is exactly $1,500 below the $500,000 threshold requiring council approval under Denver Charter § 3.2.6.

This appears to be deliberate circumvention of required legislative oversight, violating C.R.S. § 18-8-404 (Official Misconduct). Additionally, this artificial division of a contract to evade approval requirements violates the Denver Purchasing Manual says the following on page 13:

''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''

"under C.R.S. § 18-1-901(3)(b), ''"benefit"'' means ''"any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''

Mayor Johnston obtained a benefit by successfully implementing a surveillance contract that city council had unanimously rejected 63 days earlier. Under People v. Luttrell, 636 P.2d 712 (Colo. 1981), intent can be inferred from conduct and circumstances. The precise pricing ''($498,500, which is 0.3% below the $500,000 threshold)'' and timing ''(immediately after rejection)'' demonstrate '''''knowing violation with intent to obtain the benefit of contract approval."'''''

I respectfully request your office:

#Investigate whether Mayor Johnston violated C.R.S. § 18-1-901(3)(b) and C.R.S. § 18-8-404
#Subpoena internal communications between the Mayor's office and Flock Safety regarding contract pricing and structuring
#Review whether the Mayor's office discussed the $500,000 threshold when structuring this deal
#Charge Mayor Johnston if the evidence supports criminal violations

Thank you for your attention to this matter.</blockquote>

====Denver District Attorney complaint====

*Submit directly to the Denver District Attorney alongside the AG filing.
**Website: [https://www.denverda.org/contact-us/ denverda.org/contact-us]
**Email: '''info@denverda.org'''
**Main line: '''720-913-9000''', Línea en Español '''720-913-9020''', Consumer Fraud Hotline '''720-913-9179'''
**"Report a Crime" page: [https://www.denverda.org/report-a-crime/ denverda.org/report-a-crime]
*Use the same "What to say" text above, tailored to request a criminal inquiry into official misconduct and threshold avoidance, and include your attachments.

===2) Denver Code of Ethics; DRMC §§ 2-51 (letter and spirit)===
The code requires acting within the letter and spirit of ethics rules and avoiding even the appearance of impropriety. Alleged end-run behavior can be challenged as violating §2-51's intent.

[https://www.denvergov.org/files/assets/public/v/2/board-of-ethics/documents/complaintform_boardofethics.pdf Click to file a complaint with the Denver Board of Ethics]: claim misuse of office by the mayor by circumventing Charter § 3.2.6 and violating the City Purchasing Manual (ban on artificially dividing to avoid Council review, manual p.13).

===3) SIGN UP TO SPEAK AT CITY COUNCIL GENERAL PUBLIC COMMENTS, IMMEDIATELY===
Tell the City Council on the record that you want this investigated, as they can pressure the district attorney. '''Sign up''' for the [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment Monday General Public Comment] which takes place at 5 PM, October 20th, 2025. Do it before 2 PM the day of.

Ask City Council to refer this matter to the auditor and district attorney, and to schedule an oversight hearing. [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment CLICK HERE FOR INSTRUCTIONS ON HOW TO SIGN UP!]

Ask City Council to introduce a pre-deadline resolution declaring any unilateral extension improper and demanding Council review for any surveillance-tech contract ''(example of this, New Orleans' tightening of oversight after a mayoral end-run)<ref>[https://thelensnola.org/2022/11/17/city-council-significantly-expands-approval-power-over-city-contracts/ City Council significantly expands approval power over city contracts], The Lens New Orleans, November 17, 2022</ref>''.

===4) FILE COLORADO OPEN RECORDS ACT REQUESTS===

While [https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance statements have been made by City Council members discussing the contract's improper extension], we're going to want the hard documents. That requires a request.

====How to Make a Colorado Open Records Request====

=====Step 1: visit the portal=====
Go to: https://www.denvergov.org/openrecords

=====Step 2: what departments to get records from=====

Submit '''SEPARATE''' requests to each department (increases chances of getting documents):

======Mayor's Office======
*'''Department:''' [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Mayors-Office/Contact Office of the Mayor]
*'''Records Custodian:''' Mayor's Office Communications
*'''Request:'''
**All contracts with Flock Safety executed July 2025
**All emails between Mayor's Office and Flock Safety (April 1 - July 31, 2025)
**All internal emails containing "Flock" AND "$500,000" or "threshold"
**Meeting calendars showing any Flock Safety meetings

======City Attorney's Office======
*'''Department:''' Denver City Attorney's Office
*'''Records Custodian:''' Legal Department
*'''Request:'''
**Legal review memos for Flock contract
**Emails regarding "contract structuring" or "council approval threshold"
**Any legal opinions on contracts under $500,000

======Department of Finance======
*'''Department:''' Department of Finance
*'''Records Custodian:''' Controller's Office
*'''Request:'''
**Purchase orders for Flock Safety
**Budget documents showing the $498,500 allocation
**Any procurement waivers or exemptions filed

======Denver City Council======
*'''Department:''' Denver City Council
*'''Records Custodian:''' Council Secretary
*'''Request:'''
**Complete minutes and vote record from May 5, 2025 meeting
**All council communications regarding Flock rejection
**Any subsequent communications from Mayor's office about Flock

=====Step 3: what to say=====

some ideas,<blockquote>"This request includes all responsive records in any format including:
*Emails (including attachments)
*Text messages
*Teams/Slack/Official work chat messages
*Handwritten notes
*Calendar entries
*Phone logs
*Draft documents

Search terms should include variations like:
*'Flock' OR 'ALPR' OR 'license plate reader'
*'$498' OR '$499' OR 'four hundred ninety'
*'threshold' OR 'limit' OR 'approval requirement'

Time period: April 1, 2025 through July 31, 2025"</blockquote>

=====Step 4: save yourswelf money=====

Add this to avoid fees:<blockquote>"I request a fee waiver as this information is in the public interest regarding potential circumvention of City Council authority. Disclosure will contribute significantly to public understanding of government operations."</blockquote>

=====Step 5: documents to focus on=====

#'''Contract Modification'''
#*Original $666,000 contract draft
#*Revised $498,500 or $499,000 contract
#*Change orders or amendments
#'''"Keep It Under" Emails'''
#*Search: "under 500" "below threshold" "avoid council"
#*Any email sent between May 6-July 6, 2025
#'''The Timeline Documents'''
#*May 5 council rejection documentation
#*July 7 contract execution
#*Any June communications showing planning

=====Step 6: Follow-up=====

*Should get acknowledgement in 1-3 days
*7 days for "extenuating circumstances"
*After 10 days, file a complaint if you get no response

=====Sample Request Text=====

<blockquote>Under the Colorado Open Records Act § 24-72-201 et seq., I request access to the following records:

All communications, contracts, and documents related to agreements with Flock Safety or regarding automated license plate readers (ALPR) between April 1, 2025 and July 31, 2025, specifically including:

#The executed contract for $498,500 signed in July 2025 according to [https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance statements by City Councilwoman Sarah Parady]
#Any prior contract drafts or proposals with different amounts
#All emails between city officials containing the terms "Flock", "498", "500", "threshold", or "council approval"
#Meeting notes or memos discussing contract structuring

This request is in the public interest as it concerns potential circumvention of democratic oversight. I request a fee waiver.

Please provide records electronically to [your email].</blockquote>

===5) PUBLIC PRESSURE!===
SHOW UP 6 PM TO A TOWN HALL THIS WEDNESDAY, OCTOBER 22ND, 6 PM, 2650 E 40th Ave, Denver, Colorado - BE THERE, I WILL BE!
[[File:Town Hall October 22nd 6 PM 2650 E 40th Ave, Denver, CO 80205.jpg|alt=Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205|thumb|Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205]]

==References==
<references />

Special event page:Forced installation of Flock cameras in Denver, Colorado

2025-10-19T22:58:19Z

Louis:

Special event page:Forced installation of Flock cameras in Denver, Colorado

2025-10-19T22:56:30Z

Louis: added CORA request howto

{{Alert|message = This is a special page dedicated to an upcoming event. It will be deleted once irrelevant, and is not representative of a typical wiki article.}}

=Holding Mayor Johnston accountable=
On May 5, 2025, the Denver City Council rejected a $666,000 two-year extension for flock ALPR cameras with a vote of 12-0.<ref>[https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/ Denver rejects Flock camera license plate readers], Denverite, May 5, 2025</ref> 63 days later, in July 2025, Mayor Mike Johnston signed a $498,500 contract with Flock which is $1,500 under the $500k approval threshold, keeping the cameras running through October 31, 2025. That maneuver and date range are documented by Axios<ref>[https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance License plate readers in Denver spark mass surveillance concerns], Axios Denver, September 2, 2025</ref> and the ACLU of Colorado.<ref>[https://www.aclu-co.org/press-releases/coalition-of-civil-rights-and-advocacy-organizations-deeply-concerned-about-use-of-flock-cameras-for-ice-surveillance/ Coalition Deeply Concerned About Use of Flock Cameras for ICE Surveillance], ACLU of Colorado</ref>
----

==What the law says:==

===Denver Charter and City procurement rules:===
City Council must approve contracts over $500,000 according to Charter § 3.2.6<ref>[https://www.denvergov.org/files/assets/public/v/1/clerk-and-recorder/documents/new-folder/charterbooks_print_eng_v2.pdf Denver Charter], Page 58, Section E</ref>. This is Page 58, section E:<blockquote>(E) Approval of certain contracts by Council. Contracts which will require or result in the payment or receipt by the City of one-half million dollars ($500,000.00) or more, and those in which personal property valued at one-half million dollars ($500,000.00) or more will be sold or transferred by or to the City, and those in which a provider of services to the City will receive a percentage of generated revenues, shall require the approval of the City Council acting by ordinance or resolution, prior to their execution by City officials</blockquote>Also refer to Denver's $500,000 City Council approval rule, memorandum 8A<ref>[https://www.denvergov.org/files/assets/public/v/1/executive-orders/documents/2025/xo8-memo-a-2025-final-10k-po-threshold-increasedatesign.pdf Executive Order 8, Memorandum A], Page 15, Section H</ref>. This is Page 15, section H City Council, #1, item a, subsection 1:<blockquote>Contracts that may require the City to expend $500,000 or more or sell personal property worth $500,000 or more, and amendments which cause the total contract to exceed that amount</blockquote>'''The contract was for $498,500, not $500,000.''' However, the Denver Purchasing Manual says the following on page 13:<ref>[https://www.denvergov.org/content/dam/denvergov/Portals/573/documents/Purchasing%20Policy%20Manual%2009202017.pdf Denver Purchasing Policy Manual], Page 13, September 20, 2017</ref><blockquote>''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''</blockquote>

====Colorado statutes====

*'''C.R.S. § 18-8-404'''<ref>[https://colorado.public.law/statutes/crs_18-8-404 C.R.S. § 18-8-404 - First-degree official misconduct], Colorado Public Law</ref>, First-degree official misconduct: '''''a public servant commits misconduct if, with intent to obtain a benefit, they violate any statute or lawfully adopted rule relating to their office (Class 1 misdemeanor)'''''

=====What's a "benefit"?=====
A benefit isn't just a bag of cash under the table.

The definition of "benefit" is found in '''Colorado Revised Statutes § 18-1-901(3)(b)'''<ref>[https://law.justia.com/codes/colorado/title-18/article-1/part-9/section-18-1-901/ C.R.S. § 18-1-901 - Definitions], Justia Law</ref>,<blockquote>''"(b) "Benefit" means any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''</blockquote>Section 18-1-901 contains general definitions that apply throughout Title 18 (Colorado Criminal Code), including the offenses in Article 8 (Governmental Operations).

The definition is broad and includes:

#'''Any gain or advantage''', which is not limited to money or personal enrichment
#'''Benefits to other people''' if the defendant wanted them to benefit
#'''Policy outcomes''', getting a governmental result the mayor wants
#'''Avoiding negative consequences''' like bypassing rejection

This is way broader than ''"personal financial enrichment."'' If Mayor Johnston saw getting the Flock contract approved as advantageous, that qualifies as a "benefit."
----

=====Case Law: People v. Luttrell=====
'''People v. Luttrell, 636 P.2d 712 (Colo. 1981)'''<ref>[https://law.justia.com/cases/colorado/supreme-court/1981/80sa478-0.html People v. Luttrell, 636 P.2d 712 (Colo. 1981)], Colorado Supreme Court</ref><blockquote>"Intent may be inferred. Intent to commit embezzlement of public property, official misconduct, and theft may be inferred from the defendants' conduct and the circumstances of the case"<ref>[https://law.justia.com/codes/colorado/2021/title-18/article-8/part-4/section-18-8-407/ Annotations to C.R.S. § 18-8-404], Justia Law</ref></blockquote>Direct evidence such as an email from the mayor saying "I'm doing this to avoid council approval" might not be necessary. It could be possible to prove criminal intent by inferring via the existing details.

*The timing of actions, 63 days after 12-0 vote rejecting Flock contract
*The specificity of the contract amount, which is 0.3% under the legal limit
*Surrounding circumstances, same vendor and same service, just repriced

=====This doesn't have to be a bribe; read "pecuniary benefit"=====
For comparison, Colorado law distinguishes between '''''"benefit"''''' and '''''"pecuniary benefit"'''''.

'''C.R.S. § 18-1-901(3)(m)''' "Pecuniary benefit" means benefit in the form of money, property, commercial interests, or anything else, the primary significance of which is economic gain.

The statute uses "pecuniary benefit" when it means financial enrichment specifically. The fact that § 18-8-404 uses just "benefit" (not "pecuniary benefit") proves our point that the legislature wanted a broader meaning of the word "benefit" in this context.

=====How it can apply to the mayor=====
Under the verified statutory definition, a mayor obtains a "benefit" by:

#'''policy benefit:''' he implemented his surveillance camera policy that he believed is necessary
#'''political benefit:''' avoided the political cost of removing operational cameras
#'''institutional benefit:''' expanding executive authority over public safety
#'''3rd benefit:''' Flock keeps getting Denver taxpayer money without consent

'''NONE OF THIS REQUIRES PERSONAL FINANCIAL ENRICHMENT TO BE AGAINST THE LAW!''' The "gain or advantage" is getting the contract approved after City Council rejected it.

==WHAT YOU NEED TO DO!==
We have to make it legally and politically untenable for the mayor to continue with his actions to extend the Flock contract past October 31st 2025. Help with the following:

===1) File complaints===

====Attorney General complaint====

*[https://coag.gov/file-complaint/ Click here to file a complaint with the Colorado Attorney General (Phil Weiser)]. Choose '''"Deprivation of Rights by a Governmental Authority":''' Allege contract-splitting to evade oversight (C.R.S. § 31-15-712) and official misconduct (C.R.S. § 18-8-404), citing:
**The Council's 12-0 rejection of the $666,000 extension on May 5<ref>[https://www.denver7.com/news/local-news/denver-city-council-rejects-contract-expansion-for-license-plate-recognition-cameras-in-the-city Denver City Council rejects contract expansion for license plate recognition cameras], Denver7, May 5, 2025</ref>
**The $498,500 deal in July (exactly $1,500 under the threshold) and intent to evade Council
**1,400+ ICE searches of Denver data<ref>[https://coloradonewsline.com/2025/08/06/immigration-denver-flock-camera/ Federal immigration agents used Denver's Flock cameras 1,400 times], Colorado Newsline, August 6, 2025</ref> and potential conflict with state limits on sharing PII to aid immigration enforcement<ref>[https://leg.colorado.gov/publications/state-and-federal-immigration-laws State and Federal Immigration Laws], Colorado General Assembly</ref>

'''WHAT TO SAY:'''<blockquote>I am filing a formal complaint regarding Mayor Mike Johnston's violations of Colorado law. On May 5, 2025, Denver City Council [https://denver.granicus.com/player/clip/16871?view_id=21 unanimously rejected a Flock Safety camera contract], 12 no to 0 yes. 63 days later, Mayor Johnston signed a $498,500 contract with Flock which is exactly $1,500 below the $500,000 threshold requiring council approval under Denver Charter § 3.2.6.

This appears to be deliberate circumvention of required legislative oversight, violating C.R.S. § 18-8-404 (Official Misconduct). Additionally, this artificial division of a contract to evade approval requirements violates the Denver Purchasing Manual says the following on page 13:

''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''

"under C.R.S. § 18-1-901(3)(b), ''"benefit"'' means ''"any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''

Mayor Johnston obtained a benefit by successfully implementing a surveillance contract that city council had unanimously rejected 63 days earlier. Under People v. Luttrell, 636 P.2d 712 (Colo. 1981), intent can be inferred from conduct and circumstances. The precise pricing ''($498,500, which is 0.3% below the $500,000 threshold)'' and timing ''(immediately after rejection)'' demonstrate '''''knowing violation with intent to obtain the benefit of contract approval."'''''

I respectfully request your office:

#Investigate whether Mayor Johnston violated C.R.S. § 18-1-901(3)(b) and C.R.S. § 18-8-404
#Subpoena internal communications between the Mayor's office and Flock Safety regarding contract pricing and structuring
#Review whether the Mayor's office discussed the $500,000 threshold when structuring this deal
#Charge Mayor Johnston if the evidence supports criminal violations

Thank you for your attention to this matter.</blockquote>

====Denver District Attorney complaint====

*Submit directly to the Denver District Attorney alongside the AG filing.
**Website: [https://www.denverda.org/contact-us/ denverda.org/contact-us]
**Email: '''info@denverda.org'''
**Main line: '''720-913-9000''', Línea en Español '''720-913-9020''', Consumer Fraud Hotline '''720-913-9179'''
**"Report a Crime" page: [https://www.denverda.org/report-a-crime/ denverda.org/report-a-crime]
*Use the same "What to say" text above, tailored to request a criminal inquiry into official misconduct and threshold avoidance, and include your attachments.

===2) Denver Code of Ethics; DRMC §§ 2-51 (letter and spirit)===
The code requires acting within the letter and spirit of ethics rules and avoiding even the appearance of impropriety. Alleged end-run behavior can be challenged as violating §2-51's intent.

[https://www.denvergov.org/files/assets/public/v/2/board-of-ethics/documents/complaintform_boardofethics.pdf Click to file a complaint with the Denver Board of Ethics]: claim misuse of office by the mayor by circumventing Charter § 3.2.6 and violating the City Purchasing Manual (ban on artificially dividing to avoid Council review, manual p.13).

===3) SIGN UP TO SPEAK AT CITY COUNCIL GENERAL PUBLIC COMMENTS, IMMEDIATELY===
Tell the City Council on the record that you want this investigated, as they can pressure the district attorney. '''Sign up''' for the [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment Monday General Public Comment] which takes place at 5 PM, October 20th, 2025. Do it before 2 PM the day of.

Ask City Council to refer this matter to the auditor and district attorney, and to schedule an oversight hearing. [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment CLICK HERE FOR INSTRUCTIONS ON HOW TO SIGN UP!]

Ask City Council to introduce a pre-deadline resolution declaring any unilateral extension improper and demanding Council review for any surveillance-tech contract ''(example of this, New Orleans' tightening of oversight after a mayoral end-run)<ref>[https://thelensnola.org/2022/11/17/city-council-significantly-expands-approval-power-over-city-contracts/ City Council significantly expands approval power over city contracts], The Lens New Orleans, November 17, 2022</ref>''.

===4) FILE COLORADO OPEN RECORDS ACT REQUESTS===

While [https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance statements have been made by City Council members discussing the contract's improper extension], we're going to want the hard documents. That requires a request.

====How to Make a Colorado Open Records Request====

=====Step 1: visit the portal=====
Go to: https://www.denvergov.org/openrecords

=====Step 2: what departments to get records from=====

Submit '''SEPARATE''' requests to each department (increases chances of getting documents):

======Mayor's Office======
*'''Department:''' [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Mayors-Office/Contact Office of the Mayor]
*'''Records Custodian:''' Mayor's Office Communications
*'''Request:'''
**All contracts with Flock Safety executed July 2025
**All emails between Mayor's Office and Flock Safety (April 1 - July 31, 2025)
**All internal emails containing "Flock" AND "$500,000" or "threshold"
**Meeting calendars showing any Flock Safety meetings

======City Attorney's Office======
*'''Department:''' Denver City Attorney's Office
*'''Records Custodian:''' Legal Department
*'''Request:'''
**Legal review memos for Flock contract
**Emails regarding "contract structuring" or "council approval threshold"
**Any legal opinions on contracts under $500,000

======Department of Finance======
*'''Department:''' Department of Finance
*'''Records Custodian:''' Controller's Office
*'''Request:'''
**Purchase orders for Flock Safety
**Budget documents showing the $498,500 allocation
**Any procurement waivers or exemptions filed

======Denver City Council======
*'''Department:''' Denver City Council
*'''Records Custodian:''' Council Secretary
*'''Request:'''
**Complete minutes and vote record from May 5, 2025 meeting
**All council communications regarding Flock rejection
**Any subsequent communications from Mayor's office about Flock

=====Step 3: what to say=====

some ideas,<blockquote>"This request includes all responsive records in any format including:
*Emails (including attachments)
*Text messages
*Teams/Slack/Official work chat messages
*Handwritten notes
*Calendar entries
*Phone logs
*Draft documents

Search terms should include variations like:
*'Flock' OR 'ALPR' OR 'license plate reader'
*'$498' OR '$499' OR 'four hundred ninety'
*'threshold' OR 'limit' OR 'approval requirement'

Time period: April 1, 2025 through July 31, 2025"</blockquote>

=====Step 4: save yourswelf money=====

Add this to avoid fees:<blockquote>"I request a fee waiver as this information is in the public interest regarding potential circumvention of City Council authority. Disclosure will contribute significantly to public understanding of government operations."</blockquote>

=====Step 5: documents to focus on =====

#'''Contract Modification'''
#*Original $666,000 contract draft
#*Revised $498,500 or $499,000 contract
#*Change orders or amendments
#'''"Keep It Under" Emails'''
#*Search: "under 500" "below threshold" "avoid council"
#*Any email sent between May 6-July 6, 2025
#'''The Timeline Documents'''
#*May 5 council rejection documentation
#*July 7 contract execution
#*Any June communications showing planning

=====Step 6: Follow-up=====

*Should get acknowledgement in 1-3 days
*7 days for "extenuating circumstances"
*After 10 days, file a complaint if you get no response

=====Sample Request Text=====

<blockquote>Under the Colorado Open Records Act § 24-72-201 et seq., I request access to the following records:

All communications, contracts, and documents related to agreements with Flock Safety or regarding automated license plate readers (ALPR) between April 1, 2025 and July 31, 2025, specifically including:

#The executed contract for $498,500 signed in July 2025 according to [https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance statements by City Councilwoman Sarah Parady]
#Any prior contract drafts or proposals with different amounts
#All emails between city officials containing the terms "Flock", "498", "500", "threshold", or "council approval"
#Meeting notes or memos discussing contract structuring

This request is in the public interest as it concerns potential circumvention of democratic oversight. I request a fee waiver.

Please provide records electronically to [your email].</blockquote>

===5) PUBLIC PRESSURE!===
SHOW UP 6 PM TO A TOWN HALL THIS WEDNESDAY, OCTOBER 22ND, 6 PM, 2650 E 40th Ave, Denver, Colorado - BE THERE, I WILL BE!
[[File:Town Hall October 22nd 6 PM 2650 E 40th Ave, Denver, CO 80205.jpg|alt=Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205|thumb|Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205]]

==References==
<references />

Special event page:Forced installation of Flock cameras in Denver, Colorado

2025-10-19T22:39:19Z

Louis:

{{Alert|message = This is a special page dedicated to an upcoming event. It will be deleted once irrelevant, and is not representative of a typical wiki article.}}

=Holding Mayor Johnston accountable=
On May 5, 2025, the Denver City Council rejected a $666,000 two-year extension for flock ALPR cameras with a vote of 12-0.<ref>[https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/ Denver rejects Flock camera license plate readers], Denverite, May 5, 2025</ref> 63 days later, in July 2025, Mayor Mike Johnston signed a $498,500 contract with Flock which is $1,500 under the $500k approval threshold, keeping the cameras running through October 31, 2025. That maneuver and date range are documented by Axios<ref>[https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance License plate readers in Denver spark mass surveillance concerns], Axios Denver, September 2, 2025</ref> and the ACLU of Colorado.<ref>[https://www.aclu-co.org/press-releases/coalition-of-civil-rights-and-advocacy-organizations-deeply-concerned-about-use-of-flock-cameras-for-ice-surveillance/ Coalition Deeply Concerned About Use of Flock Cameras for ICE Surveillance], ACLU of Colorado</ref>
----

==What the law says:==

===Denver Charter and City procurement rules:===
City Council must approve contracts over $500,000 according to Charter § 3.2.6<ref>[https://www.denvergov.org/files/assets/public/v/1/clerk-and-recorder/documents/new-folder/charterbooks_print_eng_v2.pdf Denver Charter], Page 58, Section E</ref>. This is Page 58, section E:<blockquote>(E) Approval of certain contracts by Council. Contracts which will require or result in the payment or receipt by the City of one-half million dollars ($500,000.00) or more, and those in which personal property valued at one-half million dollars ($500,000.00) or more will be sold or transferred by or to the City, and those in which a provider of services to the City will receive a percentage of generated revenues, shall require the approval of the City Council acting by ordinance or resolution, prior to their execution by City officials</blockquote>Also refer to Denver's $500,000 City Council approval rule, memorandum 8A<ref>[https://www.denvergov.org/files/assets/public/v/1/executive-orders/documents/2025/xo8-memo-a-2025-final-10k-po-threshold-increasedatesign.pdf Executive Order 8, Memorandum A], Page 15, Section H</ref>. This is Page 15, section H City Council, #1, item a, subsection 1:<blockquote>Contracts that may require the City to expend $500,000 or more or sell personal property worth $500,000 or more, and amendments which cause the total contract to exceed that amount</blockquote>'''The contract was for $498,500, not $500,000.''' However, the Denver Purchasing Manual says the following on page 13:<ref>[https://www.denvergov.org/content/dam/denvergov/Portals/573/documents/Purchasing%20Policy%20Manual%2009202017.pdf Denver Purchasing Policy Manual], Page 13, September 20, 2017</ref><blockquote>''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''</blockquote>

====Colorado statutes====

*'''C.R.S. § 18-8-404'''<ref>[https://colorado.public.law/statutes/crs_18-8-404 C.R.S. § 18-8-404 - First-degree official misconduct], Colorado Public Law</ref>, First-degree official misconduct: '''''a public servant commits misconduct if, with intent to obtain a benefit, they violate any statute or lawfully adopted rule relating to their office (Class 1 misdemeanor)'''''

=====What's a "benefit"?=====
A benefit isn't just a bag of cash under the table.

The definition of "benefit" is found in '''Colorado Revised Statutes § 18-1-901(3)(b)'''<ref>[https://law.justia.com/codes/colorado/title-18/article-1/part-9/section-18-1-901/ C.R.S. § 18-1-901 - Definitions], Justia Law</ref>,<blockquote>''"(b) "Benefit" means any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''</blockquote>Section 18-1-901 contains general definitions that apply throughout Title 18 (Colorado Criminal Code), including the offenses in Article 8 (Governmental Operations).

The definition is broad and includes:

#'''Any gain or advantage''', which is not limited to money or personal enrichment
#'''Benefits to other people''' if the defendant wanted them to benefit
#'''Policy outcomes''', getting a governmental result the mayor wants
#'''Avoiding negative consequences''' like bypassing rejection

This is way broader than ''"personal financial enrichment."'' If Mayor Johnston saw getting the Flock contract approved as advantageous, that qualifies as a "benefit."
----

=====Case Law: People v. Luttrell=====
'''People v. Luttrell, 636 P.2d 712 (Colo. 1981)'''<ref>[https://law.justia.com/cases/colorado/supreme-court/1981/80sa478-0.html People v. Luttrell, 636 P.2d 712 (Colo. 1981)], Colorado Supreme Court</ref><blockquote>"Intent may be inferred. Intent to commit embezzlement of public property, official misconduct, and theft may be inferred from the defendants' conduct and the circumstances of the case"<ref>[https://law.justia.com/codes/colorado/2021/title-18/article-8/part-4/section-18-8-407/ Annotations to C.R.S. § 18-8-404], Justia Law</ref></blockquote>Direct evidence such as an email from the mayor saying "I'm doing this to avoid council approval" might not be necessary. It could be possible to prove criminal intent by inferring via the existing details.

*The timing of actions, 63 days after 12-0 vote rejecting Flock contract
*The specificity of the contract amount, which is 0.3% under the legal limit
*Surrounding circumstances, same vendor and same service, just repriced

=====This doesn't have to be a bribe; read "pecuniary benefit"=====
For comparison, Colorado law distinguishes between '''''"benefit"''''' and '''''"pecuniary benefit"'''''.

'''C.R.S. § 18-1-901(3)(m)''' "Pecuniary benefit" means benefit in the form of money, property, commercial interests, or anything else, the primary significance of which is economic gain.

The statute uses "pecuniary benefit" when it means financial enrichment specifically. The fact that § 18-8-404 uses just "benefit" (not "pecuniary benefit") proves our point that the legislature wanted a broader meaning of the word "benefit" in this context.

=====How it can apply to the mayor=====
Under the verified statutory definition, a mayor obtains a "benefit" by:

#'''policy benefit:''' he implemented his surveillance camera policy that he believed is necessary
#'''political benefit:''' avoided the political cost of removing operational cameras
#'''institutional benefit:''' expanding executive authority over public safety
#'''3rd benefit:''' Flock keeps getting Denver taxpayer money without consent

'''NONE OF THIS REQUIRES PERSONAL FINANCIAL ENRICHMENT TO BE AGAINST THE LAW!''' The "gain or advantage" is getting the contract approved after City Council rejected it.

==WHAT YOU NEED TO DO!==
We have to make it legally and politically untenable for the mayor to continue with his actions to extend the Flock contract past October 31st 2025. Help with the following:

===1) File complaints===

====Attorney General complaint====

*[https://coag.gov/file-complaint/ Click here to file a complaint with the Colorado Attorney General (Phil Weiser)]. Choose '''"Deprivation of Rights by a Governmental Authority":''' Allege contract-splitting to evade oversight (C.R.S. § 31-15-712) and official misconduct (C.R.S. § 18-8-404), citing:
**The Council's 12-0 rejection of the $666,000 extension on May 5<ref>[https://www.denver7.com/news/local-news/denver-city-council-rejects-contract-expansion-for-license-plate-recognition-cameras-in-the-city Denver City Council rejects contract expansion for license plate recognition cameras], Denver7, May 5, 2025</ref>
**The $498,500 deal in July (exactly $1,500 under the threshold) and intent to evade Council
**1,400+ ICE searches of Denver data<ref>[https://coloradonewsline.com/2025/08/06/immigration-denver-flock-camera/ Federal immigration agents used Denver's Flock cameras 1,400 times], Colorado Newsline, August 6, 2025</ref> and potential conflict with state limits on sharing PII to aid immigration enforcement<ref>[https://leg.colorado.gov/publications/state-and-federal-immigration-laws State and Federal Immigration Laws], Colorado General Assembly</ref>

'''WHAT TO SAY:'''<blockquote>I am filing a formal complaint regarding Mayor Mike Johnston's violations of Colorado law. On May 5, 2025, Denver City Council [https://denver.granicus.com/player/clip/16871?view_id=21 unanimously rejected a Flock Safety camera contract], 12 no to 0 yes. 63 days later, Mayor Johnston signed a $498,500 contract with Flock which is exactly $1,500 below the $500,000 threshold requiring council approval under Denver Charter § 3.2.6.

This appears to be deliberate circumvention of required legislative oversight, violating C.R.S. § 18-8-404 (Official Misconduct). Additionally, this artificial division of a contract to evade approval requirements violates the Denver Purchasing Manual says the following on page 13:

''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''

"under C.R.S. § 18-1-901(3)(b), ''"benefit"'' means ''"any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''

Mayor Johnston obtained a benefit by successfully implementing a surveillance contract that city council had unanimously rejected 63 days earlier. Under People v. Luttrell, 636 P.2d 712 (Colo. 1981), intent can be inferred from conduct and circumstances. The precise pricing ''($498,500, which is 0.3% below the $500,000 threshold)'' and timing ''(immediately after rejection)'' demonstrate '''''knowing violation with intent to obtain the benefit of contract approval."'''''

I respectfully request your office:

#Investigate whether Mayor Johnston violated C.R.S. § 18-1-901(3)(b) and C.R.S. § 18-8-404
#Subpoena internal communications between the Mayor's office and Flock Safety regarding contract pricing and structuring
#Review whether the Mayor's office discussed the $500,000 threshold when structuring this deal
#Charge Mayor Johnston if the evidence supports criminal violations

Thank you for your attention to this matter.</blockquote>

====Denver District Attorney complaint====

*Submit directly to the Denver District Attorney alongside the AG filing.
**Website: [https://www.denverda.org/contact-us/ denverda.org/contact-us]
**Email: '''info@denverda.org'''
**Main line: '''720-913-9000''', Línea en Español '''720-913-9020''', Consumer Fraud Hotline '''720-913-9179'''
**"Report a Crime" page: [https://www.denverda.org/report-a-crime/ denverda.org/report-a-crime]
*Use the same "What to say" text above, tailored to request a criminal inquiry into official misconduct and threshold avoidance, and include your attachments.

===2) Denver Code of Ethics; DRMC §§ 2-51 (letter and spirit)===
The code requires acting within the letter and spirit of ethics rules and avoiding even the appearance of impropriety. Alleged end-run behavior can be challenged as violating §2-51's intent.

[https://www.denvergov.org/files/assets/public/v/2/board-of-ethics/documents/complaintform_boardofethics.pdf Click to file a complaint with the Denver Board of Ethics]: claim misuse of office by the mayor by circumventing Charter § 3.2.6 and violating the City Purchasing Manual (ban on artificially dividing to avoid Council review, manual p.13).

===3) SIGN UP TO SPEAK AT CITY COUNCIL GENERAL PUBLIC COMMENTS, IMMEDIATELY===
Tell the City Council on the record that you want this investigated, as they can pressure the district attorney. '''Sign up''' for the [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment Monday General Public Comment] which takes place at 5 PM, October 20th, 2025. Do it before 2 PM the day of.

Ask City Council to refer this matter to the auditor and district attorney, and to schedule an oversight hearing. [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment CLICK HERE FOR INSTRUCTIONS ON HOW TO SIGN UP!]

Ask City Council to introduce a pre-deadline resolution declaring any unilateral extension improper and demanding Council review for any surveillance-tech contract ''(example of this, New Orleans' tightening of oversight after a mayoral end-run)<ref>[https://thelensnola.org/2022/11/17/city-council-significantly-expands-approval-power-over-city-contracts/ City Council significantly expands approval power over city contracts], The Lens New Orleans, November 17, 2022</ref>''.

===4) PUBLIC PRESSURE!===
SHOW UP 6 PM TO A TOWN HALL THIS WEDNESDAY, OCTOBER 22ND, 6 PM, 2650 E 40th Ave, Denver, Colorado - BE THERE, I WILL BE!
[[File:Town Hall October 22nd 6 PM 2650 E 40th Ave, Denver, CO 80205.jpg|alt=Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205|thumb|Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205]]

==References==
<references />

Special event page:Forced installation of Flock cameras in Denver, Colorado

2025-10-19T21:22:54Z

Louis: Protected "Forced installation of Flock cameras in Denver, Colorado" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

=holding mayor johnston accountable=
On May 5, 2025, the Denver City Council rejected a $666,000 two-year extension for flock ALPR cameras with a vote of 12-0.<ref>[https://denverite.com/2025/05/05/denver-rejects-flock-camera-license-plate-readers/ Denver rejects Flock camera license plate readers], Denverite, May 5, 2025</ref> 63 days later, in July 2025, Mayor Mike Johnston signed a $498,500 contract with Flock which is $1,500 under the $500k approval threshold, keeping the cameras running through October 31, 2025. That maneuver and date range are documented by Axios<ref>[https://www.axios.com/local/denver/2025/09/02/license-plate-denver-readers-mass-surveillance License plate readers in Denver spark mass surveillance concerns], Axios Denver, September 2, 2025</ref> and the ACLU of Colorado.<ref>[https://www.aclu-co.org/press-releases/coalition-of-civil-rights-and-advocacy-organizations-deeply-concerned-about-use-of-flock-cameras-for-ice-surveillance/ Coalition Deeply Concerned About Use of Flock Cameras for ICE Surveillance], ACLU of Colorado</ref>
----

==What the law says:==

===Denver Charter and City procurement rules:===
City Council must approve contracts over $500,000 according to Charter § 3.2.6<ref>[https://www.denvergov.org/files/assets/public/v/1/clerk-and-recorder/documents/new-folder/charterbooks_print_eng_v2.pdf Denver Charter], Page 58, Section E</ref>. This is Page 58, section E:<blockquote>(E) Approval of certain contracts by Council. Contracts which will require or result in the payment or receipt by the City of one-half million dollars ($500,000.00) or more, and those in which personal property valued at one-half million dollars ($500,000.00) or more will be sold or transferred by or to the City, and those in which a provider of services to the City will receive a percentage of generated revenues, shall require the approval of the City Council acting by ordinance or resolution, prior to their execution by City officials</blockquote>Also refer to Denver's $500,000 City Council approval rule, memorandum 8A<ref>[https://www.denvergov.org/files/assets/public/v/1/executive-orders/documents/2025/xo8-memo-a-2025-final-10k-po-threshold-increasedatesign.pdf Executive Order 8, Memorandum A], Page 15, Section H</ref>. This is Page 15, section H City Council, #1, item a, subsection 1:<blockquote>Contracts that may require the City to expend $500,000 or more or sell personal property worth $500,000 or more, and amendments which cause the total contract to exceed that amount</blockquote>'''The contract was for $498,500, not $500,000.''' However, the Denver Purchasing Manual says the following on page 13:<ref>[https://www.denvergov.org/content/dam/denvergov/Portals/573/documents/Purchasing%20Policy%20Manual%2009202017.pdf Denver Purchasing Policy Manual], Page 13, September 20, 2017</ref><blockquote>''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''</blockquote>

====Colorado statutes====

*'''C.R.S. § 18-8-404'''<ref>[https://colorado.public.law/statutes/crs_18-8-404 C.R.S. § 18-8-404 - First-degree official misconduct], Colorado Public Law</ref>, First-degree official misconduct: '''''a public servant commits misconduct if, with intent to obtain a benefit, they violate any statute or lawfully adopted rule relating to their office (Class 1 misdemeanor)'''''

=====what's a "benefit"?=====
A benefit isn't just a bag of cash under the table.

The definition of "benefit" is found in '''Colorado Revised Statutes § 18-1-901(3)(b)'''<ref>[https://law.justia.com/codes/colorado/title-18/article-1/part-9/section-18-1-901/ C.R.S. § 18-1-901 - Definitions], Justia Law</ref>,<blockquote>''"(b) "Benefit" means any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''</blockquote>Section 18-1-901 contains general definitions that apply throughout Title 18 (Colorado Criminal Code), including the offenses in Article 8 (Governmental Operations).

The definition is broad and includes:

#'''Any gain or advantage''', which is not limited to money or personal enrichment
#'''Benefits to other people''' if the defendant wanted them to benefit
#'''Policy outcomes''', getting a governmental result the mayor wants
#'''Avoiding negative consequences''' like bypassing rejection

This is way broader than ''"personal financial enrichment."'' If Mayor Johnston saw getting the Flock contract approved as advantageous, that qualifies as a "benefit."
----

=====Case Law: People v. Luttrell=====
'''People v. Luttrell, 636 P.2d 712 (Colo. 1981)'''<ref>[https://law.justia.com/cases/colorado/supreme-court/1981/80sa478-0.html People v. Luttrell, 636 P.2d 712 (Colo. 1981)], Colorado Supreme Court</ref><blockquote>"Intent may be inferred. Intent to commit embezzlement of public property, official misconduct, and theft may be inferred from the defendants' conduct and the circumstances of the case"<ref>[https://law.justia.com/codes/colorado/2021/title-18/article-8/part-4/section-18-8-407/ Annotations to C.R.S. § 18-8-404], Justia Law</ref></blockquote>Direct evidence such as an email from the mayor saying "I'm doing this to avoid council approval" might not be necessary. It could be possible to prove criminal intent by inferring via the existing details.

*The timing of actions, 63 days after 12-0 vote rejecting Flock contract
*The specificity of the contract amount, which is 0.3% under the legal limit
*Surrounding circumstances, same vendor and same service, just repriced

=====This doesn't have to be a bribe; read "pecuniary benefit"=====
For comparison, Colorado law distinguishes between '''''"benefit"''''' and '''''"pecuniary benefit"'''''.

'''C.R.S. § 18-1-901(3)(m)''' "Pecuniary benefit" means benefit in the form of money, property, commercial interests, or anything else, the primary significance of which is economic gain.

The statute uses "pecuniary benefit" when it means financial enrichment specifically. The fact that § 18-8-404 uses just "benefit" (not "pecuniary benefit") proves our point that the legislature wanted a broader meaning of the word "benefit" in this context.

=====how it applies to mayor johnston=====
Under the verified statutory definition, Mayor Johnston obtained a "benefit" by:

#'''policy benefit:''' he implemented his surveillance camera policy that he believed is necessary
#'''political benefit:''' avoided the political cost of removing operational cameras
#'''institutional benefit:''' expanding executive authority over public safety
#'''3rd benefit:''' Flock keeps getting Denver taxpayer money without consent

'''NONE OF THIS REQUIRES PERSONAL FINANCIAL ENRICHMENT TO BE AGAINST THE LAW!''' The "gain or advantage" is getting the contract approved after City Council rejected it.

==WHAT YOU NEED TO DO!==
We have to make it legally and politically untenable for the mayor to continue with his actions to extend the Flock contract past October 31st 2025. Help with the following:

===1) file complaints===

====attorney general complaint====

*[https://coag.gov/file-complaint/ Click here to file a complaint with the Colorado Attorney General (Phil Weiser)]. Choose '''"Deprivation of Rights by a Governmental Authority":''' Allege contract-splitting to evade oversight (C.R.S. § 31-15-712) and official misconduct (C.R.S. § 18-8-404), citing:
**The Council's 12-0 rejection of the $666,000 extension on May 5<ref>[https://www.denver7.com/news/local-news/denver-city-council-rejects-contract-expansion-for-license-plate-recognition-cameras-in-the-city Denver City Council rejects contract expansion for license plate recognition cameras], Denver7, May 5, 2025</ref>
**The $498,500 deal in July (exactly $1,500 under the threshold) and intent to evade Council
**1,400+ ICE searches of Denver data<ref>[https://coloradonewsline.com/2025/08/06/immigration-denver-flock-camera/ Federal immigration agents used Denver's Flock cameras 1,400 times], Colorado Newsline, August 6, 2025</ref> and potential conflict with state limits on sharing PII to aid immigration enforcement<ref>[https://leg.colorado.gov/publications/state-and-federal-immigration-laws State and Federal Immigration Laws], Colorado General Assembly</ref>

'''WHAT TO SAY:'''<blockquote>I am filing a formal complaint regarding Mayor Mike Johnston's violations of Colorado law. On May 5, 2025, Denver City Council [https://denver.granicus.com/player/clip/16871?view_id=21 unanimously rejected a Flock Safety camera contract], 12 no to 0 yes. 63 days later, Mayor Johnston signed a $498,500 contract with Flock which is exactly $1,500 below the $500,000 threshold requiring council approval under Denver Charter § 3.2.6.

This appears to be deliberate circumvention of required legislative oversight, violating C.R.S. § 18-8-404 (Official Misconduct). Additionally, this artificial division of a contract to evade approval requirements violates the Denver Purchasing Manual says the following on page 13:

''"Buyers shall be diligent in preventing agency avoidance of the formal or informal bid thresholds or City Council required ordinance thresholds by artificially dividing requisitions to avoid any procurement regulations described in Article 20-64 of the Revised Municipal Code."''

"under C.R.S. § 18-1-901(3)(b), ''"benefit"'' means ''"any gain or advantage to the beneficiary including any gain or advantage to another person pursuant to the desire or consent of the beneficiary."''

mayor johnston obtained a benefit by successfully implementing a surveillance contract that city council had unanimously rejected 63 days earlier. Under People v. Luttrell, 636 P.2d 712 (Colo. 1981), intent can be inferred from conduct and circumstances. The precise pricing ''($498,500, which is 0.3% below the $500,000 threshold)'' and timing ''(immediately after rejection)'' demonstrate '''''knowing violation with intent to obtain the benefit of contract approval."'''''

I respectfully request your office:

#Investigate whether Mayor Johnston violated C.R.S. § 18-1-901(3)(b) and C.R.S. § 18-8-404
#Subpoena internal communications between the Mayor's office and Flock Safety regarding contract pricing and structuring
#Review whether the Mayor's office discussed the $500,000 threshold when structuring this deal
#Charge Mayor Johnston if the evidence supports criminal violations

Thank you for your attention to this matter.</blockquote>

====denver district attorney complaint====

*Submit directly to the Denver District Attorney alongside the AG filing.
**Website: [https://www.denverda.org/contact-us/ denverda.org/contact-us]
**Email: '''info@denverda.org'''
**Main line: '''720-913-9000''', Línea en Español '''720-913-9020''', Consumer Fraud Hotline '''720-913-9179'''
**"Report a Crime" page: [https://www.denverda.org/report-a-crime/ denverda.org/report-a-crime]
*Use the same "What to say" text above, tailored to request a criminal inquiry into official misconduct and threshold avoidance, and include your attachments.

===2) Denver Code of Ethics; DRMC §§ 2-51 (letter and spirit)===
The code requires acting within the letter and spirit of ethics rules and avoiding even the appearance of impropriety. Alleged end-run behavior can be challenged as violating §2-51's intent.

[https://www.denvergov.org/files/assets/public/v/2/board-of-ethics/documents/complaintform_boardofethics.pdf Click to file a complaint with the Denver Board of Ethics]: claim misuse of office by the mayor by circumventing Charter § 3.2.6 and violating the City Purchasing Manual (ban on artificially dividing to avoid Council review, manual p.13).

===3) SIGN UP TO SPEAK AT CITY COUNCIL GENERAL PUBLIC COMMENTS, IMMEDIATELY===
Tell City Council on the record that you want this investigated, as they can pressure the district attorney. '''Sign up''' for the [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment Monday General Public Comment] which takes place at 5 PM, October 20th, 2025. Do it before 2 PM the day of.

Ask City Council to refer this matter to the auditor and district attorney, and to schedule an oversight hearing. [https://www.denvergov.org/Government/Agencies-Departments-Offices/Agencies-Departments-Offices-Directory/Denver-City-Council/Public-Input/General-Public-Comment CLICK HERE FOR INSTRUCTIONS ON HOW TO SIGN UP!]

Ask City Council to introduce a pre-deadline resolution declaring any unilateral extension improper and demanding Council review for any surveillance-tech contract ''(example of this, New Orleans' tightening of oversight after a mayoral end-run)<ref>[https://thelensnola.org/2022/11/17/city-council-significantly-expands-approval-power-over-city-contracts/ City Council significantly expands approval power over city contracts], The Lens New Orleans, November 17, 2022</ref>''.

===4) PUBLIC PRESSURE!===
SHOW UP 6 PM TO A TOWN HALL THIS WEDNESDAY, OCTOBER 22ND, 6 PM, 2650 E 40th Ave, Denver, Colorado - BE THERE, I WILL BE!
[[File:Town Hall October 22nd 6 PM 2650 E 40th Ave, Denver, CO 80205.jpg|alt=Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205|thumb|Town Hall at October 22nd, 6 PM, 2650 E 40th Ave, Denver, CO 80205]]

==References==
<references />