Checklist: Washington’s My Health My Data Act for a health app or website

Fourteen steps under chapter 19.373 RCW for apps and websites that handle consumer health data: scoping who and what is covered, the privacy policy and homepage link, separate consents to collect and share, signed authorizations to sell, the 45-day rights clock, processor contracts and the geofence ban.

A state law that reaches beyond HIPAA

Washington’s My Health My Data Act, chapter 19.373 RCW, governs consumer health data held by regulated entities and small businesses, and by their processors [1]. Consumer health data is personal information linked or reasonably linkable to a consumer that identifies past, present or future physical or mental health status, including data inferred from nonhealth information (RCW 19.373.010(8)). Protected health information under HIPAA and several other categories are exempt (RCW 19.373.100), so the act matters most for apps, websites and services outside HIPAA. Most duties applied from March 31, 2024, and from June 30, 2024 for small businesses. A violation is an unfair or deceptive act under the Consumer Protection Act, chapter 19.86 RCW (RCW 19.373.090) [1].

Reading the steps

Each step cites the section of chapter 19.373 it rests on, from the text on the Legislature’s site checked on November 14, 2026 [1]. The owner under each step is a typical role, not one the act names: the act places its duties on regulated entities, small businesses and processors. Where a step is our suggestion rather than a requirement, it says so. This checklist explains the act; it is not legal advice, and counsel should confirm how it applies to a given product.

Moraph’s teams help organizations with work like this. See our solutions.

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. Privacy counsel

    RCW 19.373.010(23) covers any legal entity that conducts business in Washington or targets products or services to consumers there and determines the purposes and means of processing; government agencies are excluded. RCW 19.373.010(28) sets the small business thresholds. Under RCW 19.373.010(7), a consumer is a Washington resident or a person whose data is collected in Washington, acting in an individual or household context, not in employment [1].

  2. Privacy lead with product engineering

    RCW 19.373.010(8)(b) lists thirteen kinds of health status data, including data identifying a consumer seeking health care services and information derived or extrapolated from nonhealth data by algorithms or machine learning. RCW 19.373.010(18) counts persistent unique identifiers as personal information, and RCW 19.373.010(19) sets precise location at a radius of 1,750 feet [1].

  3. Privacy counsel

    RCW 19.373.100(1) and (2) exempt, among others, HIPAA protected health information, information governed by the Gramm-Leach-Bliley Act, the Fair Credit Reporting Act and FERPA, and information intermingled with exempt data held by covered entities and business associates. Under RCW 19.373.100(4), an entity relying on the security and fraud exemption bears the burden of showing it qualifies [1]. A written record of each exemption relied on is our suggestion.

  4. Privacy lead with the web and app teams

    RCW 19.373.020(1)(a) and (b) require the policy and the link. RCW 19.373.010(16) defines homepage for an app as its platform or download page and a link within the app, such as from the configuration, about, information or settings page [1].

  5. Product manager

    RCW 19.373.030(1)(a). Under RCW 19.373.010(6), consent is a clear affirmative, opt-in act; it cannot come from accepting general terms of use, from hovering over, muting, pausing or closing content, or through deceptive designs [1].

  6. Product manager with privacy counsel

    RCW 19.373.030(1)(b) requires sharing consent separate from collection consent. RCW 19.373.030(1)(c) requires each request to state the categories of data, the purpose and specific uses, the categories of recipients and how to withdraw consent. Disclosures to processors consistent with the purpose are not sharing under RCW 19.373.010(27) [1].

  7. Privacy lead

    RCW 19.373.020(1)(c) and (d) [1].

  8. Privacy counsel with marketing

    RCW 19.373.010(26) defines sale and excludes transfers as part of a merger, acquisition or bankruptcy, and exchanges with a processor consistent with the purpose of collection. RCW 19.373.070 requires a plain-language authorization naming the specific data, seller and purchaser, the purpose and use, a statement that service is not conditioned on signing, the right to revoke, a redisclosure warning, an expiry one year from signing, and the consumer’s signature and date. The consumer gets a copy, and seller and purchaser keep a copy for six years from the date of signature or the date it was last in effect, whichever is later [1]. Reviewing advertising and analytics data flows against the sale definition with counsel is our suggestion.

  9. Privacy operations

    RCW 19.373.040(1)(a) to (c). A deletion must reach all parts of the network, may be delayed up to six months for archived or backup systems, and must be passed to every affiliate, processor, contractor and third party that received the data. Under RCW 19.373.040(1)(f), responses are free up to twice a year per consumer [1].

  10. Privacy operations with customer support

    RCW 19.373.040(1)(d) to (h): a secure and reliable request method described in the policy, no requirement to create a new account, a response within 45 days with one 45-day extension if the consumer is told why within the first period, and an appeal decided in writing within 45 days that, if denied, tells the consumer how to complain to the attorney general [1].

  11. CISO

    RCW 19.373.050(1)(a) and (b) require both, appropriate to the volume and nature of the data [1].

  12. Procurement and privacy counsel

    RCW 19.373.060(1) requires the contract, requires processors to assist, and treats a processor that goes beyond its instructions as a regulated entity for that data. RCW 19.373.020(1)(e) makes it a violation to contract for processing inconsistent with the policy [1].

  13. Marketing operations with privacy counsel

    RCW 19.373.080 makes this unlawful for any person; RCW 19.373.010(14) defines a geofence as a virtual boundary of 2,000 feet or less from the perimeter of the location [1]. Reviewing location targeting in advertising tools against this ban is our suggestion.

  14. Product manager

    RCW 19.373.030(1)(d) bars unlawful discrimination against a consumer for exercising rights under the chapter, and RCW 19.373.090 makes violations enforceable under the Consumer Protection Act [1].

Spotted an error? Tell us and we will check it and correct the checklist where needed.

  • Washington
  • My Health My Data Act
  • RCW 19.373
  • consumer health data
  • consent
  • health apps
  • geofencing