Protecting Personal Information on the Air: What Should Never Be Broadcast in the Clear

The radio is the most public thing your agency owns. Most public safety voice traffic still travels unencrypted, which means anyone with an inexpensive scanner, a phone app, or an internet feed can hear it in real time. That is fine for most of what crews say. It is a serious problem when the words leaving the microphone include a patient condition, a full name tied to a sensitive circumstance, or the location of someone who is trying not to be found. This guide walks through what should never go out in the clear, why, and the practical habits that keep sensitive detail off the air without waiting on an encryption project.

In this guide
  1. Assume someone is always listening
  2. What should not go out in the clear
  3. The duties behind the habit
  4. Techniques that need no encryption
  5. When encryption is the right tool
  6. Minors, victims, and protected persons
  7. Building it into training and policy
  8. Quick guidance and a do-not-broadcast list

Assume someone is always listening

The starting point is simple and uncomfortable: unless your traffic is on an encrypted talkgroup, treat every transmission as public. This is not a warning about a rare hacker. It is the ordinary state of things. Consumer scanners are cheap and widely sold. Phone applications stream many agencies live. Websites aggregate feeds from volunteers who point receivers at local systems and rebroadcast them worldwide. A transmission that lasts three seconds can be recorded, replayed, clipped, and shared long after the call clears.

That audience is not hostile by default. It includes hobbyists, journalists, neighbors, family members waiting for news, and people who simply find the traffic interesting. But it can also include the estranged partner of a person you are transporting, the parent a court has ordered to stay away, or someone looking for a reason to harass. You do not get to choose who is on the other end. So the discipline has to assume the worst listener is present on every channel, every time.

The good news is that most radio traffic does not need protecting. Unit numbers, general locations, staging instructions, apparatus movements, and routine status changes are operational and appropriate to say out loud. The problem is narrow and specific: a small set of information categories that, once spoken, cannot be recalled and can cause real harm. Knowing exactly what those categories are is what lets a crew move fast on everything else.

What should not go out in the clear

Sensitive information is easier to manage when you can name the categories out loud. These are the ones that most often cause trouble when they leave the microphone:

Notice that most of these are not single facts but combinations. A first name is low risk. A first name plus a street plus a medical detail is a dossier. The habit worth building is to hear those combinations forming in your own transmission and break them apart before they go out.

The combination is the risk

No single identifier is usually dangerous on its own. Danger comes from stacking them: name plus address, condition plus location, vehicle plus destination. When you catch two or more identifiers landing in the same transmission, that is the moment to move the detail off the air.

The duties behind the habit

This is not only good manners. Several overlapping duties push in the same direction, and it helps to understand them at a general level rather than reciting statutes.

Health information privacy. Agencies that provide medical care operate under privacy obligations covering how they handle a patient's health information. Those obligations do not evaporate because the information is spoken instead of written. Broadcasting clinical detail to an open channel is a disclosure, and disclosures are exactly what those rules govern. The precise requirements vary by jurisdiction and by the type of entity, so your agency's privacy officer or legal counsel is the authority for your situation. The general principle is durable: share the minimum necessary, and do not put protected health information where uninvolved people can receive it.

Agency policy. Most agencies already have communications and records policies that address privacy, professionalism, and channel use. When those policies exist, following them is not optional, and when they are silent on something in this article, that is a gap worth closing rather than a permission to broadcast freely.

Professional responsibility. Beyond any specific rule, there is the plain duty of care that public safety professionals owe the people they serve. A patient in the worst hour of their life did not agree to have their crisis narrated to a global audience. Protecting that dignity is part of the job even where no statute names it.

A fact-check note is worth making here: this article does not cite specific laws, penalties, or numbers, because those differ by region and change over time. If you need to know exactly what applies to your agency, confirm it with your own legal counsel or privacy officer. The behaviors described below are sound regardless of which framework governs you.

Techniques that need no encryption

Encryption is one tool, and it is not the first one. Long before an agency changes its radio system, crews can protect sensitive information with technique alone. These methods cost nothing and work today.

