Hornbeck said:

---

In the Bexar case, the officer made up a traffic violation, then had a K9 that came in because he didn't consent to search. The K9 "alerted", and they searched. Found nothing. All of this came out in discovery including the WhatsApp group police used.

---

It's worse than that.

There were multiple agencies and jurisdictions involved. Local, county, and state. Probably federal as well, I can't remember. One guy followed him and lied to get a pretextual stop. The other cops were nearby just waiting for the stop.

He didn't call the K9 unit. It was already there. They just brought it out of the car when law-abiding citizen refused to allow a search.

CS78 said:

---

Bernie Sanders and AOC taking it a step further yesterday.

NEWS: Sanders, Ocasio-Cortez, Merkley Unveil Ban Flock Act to Protect Americans' Right to Privacy Senator Bernie Sanders

Writing is on the wall!

---

This is exactly what I was talking about earlier. Your opposition to Flock isn't worth allying with people who have it made it very clear that they hate the freedoms and values you hold dear.

zigag09 said:

---

I found this interesting in light of one of our mayoral candidates' proposals to replace the city's Flock ALPR system with Axon's platform.

Axon's platform is a considerably broader mass surveillance system than a direct ALPR replacement. Axon Fusus is designed as a centralized "single pane of glass" for a Real-Time Crime Center that integrates multiple camera feeds into a single interface. This includes our city's ALPRs, body cameras, drone cameras, and other cameras and third-party systems.

The potential scope of this mass surveillance system goes beyond cameras owned by the city. Axon says Fusus can integrate public and privately-owned cameras, including cameras at businesses, schools, churches and other buildings. Axon's Community Integration program allows camera owners to provide a live feed to Axon Fusus.

Axon has also partnered with Ring to integrate city resident's cameras into their system. Law enforcement can send a geographically targeted request to Ring users in an area so they can have their video footage added to the city's Axon system. The footage provided is transferred into Axon Evidence.

Our lovely city could have an extensive surveillance network, keeping an ever-watchful eye on the city and its residents to ensure we're all safe and sound.

https://www.axon.com/resources/how-axon-assists-with-real-time-response
https://www.axon.com/products/axon-fusus/community-integration
https://www.axon.com/blog/building-safer-communities-together-axon-and-ring

---

First, it would still be grant funded where Flock is not- thusly saving the local taxpayers $300k annually. But also:

From

****Gemini AI

Proponents of Axon argue that the company offers vastly superior privacy and security controls compared to Flock. Axon CEO Rick Smith has publicly stated that law enforcement agencies are actively switching to Axon because of its stronger privacy framework and data controls.

From the perspective of police chiefs, city officials, and technology proponents, Axon safeguards privacy better through several structural advantages:

1. Eliminating the "National Dragnet" (Controlled Data Sharing)

The most common argument from proponents is that Axon does not operate an automated national database.
The Flock Problem: Flock automatically defaults to a nationwide searchable network, allowing outside law enforcement agencies from other states to search local dataa practice that blindsided officials in cities like Denver.
The Axon Solution: Proponents note that under Axon's system, data sharing is locked down by default. To share license plate data, an agency must send a direct, explicit department-to-department invitation. This connection can be revoked by the local agency at any time, keeping data sovereign to the community that collected it.

2. High-Bar Search Accountability

Proponents highlight that Axon builds strict, unalterable guardrails directly into the software to prevent officer misconduct or "fishing expeditions."
On Axon's network, an officer cannot simply type a plate number into a free-text field.
Instead, the system requires the officer to input a valid case number and select a structured offense category from a strict pre-determined list before a search can be executed. Every single search is permanently logged in a tamper-proof audit trail.

3. Oversight Through Unified Evidence Ecosystems

Rather than managing a disjointed web of third-party tech startups, proponents favor Axon because it integrates license plate readers directly into Evidence.com, a highly regulated, deeply vetted digital evidence management system. Because Evidence.com already houses body camera footage and crucial legal evidence, it is subject to rigorous, state-mandated CJIS (Criminal Justice Information Services) compliance, strict data-access logging, and clear legal workflows. Proponents argue this creates centralized oversight and maximum transparency over who touches civilian data.

