HB 1168 Washington House · 2025-2026 Regular Session

Increasing transparency in artificial intelligence.

HB 1168 requires commercial developers of generative AI systems (like text or image tools) to publicly document the data used to train their systems by January 1, 2026. This includes disclosing sources, types, and handling of training data - such as whether personal information or artificially created data was used - before releasing the AI to Washington users. Developers must post this documentation on their websites, with exemptions for AI focused solely on security, aircraft operations, or national defense. Violations carry $5,000 daily fines enforceable by the state attorney general, aiming to increase public awareness of AI development practices.

Issues: ✓ Technology

Bill status in committee 1 of 4 stages cleared

Introduction

Jan 2026

Committee Review

Floor Vote

Governor

Introduced Jan 12, 2026 Last action Jan 12, 2026

Maddy AI version diff · 1 comparison

What changed between versions

Bill → Substitute Bill · 4 edits

MODERATE

The bill was amended to expand the definition of 'developer' to include commercial entities while explicitly excluding internal researchers and API users, and to clarify that 'aggregate consumer information' refers to deidentified data. Additionally, the required disclosure of dataset sources was modified to clarify whether data was purchased or publicly available, and the reference for personal information was updated to a different RCW section.

Scope change

The scope of applicability was narrowed regarding who must comply; the definition of 'developer' now explicitly excludes individuals or entities developing AI solely for internal use, research, or via third-party APIs without substantial modification.

DEFINITION

The definition of 'developer' was expanded to require 'primary engagement' in AI design for commercial distribution, while adding specific exclusions for internal use, research, and API-only users.

The definition of 'aggregate consumer information' was updated to explicitly state that it does not mean 'deidentified' records, clarifying the distinction between anonymized and identifiable data.

REQUIREMENT

The requirement to disclose dataset sources was changed to ask if datasets were 'purchased or licensed' or 'publicly available,' replacing the previous option of asking if they were 'purchased or licensed' or 'in the public domain'.

The reference for defining 'personal information' was updated from RCW 19.255.005 to RCW 19.373.010.

Floor votes

How they voted

No floor votes recorded yet.

Full legislative history

Actions timeline

Total actions

Key actions

Committee

Jan 12, 2026

Committee

Referred to Technology, Economic Development, & Veterans.

lower

Jan 12, 2026

Lower · Passed

Committee relieved of further consideration.

lower

Jan 12, 2026

Introduced

By resolution, reintroduced and retained in present status.

lower

Feb 25, 2025

Lower · Passed

Public hearing in the House Committee on Appropriations at 1:30 PM.

lower

Jan 31, 2025

Committee

Referred to Appropriations.

lower

Jan 28, 2025

Lower · Passed

Minority; do not pass.

lower

Jan 28, 2025

Lower · Passed

Executive action taken in the House Committee on Technology, Economic Development, & Veterans at 10:30 AM.

lower

Jan 17, 2025

Lower · Passed

Public hearing in the House Committee on Technology, Economic Development, & Veterans at 10:30 AM.

lower

1 primary · 3 co-sponsors