The Flock Was Startled

Leave a comment

Pressure has been mounting on Flock Safety concerning it’s Automated License Plate Reader system. It’s widespread adoption across the United States has reached a level of public awareness and pushback that led the Georgia-based company to release an “update” to it’s policies, dated August 13, 2026. The cat of 24/7 surveillance and abuse by law enforcement officials is out of the bag, and it has startled the flock. Here are some highlights to it’s new policies, and some comments. (See the list at the end of this blog for all of the articles I’ve posted on the Flock system.)

Privacy

When we started Flock 9 years ago, we set the default ALPR retention period to 30 days, unless state or local policy decided on a shorter or longer period. We believed this struck a careful balance between safety and privacy. 

Today, we are updating our recommendation and default to a 7-day retention, and introducing “Evidence Mode.” Our analysis shows that over 90% of searches without a full plate are done within a week. Evidence Mode, which will roll out in the coming weeks, addresses the exceptional cases that take longer: detectives can preserve specific ALPR data as evidence for an active investigation in cold storage, consistent with existing laws and policies.

“Recommendation and default” to 7-day retention. That doesn’t indicate that the customer agency can’t choose the 30-day and ignore the 7-day option. I suspect many agencies will opt for the 30-day setting. The “evidence mode” will probably be useful in ongoing cases.

Existing customers will keep their current, democratically approved retention periods. Customers who adopt the 7-day recommendation will receive Evidence Mode at no cost. Every community will continue to choose the retention period that fits its public safety strategy.

So this means every agency already using the Flock Automated License Plate Reader system (currently at more than 5,000 agencies, according to Flock) will continue with the 30-day data retention plan. Only new customers will have operate under the new “option” to only keep data for 7 days. Shall we take a wild guess at how many will opt for something other than the “default” suggestion?

And that “democratically approved” line is an attempt to mask that most agencies received approval from their city councils or county board of supervisors in the “consent calendar” agenda. That usually means no public discussion by the body, and the only members of the public that knew about it were those who bother to read the consent calendar and it’s agenda packets. Most communities never realized their leaders had bought (leased, actually) the system until problems started hitting the press. That’s how the Visalia, Porterville, and Farmersville city councils approved the contracts. The police departments asked, the cities put the items on the consent agendas, and they were approved with no discussion.

We are also introducing Offense filtering for sharing. Now, cities can choose which type of offenses are permissible for other agencies to access their cameras. For example, City A could allow City B to search its cameras only for a stolen vehicle, missing person, or violent crime while blocking searches related to immigration enforcement. This gives communities more control over data sharing while preserving collaboration where policies align.

This will require agencies to use the exact same codes for access to data from another agency. Computers are notoriously literal-minded, and see ‘INVESTIGATION’ as a different code than ‘investigation’. The California code for stolen vehicle is ‘10851’. If it’s entered as ‘stolen vehicle’, that’s a different offense as far as the computer is concerned. Most agencies will likely not activate ‘Offense filtering’, and just let other agencies have access. I suspect few will institute this option.

Accountability

Abuse of Flock technology, at any level, is unacceptable. We have strengthened safeguards over the past nine years, from basic audit logs to proactive monitoring. 16 weeks ago, we introduced Audit Assistance, which detects abnormal activity and flags it for Administrator review. In recent weeks, those reviews have been associated with arrests of several law enforcement officers who allegedly abused the system. More than one-third of our customers have voluntarily adopted Audit Assistance

Just now they’re instituting more robust methods of detecting unauthorized abuse. Most past abuses have been brought to light by news media or citizen auditing of access logs, not by the departments involved themselves.

We will now require all law enforcement customers to adopt this feature by the end of this year. In addition, we will institute proactive lockout. When a user’s activity meets defined criteria for abnormal behavior, Flock will automatically suspend access pending administrator review. The goal is to intervene before misuse becomes recurring or widespread.

They’re going to take three months to institute these procedures, while current abuse goes unchecked.

In July 2025, we introduced an optional case code requirement for searches. Results from participating agencies have been promising, so we will now require case codes for all law enforcement searches by the end of the year. Agencies may bypass the requirement in emergencies, but every exigent search will be flagged for administrator review.

Only a year ago did they introduce an “optional” requirement that searches be tied to a specific case number. This allowed agencies to ‘opt out’ (or just never ‘opt in’) to this, resulting in searches listed as “investigation”, “stolen”, or “theft”. A case number should always have been required.

Data Ownership

