Is Visalia PD following it’s own License Plate Reader policy regarding Flock cameras?

Leave a comment

Image by Gemini AI

The Visalia Police Department Policy manual includes the following section (online as of 5 pm Pacific, 9/6/2026):

The devil’s in the details, as they say, and boy are there some details here! Let’s take a look.

428.3
“…to convert data associated with vehicle license plates for official law enforcement purposes, including identifying stolen or wanted vehicles, stolen license plates and missing persons. It may also be used to gather information related to active warrants, homeland security, electronic surveillance, suspect interdiction and stolen property recovery.”

“Homeland Security”. California law prohibits the release of ALPR data generated in California to Federal agencies.


California Civil Code § 1798.90.51: Mandates that an ALPR operator or end-user must not share ALPR data with agencies or entities that are not state or local law enforcement agencies operating strictly under California state law.

California Civil Code § 1798.90.55: Prohibits public agencies from selling, sharing, or transferring ALPR information, limiting valid dissemination solely to authorized local/state public agencies operating within California for defined law enforcement purposes.

As long as they’re operating only based on California law, and not in conjunction with any Federal or out-of-state agency, they could, theoretically, use ALPR data for a perceived “homeland security” threat. But if they call in the Feds, they can’t give any of the ALPR data that they developed from their investigation to them.

Here’s the real devil, in my opinion, though:

428.7

(a) The agency makes a written request for the ALPR data that includes:

  1. The name of the agency.
  2. The name of the person requesting.
  3. The intended purpose of obtaining the information.

(b) The request is reviewed by the Operations Support Division Captain or the authorized
designee and approved before the request is fulfilled.

(c) The approved request is retained on file.

On 9/6/2026, there were 258 agencies listed on the Visalia Police Department’s Flock Transparency page as “Sharing Network Data With – Organizations granted access to Visalia CA PD data.”

From May 1, 2026 through June 1, 2026, there were 507,696 “hits” on Visalia PD’s Flock data set. California Highway Patrol was the biggest user, with 46,693 inquiries. That’s just one month’s worth of data access. (Visalia PD accessed the data only 1,634 times in that month, for comparison.)

Somehow, I doubt Visalia Police Department received 507,696 written requests for information which included the name of the agency, the requesting officer’s name, and the purpose for obtaining the information, which was then processed and approved before the data was released.

Now, I’m not a lawyer. I’ve never played one on TV. Hell, I didn’t even stay in a Holiday Inn Express last night. But it seems to me that the rule book isn’t being followed. The data is being accessed randomly by any agency on the “granted” list unsupervised. None of the required review or approvals are being done. Visalia PD has simply opened it’s data to anyone on that list. (To be sure, it’s a pretty common way to operate, as far as I can determine, statewide. Agencies all over the state are allowing the same access. The policy manual is one that is from a template, used by many agencies, and modified to reflect Visalia-specific regulation. One wonders how well it’s read before operations begin.)

I’m not universally against license plate reader systems. They have legitimate uses in the law enforcement world. What I don’t like is agencies, and especially the Visalia Police Department, giving control of these systems to an outside organization. The data is taken by cameras not owned by Visalia, the data is stored on servers not under the physical control of Visalia, and the programs used to access that data are proprietary property of Flock. The only real security on the data is Flock saying, “trust us, bro”. New reports the past few years tell us we can’t.

There are plenty of other ‘devils’ playing in this ongoing drama with Flock. Their use of the data, regardless of their claims that the customers own and control it and they won’t sell it, even though there are three places in the contract where the following is stated: “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.

They also will use the data, anonymized (whatever that means. How do you anonymize data but still do this) to teach their AI program: “including the training of machine learning algorithms.”

Automated License Plate Readers are the camel’s nose. The rest of the camel is all the things they will (not can, will) do with the data we pay them to collect. The nose is in the tent. Maybe the camel has his entire head inside.

Did you ever watch the TV show, “Person of Interest”? Mr. Finch was trying to create an AI that could hunt terrorists. He succeeded. A joke of the show was that before he could create that machine, he had to create the availability of data, so he created social media. Now everyone provided the data he needed to train his AI. If you followed the show, you know how well all of that turned out.

We have some decisions to make. And some decisions already made to overturn. At the very least, change the policy manual to reflect how things are actually done.

Or we can just trust the government to always do the right thing, and protect us from bad actors. We’ve seen how well that’s worked out in the past, haven’t we?

My previous Flock-related posts:

“Will Somebody Shut Him Up??”

Leave a comment

These are all but one of the times I’ve spoken at the Visalia City Council, during Public Comments. My first time isn’t on their website, and was in 2012, when I accepted the first June Pride Month Proclamation issued by the City of Visalia. It was the first Pride Month Proclamation by a government body in the Southern San Joaquin Valley.

I got bored, so I counted the times I appeared before the City Council, according to the minutes. As of this writing, I’m at 58 times.

There are fewer than 58 entries above, because I spoke several times at several meetings. One time I had so much to say about things that I spoke five times! Another day it was four. It’s usually just once per meeting.

I still get nervous, sometimes, but I probably enjoy it more than I should.

Lest you think I’m hogging all the time, there’s a lady that has spoken over 85 times in the same time frame. I don’t know if she enjoys it or not.

If you would like to let them know what you think about things, here’s the 4-1-1:

PUBLIC COMMENTS  

This is the time for general public comment on issues within the jurisdiction of the Visalia City Council. Each speaker tonight may speak for up to 3 minutes during this general comment period on a matter that is not on this agenda. The public may also make one comment for up to 3 minutes prior to the consideration of the Consent Calendar, and immediately before any regular agenda item is heard. The Council asks that you keep you comments concise and positive. Creative criticism, presented with appropriate courtesy, is welcome. Each speaker will be allowed three minutes and a timer will notify you when your time is expired. Please begin your comments by stating and spelling your name and providing your city of residence.

There are general public comments at the beginning of each session (work session and regular session), before the Consent Calendar, and after each item on the regular agenda, regarding that item.

Come join us at the meetings, on the first and third Mondays of each month (except on holidays, when they generally meet Tuesday). The regular session starts at 7pm, at City Hall, 707 W. Acequia. Work sessions start anywhere between 4pm and 5:30pm. Check the agenda for exact times.

“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?

1 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

Is Tulare County Transparent? The Magic 8 Ball Might Say “Reply Hazy, try again”

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:

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

Older Entries