09/21/2026
For those who want to catch up on what we have so far.
The Flock Files: The Document So Far
Over the last several weeks, we have been working through Flock Safety records from Youngstown and surrounding Mahoning Valley communities one municipality at a time. We have posted the contracts, invoices, ordinances, meeting minutes, amendments, pricing documents and other records as we obtained them, along with summaries of what each document appears to establish and what questions it leaves unanswered.
Now we are putting the links together in one place.
The point is not simply to tell people what we think about Flock. The point is to put the underlying documentary record in front of the public so other people can read it, check our work, find things we missed, compare jurisdictions, make additional public-records requests and contribute their own findings.
What we have already learned is that these systems are not identical from town to town and neither are the records being produced. Some packets are only a handful of pages. Others run 19 or 26 pages. Yet even the most extensive productions still appear incomplete. We have found blank software-feature sections, referenced exhibits that were not included, contracts without clear FlockOS entitlement lists, invoices without underlying agreements, missing implementation materials and varying descriptions of network access and product capabilities.
That leaves us with two ongoing questions.
What documents are missing from the public record?
And perhaps more importantly:
what information did the governments themselves actually possess and understand when these systems were authorized?
We are continuing to pursue those questions. Follow-up requests will focus on the missing exhibits, implementation guides, software entitlements, sharing permissions, deployment records, installation and validation dates, renewal deadlines, complete ex*****on packages, policies, audits and communications surrounding the approval and operation of these systems.
But there is another front that deserves much more attention: funding.
Hubbard and Cortland have reportedly not renewed their Flock systems because funding was not available. That should immediately get our attention.
If funding can stop or prevent renewal, then opposition does not have to be limited to debating the technology after it has already been installed. Residents can also scrutinize the appropriations, renewal votes, grant applications, operating accounts, ARP allocations, police budgets and other funding streams that keep these systems alive.
Youngstown is a good example. The initial Flock deployment was supported through American Rescue Plan allocations from council wards, while later costs were expected to come from police operating funds and other available sources. That means the surveillance system is not some abstract technological inevitability. It requires money and it requires appropriations. It also requires officials to keep choosing to pay for it.
And choices can be challenged.
That is an area where we would especially encourage others to dig in:
Who controls the funding?
When does the next appropriation occur?
When does the contract renew?
What notice is required to prevent renewal?
Can funding be withheld?
What account is paying for it?
Are grants involved?
Does council have to vote again?
Can residents organize before the money is committed rather than after?
These are practical questions, and in some places they may prove more consequential than another abstract argument over whether Flock is “good” or “bad.”
So consider this post an open invitation.
Read the documents. Download them. Compare them. Search the language. Look at the invoices. Follow the money. Attend the meetings. File records requests. Check renewal dates. Ask what software features are actually enabled. Ask who the data is shared with. Ask whether the people voting on these systems were ever shown the complete capabilities of what they were buying.
And if you find something, share it.
We will continue doing the same.
This project is not finished. In many ways, the first round of documents has only shown us what questions to ask next.
The records belong to the public and the investigation can too.
City of Youngstown Flock Contract
https://drive.google.com/file/d/1Xlfl2jPJSTBsqZZBy6ZEf9pFH0GFL5K7/view?usp=sharing
Boardman Flock Contract
https://drive.google.com/file/d/1v8hd1MLwUF6W2YN5Jw6cY8Ex1qvGy9rW/view?usp=sharing
Youngstown Boardman Flock Camera Southern Blvd
https://drive.google.com/file/d/1rIMa0kFjY9vGmU6YY910YAbHMRu-APbz/view?usp=sharing
Canfield Flock Contract
https://drive.google.com/file/d/1k9UtsIjJKW3tae7KXtl2QlLIkPWn5oiq/view?usp=sharing
Poland Township Contract
https://drive.google.com/file/d/1Gc1-GC89NC2ZXNwAoWaO-3RWlPrIlUqq/view?usp=sharing
Austintown Contract
https://drive.google.com/file/d/1fQQNwTOFwm90AhEvqfQSHacvYzfM-pC8/view?usp=sharing
Flock Product and Services Description
https://docs.google.com/document/d/1FLp7nhBTJLvTVgx1NeMr8mipghx6VE8jCaG2pYrnVMQ/edit?usp=sharing
FlockOS Features & Description
https://docs.google.com/document/d/10aj_R-i3l1vhO8ztLsHvzIOHi1s3GyFDQ3tytQUhWE0/edit?usp=sharing