What happened
The Kansas City Defender reports that the Kansas City Area Transportation Authority signed a July 2025 agreement with SafeSpace Global to deploy AI-powered facial-recognition cameras on buses. The contract authorized collection of facial features, facial templates, video, audio, infrared and depth data, and entry, exit, movement and location metadata. It also permitted de-identified rider data to be used for algorithmic training and aggregated analysis, while restricting public announcements about the agreement.
The Kansas City Defender reports that KCATA executed a three-year Master Services Agreement with SafeSpace Global on July 24, 2025. According to the outlet’s account of the contract, the initial term runs through July 24, 2028, after which the agreement renews annually unless either party gives written notice at least 30 days before the end of a term. The agreement concerned AI-powered cameras for KCATA buses and authorized the creation of facial-recognition profiles from riders’ images. The Defender says the contract had not appeared in the public record for roughly a year while KCATA’s public descriptions characterized the project as delayed or stalled.
The Defender reports that the contract’s data-privacy addendum covered facial features and templates, photographs and video frames used to generate profiles, infrared and depth data, recorded video and audio, and metadata about riders’ entry, exit, movement and location. The outlet also reports that the agreement allowed SafeSpace to process de-identified customer data for algorithmic training and shared or aggregated analysis. The contract’s language extended data access to unnamed “assigned operators and/or other service providers,” according to the report. The Defender says the agreement also anticipated possible production of footage in state or federal investigations, while limiting SafeSpace’s responsibility for how customer data was retained or handed over.
KCATA interim chief executive Chuck Ferguson told The Kansas City Defender that the pilot never began because expected Missouri funding did not materialize over civil-liberties concerns. Ferguson’s claim that no cameras captured anyone and no data changed hands has not been independently verified. The Defender reports that KCATA had no policy specifically governing biometric data from AI cameras and that the agency instead pointed to a general employee technology-use policy. The outlet also reports that the contract restricted either party from issuing a press release about the agreement without the other party’s written consent.
Read the primary source: kansascitydefender.com ↗
Why it matters
The reported contract would have given a private company broad rights over biometric information collected from public-transit riders, without a rider-specific KCATA policy governing the data. The Defender reports that the agreement remained active and automatically renewable even as officials described the pilot as stalled. The story raises practical questions about consent, retention, investigative access, vendor oversight and whether public agencies can expand surveillance through contracts that are difficult for riders to see or challenge.
The central public-interest issue is the gap between the reported scope of the contract and the information available to riders. The Kansas City Defender reports that the agreement authorized collection of sensitive biometric and movement data in a public setting, while no rider-specific policy explained how that information would be retained, accessed, shared or deleted. AI Understanding has not independently reviewed the underlying contract, but the reported terms would create materially different risks from ordinary onboard security cameras because facial templates and related data can support identification across time and locations.
The Defender places the agreement within KCATA’s broader financial and service pressures, reporting that operating costs rose while city contributions remained relatively stable and that the agency has announced route or service reductions. Those details do not establish that surveillance spending directly caused service cuts, but they make the procurement decision more consequential for a public agency serving riders who may have limited transportation alternatives. The report also describes the contract as using privacy language originally associated with residential care facilities, including references to residents, rooms, hallways and common areas. That comparison is the outlet’s characterization of the document, not an independent legal finding.
The reported lack of independent testing is another important limitation. The Defender says reviewers could not locate a third-party benchmark, a National Institute of Standards and Technology evaluation, or a published assessment of performance across race or skin tone for SafeSpace’s facial-recognition system. The outlet cites broader research and prior cases involving facial-recognition errors, but those examples do not measure this vendor’s performance on KCATA buses. The practical concern is therefore not a proven failure by SafeSpace on Kansas City riders, but the reported absence of evidence that the system had been independently evaluated before deployment was contemplated.
What to watch next
KCATA’s account that the pilot never launched because Missouri funding did not materialize remains unverified. Follow-up reporting should establish whether any cameras were installed, whether any rider data was collected or transferred, whether the contract has been terminated, and what obligations attach to the reported Department of Justice funding. The public should also seek the full contract, applicable procurement records, data-retention rules, access logs, vendor testing, and any board or public-comment discussions.
The first question is whether the project truly remained dormant. KCATA’s statement that state funding never arrived is attributed by The Kansas City Defender to Ferguson and has not been independently verified. Follow-up reporting should look for installation records, purchase orders, invoices, camera or software activation logs, grant drawdowns, technical support records, and any evidence that video, audio or biometric templates were processed. If KCATA terminated the agreement, the termination notice and any deletion certification would clarify whether the reported rights still have practical effect.
The reported Department of Justice funding also warrants scrutiny. The Defender says KCATA received a $1.031 million DOJ grant connected to a gunfire-detection system and an AI camera project, but the agency had not explained what it agreed to in exchange for the funding. Relevant records would include the grant award, statement of work, data-sharing requirements, participating task forces, databases, retention periods and audit provisions. Those records could distinguish between a proposed capability, a funded but unused system, and an operating surveillance program.
Finally, public oversight should focus on the contract’s renewal and vendor-governance terms. The Defender reports that the agreement automatically renews and that data could be made available to unnamed service providers. Watch for KCATA board action, public comments, procurement disclosures, a rider-facing privacy policy, access and deletion procedures, and an explanation of whether the contract has been canceled or allowed to expire. The report also says KCATA had not substantively answered follow-up questions about data sharing and decision-making; that unanswered record is itself a meaningful unknown.
