Needles in the Flock Haystack

Leave a comment

Image generated by Gemini AI

On September 10, 2026, I filed a California Public Records Act request of the City of Visalia, and the Visalia Police Department. On October 5, I got my response.

A lot to digest there, but let’s start with “5. The Department’s case/incident number is withheld.” A lot of verbiage to deny giving me the case numbers associated with each incident that was allegedly solved with the use of the Flock ALPR system.

They’re also saying they don’t have to release “arrest and incident information” that is more than a year old, and that “much” of my requested information predates that by “many months”, but they are giving it to me (minus what they decided to withhold) “in the interest of transparency”.

They tell me how generous they were being by including information that was more than a year old, citing a court case that they claim means they didn’t have to.

Visalia, I hate to say it, but “transparency” went out the window a long time ago. (Encrypting police radio transmissions and removing a data field on the Flock transparency page was just the beginning.)

Other information gleaned from the “response” –

From January 1, 2025 through May 29, 2026, there were 123 incidents solved which were attributed to Flock ALPR use by the Visalia Police Department.

To justify mass surveillance, proponents of ALPR systems often talk about two types of incidents: missing persons, and stolen cars. In Visalia’s record, there are no cases of missing persons found using the Flock system. Out of 123 incidents that were attributed to the Flock system, only 45 are stolen vehicles.

Six were violent crimes – assault with a deadly weapon, armed robbery, and a home invasion.

The rest of the cases “solved” by Flock ALPR data are not classified as violent crimes.

I had asked for location information, as well. Either addresses of incidents, or the hundred block and street name. They refused to provide that, stating the “existing” data only listed VPD “area” zones, and they didn’t have to provide the address or location information more detailed than that.

In the time period covered by the data released, Flock ALPR cameras took more than 5,950,000 images of license plates. Perhaps many more. The “transparency” page lists an average monthly “unique plate reads” of more than 300,000 every 30 days. Multiply that by the 17 months of data released, and the total number surveillance images is staggering.

And, at $3,000 a year per camera, expensive. (The cameras are not bought by and owned by Visalia. They are a subscription. The cameras and related equipment remain the property of Flock.)

Tell Me About This Particular Flock Camera

Leave a comment

On August 26, 2016, I filed a California Public Records Act request with the City of Visalia regarding this particular Flock camera. It’s located on Demaree Street, just south of Goshen Avenue, in Visalia. When I noticed it one day driving by, I had questions.

There are all kinds of requirements for things close to city streets, especially for those items in the public right-of-way. I decided to check to see if those requirements had been met for this installation. I wrote a very involved public records request about it, and got my reply today.

The response was underwhelming.

Either most of my request was ignored, or the City let this thing be put up with almost no oversight, and in violation of it’s own documents regarding the installation.

Here’s the complete response to my request. I’ll add the entire request at the end of this blog, as it’s quite extensive.

More

Another Day, Another Public Records Request

Leave a comment

The “Training Bulletin” for the Visalia Police Department, dated January 16, 2025 contains the following sentence:

“Any successfully investigated case and/or arrest that involved the use of a Flock ALPR shall be logged in Spillman under Circumstances Code FLOCK.”

Spillman is the program which basically runs the Sheriff’s Office. Dispatch enters calls with it, it controls the Records data, and provides statistical information, among many other things.

Since the Visalia Police Department has indicated that the Flock Automated License Plate Reader system has been instrumental in a dramatic decrease in auto thefts, I’ve decided to see just how effective it actually has been. I want to see every incident they’ve attributed to the Flock cameras since this bulletin became operative.

The City’s lawyers have given themselves until October 15, 2026 to respond to my request.

Visalia City Council Misled? Or is it just semantics? More Flock shenanigans.

Leave a comment

Image by Gemini AI

