AI Compliance & Privacy
Who builds this, where it's built, and what you're responsible for when an AI talks on your license.
Haloid is 100% U.S.-owned and operated, with absolutely zero foreign interest.
Industrial and government espionage are major concerns for our clients. Our software is designed, coded, and supported in the United States. No offshore development shops, no foreign contractors on the codebase, and no third-party team you've never heard of handling the parts nobody else wanted. The people who write our software work for Haloid.
Most of what we do is to keep your systems safe from interference is kept offline; and we are happy to have this conversation with your compliance team during the scope phase.
CAGE: 9ZT38
Selling to government
Haloid is already on the other side of public procurement. We're registered with the codes above, we're a BBB Accredited Business and a member of the Enterprise Wireless Alliance, and prioritizing the needs of law enforcement, public safety, and military buyers is one of our nine core values.
That means we know how to produce the paperwork, respond to a solicitation, and price something so it survives a budget cycle. It also means hard questions about sourcing are routine here, and we're glad to answer them.
Buying commercially instead? You get the same process without the procurement paperwork. Most of our commercial customers want the same three things answered that the agencies do:
- Who has access to what goes over the channel
- What happens to recordings, if there are any
- Who is on the hook when something goes wrong
You'll get all three answered in writing during scoping, before anything is installed.
FCC and your license
One of our nine core values is that we respect the airwaves and demand our clients do the same. Here is what that means when an AI is the one talking.
You are the licensee. Everything transmitted under your callsign is your responsibility, and that doesn't change because the words came from a machine. An AI on your channel is your station transmitting. FCC rules are explicit that a licensee cannot sign that duty over to a vendor, so we won't pretend otherwise.
What that means in practice:
- Station identification requirements do not go away.
- Unless the station qualifies for unattended operation, you need a control point - a staffed position where someone can turn the transmitter on and off at will.
- The integration operates inside your existing authorization. We won't put you on frequencies or power levels you aren't licensed for.
- Unprompted transmission by the AI carries real licensing implications, so it stays off unless you ask for it and understand what you're turning on.
- Keep transmissions short. Your license requires efficient use of the channel, and a chatty assistant on a shared frequency is a compliance problem as well as an annoyance.
- What the AI talks about matters. Your authorization covers communications related to the activities you're licensed for, not general conversation.
Need licensing work? We already do it. FCC licensing sits under Haloid Consulting, and we've handled licensing engagements for commercial clients. A gap found during scoping is something we can help with rather than something that stops the project.
Outside the United States, different rules apply. This page describes US regulation because that is where most of our customers operate. If your radios are licensed somewhere else, your own national regulator sets the requirements and we scope against those instead. The principle does not change: an AI on your channel is your station transmitting.
We don't defeat encryption. If your traffic is encrypted end to end, an AI can't process it without being decrypted somewhere in the path. That's a decision to make deliberately and in the open, before deployment. For some agencies the right answer is that the AI stays off encrypted talkgroups entirely, and that's a perfectly good outcome.
Recording, retention, and consent
Call logging and transcription create records, and records have rules. Recording law varies by state. Public agencies carry retention obligations that private companies don't. Some organizations are required to keep this material, and some are required not to.
Logging is off by default. Decide with your counsel what you're permitted to record and how long you have to keep it, and we'll configure to match. We won't make that call for you, and we won't quietly switch it on because it demos well.
Law enforcement. If the AI touches criminal justice information, CJIS requirements apply. We address that during scoping, not after a purchase order, because it changes the architecture and not just the paperwork.
Personnel and labor considerations. Recording a channel your employees use all day can carry obligations under your own policies or bargaining agreements. Worth checking before rollout, not after the first grievance.
Need a formal review rather than a deployment answer? Compliance & Risk Reviews are a standing Haloid Consulting service, separate from this integration.
Bring your requirements to the first call
Have sourcing restrictions, retention rules, or a compliance framework you need to satisfy? Say so up front. It's far cheaper to design around than to retrofit.