More Twin Cities Law Enforcement Locking Down Police Radio Traffic, Stirring Debate

JASII

Memory Capacity
Joined
Apr 29, 2006
Messages
3,172
Reaction score
276

Scanner listeners in Minnesota said that while they understand the reasons for encryption, they are opposed to the trend of departments closing public police scanners.
The Minnesota Star Tribune
September 3, 2025 at 11:00AM
WFRK5BGIQBCPNASRCCRCIYIRTI.jpg

Both the Rochester Police Department and Olmsted County Sheriff's Office switched to encrypted channels for radio communication in 2025. Other cities including Minneapolis and St. Paul have also encrypted or plan to in the future. (Anthony Soufflé/The Minnesota Star Tribune)
For years, Ramsey County Sheriff Bob Fletcher advised his deputies to monitor the social media pages of devout police radio listeners for details on unfolding Minneapolis incidents in case a fleeing suspect fled east into his territory. Watching their real-time updates, he said, was easier than toggling to the scanner channels of a different jurisdiction on top of the six under his charge.
When Minneapolis encrypted its police radio traffic in May — preventing the public from listening in on radio traffic between officers and emergency dispatch — that resource largely went away.
“That’s been a big loss for us,” said Fletcher, a vocal opponent of encryption. “We used to have timely information.”
Departments that encrypt say they are trying to abide by federal requirements that prohibit publicly airing some information, and to ensure officers’ safety in situations where a suspect might be listening to the scanners.
Opponents, however, argue that it damages transparency and police accountability at a time when those issues remain under intense scrutiny following the murder of George Floyd by former Minneapolis police officer Derek Chauvin.
On Aug. 27, when Robin Westman attacked Annunciation Church, killing two children and injuring 21 other people in Minneapolis, encryption reduced what could be heard. Rick Abbott, the founder of the popular MN Crime Watch page on social media, said scanner traffic that morning gave “limited, fragmented details,” whereas in past cases, his page would have been able to provide a fuller account of the shooting more quickly.
The Hennepin County Sheriff’s Office was the first known Minnesota agency to encrypt in 2019. Police in Edina and St. Louis Park and sheriff’s offices in Carver, Dakota and Scott counties have also encrypted, and Anoka plans to do so in 2028.
This fall, St. Paul police will begin encrypting as well. Assistant Chief of Police Paul Ford said the department needs to encrypt to comply with the federal rules for radio traffic. It’s also to protect witness and victim information, he said.
“When you have the open airways and people are giving names and dates of birth and talking about violent and horrific crimes and really bad things that happen to people ... now you’re associating [that information] with a name of a victim or witnesses,” Ford said.
In Minneapolis, staff created a public 911 Emergency Incidents Dashboard to replace the information from scanners. It maps out where police are responding, the response time and block location, type of call, and how many squad cars are there. However, the dashboard doesn’t allow the data to be downloaded or even copied by users.

Related Coverage​



Minneapolis Community Safety Commissioner Toddrick Barnette said in a statement that encryption prevents the circulation of unverified early information on calls that is sometimes inaccurate.
“We will continue to keep the public informed about law enforcement activity … through our public channels and responsiveness to data requests,” Barnette said.
Emmanuel Mauleón, an associate professor of law at the University of Minnesota Law School, said that encryption can be particularly worrisome given the civil unrest following the murder of George Floyd — and the Trump administration’s dismissal of a consent-decree agreement between Minneapolis and the Department of Justice mandating police reform. The agreement with the state Department of Human Rights remains in place, and the city has said it will follow through on the federal consent decree despite the dismissal.
“Any time that you’re reducing a transparency function in a place where there is not a high degree of trust between certain communities and the police, on the back of getting rid of the federal consent decree ... I think that it would make any community that’s sort of reeling worried about, ‘What is this police department going to do?’” he said.
Steve Devine, chief technology officer for the Association of Public Safety Communications Officials, noted some examples of scanner information that should not be aired publicly: dates of birth, Social Security numbers, medical information and conviction/arrest history.
Devine said that encryption is “necessary for agencies to operate securely.”

Pushback and understanding​