At the October 21, 2024 City Council meeting, Consent Agenda item #6, file #24-0415, was approved with no separate discussion. That item was to enter into an agreement with Flock Safety out of Atlanta, Georgia, for their Automated License Plate Reader subscription service. Visalia Police Department wanted to install 22 cameras around the city, and have access to 18 other cameras operated by other organizations, for a total of 40 installations.

The issue here? The agenda packet does not reflect the reality of what the City Council was being asked to approve.

The information provided to the City Council says, “The Visalia Police Department has thoroughly researched various methods to prevent and respond to Part One crimes within the City of Visalia and County of Tulare.”

Let’s look at the “Background Discussion” presented by city staff in the agenda packet.

Background Discussion:

Flock Safety fixed-mount ALPR cameras have become one of the most popular ALPR cameras available to law enforcement and are also available to school districts, businesses, and hospitals.

True.

Currently, there are 18 Flock Safety fixed-mount ALPR cameras operating throughout the City of Visalia. These cameras are installed at various businesses and properties which are owned by private entities.

Also true.

As a Flock Safety customer, the Visalia Police Department would gain access to the 18 existing Flock Safety fixed-mount ALPR cameras at no additional cost. This would expand the network of ALPR cameras available to the Visalia Police Department significantly.

True.

Nationwide, all law enforcement owned Flock Safety ALPR cameras…

Not true. No Flock Safety ALPR cameras are owned by anyone other than Flock. They are the sole property of Flock. The City is entering into a lease.

communicate with each other, allowing law enforcement to track offenders from jurisdictions outside of the City of Visalia.

The cameras do not ‘communicate’ with each other. They take images, scan those images with a program to extract the license plate number, and send the image and the data to a central server, maintained as proprietary by Flock. The images can be further analyzed by Flock’s proprietary software for information other than simply license plate numbers. They do allow law enforcement agencies from outside the City of Visalia to access that data – if they subscribe to the service, or present a subpoena.

Locally, Flock Safety fixed-mount ALPR cameras are installed in the following cities: Farmersville, Woodlake, Porterville, Lindsay, Tulare, Hanford, Lemoore, Corcoran, Orange Cove, Reedley, Fowler, and Fresno. These cities combined have a total of more than 250 Flock Safety fixed-mount ALPR cameras, which the Visalia Police Department would gain access to after becoming a customer.

True.

Flock Safety fixed-mount ALPR cameras have no infrastructure requirements resulting in zero utility costs. The cameras are powered by solar and utilize a wireless LTE connectivity. Flock Safety services, maintains, and replaces each fixed-mount ALPR camera at no additional cost for the contracted period.

True. If the cameras or other parts of the system fail, Flock will replace them. If they are damaged or stolen, the City pays to replace them, at over $600-$800 per camera. Damage to the solar panel, cell equipment, or other parts of the unit are extra.

Flock Safety is the only fixed-mount ALPR camera company that provides connectivity with the existing Flock Safety fixed-mount ALPR cameras that are installed throughout the City of Visalia and surrounding jurisdictions. They are also the only company that features technology that is capable of capturing vehicle identifiers other than license plates.

There’s an important bit of information that I suspect many hope flies by unnoticed. “vehicle identifiers other than license plates”. And the data is used to train their own, again proprietary, AI.

Fiscal Impact:

No new appropriations required at this time.   There will be two (2) separate contracts due to separate funding sources.  Contract #1 is for nine (9) cameras and contract #2 is for 13 Cameras. The cost variance between the two projects is primarily due to differences in equipment and installation infrastructure.

I also have questions about the funding source, but that’s maybe for a different blog.

The ALPR cameras purchased under contract #1 are being installed on CalTrans right of way infrastructure which has an increased installation cost. Furthermore, two of the ALPR cameras included in this contract are more costly due to their range capabilities.

The cameras are not being “purchased”, they are being leased. While Flock claims, and contractually promises, that the data these cameras produce belong to the subscriber, and will not be ‘sold’, they do require “a non-exclusive, worldwide, perpetual, royalty-free right to use and distribute such Anonymized Data…”. There is no way (publicly revealed, anyway) for the City of Visalia to insure the data is secure, and not used in violation of California law, or the 4th Amendment to the US Constitution. (A class action lawsuit against Flock is in the beginning stages of court right now, based on 4th Amendment claims)

