Washington Security Camera Laws in 2026: Audio, License Plate Readers, and What's Legal on Your Site

Why Everyone Is Suddenly Asking About Camera Law

For most of the last decade, "is this camera legal?" was a question people in Washington rarely asked out loud. That changed in October 2025, when the University of Washington Center for Human Rights published "Leaving the Door Wide Open". Working from records of 31 law enforcement agencies, it found that at least eight Washington agencies, including the Auburn and Lakewood police departments, had enabled direct sharing of license plate reader data with U.S. Border Patrol. Border Patrol also had apparent "back door" access to at least ten more, among them Black Diamond, Eatonville, and Renton.

The Legislature responded. Engrossed Substitute Senate Bill 6002, sponsored by Senator Yasmin Trudeau of Tacoma, passed the House 84–10 on March 5 and the Senate 39–10 on March 10. Governor Bob Ferguson signed it on March 30, 2026. Because it carried an emergency clause, it took effect the same day.

The fallout was immediate. KUOW reported on April 3 that the Seattle and Kent police departments had suspended their mobile plate readers. Kent Police Chief Rafael Padilla explained that the department "could not ensure that they wouldn't incidentally capture license plates in those restricted, protected areas." Pierce County Sheriff Keith Swank went further and deactivated the department's entire system, telling MyNorthwest that complying manually was "not possible." In Seattle, Mayor Katie Wilson had already paused expansion of the police CCTV pilot on March 19, pending a privacy audit by NYU's Policing Project, and temporarily paused all city use of plate readers.

Some agencies are coming back online. Bonney Lake reactivated its 22 Flock cameras on August 31 after keeping them dark since mid-December. "I wanted to wait to see the new legislation," Police Chief Mark Berry told The News Tribune.

Meanwhile the courts and the public have been busy. In November 2025, a Skagit County Superior Court judge ruled that Flock camera images are public records because they "are created and used to further a governmental purpose," even when a vendor stores them. Stanwood and Sedro-Woolley settled that case in August for $80,000, split evenly. And on August 28, FOX 13 reported a wave of vandalism against plate-reader cameras, including four juveniles arrested in Covington for firing fireworks at one. Volunteer maps cited in the story count more than 2,100 plate readers statewide.

Almost all of that is aimed at government. But the questions land on private sites too, from neighbors, tenants, and crews who've read the headlines. And the audio law has applied to everybody for decades.

Video: The Part That's Mostly Settled

Washington has no statute that requires consent to video record areas that are open to view. MRSC, the nonprofit research center that advises Washington local governments, puts the principle plainly in its guidance on security cameras: "individuals do not have a reasonable expectation of privacy in public areas." It was written for local governments, but the same logic lets a contractor watch a fenced equipment yard or a property manager cover a parking lot.

The line is places where people do expect privacy. Washington's voyeurism statute, RCW 9A.44.115, describes one as a place "where a reasonable person would believe that he or she could disrobe in privacy" or "where one may reasonably expect to be safe from casual or hostile intrusion or surveillance." The crime requires a sexual purpose or intent to distribute, so it's rarely a criminal question for a security camera, but it's still the line to respect. On a jobsite, that means no angle on the portable toilets, the changing area in the site trailer, or the windows of the occupied building next door. Check those before you settle on mast height and pan limits.

Signs aren't legally required for video-only systems. MRSC notes that public notice "is not required for security footage that records video only," but calls signs good public policy and "a double deterrent to crime." They're also the cheapest deterrent you'll ever buy. Just sign what's true. A sign promising surveillance that went home with last month's rental is worse than no sign.

If employees are on camera, check your labor agreements. MRSC notes that for public employers, video monitoring of unionized employees for discipline is a mandatory subject of bargaining. Private-sector union contracts can have their own camera clauses.

Audio: Where Washington Is Stricter Than Most States

Here's the sentence that matters, from RCW 9.73.030(1)(b). It is unlawful for "any individual, partnership, corporation, association, or the state of Washington, its agencies, and political subdivisions" to intercept or record any "private conversation, by any device electronic or otherwise designed to record or transmit such conversation regardless how the device is powered or actuated without first obtaining the consent of all the persons engaged in the conversation."