Some Twin Cities residents said they feel left in the dark since encryption took place in Minneapolis and other cities.
Lynne Crockett regularly listened to the scanner to know what crimes were going on in her north Minneapolis neighborhood.
Since encryption, she’s left worrying when she hear sirens.
“It’s been a bit frustrating,” Crockett said. “When I could listen to the scanner, I knew whether or not it was something that was a big deal. Now I just hear a lot of sirens. To be honest, I’ve noticed more sirens than I was hearing before [encryption].”
Minneapolis’ encryption has also affected hugely popular social media pages such as Crime Watch and MN Crime, and their hundreds of thousands of followers.
Abbott, owner of MN Crime, said he thinks the new dashboard is “incredibly insufficient” compared to scanner audio, and that at times he’s seen errors on the dashboard.
Catherine Cowley listens to scanners and posts as a volunteer on the MN Crime Watchers group, which is associated with the page MN Crime. She said that about a day after Minneapolis encrypted, she saw city residents posting questions and observations about a particular shooting. Without the scanner, she and her fellow scanner listeners couldn’t provide real-time information.
“We saw no communication given to the public from MPD during or after this incident,” Cowley said. “What location? Does a threat exist? Is it over? Did you catch them? We never found out.”
While some residents voiced concern over encryption, some understood the points made by law enforcement.
Beth Pulkrabek, a resident of Hutchinson, Minn., said she agrees with encryption. She said she worried about scanner listeners swarming a crime scene, impeding police.
“I don’t want people inhibiting somebody trying to go save my mom and dad,” she said.
While more Minnesota law enforcement agencies support encryption, Fletcher is pushing back. He said that transparency is particularly important in law enforcement because each department has a monopoly on the service it provides, unlike in other fields. He argues there are alternatives to encryption, such as using electronic messages or a private channel to exchange restricted information.
“The citizens deserve to know what’s going on. That’s number one,” Fletcher said. “But they also deserve to know how fast the police are responding. That whole issue of monitoring police activity is more important than most activities.”
The sheriff added that he hasn’t seen evidence to support the argument that suspects might be listening to the scanner.
“I’ve been on the street thousands of hours and I can’t remember a call where we were jeopardized by having it go out on the air,” said Fletcher, who often livestreams his patrols on social media.
Non-encrypted radio has also helped law enforcement in some situations, according to Ramsey County deputy Patrick Scott.
Several months ago, a scanner listener helped Scott apprehend a murder suspect in St. Paul, he said. The caller said he saw someone who matched the description on the scanner.
“I was fairly close by, and spotted the kid walking down the street, and we got him into custody, recovered the gun, and he got charged with murder,” Scott said.

St. Paul details challenges of not encrypting​


In St. Paul, Ford said rioters used scanner information following Floyd’s murder.
“A lot of the violent protesters, they were listening to our radios, and they were operating and changing their tactics based on what we were doing,” Ford said.
He also described cases where suspects in high-level burglaries or drug dealing are listening, hindering police trying to apprehend them or endangering police or the public.
Megan Larson, a spokeswoman for the Hennepin County Sheriff’s Office, also explained that it “isn’t as easy as, ‘Change to channel 2.’” And the city of Minneapolis does not have “the personnel or the technology” for a different solution such as delaying public scanner audio or redacting private information in real time, a statement from the city said.
Just before Minneapolis police began encryption, MPD spokesman Sgt. Garrett Parten pointed to a case in July 2023 when a listener following the manhunt for a murder suspect beat officers to the suspect’s location and began livestreaming before officers could get there, tipping off the suspect.
The state sent out a document about a year ago explaining that agencies must at least have a plan for encrypting private information, and that full encryption is not required.
T. John Cunningham, assistant commissioner of the Minnesota Department of Public Safety, said in a statement that decisions about encryption are made by local law enforcement agencies.
Ramsey County’s emergency communications center is also planning to encrypt both of its data channels, which affects the rest of the county along with St. Paul. There are no plans to encrypt the county’s main channels, according to the center director.
Commissioner Barnette defended the decision to encrypt and said other large cities that are undergoing police reforms such as Chicago, Baltimore and New Orleans have also encrypted.
“Our reasons for encryption have not changed since May, and those reasons are the same as many other jurisdictions across the state and other major cities undertaking major community safety and police reform,” he said.
 

n0esc

