Bend's Verkada Security-Camera System — What Residents Should Know

Where things stand The City of Bend has standardized on Verkada's cloud-based security-camera platform since 2020 and continued purchasing Verkada-related installation services and hardware in 2023 and 2024. The documents reviewed so far do not prove that Bend PD has direct access to the system. They do show that key governance details — camera locations, retention settings, analytics settings, police-access rules, public-sharing rules, vendor-access limits, signage practices, and post-breach risk review — are not in the public record.

This explainer is for Bend residents who want to understand what the City has built, what's confirmed in writing, and what questions remain unanswered. It draws from the City's own Council issue summaries, contracts, meeting minutes, and Verkada's own incident report. Sources are linked at the end. Use this to inform yourself, ask better questions, or write to Council.

01What the City Has Built

The Bend system is not a single project but a layered platform that has been expanded through several contracts. Here's what the public record confirms.

A cloud-based "video-surveillance-as-a-service" platform.

In 2020, the City adopted Verkada's platform through a competitive bid. Unlike traditional on-site security cameras, Verkada's system streams and stores footage in the cloud (Amazon Web Services), managed through Verkada's "Command" platform.

Two more authorizations in 2023 and 2024.

In June 2023, Council authorized up to $165,000 for installation services with LTT Partners LLC, a licensed Verkada reseller and installer. In June 2024, Council authorized up to $150,000 to purchase additional Verkada-compatible cameras and hardware. Both were approved on the consent agenda.

Integration into new City buildings.

Verkada cameras and integrated access control are being designed into the new Public Works Campus, including the headquarters, fleet, and warm-vehicle-storage buildings.

Cameras around the Lighthouse Navigation Center.

The City's January 2026 Council Goals Status Report notes that security cameras are being installed around the Lighthouse Navigation Center as part of a public-safety effort. The report does not specify whether those cameras are part of the Verkada system.

Employee privacy protections (only).

The City's collective bargaining agreement with COBEA (the employees' union) includes rules: cameras may not be placed where employees have a reasonable expectation of personal privacy, the City may not randomly review footage for discipline, and no employee can be disciplined solely on video evidence absent misconduct. These protections cover employees — not the general public.

Worth stating plainly Security cameras at City facilities — loading docks, cash-handling areas, building entries — are a normal and reasonable thing for a city to operate. The question this explainer raises is not whether cameras should exist, but whether a cloud-based, expandable, analytics-capable surveillance platform should be operated without published rules governing how it's used.

02What the Public Record Doesn't Show

These are the governance questions the documents don't answer. Each is something a resident might reasonably expect to be on file for a system of this kind.

Gap 01

Where the cameras are, and how many there are.

The installation contract says cameras are installed "at multiple City of Bend sites on an on-call basis," with each installation initiated by a purchase order. There is no public inventory of camera locations, counts, types, or fields of view. Because each installation is administrative — not a Council vote — individual deployments don't return for public review.

What this meansThe public cannot know whether a given sidewalk, alley, park, or street near a City facility is under camera coverage.

Gap 02

A public-facing surveillance use policy.

Employee privacy is partially protected by union contract. There is no parallel public policy governing who within the City may view live footage, whether viewer access is audit-logged, standards for reviewing footage of community members, prohibited uses (e.g., monitoring of First Amendment activity), discipline for misuse, or annual reporting to Council.

What this meansThe rules that govern how this system is used in practice are not visible to the public it surveils.

Gap 03

How long footage is kept.

The contracts and issue summaries do not specify a retention period. Verkada cameras can be configured to retain footage anywhere from roughly 30 days up to a year, depending on model and settings. The retention setting is the single biggest factor determining how much historical movement data the system holds.

What this meansA 30-day setting limits exposure. A 365-day setting creates a year-long behavioral record of everyone who walks past a camera.

Gap 04

Whether and how police access the system.

The installation contract requires LTT Partners' installers to be CJIS-certified (Criminal Justice Information Services) within six weeks of award. CJIS certification of installers is a meaningful clue that some work touches public-safety-sensitive environments, but it does not by itself prove Bend PD has direct, standing access to the Verkada platform, or that Verkada footage is treated as CJIS data. None of this is spelled out publicly.