It applies to everyone, and "transmit" counts. There's no exemption for security purposes. A microphone that streams live audio to a phone or a monitoring screen is covered even if nothing is ever saved. People assume the risk is the recording. In Washington, the listening is enough.

It only covers private conversations, and "private" depends on the facts. In State v. Kipp, 179 Wn.2d 718 (2014), the Washington Supreme Court held that a secretly recorded conversation about a sensitive family matter in a home kitchen was private, and reversed the conviction. The court weighed "the duration and subject matter of the communication, the location of the communication and the presence or potential presence of third parties, and the role of the nonconsenting party and his or her relationship to the consenting party." In State v. Clark, 129 Wn.2d 211 (1996), by contrast, street drug sales offered openly to strangers weren't private. A trailer microphone at 2 a.m. on an empty, fenced jobsite is probably closer to Clark. The same microphone at 10 a.m., a few feet from where the crew eats lunch, is not.

Consent can come from an announcement, with a catch. Under RCW 9.73.030(3), consent is obtained when one party announces "in any reasonably effective manner" that the conversation "is about to be recorded or transmitted." The catch: "if the conversation is to be recorded that said announcement shall also be recorded."

The penalties are real. A violation is a gross misdemeanor (RCW 9.73.080). Anyone injured can sue for actual damages, or $100 a day up to $1,000, plus attorney fees (RCW 9.73.060). No wonder MRSC calls audio "much more problematic under state law" and doesn't recommend it for local government security programs.

Speakers and microphones are two different legal questions

This is where most of the confusion about mobile surveillance trailers comes from. A speaker broadcasts. A pre-recorded "You are on camera, leave the property now," or a live warning from someone watching the feed, doesn't intercept or record anyone's conversation. A microphone is the part the Privacy Act cares about, because two-way audio means the trailer is transmitting whatever it hears.

PA two-way audio on our trailers is an optional add-on, not a default. When a customer wants it, these are the settings we'd suggest they run past their attorney:

• No continuous audio recording. Record video around the clock and leave audio off.
• Speaker-only warnings by default. A floodlight and a loud "leave the property now" don't require anyone on the other end to talk back.
• Announce before any two-way exchange. Start with something like "This site is under video surveillance and this conversation is being recorded." If the exchange is recorded, make sure the announcement is on the recording.
• Keep microphones away from people's normal conversations. That means break areas, the site office, and the neighbor's back patio.
• Put audio on the signs only if audio is actually in use. A sign helps show notice, but don't assume it satisfies the recorded-announcement rule by itself.

License Plate Readers: What the Driver Privacy Act Actually Says

A lot of the coverage of SB 6002 has been secondhand, and some of it is wrong. There's no 500-foot rule in it, for one. The enrolled session law, now codified as chapter 10.130 RCW, runs ten pages. Here's what matters for anyone running cameras.

It regulates agencies (Sec. 2). That means state and local agencies: every county, city, town, municipal and quasi-municipal corporation, special purpose district, and local housing authority, "including their respective employees and agents." A plate reader system is anything "used to convert images of license plates into computer-readable data."

Only three kinds of agencies may use one (Sec. 3). Law enforcement agencies can check reads against state and federal databases, or search for a vehicle that is stolen, tied to a missing or endangered person, registered to someone with an outstanding felony or gross misdemeanor warrant, or involved in a felony or gross misdemeanor. Parking enforcement agencies can enforce parking rules and impound ordinances. Transportation agencies can provide traffic information, run traffic studies, and enforce commercial vehicle rules. For every other agency, use is unlawful. No agency may use plate readers for immigration enforcement, protected health care services, or tracking First Amendment activity, and a match alone isn't reasonable suspicion for a traffic stop.

Some places are off-limits. No agency may collect plate data at facilities that provide protected health care, facilities conducting immigration matters, K-12 schools, places of worship, courts, or food banks. That includes "any immediately adjacent parking lots" used primarily for those purposes.

