Skip to main content

ESSB 6002

Signed

Senate

Driver privacy

Concerning driver privacy protections.

How does a bill become law?
  1. Introduced: The bill is filed and assigned a number.
  2. Committee: A subject-matter committee holds hearings, takes public testimony, and decides whether to advance the bill.
  3. Floor Vote: The full chamber (House or Senate) debates and votes on the bill.
  4. Opposite Chamber: The bill repeats the committee and floor vote process in the other chamber.
  5. Governor: The Governor reviews the bill and decides whether to sign or veto it.
  6. Signed: The bill has been signed into law.
Introduced: January 21, 2026
Last Action: March 30, 2026
Status: C 239 L 26

AI Analysis

This analysis was generated by AI and may contain errors. It is not legal advice. Always refer to the official bill text for authoritative information.
People & CommunitiesPeople-leaningCorporate & Wealthy Interests

This bill establishes strict privacy protections and usage rules for automated license plate reader (ALPR) systems used by Washington state and local agencies. It limits when and how agencies can collect, retain, and share license plate data, bans use in sensitive locations, and requires transparency through audits and public reporting.

  • Establishes strict rules for when and how state and local agencies can use automated license plate reader (ALPR) systems—limiting use to specific authorized purposes like tracking stolen vehicles, missing persons, or enforcing parking/toll laws.
  • Prohibits use of ALPR systems to track people at or near facilities providing protected health care, immigration services, schools, places of worship, courts, or food banks.
  • Requires agencies to retain ALPR data for only short, specified time periods (e.g., 72 hours for most law enforcement uses, 12 hours for parking enforcement, 30 days for traffic studies), unless held under a court order or for active investigations.
  • Mandates creation and maintenance of detailed audit trails (e.g., who accessed data, when, why, and what was searched), retained for two years, and requires annual internal audits.
  • Bars use of ALPR data for immigration enforcement, prohibits sharing or selling the data, and makes ALPR data exempt from public records requests (except for non-identifiable research).
  • Creates criminal penalties (gross misdemeanor) for intentional misuse and provides a civil cause of action for individuals harmed by violations.

Who is affected

  • Law enforcement agenciesLaw enforcement agencies (state and local) must register ALPR systems, adopt policies, maintain audit trails, and follow strict rules about when and how they use ALPR data—including restrictions on immigration enforcement and access to sensitive locations.
  • Parking and transportation agenciesParking and transportation agencies must follow specific rules for using ALPR data—such as short data retention periods—and are prohibited from using the data for unauthorized purposes.
  • ALPR technology vendorsThird-party vendors providing ALPR services must implement technical safeguards to prevent unauthorized access or sharing and must provide audit data to agencies.
  • General publicGeneral public members may be impacted by increased transparency (e.g., agency annual reports), stronger privacy protections, and new legal recourse if their ALPR data is misused.
Effective: Immediate (upon passage)Fiscal impact: Agencies must allocate resources to register ALPR systems, develop and submit policies, conduct annual internal audits, and retain audit trail data for two years. The attorney general’s office will incur costs to develop model policies, receive and review agency submissions, and conduct audits. No specific dollar amount is provided.
Model: Intel/Qwen3-Coder-Next-int4-AutoRoundGenerated: Mar 19, 2026 at 9:30 PM

Pro/Con Analysis

Stronger case for benefits