From the beginning, we have been clear that our customers own the data captured by their ALPR cameras. This has always been the case, but some of our contractual language has confused the public on this crucial point. To make that commitment easier to understand, next week we will publish an easy to read / plain English explanation of our contract on our website, organized section by section. The principle is simple: customers own the data, decide who can access it, and choose who they share it with

The contract signed by the City of Visalia states, in three places, that data generated by the Flock cameras utilized by the Visalia Police Department is owned by the city, and will not be sold to other parties. The same contract also says:

  1. DATA USE AND LICENSING
    4.1 Customer Data. As between Flock and Customer, all right, title and interest in the Customer Data, belong to and are retained solely by Customer. Customer hereby grants to Flock a limited, non-exclusive, royalty-free, irrevocable, worldwide license to use the Customer Data and perform all acts as may be necessary for Flock to provide the Flock Services to Customer. Flock does not own and shall not sell Customer Data
    .
  • 4.2 Customer grants Flock a non-exclusive, irrevocable, worldwide, royalty-free, license to use the Customer Generated Data for the purpose of providing Flock Services. Flock does not own and shall not sell Customer Generated Data.
  • 4.3 Anonymized Data. Flock shall have the right to collect, analyze, and anonymize Customer Data and Customer Generated Data to the extent such anonymization renders the data nonidentifiable to create Anonymized Data to use and perform the Services and related systems and technologies, including the training of machine learning algorithms. Customer hereby grants Flock a non-exclusive, worldwide, perpetual, royalty-free right to use and distribute such Anonymized Data to improve and enhance the Services and for other development, diagnostic and corrective purposes, and other Flock offerings. Parties understand that the aforementioned license is required for continuity of Services. Flock does not own and shall not sell Anonymized Data.

They claim “some of their contractual language has confused the public”, and they’re going to release a “plain English” explanation of their contracts. There contracts also say this:

  1. MISCELLANEOUS
    11.1 Compliance With Laws. Parties shall comply with all applicable local, state and federal laws, regulations, policies and ordinances and their associated record retention schedules, including responding to any subpoena request(s).

Maybe I’m “confused”, but that reads to me that they’ll give up those data files to anyone with a subpoena. I’m not confident Flock will stand up to an “administrative subpoena” issued by ICE or DHS. We’ll see what the “plain English” notice says. I’m also wondering about their 3-times repeated comment that Flock does not own and will not sell customer data. They won’t sell it, but does saying the agency owns it’s data mean that Flock, while it won’t ‘sell’ it, can give it away? Like to AI training? (That is a term in the contract. They’ll use “anonymized” data to train “machine learning algorithms”. Who else?)

There’s been a growing pushback against Flock for several years, and it’s reached a tipping point. They’re now adjusting their contracts and attempting to make “options” look like the operating standards. The 7-day retention is a choice, not a requirement, as some media sources are reporting. New contracts can still opt for the 30-day retention, and existing users don’t have to change, either.

This action by Flock is much like that line from Macbeth, “Told by an idiot, full of sound and fury, signifying nothing”. It is doubtful most agencies will lock themselves into 7-day time frames unless their controlling governments force it upon them. On their own, they’ll opt for the 30-day, and possibly longer, if that option is afforded to them. I don’t mean that as a slam, but it would be organizationally logical to take advantage of the abilities presented.

The real problem is the warrantless dragnet collection of data on citizens in every community with these cameras (of whatever brand, it’s not just Flock). Courts are finding similar mass data-gathering to be in violation of the 4th Amendment, and eventually one will make it to the Supreme Court of the United States dealing with license plate readers. While Flock and others insist there is no facial recognition capability, it’s only a matter of time and software development. The cameras are already technologically advanced to provide that data, it just has to be programmed. It’s just a matter of time.

Here are my previous Flock-related posts:

Another Flock of Cameras in Visalia

Leave a comment

On July 14, 2026, I made the following Public Records Act request of the City of Visalia, and the Visalia Police Department:

Pursuant to the California Public Records Act (CPRA), California Government Code § 7920.000 et seq., I am writing to request copies of public records held by the City of Visalia and the Visalia Police Department (VPD) regarding the integration, access, sharing, or use of Automated License Plate Reader (ALPR) systems owned, operated, or deployed by certain private-sector entities.

Specifically, I request copies of all records, regardless of physical form or characteristics, from January 1, 2023, to the present, relating to the following three categories of private ALPR deployment:

1. Visalia Economic Development Corporation (VEDC) ALPR Systems