4. Mitigation of Security Breach Risks

Proponents point to Axon's decades-long track record as an established public safety giant as a security advantage. Amid public backlash over security vulnerabilities and data breaches associated with Flockwhich led police departments like Abington Township to cancel their contractsAxon is viewed by city IT directors as a safer, more stable enterprise partner capable of protecting data from international and domestic cyber threats.

*****AI ends

Respectfully

Yancy '95

EriktheRed said:

---

The biggest complaint with Flock is not owning our own data, and the ability for others to search it, and the mis-use by others that dont have our standards.

---

Flock says its customers own and control the data, like Axon, but its standard contractual language has generated controversy because it gives Flock certain licenses and data-use/disclosure rights that allowed it to share data with federal agencies. Flock has said it stopped that practice. Whose to know if Axon give the government backdoor access, perhaps under the pretense on national security.

The Axon platform allows other agencies to search customer data.

What standards does the city of College Station have?

There a many more BIG complaints about these surveillance systems, like the one that led to the landmark federal ruling on October 1, 2026, United States v. Kyle.

Since you used AI, the following is an AI rebuttal via ChatGPT.

The strongest rebuttal is not that Flock and Axon have identical privacy architecturesthey don'tbut that the argument conflates vendor-controlled security features with actual privacy outcomes, overstates several Axon safeguards, and treats Axon's enterprise reputation as evidence that its surveillance system is inherently safer or more accountable.

1. "Eliminating the national dragnet" is overstated

The claim that Axon eliminates the national-dragnet problem because sharing requires an explicit department-to-department invitation does not, by itself, establish stronger privacy protection.

The important question is what an agency can ultimately access once those relationships are established, how many agencies can be connected, what information can be queried across those connections, and what restrictions govern subsequent use. An opt-in sharing architecture can still produce a very large interstate surveillance network if agencies routinely establish reciprocal connections.

Moreover, making access technically controllable by the collecting agency is not the same as guaranteeing meaningful community sovereignty. A local agency can authorize extensive sharing, enter into numerous reciprocal arrangements, or retain data for long periods. Those are governance decisions, not simply software-security decisions.

There is also a conceptual problem with comparing Axon's architecture to Flock's most controversial implementation and then treating the difference as proof of superior privacy. A better comparison would examine:

• default retention periods;
• historical-search capabilities;
• geographic and temporal search limits;
• the number of agencies with access;
• whether searches can be conducted across jurisdictions;
• policies governing secondary uses;
• mechanisms for deleting or correcting data;
• independent auditing; and
• whether residents have any meaningful ability to challenge inappropriate searches.

A network being opt-in rather than automatic is a privacy advantage, but it is not equivalent to eliminating mass surveillance.

2. Audit logs don't necessarily prevent abusive searches

The second argument makes an important logical leap: logging a search is not the same as preventing an improper search.

Requiring a case number and offense category can create accountability, but it does not necessarily establish that the underlying search is legitimate. An officer determined to conduct an improper search may be able to associate it with a legitimate case number or select an available offense category.

The more meaningful questions are:

• Who reviews the logs?
• Are suspicious searches automatically flagged?
• Are supervisors required to investigate them?
• Can searches be performed without meaningful individualized suspicion?
• Are audit records themselves independently protected from alteration?
• How long are the logs retained?
• Are disciplinary consequences actually imposed for misuse?
• Can the public, courts, inspectors general, or civilian oversight bodies audit the system?

Even a genuinely immutable audit trail is primarily a forensic accountability mechanism. It tells investigators what happened after the fact. It does not necessarily prevent surveillance abuse in the first place.

And the phrase "tamper-proof" should be treated carefully. A vendor's technical description of an audit trail is not the same thing as independent verification that the entire systemincluding administrator access, underlying databases, integrations, and exported recordsis incapable of manipulation.

3. CJIS compliance does not equal strong privacy protection

This is arguably the biggest weakness in the original argument.

Security, CJIS compliance, and privacy are related but distinct concepts.

CJIS controls are principally concerned with protecting criminal-justice information from unauthorized access and misuse. They do not establish that a particular surveillance program collects only information that is necessary, retains it for an appropriate period, permits access only when there is reasonable justification, or provides adequate democratic oversight.