Purchased? Leased? Semantics? Maybe. But reading the Consent Agenda packet, would a City Council person necessarily understand that, one, the City was not “purchasing” the system, and, two, that the details presented in the agenda packet were not accurate? Many city council members rely heavily on the city staff to provide them with reliable information on which to base their decisions. Incomplete or misleading information, put in a consent calendar item, might reasonably fly right past them.

The Police Department recently told the Valley Voice that “according to their data, 2025 saw a 39% reduction in stolen vehicles, which VPD attributes to the Flock cameras it began using in 2024.” While that may be, correlation is not causation. We are not given the data required to authenticate the effectiveness of the Flock cameras.

As I’ve stated in previous blogs, I’m not against these kinds of camera systems, if they are the property of, controlled by, and accessed only by local government(s). With Flock, agencies do not control the system, they only have access to it. The data, while said to be owned by the agency and not sold to anyone else, is solely controlled by Flock. Past incidents have shown the ease at which access control is lost, and how the system can be abused, even by authorized personnel.

Look at the Consent Calendar agenda item yourself, and decide. Did it accurately reflect what the Police Department wanted the City to do? Does it fully inform the Council about what they were being asked to authorize? Did it really result in a 39% reduction in stolen vehicles?

Or is “lease” and “purchase” just an issue of semantics?

Here are my previous blogs about Flock:

“Hide my ex’s name (for the kids safety), but here’s my address!”

Leave a comment

Meet Jason Bailey of Visalia.

Jason is not happy.

I think I’ve made him mad.

Jason is upset that some previous posts of mine have included his ex-wife’s name, and he’s very concerned. He even wrote an op-ed in GV Wire about it (which means he’ll generate even more exposure of his ex-wife’s name). He neglected to include some pertinent facts as he called me out by name, though.

On June 22, 2026, I received this through Facebook Messenger:

On June 23, he sent two more messages, linking a story about an intruder at the home of the Fresno City attorney. I replied “Yes, I read your message. I’m still considering it.” (and what’s with the “MBA”? Like that somehow makes a difference?)

On July 4, I received the following message:

I think he’s mad. He posted the following as a comment on a posting on Porterville Communists, regarding me. The poster started recording me shortly after I began my remarks, but I suspect the speaker after me was who they were actually interested in. (I have no connection to this group. I don’t know if it’s a legit site for a group, or if it’s satire.)

He never contacted me in any way to ask for my phone number. Notice the hostility growing already. (It’s ridiculously easy to find my phone number online, BTW.)

On August 20, 2026, I received this SMS message:

Was it from Bailey? I don’t know, but it’s mighty coincidental, isn’t it? Like I said, it’s not difficult to find my phone number online. (As an aside, this image had to be taken before the construction began on my street, at least two months before this appeared on my phone. Whoever sent this message had been holding on to this image for a while. Stalking?)

The online anger continued. More from the Porterville Communist’s comment thread:

Now it gets really weird. He’s all worried that his ex-wife’s name will somehow put his children in danger, but he does this:

After going on about his children’s safety, he posts his address on Facebook, and challenges a stranger to come “continue this conversation”. That doesn’t seem like he’s really very concerned about his children’s safety.

So it boils down to this: His ex-wife (who has my email and can contact me directly) appears on the signatory line of an official letter from the City of Visalia’s attorneys. Bailey fears someone will see her name, and attack their children. Because – something something something.

Since he’ll blast his own address out on the Internet, I think this entire thing is simply someone who doesn’t like to be told “No”.

Unless the attorney in question asks me directly, I’m not redacting her name.

Flock and Ding Dong Dash in Porterville

Leave a comment

Image by Gemini AI

“Knocking on people’s doors and leaving the area”.