Feed Provider
Joined
Dec 19, 2002
Messages
240
Reaction score
240
Location
SE MN EN33
So the short answer here seems to be a bunch of employees (Officers), refuse to educate and familiarize themselves with the technology they already have and develop the same level of muscle memory expected with any other tool on their duty belt to switch to any number or encrypted talkgroups virtually all state LE agencies have had since the buildout of ARMER started so they're taking the easy excuse out to just blanket encrypt and pointing fingers at vague CJIS requirements that they might run afoul of data privacy regulations if something is accidentally aired in the clear.

Something stinks in here.
 

ScanWI

MN & WI DB Admin
Database Admin
Joined
Feb 6, 2009
Messages
953
Reaction score
101
Location
Wisconsin
So if you read the CJIS Policy and the sections that they cite there is nothing in the section requiring any encryption for radio communication.

MN's Memo - https://www.mnecb.org/DocumentCente...raffic-Encryption-FAQ-Final_January-2025-PDF-

North Dakota's memo also changed wording from the policy to make it sound like it does.

North Dakota's Memo - https://www.ndit.nd.gov/sites/www/f...on/siec/radio-encryption-requirement-memo.pdf

Note their quote of section 5.13.1(Version 6.0 moves it to 5.20.1) and compare it to the actual policy. If you are familiar with reading statutes, which cops are supposed to be then you will see there is no actual black and white requirement.

The Actual CJIS Policy, version 6.0, some section numbers have changed since the memos came out.

If someone was actually able to corner someone and have them show the actual order or rule that is stating this requirement, it might be telling. What is the real drive behind encrypt it all?
 

ofd8001

Member
Premium Subscriber
Joined
Feb 6, 2004
Messages
8,268
Reaction score
1,397
Location
Louisville, KY
I think they are using the "non-disclosure" of NCIC information as an excuse. They could leave their main dispatch channels unencrypted and other things like Intel, Swat, tactical situations go to encrypted channels. Same with doing records checks.

If nothing else, perhaps do like they did here in Louisville - encrypt main dispatch channels, but do an official Broadcastify feed.

All that said, I can just see the situation of me and the kids outside and cops chasing a bad guy down my street. If I knew it was happening, we'd go inside.

I'd like to see research on how many more in-progress crimes have been foiled after encryption happened. Also how many fewer officer injuries there have been post-encryption.
 

kayn1n32008

ØÆSØ Say it, say 'ENCRYPTION'
Joined
Sep 20, 2008
Messages
7,376
Reaction score
2,321
Location
Sector 001
So the short answer here seems to be a bunch of employees (Officers), refuse to educate and familiarize themselves with the technology they already have and develop the same level of muscle memory expected with any other tool on their duty belt to switch to any number or encrypted talkgroups virtually all state LE agencies have had since the buildout of ARMER started so they're taking the easy excuse out to just blanket encrypt and pointing fingers at vague CJIS requirements that they might run afoul of data privacy regulations if something is accidentally aired in the clear.
Tell me you are not a cop, with out telling me you are not a cop.

Back in the day, the local police, when when major incident, or high speed chase kicked off(or entered their jurisdiction) would direct UNINVOLED officers to switch from an analogue dispatch channel to a digital provoice Tac Channel for the duration of the event. The INVOLVED units would remain on the dispatch channel.
Something stinks in here.
LMFAO. Nothing stinks, except the tears of the scanner whackers that now can't listen in.

"Just before Minneapolis police began encryption, MPD spokesman Sgt. Garrett Parten pointed to a case in July 2023 when a listener following the manhunt for a murder suspect beat officers to the suspect’s location and began livestreaming before officers could get there, tipping off the suspect."

Yeah, THIS is why agencies are encrypting. Stupid ****s that can't help themselves, that show up to scenes and knowingly, or even unknowingly, interfere with police doing their jobs.

Or the media decides to sensationalize a dying officers final words, as in the case of Cst Styles in Ontario a number of years ago.

Maybe if people were not stupid ****tards, getting in the way, and didn't blab about it, or tweet police actions second by second, and kept it to a hobby in their homes, they wouldn't feel the need to encrypt their comms.
 

n0esc

Feed Provider
Joined
Dec 19, 2002
Messages
240
Reaction score
240
Location
SE MN EN33
Tell me you are not a cop, with out telling me you are not a cop.