Potential Benefits (5)
  • Prohibiting ALPR use at facilities providing protected health care (e.g., reproductive, gender-affirming, mental health services), immigration services, schools, places of worship, courts, and food banks prevents surveillance-based chilling of constitutionally protected activities and protects vulnerable populations from discriminatory targeting.

    Rights & LibertiesPeopleRef: Sec. 3(4)
  • Short, purpose-specific data retention periods (e.g., 12 hours for parking, 72 hours for most law enforcement, 30 days for traffic studies) significantly reduce the risk of long-term profiling, mission creep, and data breaches, protecting everyday Washingtonians from persistent government surveillance and potential misuse of their movement data.

    Rights & LibertiesPeopleRef: Sec. 4
  • Criminal penalties (gross misdemeanor) for intentional misuse and a private civil cause of action provide meaningful accountability and redress for individuals harmed by unauthorized ALPR use, especially those targeted for immigration enforcement, protest participation, or accessing sensitive services.

    Rights & LibertiesPeopleRef: Sec. 11 & 12
  • Exempting ALPR data from public records disclosure (except for non-identifiable research) prevents sensitive movement data from being weaponized against individuals or groups (e.g., activists, immigrants, domestic violence survivors), while still enabling oversight through internal and state auditor reviews.

    Rights & LibertiesPeopleRef: Sec. 5(5)
  • Mandating annual public reporting on ALPR usage (e.g., arrests resulting from matches, stolen vehicles recovered, sharing with other agencies) increases transparency and enables public oversight, helping communities hold agencies accountable for surveillance practices.

    Local GovernmentPeopleRef: Sec. 8(2)(a)(A)-(H)
Potential Concerns (5)
  • The bill prohibits ALPR use for immigration enforcement, which may hinder some law enforcement efforts to locate individuals with outstanding immigration-related warrants, though federal immigration enforcement is already restricted under RCW 10.93.160; this restriction is unlikely to meaningfully impair core public safety functions but could reduce investigative flexibility in multi-jurisdictional cases.

    Public SafetyRef: Sec. 3(2)(a)(ii)
  • The requirement that a positive ALPR match alone does not constitute reasonable suspicion for a stop may slow response times in time-sensitive investigations (e.g., stolen vehicles, Amber Alerts), especially in rural or under-resourced jurisdictions lacking redundant verification tools.

    Public SafetyRef: Sec. 3(2)(a)(ii)
  • Mandating annual public reporting of ALPR usage (e.g., total reads, hits, matches) imposes administrative burdens on small agencies without dedicated data infrastructure, potentially diverting limited staff time from frontline services.

    Local GovernmentLean peopleRef: Sec. 8(2)(a)(H)
  • Two-year retention of audit trail data and annual internal audits increase operational costs for local agencies, especially smaller jurisdictions that may lack dedicated IT or compliance staff.

    Local GovernmentLean peopleRef: Sec. 9(1)
  • Applying the Consumer Protection Act (CPA) to ALPR misuse expands the scope of CPA enforcement to government conduct, which could create uncertainty for vendors and agencies about what constitutes an “unfair or deceptive” practice in good-faith use, potentially chilling legitimate data use.

    Business & EmploymentRef: Sec. 10

Who Is Most Affected

Law enforcement agenciesMixed Impact

Law enforcement agencies gain stronger legal clarity and accountability safeguards, but must invest in compliance (training, policies, audits); overall impact is mixed but leans positive for agencies that already use ALPR responsibly, while potentially constraining agencies with less rigorous protocols.

Parking and transportation agenciesPositive Impact

Parking and transportation agencies benefit from clear usage boundaries and reduced liability risk, but must adjust operations (e.g., shorter data retention for parking enforcement), which may require minor system upgrades; overall impact is modestly positive.

ALPR technology vendorsNegative Impact

ALPR vendors face new technical and contractual obligations (e.g., preventing unauthorized access, providing audit data), increasing compliance costs; while this may reduce demand for non-compliant systems, overall impact is negative for vendors lacking robust security infrastructure.

General publicPositive Impact

The general public gains significant privacy protections—especially vulnerable groups (immigrants, reproductive health patients, protesters)—and new legal recourse for misuse; minimal downside beyond modest tax-funded compliance costs for agencies.

Local governmentsMixed Impact

Local governments (especially small cities and counties) face new administrative burdens (policy adoption, annual reporting, audits), but benefit from reduced liability exposure and alignment with constitutional privacy standards; impact is mixed but net positive for jurisdictions already practicing responsible data governance.