What this bill does
Senate Bill 6002 and its identical companion bill HB 2332, creates a statutory framework governing how state and local agencies in Washington may operate automated license plate reader systems (ALPRs) devices that scan and digitize license plates into searchable databases. The bill sets definitions, use-limits, data retention rules, access controls, and prohibited uses for these surveillance systems.
On its face, SB 6002 restricts certain uses of ALPR data, especially uses tied to civil immigration enforcement. But a close look reveals that the bill also normalizes and embeds widespread data collection while relying on bureaucratic self-restraint rather than constitutional checks. This bill is part of an “Immigrants’ Rights” package of bill by the Senate Democrats. SB 6002 is co-sponsored by Republican Senator Jeff Holy (Spokane).
Key Provisions With Real-World Impact
1. Universal Plate Scanning Without Suspicion
SB 6002 authorizes agencies to use ALPR systems broadly for law enforcement and related purposes (e.g., stolen vehicles, felony warrants). There is no requirement for probable cause or individualized reasonable suspicion before scanning the license plates of every passing vehicle.
That means:
- Every driver, commuter, visitor, or family taking their kids to school can be captured.
- The state endorses mass, suspicionless automated surveillance, normalized as a “tool” rather than a power that implicates privacy rights.
This is important because where you go — repeatedly or even once — tells a story about your life: where you live, worship, work, seek healthcare, socialize, or join political gatherings.
2. Retention Rules: Short, But Still Invasive
The bill generally limits ALPR data retention to brief periods (e.g., 72 hours) unless tied to an ongoing criminal investigation with probable cause. While that sounds protective, even short windows of stored plate scans can be stitched into movement profiles that reveal:
- Personal routines
- Associations
- Patterns linked to sensitive locations
A few days of data is enough to map someone’s life. Short retention does not equate to meaningful privacy protection.
3. Use Restrictions and “Purpose Limits”
SB 6002 prohibits ALPR use for immigration enforcement purposes. It also bans scanning near designated “sensitive locations” when the intent is to support immigration or civil enforcement.
But here’s the catch:
- The restrictions are purpose-based, not structural.
- They rely on agencies to self-classify investigations and comply with internal policy rather than on external oversight or independent warrants.
This breeds a two-tier system: some uses are expressly forbidden, others are broadly permitted. The difference isn’t necessarily privacy itself, it’s politically preferred categories of use. That’s a policy choice, not a robust privacy principle.
4. Data Sharing and Access Controls
The bill does impose access controls and restricts data sharing:
- Data may only be shared with authorized agencies and for specific criminal justice purposes.
- Vendors must build systems that prevent unauthorized access.
- The state auditor and attorney general have roles in compliance and auditing.
But lack of a strong private right of action means:
- Citizens whose data is misused have limited legal recourse.
- Enforcement and penalty mechanisms sit largely inside government structures rather than giving the public a way to hold agencies accountable themselves.
What’s Missing — From a Civil Liberties Standpoint
No Warrants Required
The bill does not require warrants for using ALPRs in the first place. It treats plate scanning as analogous to a speed camera or tolling camera, ignoring that persistent, automated collection of movement data is fundamentally different from a one-off radar reading.
This is the core of the privacy concern: mass collection without judicial oversight, justified after the fact by statutory categories of “acceptable use.”
This is a governance posture that assumes the power to collect first and justify later, precisely the reverse of how constitutional protections are supposed to work.
Immigration Angle
Explicit Restriction
SB 6002 prohibits the use of ALPR technology for immigration enforcement purposes. In legislative language, this limits agencies from using plate reader systems to locate individuals for federal immigration action or civil immigration investigations.
This is the part most often touted by advocates as shielding immigrants from federal enforcement by denying access to a state-controlled surveillance tool.
Implicit Effects
Because the bill restricts sharing and use for immigration purposes, it also:
- Limits how federal agencies like ICE or CBP could piggyback on state ALPR data without a warrant.
- Reduces the utility of ALPR data as a source for movement tracking in immigration investigations.
However, since plate data still exists in the system for other law enforcement purposes, and because the privacy framework is internally governed rather than constitutionally secured, the restriction could be circumvented or reinterpreted over time.
Why Privacy Advocates Should Still Be Concerned
Normalization of Mass Surveillance
By creating a statutory regime rather than erecting constitutional safeguards, the bill legitimizes a world in which continuous, automated location data collection is standard police practice.
Weak Checks and Balances
The primary guardrails are:
- Internal policies
- Audits
- Prosecutorial exclusion of tainted evidence
There is no structural limit on how the data is initially collected, who ultimately examines it, or how easily the purposes may expand.
No Citizen Enforcement Pathway
If your data is misused — including being used for unlawful purposes — your remedies are limited. There’s no robust private right to sue, which means bureaucratic compliance becomes the main enforcement mechanism. That’s a familiar pattern in surveillance law: lots of rules on paper, limited teeth in practice.
Bottom Line
SB 6002 is not a “privacy win.” On its face, it appears to protect civil liberties by limiting certain uses of ALPRs — including immigration enforcement. But it simultaneously:
- Embeds suspicionless, pervasive surveillance into state practice,
- Relies on bureaucratic self-restraint rather than judicial oversight,
- Allows retention and profiling of movement data, and
- Provides limited citizen enforcement options.
The result is a regulatory compromise: it tucks one particular enforcement function (immigration use) out of sight, while leaving the underlying surveillance infrastructure largely intact and loosely governed.
That’s not a robust defense of privacy — it’s an exercise in transactional policy engineering that creates layers of permitted surveillance rather than actual limits on government power.