Data expires in 21 days (Sec. 4). Longer retention is allowed only under a court-issued warrant, subpoena, or court order; for parking cases (12 hours after final disposition); for traffic studies (30 days); for commercial vehicle enforcement (six months); or as evidence of the listed crimes.

Sharing is locked down (Sec. 5). Agencies may not share plate data "except as required in a judicial proceeding." They can give system access only to other authorized agencies, and to vendors only as far as an authorized purpose requires. They may not buy or sell the data. Agency plate data is exempt from the Public Records Act. Vendors must block unauthorized access, including by federal civil immigration enforcement, and ship with sharing turned off. Vendors that contract with agencies can also face claims under the Consumer Protection Act.

It has teeth (Sec. 6, 10, 11). Willful misuse is a gross misdemeanor. People harmed can sue for damages and attorney fees. Evidence from a knowing violation of the use rules is inadmissible.

The paperwork runs into 2027. Agencies must register their systems with the Attorney General's Office. According to the Association of Washington Cities, the registration forms became available in August and there's no fixed registration date. Audit trails must be kept for two years. The AG's model policies are due July 1, 2027. Agency policies and public annual reports, including camera locations, are due December 1, 2027.

If you're a private business, contractor, or HOA

You aren't the "agency" this law regulates, so the 21-day clock, the registration forms, and the purpose limits don't apply to you directly. But three parts of it still reach private sites.

Police need a warrant for your plate data. Under Section 5(4), "an agency may obtain privately held automated license plate reader data only pursuant to a valid, court-issued, probable cause warrant." A detective can no longer simply ask a retailer or warehouse operator for its plate-read log.

Ordinary video probably isn't "plate reader data." The law ties that term to systems that convert plate images into computer-readable data. It even excludes dashboard and body camera video unless that video is converted into plate characters or indexed by plate. By that logic, a video clip of someone cutting your fence is a different thing from an exported list of every plate that passed your gate this month. No court has tested the distinction, so ask your lawyer before you share anything that came out of a plate-reading module.

The criminal penalty says "any person," but it's aimed at misuse of government systems. Section 10 (now RCW 10.130.100) makes it a gross misdemeanor for "any person" to willfully use a plate reader system "for a purpose not specifically authorized under this chapter." Out of context, that could seem to reach a store's own camera. In context, it's hard to get there. The operating rules are addressed to agencies, and Section 5(4) assumes private plate data exists and only limits how agencies get it. The House also stripped recordkeeping duties that earlier drafts placed on "ALPR operators," calling them duplicative of the agency audit rules. "Any person" is how a criminal statute reaches the individual officer, employee, or contractor who misuses an agency's system. No court has ruled on it yet. For private sites, the provision more likely to matter is Section 5(7): plate reader vendors may not sell or give access to plate data to anyone unauthorized, and that text isn't limited to agency data. Don't sell or broker plate data, and ask your vendor who else can see yours.

If you're a public agency renting a trailer

If you aren't police, parking enforcement, or a transportation agency, rent without plate reading. A parks department covering a trailhead lot, a school district securing a summer construction project, or a housing authority watching a parking area has no authorized purpose under Section 3, and "agency" includes your agents. Even police can't collect plate data at a K-12 school.

Your footage is a public record. MRSC is blunt: "anyone can submit a public records request to inspect or obtain a copy of the video footage from a security camera." The Skagit County ruling applied the same logic to images a vendor stored for the city. SB 6002 shields agency plate reader data from disclosure. Regular video isn't covered by that exemption.

Know your retention schedule. According to MRSC, routine surveillance video is kept 30 days, or until it's determined no security incident occurred, whichever is sooner. Footage tied to an incident is kept six years after the matter is resolved. Our trailers keep two weeks of motion-only history on a rolling loop by default, and the archive can be capped at a set number of days to match your schedule. Incident clips still need to be exported and filed on your side.

In Seattle, check the Surveillance Ordinance first. Under SMC 14.18, city departments need Council approval before acquiring surveillance technology, subject to the ordinance's own definitions and exemptions. Talk to the city's privacy team before scheduling a delivery.