In other words:

Quote:

---

A database can be extremely secure and still contain too much information about too many innocent people.

---

Putting ALPR data into an enterprise evidence-management ecosystem may actually create a different concern: centralization.

If body-camera footage, digital evidence, ALPR information, investigative records, and other sensitive material increasingly flow into the same vendor ecosystem, the consequences of a compromised account, compromised integration, insider misuse, or overly broad administrative privileges could become more significantnot less.

Axon's scale and integration can therefore be characterized in two ways. Supporters see centralized governance and security; critics can reasonably see concentration of sensitive surveillance information and increased consequences if access controls fail.

Furthermore, describing Evidence.com as "deeply vetted" does not establish that every particular ALPR deployment inherits every privacy protection applicable to evidence stored in the system. The relevant question is the actual configuration and policy governing ALPR data, not merely the reputation of the platform hosting it.

4. Axon's corporate reputation is not evidence of superior ALPR privacy

The fourth argument relies heavily on an appeal to institutional credibility:

Quote:

---

Axon is an established public-safety company, therefore its ALPR system is safer.

---

That is not enough.

An established vendor may have more cybersecurity personnel, more resources, mature compliance programs, and greater experience responding to government security requirements. Those are legitimate advantages. But company size and longevity cannot substitute for evidence about the specific product's privacy architecture and real-world performance.

Likewise, a Flock breach, vulnerability, or contract cancellation would demonstrate a problem with Flocknot automatically demonstrate that Axon is immune to comparable problems.

Large government technology vendors have suffered security incidents, vulnerabilities, misconfigurations, insider-access problems, and other failures. The relevant comparison therefore isn't:

"Which company has the better reputation?"
It is:

"Which system demonstrably minimizes collection, retention, access, sharing, misuse, and breach consequences?"

That requires empirical evidence.

5. The argument ignores the most important privacy question: innocent people's data

There is a deeper issue missing from all four points.

ALPR systems don't merely identify vehicles associated with criminal investigations. They can record the movements of ordinary people who have done nothing wrong.

Consequently, the central privacy question isn't simply whether an officer has to provide a case number before searching the database. It is:

Why should the government retain a searchable historical record of where potentially innocent people drove in the first place, and for how long?

Suppose both Axon and Flock have excellent encryption, authentication, audit logs, and access controls. If one system nevertheless retains millions of location records for months or years, makes them searchable across jurisdictions, and permits retrospective analysis of people's movements, it can still present a substantial civil-liberties concern.

Better cybersecurity can actually make such a system more durable, not necessarily less intrusive.

6. The real comparison should be "privacy by architecture" versus "security by enterprise"

The argument also mixes two different propositions:

• Axon may offer stronger enterprise security and administrative controls.
• Axon's surveillance architecture necessarily provides better privacy.

The first could be true without the second.

zigag09 said:

---

Since you used AI, the following is an AI rebuttal via ChatGPT.

The strongest rebuttal is not that Flock and Axon have identical privacy architecturesthey don'tbut that the argument conflates vendor-controlled security features with actual privacy outcomes, overstates several Axon safeguards, and treats Axon's enterprise reputation as evidence that its surveillance system is inherently safer or more accountable.

1. "Eliminating the national dragnet" is overstated

The claim that Axon eliminates the national-dragnet problem because sharing requires an explicit department-to-department invitation does not, by itself, establish stronger privacy protection.

The important question is what an agency can ultimately access once those relationships are established, how many agencies can be connected, what information can be queried across those connections, and what restrictions govern subsequent use. An opt-in sharing architecture can still produce a very large interstate surveillance network if agencies routinely establish reciprocal connections.

Moreover, making access technically controllable by the collecting agency is not the same as guaranteeing meaningful community sovereignty. A local agency can authorize extensive sharing, enter into numerous reciprocal arrangements, or retain data for long periods. Those are governance decisions, not simply software-security decisions.

There is also a conceptual problem with comparing Axon's architecture to Flock's most controversial implementation and then treating the difference as proof of superior privacy. A better comparison would examine:

• default retention periods;
• historical-search capabilities;
• geographic and temporal search limits;
• the number of agencies with access;
• whether searches can be conducted across jurisdictions;
• policies governing secondary uses;
• mechanisms for deleting or correcting data;
• independent auditing; and
• whether residents have any meaningful ability to challenge inappropriate searches.

A network being opt-in rather than automatic is a privacy advantage, but it is not equivalent to eliminating mass surveillance.

2. Audit logs don't necessarily prevent abusive searches

The second argument makes an important logical leap: logging a search is not the same as preventing an improper search.

Requiring a case number and offense category can create accountability, but it does not necessarily establish that the underlying search is legitimate. An officer determined to conduct an improper search may be able to associate it with a legitimate case number or select an available offense category.

The more meaningful questions are:

• Who reviews the logs?
• Are suspicious searches automatically flagged?
• Are supervisors required to investigate them?
• Can searches be performed without meaningful individualized suspicion?
• Are audit records themselves independently protected from alteration?
• How long are the logs retained?
• Are disciplinary consequences actually imposed for misuse?
• Can the public, courts, inspectors general, or civilian oversight bodies audit the system?

Even a genuinely immutable audit trail is primarily a forensic accountability mechanism. It tells investigators what happened after the fact. It does not necessarily prevent surveillance abuse in the first place.

And the phrase "tamper-proof" should be treated carefully. A vendor's technical description of an audit trail is not the same thing as independent verification that the entire systemincluding administrator access, underlying databases, integrations, and exported recordsis incapable of manipulation.

3. CJIS compliance does not equal strong privacy protection

This is arguably the biggest weakness in the original argument.

Security, CJIS compliance, and privacy are related but distinct concepts.

CJIS controls are principally concerned with protecting criminal-justice information from unauthorized access and misuse. They do not establish that a particular surveillance program collects only information that is necessary, retains it for an appropriate period, permits access only when there is reasonable justification, or provides adequate democratic oversight.

In other words:

Quote:

---

A database can be extremely secure and still contain too much information about too many innocent people.

---

Putting ALPR data into an enterprise evidence-management ecosystem may actually create a different concern: centralization.

If body-camera footage, digital evidence, ALPR information, investigative records, and other sensitive material increasingly flow into the same vendor ecosystem, the consequences of a compromised account, compromised integration, insider misuse, or overly broad administrative privileges could become more significantnot less.

Axon's scale and integration can therefore be characterized in two ways. Supporters see centralized governance and security; critics can reasonably see concentration of sensitive surveillance information and increased consequences if access controls fail.

Furthermore, describing Evidence.com as "deeply vetted" does not establish that every particular ALPR deployment inherits every privacy protection applicable to evidence stored in the system. The relevant question is the actual configuration and policy governing ALPR data, not merely the reputation of the platform hosting it.

4. Axon's corporate reputation is not evidence of superior ALPR privacy

The fourth argument relies heavily on an appeal to institutional credibility:

Quote:

---

Axon is an established public-safety company, therefore its ALPR system is safer.

---

That is not enough.

An established vendor may have more cybersecurity personnel, more resources, mature compliance programs, and greater experience responding to government security requirements. Those are legitimate advantages. But company size and longevity cannot substitute for evidence about the specific product's privacy architecture and real-world performance.

Likewise, a Flock breach, vulnerability, or contract cancellation would demonstrate a problem with Flocknot automatically demonstrate that Axon is immune to comparable problems.

Large government technology vendors have suffered security incidents, vulnerabilities, misconfigurations, insider-access problems, and other failures. The relevant comparison therefore isn't:

"Which company has the better reputation?"
It is:

"Which system demonstrably minimizes collection, retention, access, sharing, misuse, and breach consequences?"

That requires empirical evidence.

5. The argument ignores the most important privacy question: innocent people's data

There is a deeper issue missing from all four points.

ALPR systems don't merely identify vehicles associated with criminal investigations. They can record the movements of ordinary people who have done nothing wrong.

Consequently, the central privacy question isn't simply whether an officer has to provide a case number before searching the database. It is:

Why should the government retain a searchable historical record of where potentially innocent people drove in the first place, and for how long?

Suppose both Axon and Flock have excellent encryption, authentication, audit logs, and access controls. If one system nevertheless retains millions of location records for months or years, makes them searchable across jurisdictions, and permits retrospective analysis of people's movements, it can still present a substantial civil-liberties concern.

