City Council says Troy police gave incomplete data from surveillance cameras 11%

By Jesse Taylor7%

7/31/2026, 12:51:05 PM

BS Summary: This article contains 16 faulty reasoning types, including Negativity Bias, Representativeness Heuristic, and Self-Serving Bias, with Confirmation Bias as the most egregious example at 9.3% saturation with 62 hits. Analysis detected 480 faulty-reasoning hits from 665 analyzed words, generating a BS Score of 22.7% and a BS Rank of 11% (22,877 of 25,460 articles). This article is better (less manipulative) than 89.90% of the article peer group.

TROY  City Council member Noreen McKee says the Troy Police Department provided incomplete information that lawmakers asked for as they deliberate how long the law enforcement agency can hold onto video recordings and license plate data made by Flock Safety cameras stationed around the city. 
Mckee, who chairs the council’s public safety committee, said the department turned over only a fraction of the data the devices collected during a recent 60-day period for the purpose of investigating criminal activity. 
The Democrats who hold all the seats on the City Council asked for the data as they consider whether to set a 48-hour limit on the amount of time police can keep data gathered by the machines. 
Currently, the information is stored for 30 days. 
The proposal has been a source of contention between Mayor Carmella Mantello, a Republican, and the council. 
Mantello and police say the devices are a useful tool for fighting crime, but lawmakers say they pose a potential privacy infringement. 
After the legislation was proposed in May, the mayor and the council reached an agreement on a 60-day pause so the Troy Police Department could gather data on how many crimes were reported more than 48 hours after they took place, a key piece of information that would influence the final version of the legislation, McKee said. 
The data collected during the 60 days was given to the council Wednesday, according to McKee, who said Friday that it does not adequately answer how many crimes were reported more than 48 hours after they took place. 
She said complete data was only turned over for only 30 of the 81 cases in which police used information collected by the cameras. 
Council President Susan Steele agreed that data was incomplete, saying lawmakers needed the full picture in order to finalize the legislation. 
But Mantello and Police Chief Daniel DeWolf say the data provided is exactly what was requested. 
“The information was available for review, but they were too lazy to review it in its entirety,” the mayor said. 
Mckee, in an email, told the police department to provide the information she claims was missing, including dispositions and case numbers, by Aug. 
7. 
“Without complete data for all 81 cases, it is impossible to determine how many were reported more than 48 hours after the crime occurred,” she wrote. 
But DeWolf wrote back that she was given exactly what was requested. 
“The police department is providing you with the requested information and additional information that we believe shows even more transparency,” DeWolf’s email states. 
Mantello, in a separate statement, said McKee “specifically requested data indicating whether each of the 81 incidents resulted in an investigation or an arrest.” 
She said the information provided to the council is “straightforward.” 
“The report reflected exactly what was requested. 
There was no attempt to conceal, omit, or withhold information. 
The City Council received all 826 [automated license plate readers] searches conducted during the audit period,” she said. 
The City Council was provided with two spreadsheets of data collected from Flock cameras as well as an explanation of the data’s findings and a table detailing automated license plate reader tracking by case number. 
McKee said she did not know whether the data in the spreadsheets represented all 81 cases. 
The police department’s report indicates officers searched Flock camera data 826 times during the 60 days. 
According to the report, over 115 searches were conducted to identify the driver responsible for a July 4 hit-and-run incident, which made up nearly 14 percent of the department’s total 60-day search activity. 
The report’s narrative said that given the narrow 60-day window, the data should not “be viewed as representative of our typical long-term data retrieval timelines.” 
Mckee said the public safety committee will meet Aug. 20 to discuss the information the council has been provided. 
She is confident the current 30-day retention of data collected by Flock cameras will be reduced. 
Confirmation Bias
9.3%
Anchoring Bias
3.8%
Availability Heuristic
3.6%
Representativeness Heuristic
7.7%
Hindsight Bias
0%
Overconfidence Bias
3.9%
Framing Effect
3.3%
Loss Aversion
0%
Status Quo Bias
0%
Sunk Cost Effect
0%
Optimism Bias
3.9%
Pessimism Bias
0%
Negativity Bias
8.7%
Self-Serving Bias
7.2%
Fundamental Attribution Error
3%
Actor-Observer Bias
0%
In-Group Bias
0%
Out-Group Homogeneity Bias
0%
Halo Effect
3.5%
Horn Effect
0%
Dunning-Kruger Effect
0%
Recency Bias
0%
Primacy Effect
0%
Blind-Spot Bias
2.4%
Ad Hominem
3%
Straw Man
0%
Appeal to Authority
0%
False Dilemma
3.9%
Slippery Slope
0%
Circular Reasoning
0%
Hasty Generalization
0%
Red Herring
0%
Bandwagon
0%
Appeal to Emotion
0%
Begging the Question
1.5%
Post Hoc (False Cause)
0%
Tu Quoque
0%
Burden of Proof
0%
Appeal to Nature
0%
Composition/Division
0%
Anecdotal
0%
No True Scotsman
0%
Ambiguity (Equivocation)
0%
Gambler’s Fallacy
0%
Middle Ground
0%
Personal Incredulity
0%
Special Pleading
0%
Genetic Fallacy
0%
Unattributed Quote
0%
Quote-first Misdirection
3.5%
Biased Writer Voice
0%
Indoctrination
0%
Politically Left Leaning Bias
0%
Politically Right Leaning Bias
0%
Attempt to Sell a Product or Service
0%

665 words analyzed.

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.