Handing Footage to Police, and Getting Them to Show Up

Legal footage only matters if it leads somewhere. In the Puget Sound's two biggest cities, the rules now reward verified activity over raw alarms.

Seattle. Since October 1, 2024, the Seattle Police Department has dispatched officers to alarm-company calls only when there's supporting evidence, which The Monitoring Association quoted as "audio, video, panic alarms or eyewitness evidence that a person is illegally entering or attempting to enter a residence or commercial property." Sensor or motion activations alone no longer get a response. The reason: of roughly 13,000 intrusion alarm calls in 2023, only about 4% were tied to a confirmed crime that produced a report or arrest, according to SPD figures reported by BOS Security.

Tacoma. The city's alarm program requires monitoring companies to verify an alarm before requesting police. Verification is "not needed if the system has live video/audio showing a crime in progress or if someone on-site reports a crime." False alarms cost $115 each for the first two, rising to $315 from the seventh on. More than four in twelve months can earn a "No Response" designation for up to a year.

Why the difference matters. A June 9, 2026 Seattle City Council staff report put SPD's first-quarter 2026 median response at 7 minutes for Priority 1 calls, 24.3 minutes for Priority 2, and 75.7 minutes for Priority 3. The same report said the number of patrol officers "has consistently hovered at 490 since 2023," down from 694 in September 2020. With patrol that thin, "people are cutting the fence right now, I'm watching them" is a very different call from "the motion sensor went off."

On a trailer, the sequence goes like this. An AI alert fires. Whoever is watching the site pulls up the live view and confirms what's happening, then triggers a speaker warning or the floodlights. If the intruders stay, they call 911 and describe what they're watching. That's the kind of call both cities' rules prioritize, and sometimes the warning ends it before anyone has to make it.

Evidence handling that holds up

Export the clip right away, and write it down. Our trailers keep two weeks of motion-only history on a rolling loop by default (less if the archive is capped), and then it's gone. The morning after an incident, export the video, save it somewhere that isn't the trailer, and note the camera, the times, what you saw, and the police report number. Keep the original and hand over a copy. The S-VIDIA platform our trailers run watermarks and encrypts recorded frames and stores them as separate images, which lets you step through an incident frame by frame and helps show the footage wasn't altered.

Treat plate-read logs as their own category. A video clip of a break-in is one thing. Plate reader data is another. Under Section 5(4), expect the agency to need a warrant for it, and involve your attorney.

A Pre-Deployment Checklist for Washington Sites

Work through this before any trailer, ours or anyone else's, goes up on a Washington site.

Comparing vendors? Ask whether audio and plate reading can be switched off completely, who at the vendor can see your footage, and how long the recorder keeps history. Public agencies should also get in writing that plate-reader sharing defaults are off, as Section 5(8) requires.

Frequently Asked Questions

The Bottom Line

Washington's camera rules come down to three different questions, and most mistakes happen when people treat them as one. Video of areas open to view is generally fine, as long as you keep private spaces out of frame and your signs tell the truth. Audio is governed by one of the country's stricter consent laws, which covers live listening as well as recording. The safe default is speaker-only warnings, with any two-way conversation starting with a recorded announcement. License plate reading became a regulated, government-focused technology on March 30, 2026. Agencies outside police, parking, and transportation shouldn't run it at all, and private operators should treat it as a deliberate decision with a written plan, not a feature that comes bundled with the rental.

None of this makes cameras less useful. If anything, 2026 has made verified video more valuable. Seattle and Tacoma both put live, confirmed activity at the front of the line, and lawfully captured, carefully handled footage is what holds up afterward. Legislators will keep arguing about surveillance next session. For a contractor with a copper-stuffed jobsite or a property manager with a lot full of cars, the question is simpler: are your cameras aimed, configured, and documented so they help when something happens?

If you're planning a deployment and want to talk through camera angles, audio settings, and whether plate reading belongs on your site at all, we're glad to walk it with you. Get in touch or call us at (253) 683-2288.