Better cybersecurity can actually make such a system more durable, not necessarily less intrusive.

6. The real comparison should be "privacy by architecture" versus "security by enterprise"

The argument also mixes two different propositions:

• Axon may offer stronger enterprise security and administrative controls.
• Axon's surveillance architecture necessarily provides better privacy.

The first could be true without the second.

---

Some good points in there. Proof positive that AI, like us humans, can and often do, disagree.

The question of privacy will ultimately be defined, and decided, by case law that'll become precedent law, elevated in many cases all the way to SCOTUS.

It'll also be decided by legislation- maybe even ultimately a Privacy Amendment to the Constitution itself.

In the meantime, we do the best we can at the local level and make the call- as we did. Only through the prism of time do we ultimately find out how close, or off, our local decisions are to what's ultimately decided.

Respectfully

Yancy '95

zigag09 said:

---

Quote:

---

The question of privacy will ultimately be defined, and decided, by case law that'll become precedent law, elevated in many cases all the way to SCOTUS.

---

Just because it's legal doesn't mean we should do it, or that your constituents want you to do it.

---

That's very true.

Respectfully

Yancy '95

Did you read the article "Soman told KBTX that while the city has access to other ALPR systems and technologies, the city doesn't have a contract with Flock. Soman said the Flock cameras in town are owned by Washington County, TxDOT and private businesses."

So they don't have access to College Station Flock.

College Station has a public portal that list every agency with access. Brenham PD isn't listed.

Where can we access this "public" portal?

https://transparency.flocksafety.com/college-station-tx-pd

mason12 said:

---

College Station has a public portal that list every agency with access.

---

You seem to be very well educated on the happenings of local law enforcement. Do you or someone you know have a working relationship with government/ law enforcement in Brazos county? Or are you just a citizen that's a proponent of ALPRs?

Well Hot wheels has weighed in

Quote:

---

Abbott defended his decision to pause state funding for Flock license plate reader cameras, pointing to misuse of the technology by law enforcement.

"Listen, a lot of controversies have arisen about Flock cameras," Abbott said. "One is that there is a law enforcement officer who has been indicted 100 times for 100 felonies for abuse of Flock cameras. There have been other allegations about similar actions by other officials across the state, including violations by people who are in the private sector. And so this is an issue that we're going to need to step back, put a pause on it, gather information to figure out what is the best pathway forward. Fundamentally, we cannot have people's Fourth Amendment rights violated."

Abbott pushed back on the idea that the funding freeze was politically timed to the election, saying he views it as a legal matter.

"I view it as a legal issue, and I'm looking at it from the perspective of the Fourth Amendment, the right to privacy," Abbott said. "Some people's privacy is being invaded by these Flock cameras. We've got to find a solution for it."

---

The city has advertised this transparency portal in both of their Flock presentations this year. I checked it out myself the first time around. They probably sat in a council meeting and took a picture of the link or something.

That being said, I'm just pointing out a source of info. That user could very well be involved with the City somehow

I 100% got it from a simple Google search. It was in the city's presentation. https://blog.cstx.gov/wp-content/uploads/2026/07/5-Flock-Safety-License-Plater-Readers.pdf

mason12 said:

---

I'll admit that I will not answer your question directly. I'm not going to say who I know, or who I am related to, or where I work on the open internet. I also am not trying to hide behind an anonymous username. I really just don't want to dox myself. I have been to many TexAgs meetups over the years (lunches and dinners hosted by Trouble, Billucci Hours at The Tap, Preseason Kickoffs, crawfish boils, radio shows). By engaging in TexAgs I hope to add value to conversations while also learning things from others. If we ever meet in person, even if we disagree on things, I hope we can have a cordial conversation.

---

No, I definitely wouldn't expect you to say who you are. But, some type of disclosure to show that you aren't part of the basic citizenry would be nice, so people can put your post into perspective.

If a councilman, police chief, officer, or anyone else wishes to post here, I think we'd all be happy to have them. And Id respect their choice to stay anonymous. So long as they weren't here trying to sway public opinion, without disclosing a conflict of interest.