Fire Department Partially Encrypted

San Francisco Fire

San Francisco, California

How we verified this

SF County/City P25 (sid 6758), category 'San Francisco Fire': Control A1-A3 dispatch, commands, tacs, EMS dispatch are T (clear, many online); SFFD E7 'Arson' is T Enc. Checked ctid 220/trs. As of October 2026.

Checked against a primary source on 2026-10-14: radioreference.com . Status changes without notice: confirm on the live RadioReference database.

What you can do right now

Encryption Details

Encryption type Algorithm not published
Scope Some talkgroups encrypted; others remain in the clear.

Talkgroup Data Under Review

Our October 2026 audit removed 4 talkgroups because it could not tie them to San Francisco Fire by RadioReference category. Those found on RadioReference are filed under Hospital (3) and California Highway Patrol - Valley Division (1). Totals and percentages computed from that list are withheld.

No talkgroups remain on file for San Francisco Fire.

Current list: RadioReference, San Francisco County.

San Francisco County Context

Of the 2 public-safety agencies we track in San Francisco County, 2 are listed as partially encrypted and none as fully encrypted.

What This Means

This is a split system: certain talkgroups are encrypted while others remain in the clear, which means partial monitoring is still possible.

See encryption status nationwide Interactive map showing which US police departments have encrypted their radios. Open the encryption map →

Frequently Asked Questions

Is San Francisco Fire radio encrypted?

Only in part — San Francisco Fire encrypts some of its talkgroups while leaving others open (algorithm not published). This is a split system: certain talkgroups are encrypted while others remain in the clear, which means partial monitoring is still possible.

Can I listen to San Francisco Fire on a police scanner?

Partially. San Francisco Fire encrypts some of its talkgroups while leaving others open, so some channels may still be accessible. Check RadioReference for specific talkgroup status.

Why did San Francisco Fire encrypt their radio?

Ask why, and the answer is usually officer safety, sometimes operational security. What is harder to obtain is any documented case in San Francisco County where an open channel caused harm. The costs need no such documentation: reporting on the encrypted share of fire department response slows down, and mutual-aid coordination gets more awkward, immediately.

Can San Francisco Fire's encryption decision be reversed?

Yes. Whoever makes this call for an agency like San Francisco Fire can also unmake it; there's no technical lock-in. The approach that has worked elsewhere combines public-records requests, direct council pressure, and a coordinated local coalition.

What can I do about San Francisco Fire encryption?

Start local: show up when local officials discuss the budget for San Francisco Fire, and ask specifically why encryption was chosen over a delayed feed. File a FOIA request for recordings or policy documents, and connect with others nearby who want the same information — a coordinated ask carries more weight than an individual one.

Data source: RadioReference Wiki + checked against RadioReference database

Checked against a primary source on 2026-10-14 — see "How we verified this" above. Encryption status changes; confirm at RadioReference before relying on it.