That was the ‘reason’ Porterville Police Department entered into the Flock Automated License Plate Reader system for three searches in late July and early August, 2026. Each time, they searched over 700 networks.

On July 29, 2026, they checked the system twice, for a ‘487’ (grand theft). Both times, they checked 1 network.

On August 19, 2026, they checked 710 networks for “RED TOYOTA CAMRY”.

Ding dong dash, over 700 networks. (fast runners? Fast and Furious ready to pick them up and flee the state? The long way?)

Grand theft, 1 network. (Too much to carry out of town?)

How many Red Toyota Camrys do you suspect are in those 710 networks?

I wonder if Arte Johnson’s character Wolfgang would say “verrrry interesting… but shtupid!”?

Can I See Your Flock?

Leave a comment

Image by Gemini

On July 14, 2026 I filed a second public records act request for information about the Visalia Police Department‘s use of the Flock Automated License Plate Reader system. In that request, I asked for information regarding any agreements or other documentation that would allow VPD to access any Flock cameras operated by the Visalia Economic Development Corporation, Lowe’s, and Home Depot. The following is what I received today, August 20, 2026.

No documents were presented regarding Lowe’s and Home Depot, so, assuming the lawyers are giving me the all the information the city has, there are no agreements of any kind for the Visalia Police Department to access any data collected by cameras owned by those companies.

Does that mean if VPD wanted to check that data, they’d have to get a subpoena? Can they simply call over and ask? If granted permission (and why would they not be?), do they have to go to the location and get access using the store’s system, or can they log in and take the data directly from Flock’s servers? I don’t know.

As far as the Visalia Economic Development Corporation is concerned, I’m not certain they’ve ever actually installed any cameras. One camera is shown in the industrial park, but I have as yet been unable to determine if that is part of the VPD network, or is operated by VEDC. At approximately $3,000 each per year, VEDC may not have the money to maintain the subscription.

What’s more interesting is the letter from the VEDC to a rather extensive email list about Flock needing to preserve data due to a class-action lawsuit that is pending. Check out some of the people they sent it to:

A Visalia City Council member, the Visalia City Manager, the Visalia Assistant City Manager, someone at Southern California Edison, two or more construction companies, the Visalia Unified School District Superintendent, the Tulare County Office of Education Superintendent, and several others identified by name only. Why most of them need to be informed about a class action lawsuit against Flock is puzzling.

The City of Visalia has closed out this public records request, telling me “no other records matching your request exist or are in the possession of the City of Visalia”.

My previous Flock-related posts:

P.S. – Since Visalia is using grant money for the first four years of this contract, there has been no ongoing expense for the city. They will eventually have 22 cameras up, which could result in a $66,000 a year cost to maintain the system, once those grants expire. Your tax dollars are and will be paying to surveil you every time you drive by a Flock camera. Smile, won’t you?

Hidden in plain sight, but you are not allowed to see it

Leave a comment

Half A Million Flocks in May, 2026

Leave a comment

In April of 2026, I made a public records request of the Visalia Police Department. One of the things I asked for in that request was the logs of every outside agency that accessed the data collected by Visalia’s police department. I didn’t expect the sheer size of the results. I received audit logs for 18 months, running to tens of thousands of pages. I’m going to look at the latest (and biggest) of those files here.

From May 1, 2026 through June 1, 2026, there were 507,696 “hits” on the Flock data collected by Visalia PD. I’ve tallied the results to see who is searching license plate files (and other search terms) in Visalia. (Visalia accessed it’s own data 1,634 times in that month)

The biggest searcher was the California Highway Patrol, at 46,693 inquiries in just that one month’s time. Riverside County Sheriff’s Office was next, at 42,957.

There’s no way they thought vehicles they were “checking” for were in Visalia over 40,000 times each. It looks very much as if they simply have “all” selected for any search they do. Other agencies on down the list seem to be a bit more circumspect in their searches, but still cast wide nets when they do a Flock search.

Here’s a .txt file with the list, followed by an Excel list.

