San Francisco Fire
San Francisco, California
Encryption Details
Verified Talkgroup Data
View 4 talkgroups
| DEC | Alpha Tag | Description | Status |
|---|---|---|---|
| 1413 | SFGH | San Francisco General Hospital | Encrypted |
| 1414 | SFGH BASE | San Francisco General Hospital - Base | Encrypted |
| 1420 | VA | San Francisco VA Medical Center | Encrypted |
| 783 | VA White | Valley White - Stockton (62) / Tracy (103) / Amador (94) / San Andreas (49) | Encrypted |
Verification Status
We do have per-talkgroup data for San Francisco Fire from the RadioReference API, and used it to set the encryption scope shown above — but no additional human-reviewed source (a live feed check or a dated news account) has been recorded for this record, so treat it as a data-quality correction rather than an independently confirmed verification. Check the live RadioReference database directly for current status.
If you monitor San Francisco Fire directly or have more current information, the fastest way to fix this is to update the RadioReference Wiki entry — our data pulls from there and from the RadioReference API on a regular refresh cycle.
San Francisco County Context
Of the 2 public-safety agencies we track in San Francisco County, San Francisco Fire is currently the only one we have flagged as encrypted.
See every agency we track in San Francisco County → County encryption overview →
What This Means
This agency is listed as encrypting some communications while leaving others open. The per-channel breakdown is unverified — check RadioReference for current status.
Frequently Asked Questions
Is San Francisco Fire radio encrypted?
San Francisco Fire is listed in our records with P25 AES-256 encryption — a listing we haven't yet verified against live talkgroup data. This agency is listed as encrypting some communications while leaving others open. The per-channel breakdown is unverified — check RadioReference for current status.
Can I listen to San Francisco Fire on a police scanner?
Possibly. Our database lists San Francisco Fire as encrypting some of its talkgroups while leaving others open, which would leave some channels accessible. The listing is unverified — check RadioReference for specific talkgroup status.
Why do agencies like 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 fire department response slows down, and mutual-aid coordination gets more awkward, immediately.
Can San Francisco County reverse the encryption decision?
Yes. Whoever made this call for 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 San Francisco County officials discuss the budget for San Francisco Fire, and ask specifically why full encryption was chosen over a delayed feed or tactical-only approach. 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.