Back in the day, the local police, when when major incident, or high speed chase kicked off(or entered their jurisdiction) would direct UNINVOLED officers to switch from an analogue dispatch channel to a digital provoice Tac Channel for the duration of the event. The INVOLVED units would remain on the dispatch channel.

LMFAO. Nothing stinks, except the tears of the scanner whackers that now can't listen in.

"Just before Minneapolis police began encryption, MPD spokesman Sgt. Garrett Parten pointed to a case in July 2023 when a listener following the manhunt for a murder suspect beat officers to the suspect’s location and began livestreaming before officers could get there, tipping off the suspect."

Yeah, THIS is why agencies are encrypting. Stupid ****s that can't help themselves, that show up to scenes and knowingly, or even unknowingly, interfere with police doing their jobs.

Or the media decides to sensationalize a dying officers final words, as in the case of Cst Styles in Ontario a number of years ago.

Maybe if people were not stupid ****tards, getting in the way, and didn't blab about it, or tweet police actions second by second, and kept it to a hobby in their homes, they wouldn't feel the need to encrypt their comms.

Show me on the doll where they hurt you.

Let's go at it the other way. Tell me you're not from Minnesota, and have zero understanding of how the ARMER system works without telling me you're not from Minnesota and have no understanding of how it was designed.
 

ofd8001

Member
Premium Subscriber
Joined
Feb 6, 2004
Messages
8,268
Reaction score
1,397
Location
Louisville, KY
"Just before Minneapolis police began encryption, MPD spokesman Sgt. Garrett Parten pointed to a case in July 2023 when a listener following the manhunt for a murder suspect beat officers to the suspect’s location and began livestreaming before officers could get there, tipping off the suspect."

Yeah, THIS is why agencies are encrypting. Stupid ****s that can't help themselves, that show up to scenes and knowingly, or even unknowingly, interfere with police doing their jobs.

Or the media decides to sensationalize a dying officers final words, as in the case of Cst Styles in Ontario a number of years ago.

Maybe if people were not stupid ****tards, getting in the way, and didn't blab about it, or tweet police actions second by second, and kept it to a hobby in their homes, they wouldn't feel the need to encrypt their comms.

It's never a good idea to "shift gears" and change how you go about business based on one incident. And I'm sure Minnesota has laws regarding interfering with an on-going incident.

Seems to me there was a big hullabaloo in Minneapolis about the PD and ICE that was built on false information and speculation. Perhaps if the public could have listened-in, the truth could have been told.
 

kayn1n32008

ØÆSØ Say it, say 'ENCRYPTION'
Joined
Sep 20, 2008
Messages
7,376
Reaction score
2,321
Location
Sector 001
It's never a good idea to "shift gears" and change how you go about business based on one incident. And I'm sure Minnesota has laws regarding interfering with an on-going incident.

Seems to me there was a big hullabaloo in Minneapolis about the PD and ICE that was built on false information and speculation. Perhaps if the public could have listened-in, the truth could have been told.
Go FOIP the audio.
 

kayn1n32008

ØÆSØ Say it, say 'ENCRYPTION'
Joined
Sep 20, 2008
Messages
7,376
Reaction score
2,321
Location
Sector 001
Show me on the doll where they hurt you.

Let's go at it the other way. Tell me you're not from Minnesota, and have zero understanding of how the ARMER system works without telling me you're not from Minnesota and have no understanding of how it was designed.
Uh, it's a 'wide area' trunk system. Wide being relative, considering Minnesota isn't that big area wise.

Let me guess, and let me know if I'm close.

Local agencies have their own talk groups that have a local coverage class. Pobably their home county, and maybe each surrounding county.

State agencies probably have regional coverage classes, not knowing Minnesota, it is probably logicaly(to someone from Minnesota)

Then you have all the local, regional and state wide interop talkgroups. Some for LEO, some for Fire, some for Para medicine, some encrypted, some in the clear and some for all three to talk to each other. The local, and regional interops are also geographically limited.

That was a learning lesson out of the bridge collapse where the P16 system(I think it was still a P16 system at the time) worked as it was designed, EXCEPT in the rural areas, users were dragging the talkgroups that were being used at the collapse, to areas far away and busying out rural, low RF channel sites.

That learning lesson was one that was incorperated into the largest P25 system(by area covered and site count) system in North America. That learning lesson has probably been incorpersted in many other wide area trunking systems as well.