What this means"Security cameras to protect public property" and "a feed integrated into police operations" are very different programs. The record doesn't say which one Bend has.

Gap 05

Which Verkada features are enabled.

Verkada's documentation confirms its platform supports — when enabled by a customer — People Analytics, face search across cameras, license plate recognition and plate-of-interest alerts, vehicle search by attribute, audio recording and audio analytics, and integration with access control to correlate badge swipes with video. Which of these features the City of Bend has turned on or off is not documented in the public record.

What this meansA camera that records video is one thing. A camera plus a searchable face database across City facilities is a substantially different capability.

Gap 06

Community engagement before approval.

Both the 2023 and 2024 issue summaries list "Community Outreach Process and Potential Impacts: N/A." Both authorizations went through the consent agenda — the 2024 purchase appears grouped with routine items like fuel purchases and meter-box upgrades. No public hearing, impact analysis, or community engagement process appears in the record.

What this meansThe expansion of a surveillance-capable platform was treated as routine procurement, not as a matter the public might want to weigh in on.

Gap 07

Whether the vendor was re-evaluated after a major 2021 breach.

In March 2021, attackers compromised Verkada's platform by exploiting a misconfigured customer-support server. They accessed live and archived video for 97 customer organizations, across approximately 4,500 cameras. Eight customers also had access-control product data accessed, including badge credentials. The breach was vendor-side, meaning customer security depended heavily on Verkada's internal controls. The City standardized on Verkada in 2020 — before the breach — and re-authorized two more Verkada-tied contracts in 2023 and 2024, after the breach. No document in the public record shows the City re-evaluated Verkada's security posture before those re-authorizations. In August 2024, the FTC announced a settlement requiring Verkada to implement a comprehensive information-security program with biennial third-party assessments; a separate $2.95 million civil penalty was imposed for CAN-SPAM email-marketing violations (FTC Matter 2123068; stipulated order entered Sept. 4, 2024, N.D. Cal.).

What this meansVendor risk doesn't disappear after a breach. A buyer that doesn't document re-evaluation is making an implicit bet that isn't in the record.

Gap 08

Public notice and signage.

Oregon does not have a general statute requiring video-surveillance signage in public areas, though federal law restricts audio recording without notice in most contexts. Whether camera locations carry visible signage — and what those signs say about the purpose, retention period, records-request process, and complaint process — is not addressed in the project record.

What this meansNotice is the floor of meaningful consent. It deters the conduct the City says it's trying to deter, and it signals accountability to the people walking past.

03Questions Worth Asking

Whether you're writing to Council, filing a public-records request, or just trying to understand your city better, these are reasonable, specific questions that the existing public record does not answer:

04Context: How Other Cities Handle This

Several cities — including Seattle, San Francisco, Oakland, Cambridge MA, Berkeley, and the Bay Area Rapid Transit (BART) system — have adopted surveillance-technology review processes that require public documentation, hearings, or annual reporting before a surveillance technology is acquired or expanded. These ordinances typically require a written impact report covering the technology's capabilities, retention rules, access policies, and civil-liberties risks; a public hearing before procurement; and annual use audits.

Bend's 2023 and 2024 Verkada-related authorizations went through the consent agenda with no documented community outreach.

05Sources

· Verkada Security Incident Report (March 2021 breach): Security_Incident_Report_Version1.2.pdf
· FTC press release: "FTC Takes Action Against Security Camera Firm Verkada" (Aug. 30, 2024): ftc.gov
· FTC case file: United States v. Verkada Inc., FTC Matter 2123068, Civil Action 3:24-cv-06153 (N.D. Cal., stipulated order entered Sept. 4, 2024): ftc.gov/legal-library

This explainer is educational and informational. It summarizes publicly available City of Bend documents and Verkada/FTC records as of the date above, and reflects a privacy and civil-liberties reading of those documents. It is not legal advice. Document contents and current City practices can change; verify primary sources before relying on specific details.