Agreements and Authorizations: Any Memorandums of Understanding (MOUs), contracts, operational agreements, data-sharing agreements, or software integration permissions allowing the Visalia Police Department (VPD) to access, receive, search, or query ALPR data, logs, “hot lists,” or real-time alerts generated by cameras owned, leased, or managed by the VEDC (including those deployed in the Visalia Industrial Park).

Correspondence: All correspondence (including emails, text messages, and written memos) between the City of Visalia officials, staff, or representatives, VPD personnel and representatives, contractors, or board members of the VEDC (including but not limited to Executive Director Bruce Nicotero) regarding the installation, funding, maintenance, or law enforcement usage of VEDC-managed ALPR cameras.

Locations: Physical location of all cameras to which VPD has been granted access.

2. Home Depot Corporation ALPR Systems

Data-Sharing & Integration: Any agreements, MOUs, API integration credentials, or authorizations (via third-party platforms such as Flock Safety, Vigilant Solutions, or similar vendors) enabling VPD to query or receive automatic alerts from ALPR/surveillance systems operating at or around the Visalia Home Depot location (located at 3500 W. Orchard Ave.).

Correspondence: All communications between City staff or VPD personnel and Home Depot corporate security, store management, or representing investigators concerning ALPR data access, direct feeds, or digital “hot list” coordination.

3. Lowe’s Corporation ALPR Systems

Data-Sharing & Integration: Any agreements, MOUs, API integration credentials, or authorizations enabling VPD to query or receive automatic alerts from ALPR/surveillance systems operating at or around the Visalia Lowe’s locations (located at 1400 S. Demaree St. and 3020 N. Demaree St.).

Correspondence: All communications between City Staff, VPD personnel, and Lowe’s corporate security, store management, or representing investigators concerning ALPR data access, direct feeds, or digital “hot list” coordination.

Format of Records: I request that these records be provided in their original electronic format (e.g., PDF, Excel, .msg, or .eml) to avoid unnecessary printing costs and to preserve metadata.

Fee Waiver/Limitation: If there are any administrative fees associated with searching or duplicating these records, please notify me before they are incurred. (As these records concern public safety technology oversight and civil liberties, they are in the public interest, and I request a waiver of any fees).

Severability and Redactions: If the City determines that certain portions of the requested records are exempt from disclosure (such as specific law enforcement investigative techniques under Gov. Code § 7923.600), please disclose all reasonably segregable, non-exempt portions of the records with appropriate redactions, accompanied by a written explanation citing the specific statutory exemption.

As provided by Government Code § 7922.535, I look forward to receiving your determination on this request within 10 days of receipt.

On July 28, 2026, I received this notice (a bit past their ten-day required response window):

To whom it may concern:

The Visalia Police Department is diligently working on your request. Per Government Code 7922.535(b) we will be utilizing the fourteen-day extension to fulfill your request. Thank you for your patience.

July 28, 2026, 4:42pm by Staff

Today, August 10, 2026, I received this email:

They’re still looking, by golly!

Lowe’s shopping center, on South Mooney Blvd, Visalia. Image from Deflock.org.

Lowe’s Shopping center, Riggin and Demaree, Visalia. Image from Deflock.org.

I don’t know if the Visalia Home Depot has cameras, but I’ve read they grant law enforcement access to those they do have, so I want to see if there’s an agreement with Home Depot about it.

More tick tock tick Flock.

As is my practice, here are the previous blog posts about Flock Automated License Plate Readers in Visalia, California.

  1. What the Flock?
  2. Well, Flock Me!
  3. More Flock, more fun
  4. Flock you later
  5. Flock the Lawyers
  6. Flock Me A Little Bit
  7. Tick tock tick Flock
  8. The Final Flock – and the answer is “NO”
  9. Hidden in the Flock
  10. Reason me this, Flock
  11. Flock Me – Round 2

“Reason” me this, Flock

Leave a comment

Cartoon image by Gemini AI

In June of 2026, Visalia Police Department decided they no longer wanted the public to know why they were accessing the Flock Automated License Plate Reader system.

Let’s look at Visalia PD’s “Transparency Page” .CSV file for two different 30 day periods this year. Here’s the one starting on May 5, 2026, which contains the “reason” field in the log.

From the left to the right, we see the following ; an ID number, apparently coded. The “user ID” is merely asterisks. No public idea who is accessing the data. Next is the date and time, in “Zulu” time, which is UTC, which is Greenwich Mean Time. (London, England) Next is the number of “networks” being searched. I don’t know if this means number of cameras, or number of agencies, businesses, and organizations. The final field is “reason”. Each search of the database requires a reason for the search. They’ve told us each access requires a case number, but it’s never been listed on the public facing page. As it is, some of the “reason” entries are simply meaningless. More on that in a bit.

