Surveillance-tech report: Putnam¶
Mentions current to 27 September 2026
This report covers meetings processed up to 2026-09-27. Anything newer shows up first in This Week in Surveillance.
Want to do something about it?
Visit flockoff.io to find out what you can do.
At a glance: Putnam¶
334 licence-plate searches by Putnam police in six towns' released Flock logs
Meetings not available yet: we have not found Putnam's meeting recordings in a form we can use -- they may not be published online, or only behind a login or password. If you know where they are, or can help us get access, use the Questions? Feedback? button on any page (or the feedback page) to reach out and work with us to get Putnam into the system.
This report collects every mention of surveillance technology in Putnam's public record that this project can read -- its recorded meetings once they are transcribed, its published agendas and minutes, and its police department's licence-plate search log where one has been released.
Contents¶
- Licence-plate searches by Putnam police
- Mentions by topic: first seen / most recent
- Timeline
- Findings by topic
- Agenda/minutes mentions (unreviewed -- live keyword scan, no human review queue yet)
- How this report was built
- Coverage status
- Registered meeting bodies
- Agenda/minutes coverage
- Research log
- Gaps and caveats
- Get the full transcripts
Licence-plate searches by Putnam police¶
Six Connecticut towns have released the Flock audit log of every search run against their cameras. Below is what that record holds for Putnam's own police department -- not a finding, just the log.
Putnam CT PD
- 334 searches between 2025-05 and 2026-08 (13 months with at least one search)
- 2,346 camera networks swept by the average single search
- 100% of them reached beyond Putnam's own cameras
- Most-used stated reason: Hit and Run/Car Accident
Open Putnam CT PD's search dashboard -- every one of those searches, filterable by month, stated reason, search type and how far it reached, with a How to read this tab covering what each field means and what the record cannot tell you.
A floor, not a total. The record only sees queries that reached those six towns' cameras. A single Flock query typically sweeps thousands of networks at once, so most of a Connecticut department's searching does land in it -- but the real count is higher. Nothing in it names an officer, shows a plate, or records what any search returned.
Mentions by topic: first seen / most recent¶
Back to the meetings. Everything above this point was about licence-plate searches -- what the town's police looked up. Everything below is about what was said: each mention is a moment in a recorded public meeting where a surveillance technology came up, with a link to that moment in the video.
No surveillance-technology mentions found in this town's transcribed meetings yet.
Timeline¶
No meetings have surfaced a finding yet.
Findings by topic¶
ai_data_fusion¶
(no findings)
alpr¶
(no findings)
biometrics_other¶
(no findings)
body_camera¶
(no findings)
cad¶
(no findings)
cell_site_sim¶
(no findings)
data_broker¶
(no findings)
doorbell_partnership¶
(no findings)
drone¶
(no findings)
facial_recognition¶
(no findings)
gunshot_detection¶
(no findings)
mobile_forensics¶
(no findings)
osint_social_monitor¶
(no findings)
predictive_policing¶
(no findings)
purchasing_broker¶
(no findings)
rtcc¶
(no findings)
surveillance_general¶
(no findings)
undercover_tools¶
(no findings)
vehicle_forensics¶
(no findings)
video_analytics¶
(no findings)
Agenda/minutes mentions (unreviewed -- live keyword scan, no human review queue yet)¶
ai_data_fusion¶
(no mentions)
alpr¶
(no mentions)
biometrics_other¶
(no mentions)
body_camera¶
(no mentions)
cad¶
(no mentions)
cell_site_sim¶
(no mentions)
data_broker¶
(no mentions)
doorbell_partnership¶
(no mentions)
drone¶
(no mentions)
facial_recognition¶
(no mentions)
gunshot_detection¶
(no mentions)
mobile_forensics¶
(no mentions)
osint_social_monitor¶
(no mentions)
predictive_policing¶
(no mentions)
purchasing_broker¶
(no mentions)
rtcc¶
(no mentions)
surveillance_general¶
(no mentions)
undercover_tools¶
(no mentions)
vehicle_forensics¶
(no mentions)
video_analytics¶
(no mentions)
How this report was built¶
Everything below describes the corpus and its limits, rather than what was found in it.
Coverage status¶
- Channels registered: 0
- Active meeting bodies: 0
- Videos registered: 0 (fetched: 0, no captions: 0)
- Date range covered: no video in this corpus has a parseable upload date, so no range can be stated
Channels¶
(none)
Tab crawl history¶
(none)
Registered meeting bodies¶
(none)
Agenda/minutes coverage¶
- Agenda sources registered: 1
- Documents registered: 0 (fetched: 0)
- Date range covered: no agenda document on file carries a parseable date yet
Agenda sources¶
| source_id | platform | base_url | status |
|---|---|---|---|
| putnam_custom | custom | https://www.putnamct.us/government/boards/board-of-selectmen | unconfirmed |
Research log¶
| logged_at | field_name | new_value | source | by |
|---|---|---|---|---|
| 2026-08-27 07:45:02.448519 | channel_not_found | No viable YouTube channel found after: (1) recurring cross-town-noise video IDs verified via yt-dlp to belong to Marlborough CT, Freetown MA, and Fairfield CT respectively, plus unrelated "Putnam County" (TN/NY) channels, (2) the regional SEC-TV Waterford Studio channel (which lists Putnam among its 9 served towns) crawled in full and found to carry essentially no Putnam government-meeting content, (3) putnamct.us has no video/livestream links on its meetings pages. | WebSearch (multiple queries) + yt-dlp verification of the recurring video/playlist IDs + full crawl of youtube.com/@sec-tvwaterfordstudio7333 + WebFetch of putnamct.us, 2026-08-27 | claude |
Gaps and caveats¶
Videos with no captions available (0 shown, max 25)¶
(none)
Tabs never crawled¶
(none)
Get the full transcripts¶
Putnam has 0 transcripts so far -- too few to publish as an archive yet. It will appear here once the corpus grows.
Generated 2026-09-27T16:34:58 from Putnam's meeting transcripts and agenda documents. Home addresses spoken during public comment are redacted; see the archive MANIFEST for what that means.
Questions? Feedback?