8 Ways To Take Down Flock Without A Sawzall:
1. Demand An Audit
Most cities never independently audit whether Flock cameras in town actually reduce crime. Ask your city council to show evidence that these cameras reduced violent crime. Make them prove it. They usually can't.
2. Find Out When the Contract Expires
Every Flock camera program has a contract renewal date. Use FOIAs to request the original contract, all amendments, renewal dates, and termination clauses.
This one is SO important because we must organize BEFORE renewal, not AFTER the cameras go up.
3. Demand the Privacy Impact Assessment
Before deploying any type of surveillance devices with public funds, many city governments are supposed to evaluate the privacy risks.
Ask for privacy Impact Assessment, civil liberties review, and constitutional analysis. If they never conducted one... Ask why not (they hate that.)
4. Show Up Before They Vote
Flock cameras aren't installed overnight. They usually require budget approval, council approval, contract approval. Use tools like "Citizen Portal" to setup automatic notifications for upcoming city council meetings. Speak before, not after installation.
5. Follow the Money
Want to know why your city suddenly wants Flock cameras? It's usually always grants or cronyism.
Ask for grant applications: DHS grants, DOJ grants, Homeland Security funding, ect. Surveillance programs begin because outside money make them "free."
6. Ask About Data Sharing
Every city should have to answer this question: "Exactly which agencies can search our city's license plate database?"
Ask for sharing agreements, MOUs, list of agencies with approval, and search logs. Most people think it's just local police. It rarely is, usually the feds too.
7. Audit Every Search
Public records requests aren't just for the contracts. You can publicly request every audit log showing who searched the Flock system and why.
Ask for date, user, reason for search and any case numbers. Abuse often shows up in the logs before it makes the news or a viral social media post.
8. Compare Crime Before & After
Download your city's crime data. Compare property and violent crime before and after Flock was installed.
If there's no meaningful change... Ask why taxpayers are still paying for it. If officials claim the cameras are effective, ask them to produce the evidence supporting continued funding.
A former Microsoft engineer has created a new text editor called TinyRetroPad, only 2.5KB in size
Dave Plummer, who created Windows Task Manager during his time at Microsoft, said Notepad was originally designed as a basic text editor, while WordPad handled more advanced formatting.
He believes Notepad has become too complicated over the years with features like AI writing tools.
TinyRetroPad is written in x86 assembly and based on Matt Power’s Tiny Editor (DTE). Despite its tiny size, it can open and save text files, change fonts, and print documents using Windows’ built-in features.
“No bloat. No telemetry. No nonsense. Just pure old school Windows done right.”
We've been quiet recently because Mark Goodwin and I have been working to write the most comprehensive investigation into Polymarket's origins and ambitions to date.
We found that Polymarket's "official" origin story, that Shayne Coplan founded the company alone in 2020 and then built "the company in his bathroom", is a lie. Polymarket really started years earlier as another company called TokenBnk that was deeply tied to Israeli interests, specifically a crypto company founded by Benjamin Netanyahu's niece and nephew. Coplan has actively tried to obfuscate this company from his story and it's not the only thing either.
In Part 1 of this two-part series, we unravel the real history of Polymarket, directly connecting the company to Peter Thiel's efforts to resurrect controversial DARPA programs from its now defunct Information Awareness Office. Polymarket appears to have been chosen by Thiel and his associates to succeed in resurrecting DARPA's Policy Analysis Market where another Thiel-linked company, Augur, had previously failed.
Stay tuned for Part 2, where we explore the current influence of prediction markets and Polymarket, including how an insidious effort to have prediction markets replace representative democracy as a governance model is already being slowly implemented by the White House.
Read Part 1 here: https://t.co/xTmU5RzoZz
I don’t know who’s behind @therealDeFlock but if @glangley is out here calling them a “terrorist organization,” that’s basically a five star review.
👇👇👇👇
🚨 Flock has a hidden weakness many don’t know: public records requests.
Activists have successfully forced at least 8 cities to shut down Flock programs, either by exposing unauthorized data access or showing the footage was publicly accessible.
One of the most effective ways to take down Flock cameras? FOIA/PRA requests.
Here’s a template to file one in your city:
To the Custodian of Records:
Pursuant to the (your state here) Public Records Act (your state's public records act code.), I request access to and copies of the following public records relating to the (your local police) Police Department’s surveillance camera network reportedly consisting of more than 2,600 cameras deployed throughout the city.
Please provide records covering the period January 1, 2020 through present unless otherwise specified.
1. Policies and Legal Authority
All policies, procedures, memoranda, directives, or legal analyses governing:
-The deployment and operation of surveillance cameras within __________
-Any legal justification for the program under federal or state constitutional law
-Policies governing Fourth Amendment considerations or privacy protections
-Any City Council ordinances or resolutions authorizing the camera network
2. Contracts and Vendors
All contracts, agreements, memoranda of understanding, purchase orders, or amendments with vendors or service providers related to:
-Surveillance cameras
-Automated license plate readers
-Real-time crime centers
-Video analytics, facial recognition, or artificial intelligence
-Data storage or cloud services used for camera footage
Please include vendor proposals, RFP responses, and bid documents.
3. Camera Locations
Records identifying:
-The number and location of cameras deployed
-Maps, GIS datasets, or inventories of surveillance devices
-Any classification of cameras as public, private-partner, or third-party integrated cameras
(If precise coordinates are withheld, provide generalized location records or district-level inventories.)
4. Data Retention and Access
All records describing:
-Video retention schedules
-Policies for deletion or archiving of footage
-Which agencies or departments have access to the camera network
-Any data sharing agreements with other agencies including but not limited to:
-(your state) Highway Patrol -Federal agencies (FBI, DHS, ICE, etc.) -Regional task forces
5. Private Camera Integration Programs
All records relating to programs that integrate privately owned cameras into the police network, including:
-Agreements with homeowners, businesses, or HOAs
-Terms of participation
-Data access rights granted to the police department
6. Surveillance Technology Capabilities
Records describing whether the system includes or supports:
-Facial recognition
-License plate recognition
-Behavioral analytics
-Crowd detection
-Real-time monitoring centers
7. Crime Reduction Claims
All records, reports, studies, or internal analyses supporting claims that the surveillance network caused reductions in crime, including:
-Statistical reports
-Internal evaluations
-Communications discussing the effectiveness of the system
8. Communications
Emails, memoranda, and internal communications between (your city) Police Department personnel, City officials, or vendors referencing:
-Expansion of the camera network
-Privacy concerns
-Public opposition or legal review
Search terms should include: “camera network”, “surveillance cameras”, “real time crime center”, "Aerodome", "Raven", “ALPR”, “Flock”, “facial recognition”, and “camera integration”.
Format
Please provide records in electronic format via email or download link.
If any records are withheld, please provide the specific statutory exemption relied upon and produce all reasonably segregable portions of responsive documents.
Fee Waiver
This request concerns matters of significant public interest involving government surveillance and constitutional rights, and any fees should be waived or minimized.
I look forward to your response within the statutory timeframe.
Ahead of mounting labor violations, the private prison contractor GEO Group says it should be granted qualified immunity--the same tactic the police use to shield their officers from police brutality claims.
The company argued that, because they operate on behalf of the government, they should be treated as a public servant and therefore should be offered the same protections that “shield public officials from liability for misconduct, even when they have broken the law.”
https://t.co/WzeEYhaaY2
BREAKING: The US Pentagon delayed publicly announcing US strikes on Iran until after the US stock market had closed at 4 PM ET on Friday, per NBC News.
The timing of the announcement was reportedly intended to "reduce the immediate impact on financial markets."
Patent number US20250104469A1.
This is a biometric system that scans people, compares against law enforcement/security databases, and alerts authorized personnel when a match is found.
Patent: https://t.co/HxokSZcSrx
By @Ford
The Mount Vernon City Council voted Wednesday to turn off the city’s Flock Safety cameras.
The vote was 4-1, with councilmembers Melissa Beaton and Mary Hudson absent.
https://t.co/znDPoxddh2
Flock Safety is one of the most contested surveillance technologies in the US right now and the story has accelerated significantly in 2026.
The basic product is an Automatic License Plate Reader network. Flock Safety cameras do not just record video. They capture, analyse, and store license plate data along with vehicle characteristics including roof racks and bumper stickers, creating searchable databases that law enforcement and private entities can access. 
The scale is significant. Flock has more than 12,000 clients across the US including more than 5,000 law enforcement agencies, HOAs, and businesses.  What started as neighbourhood security cameras became a nationwide surveillance network that most people never consented to or even knew existed.
The core controversy is data sharing. Dayton, Ohio found more than 7,000 cases of searches relating to immigration enforcement made by outside entities on their Flock data, which city officials called egregious violations of policy. The city covered the cameras with trash bags pending removal. 
EFF obtained datasets representing more than 12 million searches logged by more than 3,900 agencies and found agencies logged hundreds of searches related to political demonstrations including protest movements throughout 2025.  People attending protests were being tracked by license plate.
The backlash is now substantial. Between August 2021 and May 2026, 82 Flock contracts were terminated across 28 states, with the pace accelerating sharply in the last six months. 
The structural problem is deeper than any single misuse. Many cameras are privately owned by HOAs but connected to regional and national law enforcement networks, far beyond what residents originally agreed to when they approved neighbourhood security cameras. 
Over 22,000 law enforcement users have system access with minimal oversight on who searches the databases and why. 
The technology itself is not inherently malicious. It has solved real crimes. The problem is that a system installed to find stolen cars in a gated community is now feeding into federal immigration enforcement, political protest monitoring, and databases accessible by thousands of agencies with no warrant requirement and no notification to the people being tracked.
Your car’s location history is being logged, stored, and shared. You were never asked.
A Richmond County deputy has been arrested and fired after he is accused of misusing license plate readers.
The sheriff’s office conducted a routine audit of its Flock License Plate Reader (LPR) camera system on June 25.
#Surveillance#Privacy#DeFlock
https://t.co/RAT8dsLa5K
GM - These Mass Surveillance cameras go up in secret, then they can't even be proved to be effective for "safety".... the main justification by police.
FOIA the crime stats, if they even exist...
🚨 THE CEO OF FLOCK JUST SAID THE QUIET PART OUT LOUD — AND PEOPLE ARE LOSING IT
Remember when Flock cameras were only supposed to read license plates?
Apparently that's not enough anymore.
Now we're talking about AI that can find a vehicle from a simple description.
Microphones that are always listening for so called "sounds of distress."
Drones that can be launched automatically after a 911 call.
And camera networks that can follow movement across entire cities.
Every year the cameras get smarter.
The databases get bigger.
The AI gets more powerful.
And the amount of information being collected keeps growing.
Then came the comment that really got people's attention.
The CEO behind Flock, one of the largest camera networks in America reportedly compared people who map camera locations to terrorists.
Think about that for a second.
The cameras aren't the problem.
The people tracking the cameras are.
Some people see a tool that makes communities safer.
Others see a system that knows where you've been, where you are, and eventually where you're likely to go next.
If mapping Flock cameras makes you a "terrorist," what does that make the people putting cameras everywhere?
FLOCK IS FINAL piece for “NSA” SURVEILLANCE🚨. And am 99% certain that Flock Camera 📸 company deliberately refuses to implement MFA “MULTI FACTOR AUTHORIZATION” because MFA would block federal agents from using shared local police credentials to access the national surveillance grid.🚨🚨🚨⚠️⚠️⚠️the LACK of “MFA” is a FEATURE. It allows federal agents to access the system through "stolen" credentials without leaving a formal access trail. All these "hacked" accounts are cover stories for federal access.🚨🚨
And FLOCK serves the “NSA” . The NSA has collection programs its MISSING the vehicular movement data⚠️⚠️⚠️⬅️
• Phone metadata (Section 215)
• Internet traffic (PRISM)
• Email metadata (STELLAR WIND)
• Who you called (Section 215)
• What you searched (PRISM)
• Who you emailed (STELLAR WIND)
• Where you drove (Flock)
Flock is the missing piece of the NSA's domestic surveillance architecture. 🚨🚨
The federal government requires MFA for all federal agencies. MFA is the "gold standard" of cybersecurity protection🚨🚨🚨
Flock knows this. Flock's customers are police departments handling sensitive criminal justice data. Any competent security engineer would implement MFA.
🚨🚨
But Flock's lack of mandatory MFA proves its INTENTIONAL which allowed law enforcement to see other agencies' Flock data through improper password sharing🚨🚨
Congressman Krishnamoorthi and Senator Wyden sent a letter to the FTC documenting that Flock does not require MFA. The letter states that "at least 35 Flock customer accounts have reportedly had passwords stolen by hackers."⚠️
these are NOT hacks at all. They are intentional backdoors. Flock deliberately does not implement MFA because MFA would prevent federal agents from using shared credentials. The "35 hacked accounts" reported by Hudson Rock are not the work of random criminals - they are the visible footprint of federal agents accessing the system through credential sharing arrangements with local police. 🚨🚨🚨
The way it works is when a federal agent uses a local officer's credentials, it looks like a hack. Thats so Flock can blame "hackers" while the data flows to federal agencies.⚠️⚠️ It is an intentional architecture that enables federal surveillance through credential sharing while providing plausible deniability for both Flock and the federal government.
So the "hacks" and the "inadvertent" opt-ins are the same mechanism. They are both designed to look like accidents while facilitating intentional data sharing. The system is designed to fail in a way that benefits federal surveillance.🚨🚨
Articles state the proof …🚨
It says “ When a local agency accepts an invitation from another agency, they are "automatically opted in" to the national network”
You can see the Architecture:
• No MFA = credential sharing is possible
• "Automatic opt-in" = national data sharing is the default
• "Hacked" accounts = are actually federal access without formal agreements
• CBP "National Lookup Search" = federal agents query the entire network through a single local agency
The system is designed to fail in ways that facilitate federal surveillance while providing plausible deniability for both Flock and the federal government.
https://t.co/p1B7jjSfiL
https://t.co/HC651CzSpj
https://t.co/nY8qe7ij8X