Now, starting sometime in June of 2026, VPD has removed the “reason” field from the file. I’m going to assume it’s visible on their side of the site (all of this stuff sits on Flock servers, requiring users to log in and access the information remotely), but we can no longer see it. Our “transparency” is becoming more opaque.

More

Hidden in the Flock

Leave a comment

Gemini AI image

Flock Automated License Plate readers have been increasingly in the news recently, as problems with the surveillance system have come to light. Many communities have begun to re-think their use of Flock. Los Angeles PD is one large agency that has decided to revisit their use, and has put renewing their subscription on hold for now. Here are my thoughts on Flock and other similar license plate reader operations.

In a perfect world, computer-based information systems like Flock would be a powerful tool for law enforcement. Put in a license plate number, or a vehicle description, and given enough cameras in the system, pinpoint where a stolen car went (or is), find a missing elderly person who drove off and has become confused on how to get home, or a myriad of other scenarios that might benefit from accessing such a database.

The problem is, we don’t live in a perfect world.

More

The Final Flock – and the answer is: “NO”

Leave a comment

It started April 24, 2026. I filed a public records request for information on the Flock Automated License Plate Reader system the City of Visalia was utilizing. Today, August 3, 2026, I got the final response. Basically, “NO”. The only thing they sent me that was not readily available on the Visalia Police Department Flock Transparency page was a list of “audits”, reporting which agencies had access to Visalia’s Flock network. It was in the tens of thousands of PDF pages. What that revealed is a whole blog post in itself, perhaps at a later date. (I did not see any evidence in those pages of any non-California agencies accessing Visalia Police Department’s database, such as ICE or Homeland Security. There’s a loop-hole about that, however.)

The only thing they were willing to tell me about my vehicle being identified, cataloged, and stored in the Flock database was that they didn’t have any record of Visalia PD checking for my plate. I suppose that’s good. Of course, it doesn’t mean that they haven’t, after my request.

Here are the blog posts I’ve made during this investigation:

  1. What the Flock?” My first notice of the Flock cameras in Visalia.
  2. Well, Flock Me!” Stories about agencies cancelling their Flock contracts due to violations of state law by Flock.
  3. More Flock, More Fun” Another blogger runs the stuff I’ve done through an AI for analysis.
  4. Flock You Later” The Police Department opts to take their allowed 14 day extension to respond to my request.
  5. Flock the Lawyers” The Police Department hands my request off to the City’s lawyers. That’s seldom a good sign.
  6. Flock Me A Little Bit” They send me the list of which agencies can access VPD Flock data, and want me to prove the license plate I asked about is mine.
  7. Tick Tock Tick Flock” The lawyers dump a huge file on me, with audit logs of agencies that accessed Visalia’s Flock data. Want to know the biggest user, by far? California Highway Patrol. They routinely check thousands of camera files.

So they’ve decided “…data is exempt from public disclosure under the public records act balancing test because the public interest in preventing disclosure clearly outweighs the public interest in disclosure…” and “Visalia PD’s policy “Because such data may contain confidential information, it is not open to public view.” (Policy 428.2.)”

They took 14 weeks to determine they wouldn’t give me data on myself. Due diligence, or deliberate delay?

This story is not over.

Image by Gemini AI

Tick tock tick Flock

1 Comment

Visalia Police Department Public Records Request – update

On April 19, 2026, I posted “What the Flock?“, my first entry about the proliferation of Flock Automated License Plate Readers in Visalia, California.

On April 24, 2026, I posted “Well, Flock Me!“, about a nearby community (Merced, California) disabling their Flock ALPR system after problems with unauthorized access were discovered. On that same day, I filed a Public Records Request with the Visalia Police Department, about Visalia’s recent installation of Flock cameras. The City had ten days to respond.

On May 5, 2026, I posted “Flock you later“, where the City of Visalia takes advantage of a 14 day extension to provide the requested documents.

On May 11, 2026, I posted “Flock the Lawyers“, wherein the City informs me they have to run it past the lawyers first, and they were targeting June 1, 2026 for release of the documents.

On May 27, 2026, “Flock Me A Little Bit” is the next chapter, in which the City is initially refusing to provide some of the requested documentation, since I was requesting the images in the system of a particular license plate. My license plate. I sent them a copy of my vehicle registration. The next target date for complying with my request was June 20, 2026.