May 2026 audit

Beginning Search Time: May 1, 2026, 07:00:00 AM UTC
Ending Search Time: June 1, 2026, 06:59:59 AM UTC
Unique organizations: 309
Records tallied: 507,696

Org Name Tally

RankAgency / OrganizationCount
1California Highway Patrol46,693
2Riverside County CA SO42,957
3San Francisco CA PD28,422
4Los Angeles CA PD19,367
5Orange County SO CA19,114
6Los Angeles County CA SD17,766
7San Jose CA PD15,670
8San Bernardino County CA SO12,167
9Oakland CA PD11,855
10San Diego County CA SD9,855
11Fremont CA PD7,241
12City of Riverside CA PD7,054
13Sonoma County CA SO7,054
14Ontario CA PD6,786
15NCRIC6,742
16Irvine CA PD6,585
17Fontana CA PD5,588
18Ventura County CA SO5,543
19Santa Clara CA PD5,472
20Contra Costa County CA SO5,191
21Elk Grove CA PD4,942
22Daly City CA PD4,939
23San Joaquin County CA SO4,724
24Kern County CA SO4,660
25Santa Rosa CA PD4,550
26Stockton CA PD4,516
27San Bernardino CA PD3,851
28Solano County CA SO3,792
29Chula Vista CA PD3,725
30Bakersfield CA PD3,560
31Vacaville CA PD3,402
32Sunnyvale CA PD3,218
33Corona CA PD3,185
34Placer County CA SO3,028
35Salinas CA PD3,014
36Hayward CA PD2,878
37Murrieta CA PD2,854
38Pasadena CA PD2,761
39Chino CA PD2,691
40Concord CA PD2,613
41Sacramento CA PD2,569
42Newport Beach PD CA2,510
43California Department of Corrections2,476
44Buena Park CA PD2,463
45Livermore CA PD2,434
46Napa County CA SO2,422
47Costa Mesa CA PD2,408
48Anaheim CA PD2,324
49San Mateo CA PD2,259
50Santa Maria CA PD2,245
51Marin County CA SO2,239
52Sacramento County CA SO2,142
53Orange CA PD2,139
54Fairfield CA PD2,120
55National City CA PD2,038
56Alhambra CA PD1,984
57Montclair CA PD1,956
58Petaluma CA PD1,939
59Santa Barbara County CA SO1,891
60Cypress CA PD1,805
61Morgan Hill CA PD1,787
62Garden Grove CA PD1,699
63Rialto PD CA1,693
64San Leandro CA PD1,665
65Fullerton CA PD1,646
66Visalia CA PD1,634
67Turlock CA PD1,608
68Santa Ana CA PD1,465
69Tracy CA PD1,440
70West Sacramento CA PD1,433
71Union City CA PD1,391
72Monterey County CA SO1,389
73Rocklin CA PD1,384
74Manteca CA PD1,367
75Simi Valley CA PD1,364
76Greenfield CA PD1,323
77Burbank CA PD1,289
78Butte County CA SO1,287
79Ventura CA PD1,275
80Citrus Heights CA PD1,242
81Gilroy CA PD1,237
82Upland CA PD1,227
83Redwood City CA PD1,191
84Downey PD CA1,166
85Hanford CA PD1,153
86El Cajon CA PD1,149
87Tulare County CA SO1,136
88Hercules CA PD1,136
89Riverside County CA District Attorney1,121
90Brentwood CA PD1,115
91Oceanside CA PD1,112
92Vallejo CA PD1,099
93Merced County CA SO1,079
94San Bruno CA PD1,054
95Desert Hot Springs CA PD1,049
96Cal Fire1,042
97Placentia CA PD1,028
98Marina CA PD990
99Glendora (CA) PD982
100Imperial City CA PD932

There are 209 additional unique organizations with counts ranging from 899 down to 1. You can see the entire list in the Excel file.

Here are my previous Flock-related posts:

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:

Older Entries