From the Public Safety edition of October 7, 2026
Seattle auditor and OIG reports find undisclosed traffic-camera feeds in SPD's AI-enabled crime center, a federal data-rights clause, and no controls on proactive surveillance
Seattle Office of the City Auditor and Office of Inspector General for Public Safety (reported by The Urbanist) · Municipal policing / real-time crime center oversight · Seattle, Washington, United States
- Publisher
- The Urbanist
- Original publication
- Oct. 7, 2026
- Source retrieved
- 2026-10-08
What happened
The Urbanist summarized two newly released city reports on the Seattle Police Department's real-time crime center, whose software uses AI to analyze CCTV, traffic-camera and other feeds. The auditor found traffic cameras not on SDOT's public map streaming into the center, more recordings created than under SDOT's manual practice, and an SDOT contract with AI vendor Derq that lets the federal government obtain data from federally funded projects. The Inspector General found private cameras joining from anywhere in the city via Connect Seattle without formal policy, weak control over private-camera masking and retention, delays masking SPD's own cameras, and no controls to prevent or monitor proactive surveillance by analysts, which policy prohibits. Before in-vehicle ALPR was suspended under state law SB 6002, officers failed to log a reason for 47% of 2025 searches, per an advocacy group citing the report. The Seattle Times count cited is 427 cameras streaming, including 23 private.
Why it matters
An internal-audit view of a live AI-enabled real-time crime center, showing where controls were missing after go-live; directly useful to agencies building similar centers.
Evidence and measured results
Independent local reporting summarizing two government reports (auditor and OIG) and adding advocacy quotes. The underlying reports were not opened tonight; specific figures (47%, 427 cameras) are attributed second-hand.
Limitations and uncertainty
Secondary reporting from an outlet with an editorial stance; primary reports not opened; advocacy statements mixed with findings. Other outlets describe the OIG review as finding some safeguards working; this record relies on The Urbanist's account.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Real-time crime centers integrate feeds faster than policies and technical controls are put in place.
- Stakeholders
- Police real-time crime center leadership
- Transportation department
- Office of Inspector General and city auditor
- Mayor's office
- Private camera owners
- Discovery questions
- Is there an authoritative list of every feed entering the center?
- Do any feed contracts grant federal data rights?
- Are analyst views tied to a recorded reason?
- How are private-camera masking and retention controlled?
- Value hypothesis
- A control assessment before expansion can find feed, contract and access gaps that later audits otherwise surface publicly.
- Potential engagement
- Pre-expansion RTCC control assessment covering feed inventory, contract data rights, masking and access logging.
- Unsupported claims
- That RTCCs reduce violent crime
- That federal agencies accessed Seattle data
- That all OIG findings were negative
- Specific figures not verified in primary reports
Pre-sales engineering
Role takeaway
- Fit
- Relevant to agencies operating or planning AI-enabled real-time crime centers with mixed public and private feeds.
- Architecture and integration
- RTCC software ingests SPD CCTV, SDOT traffic cameras and private cameras via Axon devices, with AI analysis on streams.
- Prerequisites
- Feed inventory
- Masking capability and technician capacity
- Analyst access logging
- Contract review of feed sources
- Constraints
- Washington SB 6002 ALPR restrictions
- Federal data rights in grant-funded contracts
- City facial-recognition prohibition
- Private owners control camera orientation
- Security
- Enforce search justification before footage views, log analyst sessions, centrally manage masking and block unapproved feeds.
- Proof of value
- Reconcile live feeds against approved list
- Sample analyst sessions for proactive surveillance
- Review contracts for federal data clauses
- Measure masking turnaround time
Delivery
Role takeaway
- Work
- Close audit findings: reconcile feeds, codify private-camera onboarding, add search justification and set an audit cadence.
- Dependencies
- Axon configuration changes
- SDOT cooperation
- OIG follow-up
- Mayor's decision on expansion
- Ownership
- SPD real-time crime center, with SDOT for traffic feeds and OIG oversight.
- Skills and adoption
- Analysts need training on justification requirements; technicians need capacity for masking.
- Governance checkpoints
- Feed inventory sign-off
- Private camera policy adoption
- Search justification go-live
- OIG follow-up review before expansion
- Acceptance criteria
- Proposed: zero unapproved feeds in monthly reconciliation
- Proposed: 100% of footage views carry a recorded reason
- Proposed: masking applied within a defined number of days of install
- Proposed: federal data-rights clauses removed or disclosed
- Risks
- Expansion before fixes
- Federal access via contract terms
- Analyst drift to proactive surveillance
- Private feeds outside policy
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
The center ingests SPD CCTV, SDOT traffic cameras and private cameras through Axon-supplied devices; scope control depends on camera lists, masking and analyst behavior rather than technical enforcement.
Governance
Who approves, reviews and stays accountable for outcomes?
Policies existed on paper (no proactive surveillance, traffic cameras not for enforcement) without technical controls; SPD is discussing a search-justification requirement with Axon after more than a year live.
Security and privacy
What data, permissions and controls need testing?
Federal data rights in a grant-funded AI traffic contract could expose footage to federal agencies, including immigration enforcement, beyond city facial-recognition limits.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Masking delays tied to technician availability show staffing limits on privacy controls.
Procurement
What should contracts, pricing and exit terms secure?
Grant-funded technology contracts can carry federal data-rights clauses that conflict with city privacy commitments; review these before integrating feeds.
Operating model
Which teams own the service once it runs?
Mayor Wilson's paused expansion awaits a delayed NYU Policing Project audit; these reports add evidence to that decision.
Publication history
- 2026-10-07Public Safety · Issue 316 resources
Stable resource ID: seattle-audit-oig-rtcc-federal-access-search-controls-20261007