ARMER isn't a secret system, how a wide area 9600baud Motorola trunk radio system works isn't secret either.
 

n0esc

Feed Provider
Joined
Dec 19, 2002
Messages
240
Reaction score
240
Location
SE MN EN33
I'd ask you to show me on the doll where I hurt you, but I'd say it's pretty clear:

View attachment 189442

Would you like a cookie?

Or maybe a Snickers would be better.

I know it might come as a shock, but sometimes, just sometimes, hobbies intersect and overlap with professional occupations. My skin in the game is not "missing out on the hot neighborhood gossip" so some wacker nut-job or nosy neighbor can know what's going on every time they hear sirens.

My point aligns with many others, both quoted in the initial article, and has been thoroughly rehashed ad nauseum, which you sadly missed in your diatribe trying to prove how well you know how ARMER works just like any other trunked system. The nuance in it was the planning and implementation of TG layouts, radio and console programming, and ensuring compliance and cooperation from all agencies and users statewide to ensure that they weren't creating islands of incompatibility and communication breakdowns, but now a bunch of misguided and ill informed administrative desk pilots are using a misunderstood or at least misrepresented guideline to justify keeping non-sensitive communications encrypted because their end users might screw up and accidently transmit PII in the clear. Give me a break.
 

kc2asb

Member
Joined
Dec 31, 2015
Messages
1,639
Reaction score
2,318
Location
NYC Area


In Minneapolis, staff created a public 911 Emergency Incidents Dashboard to replace the information from scanners. It maps out where police are responding, the response time and block location, type of call, and how many squad cars are there. However, the dashboard doesn’t allow the data to be downloaded or even copied by users.
The "Dashboard" might not be completely useless, but it's pretty close. The right answer is delayed dispatch-only feeds, as Boston, Baltimore and Chicago have provided. ( Boston is on a 5 minute delay, Baltimore & Chicago - 30 minutes)
 

wogggieee

Member
Joined
Sep 30, 2005
Messages
1,426
Reaction score
131
Location
Hugo , MN
So the short answer here seems to be a bunch of employees (Officers), refuse to educate and familiarize themselves with the technology they already have and develop the same level of muscle memory expected with any other tool on their duty belt to switch to any number or encrypted talkgroups virtually all state LE agencies have had since the buildout of ARMER started so they're taking the easy excuse out to just blanket encrypt and pointing fingers at vague CJIS requirements that they might run afoul of data privacy regulations if something is accidentally aired in the clear.

Something stinks in here.
They finally have the excuse and the ability to do what they've wanted to do for years. If this were really about data privacy fire and EMS channels would have been encrypted a long time ago. I wouldn't be able to listen to MRCC while sitting in the regions ER to know what the trama team activation is about with details of the persons injuries.
 

n0esc

Feed Provider
Joined
Dec 19, 2002
Messages
240
Reaction score
240
Location
SE MN EN33
They finally have the excuse and the ability to do what they've wanted to do for years. If this were really about data privacy fire and EMS channels would have been encrypted a long time ago. I wouldn't be able to listen to MRCC while sitting in the regions ER to know what the trama team activation is about with details of the persons injuries.

That's the thing about this all that makes me scratch my head. HIPAA and the issues around data privacy for healthcare data have been around for almost 30 years, and for as afraid of the big ugly HIPAA monster that industry is, I agree with you, they ALL would have encrypted every single thing they could of a long time ago. Instead it feels like they all asked questions and fought to clarify rules about exactly what they could and could not transmit in the clear, and provided training to their pre-hospital and communications areas about that.

A few are getting around to encryption now, but seemingly in no real hurry to do it. FBI comes out with updated CJIS guidance that reads pretty similarly to PHI/PII data privacy and LE jumps on it like a dog with a bone.
 
Last edited:

ofd8001

Member
Premium Subscriber
Joined
Feb 6, 2004
Messages
8,268
Reaction score
1,397
Location
Louisville, KY
Actions always speak louder than words when it comes to claiming to be transparent. The dashboard allows them to say they are transparent, even though information there is scant. How are citizens to know from it what dispositions were and how significant a problem may or may not be.

That said, perhaps we could be a tad more respectful when someone posts something here we don't like or agree with.
 

stmills