These habits share a theme. The radio is for coordinating the response; the sensitive specifics belong on a channel where you can control who receives them. Getting a crew fluent in that distinction removes most of the risk without any equipment change.

Practice the switch, not just the rule

Crews will not reach for the phone under stress unless the move is automatic. Rehearse the handoff in training until "go to phone" is a reflex, the same way you rehearse a mayday. A technique that only exists in a policy binder does not protect anyone at three in the morning.

When encryption is the right tool

Sometimes technique is not enough, and full encryption of a channel is the correct answer. Tactical operations where a suspect could exploit overheard traffic, sensitive investigative work, and channels that routinely carry protected information are common candidates. Encryption removes the open audience entirely, which is exactly what those situations demand.

Encryption also carries a real cost that agencies should weigh honestly: interoperability. When a channel is encrypted, only radios provisioned with the correct keys can hear it. That can complicate mutual aid, since a neighboring agency responding to your incident may not be able to monitor your encrypted talkgroup. It can slow coordination with partners who are not on your system. It also removes the transparency that some communities and journalists value, which is a policy conversation in its own right, not just a technical one. We reference these tradeoffs in general terms here; the specifics depend on your radio system, your region's shared channels, and your mutual aid agreements.

The practical stance is that encryption and technique are not competitors. A well run agency uses encryption where the mission requires it and disciplined off-air habits everywhere else. Encrypting one tactical talkgroup does not excuse broadcasting a patient's condition on the dispatch channel, and being careful on dispatch does not remove the need for a protected tactical channel. Decide which channels need which tool as a deliberate policy choice, not by accident.

Minors, victims, and protected persons

A few categories deserve special mention because the harm from getting them wrong is severe and often permanent.

Minors. Anything identifying a child, a child's injuries, a child's school, or the circumstances of an incident involving a child should be treated as off-air by default. Children cannot consent, they cannot protect themselves from a listener, and the consequences of exposure can follow them for years. When you must coordinate about a minor, coordinate by phone.

Domestic violence and stalking situations. The location of a survivor is frequently the exact thing an abuser is trying to learn. Broadcasting an address, a shelter location, or a survivor's movements can directly enable an attack. Treat these locations as protected information and pass them privately.

Protected persons. Some individuals have specific legal or safety reasons that their address and movements stay confidential. Your agency may not always know who falls into this category, which is one more reason to keep the default cautious: minimize identifiers for everyone rather than trying to remember who is special.

Behavioral and mental health calls. A psychiatric crisis is protected health information and also a moment of profound vulnerability. The person may be a neighbor, a coworker, or a member of your own community who will still be living here next week. Naming them and their crisis on an open channel is a lasting injury on top of the emergency itself.

Building it into training and policy

None of this holds without structure. Individual good judgment is real but it is not a system, and it fails on the busy night when everyone is tired. The habit has to live in written policy and repeated training.

The goal is a culture where reaching for the phone with sensitive detail is as normal as putting on a seatbelt. That culture is built through repetition and modeling, not through a single memo.

Quick guidance and a do-not-broadcast list

Bringing it together, here is the practical short version. When you key up, ask yourself one question: could a stranger use what I am about to say to identify, locate, or harm someone? If the answer is yes, move it off the air. Coordinate the response on the radio; pass the sensitive specifics by phone or a protected channel; minimize identifiers everywhere; and confirm your agency's own policy and legal counsel for the requirements that bind you specifically.

The do-not-broadcast list, in plain terms:

When any of these come up, the move is the same: say the minimum on the radio, then go to phone or a secure channel for the rest. It is a small habit that prevents a large and permanent kind of harm.

Keep the standard where the crew can find it

A communications privacy standard only works if the do-not-broadcast list and the off-air procedures live somewhere crews actually reach for them, and if new members get trained on both from day one. RunBoard keeps your SOPs, policies, and training records organized in one place, so the standard stays current, every member can pull it up in seconds, and completion is easy to track.