If you’ve followed the Flock Safety license plate reader posts on this blog, you already know the pattern: a private company sells local government a tool framed as public safety or civic improvement, the contract gets signed with little or no public vote, and residents find out what they’re actually paying for only after someone starts asking questions. Zencity follows the same playbook, but it’s dressed up differently. Instead of cameras on the roadway, it’s software that reads what you post online.
What Zencity says it is
Zencity markets itself as “the platform for community trust.” Its pitch to city councils, county governments, and police departments is simple: run surveys, measure resident satisfaction, and use that data to make better budget and policy decisions. The company says it serves around 400 local government customers, including cities, counties, and law enforcement agencies. On paper, that sounds like a reasonable use of technology, a faster, more scientific version of the town hall meeting.
That framing is accurate as far as it goes. But it’s not the whole product.
What the product actually does
Underneath the survey tools is a social media monitoring system. Zencity scans public posts, comments, and online chatter across platforms to build “sentiment” dashboards for city officials and police leadership. It doesn’t just count how many people filled out a satisfaction survey. It analyzes what residents are already saying online, whether or not they ever agreed to be part of any survey, and sorts that activity into categories like supportive or critical.
Zencity also runs targeted digital advertising. According to the company’s own CEO, Zencity buys ads on Meta, Google, and X aimed at specific residents based on their demographic information, then uses those ads to solicit input. That means a government agency is using the same commercial ad-targeting infrastructure that follows you around the internet for retail products, except the client buying the ad space is your local police department or city government.
How this has played out in practice
This isn’t a hypothetical risk. It has already caused real friction in several cities that adopted the tool.
Pittsburgh. City council members learned, a full year after the fact, that the Peduto administration had been using Zencity without any public discussion of guidelines for its use. When the dashboard was reviewed, it wasn’t just tracking COVID-19 sentiment, the stated reason for the contract. It was also monitoring public sentiment around police reform and the George Floyd protests. Councilmember Erika Strassburger and others pushed back publicly, arguing that surveilling residents is not the same thing as engaging them.
Minneapolis. The city signed a three-year, $500,000 contract between the Minneapolis Police Department and Zencity, adopted after a federal consent decree had already found misconduct within MPD. Critics, including city council members and a retired Minneapolis resident, raised concerns specifically about a Zencity product called “Organic for Social Listening” and about the company’s use of commercial ad networks to target residents based on their online activity. Minneapolis is not currently using that specific product, but the contract drew renewed scrutiny over what the platform is capable of even when a city says it isn’t using every feature.
Douglas County, Colorado. The sheriff’s department signed a $72,000 contract and described the tool as a way to separate “the noisemakers” from residents with genuine concerns after a deputy-involved shooting. The ACLU responded that social media monitoring like this can cross into civil rights violations when departments use it to specifically track people criticizing police conduct.
Long Beach, California. The Electronic Frontier Foundation weighed in directly, warning that monitoring social media to gauge “resident sentiment” can easily slide into surveillance that targets individual activists, journalists, or entire community groups, not just aggregate public mood.
The consistent thread across all four cases: officials describe the tool narrowly when introducing it, the actual capability turns out to be broader, and the public finds out well after the contract is signed and the system is already running.
The company’s defense
Zencity’s standard response, and the one echoed by law enforcement leaders who defend the tool, is that it only analyzes information that’s already public. Nobody’s private messages are being read. If you post something publicly, the argument goes, you’ve already accepted that anyone can see it.
That’s true as a technical matter, but it sidesteps the actual concern. One person reading a public post is not the same thing as a government contractor aggregating, categorizing, and algorithmically flagging thousands of public posts to build a searchable sentiment profile of a community, sortable by topic, by area, and reportedly by how critical or supportive someone is of a given agency. Scale changes what a capability means. A neighbor noticing your car in the driveway is not the same as a plate reader network logging every driveway in the county. The same logic applies here.
It’s already in North Texas
This isn’t a coastal-city problem. In an interview about Zencity’s pricing model, the company’s own CEO named Denton, Texas, directly as a customer, alongside Austin and Sugar Land, noting that larger cities like Austin pay more than smaller ones like Denton. Houston is also a confirmed customer, brought on through a partnership with Microsoft to help the city manage data collection and analysis.
Denton is roughly 45 minutes from Cooke County. This is not a tool operating somewhere else in the country. It is already active in North Texas municipal government.
I could not find any public record confirming a Zencity contract with Cooke County, Gainesville, or any surrounding municipal government at the time of writing. That absence doesn’t mean one doesn’t exist. It means nobody has confirmed it publicly yet, which is exactly the same starting point the Flock Safety cameras were at before records requests surfaced what had actually been purchased and deployed. A Texas Public Information Act request to county or city government asking for contracts, invoices, or purchase orders referencing Zencity would settle the question either way.
Why this fits the larger pattern
Readers of this blog have seen this shape before. It doesn’t matter whether the technology is a camera on a road, a cell-site simulator in a patrol vehicle, or software reading a Nextdoor thread. The pattern repeats:
A vendor sells the tool using a public-benefit framing: catch criminals, save lives, improve city services, build community trust. The purchase gets funded or approved through a channel that avoids a direct public vote, seized asset forfeiture funds for Stingray devices, state grants and forfeiture money for Flock, a line-item software contract for Zencity. The agency emphasizes oversight and audit trails after the fact, once questions get asked, rather than publishing a policy before deployment. And the tool’s actual capability, once examined closely, turns out to be broader than the pitch that got it funded.
None of this means Zencity, Flock, or any of these tools have zero legitimate use. Cities do need to understand what residents think. Police do solve real crimes with plate reader footage. But “the tool can be useful” is not an argument for skipping public approval before it goes in. It’s an argument for asking the public first.
Right now, the standard practice runs backward. A vendor pitches an agency, a contract gets signed through a budget line or a grant or a forfeiture fund, the system goes live, and residents find out afterward what their government bought and what it’s actually capable of. Audit trails and usage policies published after the fact don’t undo that sequence. They just make the surveillance look accountable once it’s already running.
That should be inverted. Any company proposing to build this kind of data infrastructure, cameras logging every plate, software reading every public post, should have to get public sign-off before deployment, not offer transparency about it after the contract is signed and the hardware is installed. If the tool is as valuable as these companies claim, it should be able to survive a public vote before it goes live. If it can’t, that says something on its own.
If you want to know whether your local government has signed one of these contracts, the only reliable way to find out is to ask, formally, in writing, through a public records request. Waiting for a company’s CEO to casually mention your city in a podcast interview is not a substitute for public disclosure.