Member
Joined
Dec 19, 2002
Messages
1,140
Reaction score
153
Location
Twin Cites Area MN
That's the thing about this all that makes me scratch my head. HIPAA and the issues around data privacy for healthcare data have been around for almost 30 years, and for as afraid of the big ugly HIPAA monster that industry is, I agree with you, they ALL would have encrypted every single thing they could of a long time ago. Instead it feels like they all asked questions and fought to clarify rules about exactly what they could and could not transmit in the clear, and provided training to their pre-hospital and communications areas about that.

A few are getting around to encryption now, but seemingly in no real hurry to do it. FBI comes out with updated CJIS guidance that reads pretty similarly to PHI/PII data privacy and LE jumps on it like a dog with a bone.
1. When HIPAA came out most of EMS was using analog VHF and UHF and encryption was a different animal to implement compared to what it is today with large area P25 Trunked systems.
2. A few years back on an investors call Motorola identified encryption for law enforcement radios as a market for growth they were looking to capitalize on. Amazingly they started marketing the need for LE encryption and providing the talking points to LE leaders - a few years into this marketing campaign a new guideline comes out that pushes more LE to encrypt. I believe this push to encryption is being driven more by corporate profits than true needs.
 

n0esc

Feed Provider
Joined
Dec 19, 2002
Messages
240
Reaction score
240
Location
SE MN EN33
1. When HIPAA came out most of EMS was using analog VHF and UHF and encryption was a different animal to implement compared to what it is today with large area P25 Trunked systems.
2. A few years back on an investors call Motorola identified encryption for law enforcement radios as a market for growth they were looking to capitalize on. Amazingly they started marketing the need for LE encryption and providing the talking points to LE leaders - a few years into this marketing campaign a new guideline comes out that pushes more LE to encrypt. I believe this push to encryption is being driven more by corporate profits than true needs.
That's just crazy talk there. Motorola would absolutely never package and market a product to its customer base purely as an attempt to increase profit margins and sales. /s

I mean it's not like they would line item out every single component to make a radio work as a necessary separate purchasable or anything? Or end of life perfectly serviceable radio models in favor of unnecessary features and functions also locked behind additional programming paywalls.
 

ofd8001

Member
Premium Subscriber
Joined
Feb 6, 2004
Messages
8,268
Reaction score
1,397
Location
Louisville, KY
Back in about 2008/2009 when Louisville-Jefferson County converted to a P25 trunked system, a lot of radios had to be purchased, something like 5,000. Rightfully so, they were pretty frugal on options. Very few radios got the AES option, which cost $475 back then.

Motorola did sell us the ADP encryption option at a mere $10 per unit. This would be for EMS, giving police encryption for tactical situations, etc. Problem then was only Motorola offered ADP, which locked us in to buying their stuff when replacement became necessary.

I understand that these days AES encryption is on the order of $1K per unit. Media seems to overlook, or doesn't know enough to ask, how much encrypting radios cost.

Fortunately Minnesota has a good system where they patch things like pursuits on an L TAC channel, so the left hand knows what the right hand is doing. Unfortunately around here "they" haven't created any best practices for similar events. (They do have channels that can be used, but no one has decried their use in pursuits.)
 

tadsmith

Member
Premium Subscriber
Joined
Jan 19, 2018
Messages
44
Reaction score
29
They pick and choose what parts of the memos that they want to enforce.

Transmitting FBI CJI on an ARMER talkgroup that is encrypted with DES-OFB or ADP does not meet the FBI requirement. A talkgroup must use Advanced Encryption Standard (AES) encryption to meet FBI CJIS Security Policy requirements.

Ramsey County, Hennepin County, Dakota County, Minneapolis Police all use DES-OFB. Washington County uses ADP which is even worse.

AES is pretty much limited to federal agencies on ARMER.
 

mmckenna

I ♥ Ø
Joined
Jul 27, 2005
Messages
27,133
Reaction score
32,410
Location
United States
I understand that these days AES encryption is on the order of $1K per unit. Media seems to overlook, or doesn't know enough to ask, how much encrypting radios cost.

Harris single key AES-256 on the XL-200's is $0.01 per radio. Part number XS-PL9E if you want to look it up.
Motorola AES-256 + ADP is about $381 on the APX-Next. Part number Q629BD, if you want to look that up, also. With better contract pricing, it can probably be had cheaper.
 
Top