On June 29, 2026, I posted to Facebook, tagging both the City of Visalia and the Visalia Police Department, that they were nine days past their own due date for information. That was at 1pm. By 3pm, I received a “supplemental response to your public records request”, via email. This response stated “The attached document shows the result of a Department audit searching for any monitoring and investigating activity for JJRJR. No data exists.” Except that wasn’t what I asked them to provide. I had no reason to suspect the Police Department deliberately did a search for my license plate, for whatever reason. What I asked for was every instance of my plate being recorded by the system. Those are two different things. They are not going to convince me that my plate has never been recorded by their system.

In that response, they also moved the date again. More information was supposed to be available July 20, 2026.

On July 10, 2026, I received this letter, and a link to a DropBox file with audit logs.

There are tens of thousands of pages (PDF file pages) in response to this part of my request. In case the link in the letter doesn’t work, you can see them at my Dropbox, at this link: https://www.dropbox.com/scl/fo/6u6l4w0jwe54w6y1fvllu/AAZ4mAaSF8XPUJfqUpd2lwo?rlkey=iuqasfx1t6r8hhwgz02h36us1&st=qkgkdqht&dl=0

They state “The Department’s staff is continuing its diligent search and review of requested records. The Department’s staff members estimate they will be able to supplement this response on or about August 20, 2026, earlier if able.”

Tick tock tick Flock

Well, Flock me!

Leave a comment

Flock ALPR, Visalia, California

Some more License Plate Reader fun. KMPH 26 posted a story about Merced’s Police Department discovering a, shall we say – just to be very understanding of the complexity of computerized systems – a “mis-configuration” of their automated license plate reader system. Although not the Flock ALPR, like Visalia’s, they released a statement on April 23, 2026, saying, in part, the following:

Merced, Calif – In the interest of transparency, the Merced Police Department is addressing recent concerns regarding automated license plate reader (ALPR) data sharing.

Following these reports, the Department conducted a comprehensive internal review of its ALPR system. That review determined that prior system configurations allowed data sharing with certain federal agencies.

Upon identifying this issue, the Department immediately disabled the identified connections and will continue to conduct additional audits to ensure ongoing compliance.

Merced joins Santa Cruz, Oxnard, and Ventura Police Departments to identify (through media reports, not, apparently, through their own oversight) problems with unauthorized access to their databases. Each agency has said they’ve fixed the problems, but one has to wonder how many other instances of unauthorized access have occurred.

I’ve sent the following Public Records Request to the Visalia Police Department:

To: Custodian of Records
Visalia Police Department
303 S Johnson St.
Visalia, CA 93291
(Or via NextRequest Portal)

Date: April 24, 2026

RE: CALIFORNIA PUBLIC RECORDS ACT REQUEST – FLOCK ALPR DATA SHARING AND SPECIFIC PLATE RECORDS

To the Custodian of Records:

Under the California Public Records Act (Gov. Code § 7920.000 et seq.) and California Civil Code § 1798.90.5 et seq., I am requesting the following public records held by the Visalia Police Department (VPD):

System Access & Inter-Agency Sharing Logs: Any and all records, audit logs, or documentation showing access to data compiled by the VPD via the Flock Safety ALPR system by any agency other than the Visalia Police Department. This request includes, but is not limited to:

Lists of “Hot List” hits shared with outside agencies.

Audit trails showing when outside agencies (federal, state, or local) queried the VPD’s Flock database.

Current lists of all agencies with whom the VPD has a data-sharing agreement for ALPR data.

The time frame for this request is from the initial installation/implementation of the Flock system to the present date.

Specific License Plate Records: All records, images, and data points captured by the VPD ALPR system (including fixed cameras and mobile units) that reference or identify the following California license plate: JJRJR.

This request includes time stamps, location data (GPS coordinates or camera IDs), and associated photographs for every instance this plate was recorded from the time of system installation to the present date.

Redactions and Privacy:
If the Department contends that any portion of these records is exempt from disclosure, please provide the non-exempt portions pursuant to Gov. Code § 7922.525. If any portion of the request is denied, please provide a written response citing the specific legal authority for the denial within the ten (10) days required by statute
.

Request for Digital Format:
Please provide these records in electronic format. If the records exist in a searchable database or spreadsheet (such as CSV or Excel), I request they be provided in that native format
.

Thank you for your assistance.

Sincerely,

Jimmie Joe Reeves
Visalia, CA

That license plate request is for my own car, and I’m interested how many times the system has seen me while I’m running around town. From what I understand of their operational rules, they should have no images older than 30 days. We’ll see if I get anything, or get buried with data files.