Status is given as of November 17, 2026. The Act has applied since 2024-03-31 and is the strictest of the three for a sale, so most of this page follows it. These rules form the Washington layer of AI training data licensing.
Three Washington Statutes on a Training Data Deal at a Glance
Three Washington statutes decide whether health, biometric or recorded data may be licensed for training, and the table gives each one's citation, start date, duty and enforcer as of 2026-11-17.
| Instrument | Citation | In force | Who it binds | What it requires in a data deal | Enforcement | Status | Source |
|---|---|---|---|---|---|---|---|
| Washington My Health My Data Act | RCW 19.373 (2023 c 191) | 2024-03-31; small businesses 2024-06-30 | regulated entities and small businesses; the sale ban binds any person | separate consent to share, including licensing (19.373.030, 19.373.010(27)); signed authorization naming the buyer to sell (19.373.070) | Consumer Protection Act, private suits and the state (19.373.090) | in force | app.leg.wa.gov |
| Biometric identifiers | RCW 19.375 (2017 c 299) | 2017 | persons enrolling biometric identifiers for a commercial purpose | notice, consent or a mechanism to prevent later commercial use before enrolling; consent before sale except listed cases (19.375.020(1), (3)) | attorney general only (19.375.030(2)) | in force | app.leg.wa.gov |
| Washington Privacy Act (recording) | RCW 9.73.030 | chapter history from 1967 | any individual, partnership, corporation, association or the state | consent of all participants to record private communications or conversations (9.73.030(1)) | civil damages action (9.73.060) | in force | app.leg.wa.gov |
The sections follow the deal, with biometrics and recordings last.
What Counts as Consumer Health Data Under RCW 19.373.010
Consumer health data is personal information linked or reasonably linkable to a consumer that identifies the consumer's past, present or future physical or mental health status (RCW 19.373.010(8)(a)).
The list in (8)(b) runs from conditions and prescribed medication to precise location that could indicate an attempt to obtain health services. Deidentified and publicly available information is outside personal information (010(18)(b), (c)), but public information never includes biometric data collected without the consumer's consent (010(22)).
Inferred, Biometric and Genetic Data Inside the Definition
Health status inferred from non-health data counts too: the definition reaches information derived or extrapolated from non-health information, including by algorithms or machine learning (RCW 19.373.010(8)(b)(xiii)).
Biometric data (010(4)), which includes voice recordings from which an identifier template can be extracted, and genetic data (010(13)) are both listed in (8)(b)(ix) and (x). Genetic sets as a data type are covered under genetic and genomic data for AI training.
Regulated Entities, Small Businesses and the 2024 Start Dates
The Act binds any legal entity that does business in Washington or targets Washington consumers and decides the purpose and means of collecting, sharing or selling consumer health data (RCW 19.373.010(23)), with no revenue threshold.
Small businesses, defined by the thresholds in 010(28), comply from 2024-06-30 instead of 2024-03-31. The sale ban in 070(1) applies to "any person".
What the Act Leaves Out: HIPAA Records, Staff Data and Deidentified Data
Protected health information under HIPAA, staff records and deidentified data fall outside the Act, which is why a hospital's patient archive and a wellness app's user data sit under different rules.
Exemptions cover HIPAA protected health information (19.373.100(1)(a)(i)), information deidentified under 45 CFR Part 164 and derived from listed health care information ((1)(a)(viii)), public health use and limited data sets ((1)(c)), and data governed by the Gramm-Leach-Bliley Act, the Fair Credit Reporting Act or FERPA ((2)).
Deidentified data under 010(10) must meet three tests: reasonable measures against association with a consumer, a public commitment not to reidentify, and a contract binding every recipient to the same criteria, so the promise travels with the license. The federal rules are covered under HIPAA and AI training data.
Licensing Consumer Health Data Counts as Sharing: Separate Consent Under RCW 19.373.030
The Act defines sharing to include licensing consumer health data to a third party (RCW 19.373.010(27)(a)), so a training license needs the consumer's consent to share, separate and distinct from the consent given at collection (19.373.030(1)(b)). The request for consent, made before the sharing, must disclose (030(1)(c)):
- the categories of consumer health data shared;
- the purpose, including the specific ways the data will be used;
- the categories of entities receiving it;
- how the consumer can withdraw consent from future sharing.
Consent is an opt-in act, not given by accepting general terms of use (010(6)). A training purpose missing from the consumer health data privacy policy needs new disclosure and affirmative consent (020(1)(d)), and a processor acting outside its instructions becomes a regulated entity (060(1)(c)). Existing customer terms are examined under customer consent and confidentiality clauses before licensing data.
The Valid Authorization to Sell Consumer Health Data (RCW 19.373.070)
Since March 31, 2024, it is unlawful to sell or offer to sell consumer health data without first obtaining a valid authorization signed by the consumer, separate from the collection and sharing consents (RCW 19.373.070(1)).
The table lists the nine elements the authorization must contain, as of 2026-11-17.
| Element | What the authorization must contain | Subsection | Source |
|---|---|---|---|
| 1 | the specific consumer health data the seller intends to sell | 070(2)(a) | app.leg.wa.gov |
| 2 | name and contact information of the person collecting and selling | 070(2)(b) | app.leg.wa.gov |
| 3 | name and contact information of the purchaser | 070(2)(c) | app.leg.wa.gov |
| 4 | purpose of the sale, including how the data will be gathered and how the purchaser will use it | 070(2)(d) | app.leg.wa.gov |
| 5 | statement that goods or services may not be conditioned on signing | 070(2)(e) | app.leg.wa.gov |
| 6 | statement of the right to revoke at any time and how to revoke | 070(2)(f) | app.leg.wa.gov |
| 7 | statement that the purchaser may redisclose the data and it may no longer be protected | 070(2)(g) | app.leg.wa.gov |
| 8 | expiration date one year from signature | 070(2)(h) | app.leg.wa.gov |
| 9 | consumer's signature and date | 070(2)(i) | app.leg.wa.gov |
An authorization is not valid if it has any of five defects (070(3)):
- the expiration date has passed;
- it lacks any required information;
- the consumer has revoked it;
- it is combined with other documents in a compound authorization;
- goods or services are conditioned on signing it.
A sale is any exchange for monetary or other valuable consideration (010(26)(a)), so a paid training license is one. The authorization names the buyer and the buyer's use, so it cannot cover later, unnamed buyers, and the consumer receives a copy (070(4)).
One-Year Expiry, Six-Year Retention and Revocation
Every valid authorization expires one year after the consumer signs it, and both seller and purchaser must keep a copy for six years from signature or from the date it was last in effect, whichever is later (RCW 19.373.070(2)(h), (5)).
The consumer may revoke at any time, and a revoked authorization is void (070(2)(f), (3)(c)). A license therefore needs a renewal route and a records clause binding the developer, as set out under AI data licensing agreements. No court or regulator text decides how expiry affects data already used in a trained model.
Deletion Requests That Follow the Data to the Buyer
A Washington consumer can ask a seller to delete their consumer health data, and the seller must pass the request to every third party that received the data, which must delete it too (RCW 19.373.040(1)(c)(i)(B), (ii)). Related rights are:
- access to the data, including a list of all third parties and affiliates it was shared or sold to (040(1)(a));
- withdrawal of consent to collection and sharing (040(1)(b));
- compliance within 45 days of the request, extendable once by 45 days, with deletion from backups delayed by no more than six months (040(1)(g), (c)(iii)).
Transfers in a Merger or Bankruptcy: The Asset Exception
Transferring consumer health data as an asset in a merger, acquisition or bankruptcy in which the acquirer takes control of all or part of the business is neither a sale nor a share, provided the acquirer complies with the Act (RCW 19.373.010(26)(b)(i), (27)(b)(iii)).
No court or regulator text addresses a sale of the data set alone under this exception. The court process is described under US bankruptcy data sales under Section 363(b)(1).
Lawsuits and Penalties Under Washington Law
A violation of the My Health My Data Act is an unfair or deceptive act under the Consumer Protection Act, chapter 19.86 RCW (RCW 19.373.090), so injured persons can sue as well as the state.
As of 2026-11-17, RCW 19.86.090 allows an injunction, actual damages, costs and a reasonable attorney's fee, and the court may increase damages up to three times actual damages, with the increase capped at USD 25,000 for a violation of RCW 19.86.020.
RCW 19.86.140 sets a civil penalty of not more than USD 7,500 for each violation of 19.86.020.
The table compares the remedies of the three statutes, as of 2026-11-17.
| Statute | Who can enforce | Remedy as stated | Sections | Source |
|---|---|---|---|---|
| My Health My Data Act | injured persons; the state | injunction, actual damages, costs and reasonable attorney's fee; discretionary increase up to three times actual damages, capped at USD 25,000; civil penalty up to USD 7,500 per violation | 19.373.090; 19.86.020, .090, .140 | app.leg.wa.gov |
| Biometric identifiers | attorney general only | under the Consumer Protection Act; no private action | 19.375.030(1), (2) | app.leg.wa.gov |
| Washington Privacy Act (recording) | injured persons | actual damages including mental pain and suffering, or liquidated damages of USD 100 a day up to USD 1,000, plus reasonable attorney's fee | 9.73.060 | app.leg.wa.gov |
No ruling under the Act is recorded with a docket number, so no case is named here.
Washington's Biometric Identifier Statute Beside the Health Data Act
Washington has a second, older biometric law: RCW 19.375 (2017) bars enrolling a biometric identifier for a commercial purpose without notice, consent or a mechanism to prevent later commercial use, and bars selling it without consent except in listed cases (19.375.020(1), (3)).
The two definitions split on voice. The Act's biometric data covers voice recordings from which an identifier template can be extracted (19.373.010(4)(a)), while RCW 19.375.010(1) excludes audio recordings and data generated from them, so a voice archive can fall under one statute and not the other.
Only the attorney general enforces RCW 19.375 (030(2)), and Gramm-Leach-Bliley financial institutions are excluded (040(1)). The comparison across states is in biometric data in AI training compared across laws.
Recorded Calls and Meetings Under RCW 9.73.030: Every Participant Consents
Washington makes it unlawful to record a private communication or conversation without first obtaining the consent of all participants (RCW 9.73.030(1)(a), (b)), so a call or meeting archive recorded under a one-party practice carries that defect into any sale.
Consent is treated as obtained when one party announces to all others, in a reasonably effective manner, that the recording is about to start, and the announcement is itself recorded (030(3)).
A person injured by a violation can sue for actual damages or liquidated damages of USD 100 a day up to USD 1,000, plus a reasonable attorney's fee (RCW 9.73.060, as of 2026-11-17). In In re Otter.AI Privacy Litigation (N.D. Cal.
No. 5:25-cv-06911-EKL), plaintiffs allege recording without all-party consent and use of conversations and voiceprints for training, and the court dismissed the Washington Privacy Act count with leave to amend on 2026-08-13 (ECF 68). The allegations are unproven, and no later order on that count is recorded as of November 17, 2026.
Federal law is a one-party floor (18 U.S.C. 2511(2)(d)), and Washington is stricter. The state-by-state comparison is in call and meeting recording consent rules by jurisdiction.
Benefits, Risks, Downsides and Alternatives for a Seller Under Washington Law, Including Not Selling
Washington law lets a company license health, biometric or recorded data for AI training, but each statute adds a consent step, and licensing only exempt or deidentified data, or not licensing at all, remain valid choices.
Benefits
- HIPAA protected health information, HIPAA-deidentified data and GLBA, FCRA and FERPA data are exempt (19.373.100).
- Deidentified data meeting 19.373.010(10) is outside personal information.
- An asset transfer with the business is neither a sale nor a share (010(26)(b)(i)).
Risks
- Consumer Protection Act suits and penalties of up to USD 7,500 per violation (as of 2026-11-17).
- Recording damages under RCW 9.73.060.
- A void authorization, which leaves the sale unlawful.
Downsides
- One authorization per named buyer, valid one year and kept six years.
- Deletion requests that flow to the buyer.
- A separate consent to share on top of the collection consent.
Alternatives
- License deidentified or exempt data only.
- Exclude recordings made without all-party consent and biometric templates.
- License non-health data.
- Not selling or licensing at all.
The wider range of alternatives to selling data to AI labs has its own page.
Beyond Washington: Other States, Federal Rules and the Seller Process
Washington is one state layer on top of federal law. The United States AI training data law page compares it with eleven other states, and the seller pages turn these rules into steps.
- AI training data law by jurisdiction
- Privacy law and AI training data compared
- The other all-party state with a deidentification test
- Biometric law with a private action
- A state that bans the sale outright
- The federal one-party rule
- Financial data exempt from the Act
- Education records exempt from the Act
- Another state biometric statute
- Health data as a data type
- Clinics and health apps as sellers
- Meeting the three-part deidentification test
- Call archives as a data type
- The case with a Washington Privacy Act count
- The decision before any Washington sale
How This Page Is Sourced and Dated
Every rule here cites the Revised Code of Washington section or the court docket, with the date it was read. The methodology page explains how we source and date every rule. This page is general information about Washington law, not legal advice for any specific deal.
Frequently Asked Questions
Does the My Health My Data Act apply to AI training data?
Yes, whenever the set holds consumer health data of Washington consumers. That includes health status inferred by machine learning, biometric data and genetic data.
Can a company sell consumer health data to an AI developer in Washington?
Only with a valid authorization signed by each consumer, naming the buyer and the purpose. The authorization is valid one year and comes on top of separate consent to share.
Who can sue under the My Health My Data Act?
Injured persons can sue under the Consumer Protection Act, and the state can seek penalties. Damages can be trebled, with the increase capped at USD 25,000, and the civil penalty is up to USD 7,500 per violation (RCW 19.86.090, 19.86.140, as of 2026-11-17).
Does health data de-identified under HIPAA fall under the Act?
No, it is exempt. RCW 19.373.100(1)(a)(viii) excludes information deidentified under 45 CFR Part 164 and derived from listed health care information.