At a Glance
- The MHMDA protects consumer health data that falls outside HIPAA, including inferred data and precise location data that could indicate an attempt to obtain health services.
- It applies to any business that operates in Washington or targets Washington consumers, wherever the business is located.
- Businesses need opt-in consent to collect consumer health data and separate consent to share it. Selling it requires a signed authorization.
- Consumers can access, delete, and withdraw consent for their data, and businesses must respond within 45 days, extendable once by 45 days.
- The Washington Attorney General enforces the Act, and consumers can sue through the Consumer Protection Act.
- Litigation to date has centered on tracking technologies such as SDKs and website pixels.
The Washington My Health My Data Act (MHMDA) aims to enhance consumer privacy protections specifically related to health data. Unlike most other U.S. state-level data privacy laws, which cover a wider range of information that is considered personal information or personal data, the Washington MHMDA focuses solely on protecting consumer health data.
As of November 2026, Washington still has no comprehensive state privacy law, unlike its neighbor Oregon. Lawmakers have introduced bills repeatedly since 2019, and the latest proposal, HB 1671, has not passed. The Washington Attorney General’s first Data Privacy Report, published in August 2026, again highlighted the gap.
The Act defines a consumer as either a natural person who is a Washington resident or someone whose consumer health data is collected in the state of Washington. It does not include individuals acting in an employment context.
While U.S. federal laws such as the Health Insurance Portability and Accountability Act (HIPAA) already protect some health data of Washington residents, HIPAA applies only to health data collected by specific healthcare entities, such as most healthcare providers.
The Washington My Health My Data Act extends comparable protections to health data collected by entities not bound by HIPAA, including certain apps, websites, and small businesses.
The Act has four main aims:
- Require additional disclosures and consumer consent regarding the collection, sharing, and use of health data
- Empower consumers with the right to have their health data deleted
- Prohibit the selling of consumer health data without valid authorization signed by the consumer
- Make using a geofence around a facility that provides healthcare services unlawful
What Does the Washington My Health My Data Act Protect?
The Washington MHMDA protects the health data of those defined as consumers under the Act. It provides a broad definition of consumer health data, which means “personal information that is linked or reasonably linkable to a consumer and that identifies the consumer’s past, present, or future physical or mental health status.”
It further specifies that physical or mental health status includes, but is not limited to, 13 types of data:
- Individual health conditions, treatment, diseases, or diagnosis
- Social, psychological, behavioral, and medical interventions
- Health-related surgeries or procedures
- Use or purchase of prescribed medication
- Bodily functions, vital signs, symptoms, or measurements of the data types included under the definition
- Diagnoses or diagnostic testing, treatment, or medication
- Gender-affirming care information
- Reproductive or sexual health information
- Biometric data
- Genetic data
- Precise location information that could reasonably indicate a consumer’s attempt to acquire or receive health services or supplies
- Data that identifies a consumer seeking healthcare services
- Any information that a regulated entity or a small business, or their respective processor, processes to associate or identify a consumer with this data described that is derived or extrapolated from non-health information (such as proxy, derivative, inferred, or emergent data by any means, including algorithms or machine learning)
Exemptions Under the Washington MHMDA
The Act exempts certain categories of data rather than entire organizations. Exempt data includes personal information governed by:
- Gramm-Leach-Bliley Act (GLBA)
- Family Educational Rights and Privacy Act (FERPA)
- Social Security Act
- Fair Credit Reporting Act (FCRA)
- Protected health information under HIPAA
- Washington’s Uniform Health Care Information Act (chapter 70.02 RCW)
- Substance use disorder patient records under 42 C.F.R. Part 2
The definition of consumer health data also excludes personal information used in public or peer-reviewed scientific, historical, or statistical research in the public interest that follows other applicable ethics and privacy laws.
The research must be approved, monitored, and governed by one of the following bodies, which must determine that the regulated entity or small business has implemented reasonable safeguards, including against reidentification:
- An institutional review board
- Human subjects research ethics review board
- Similar independent oversight entity
The Act also permits processing needed to prevent, detect, or respond to security incidents, identity theft, fraud, harassment, or other illegal activity. A business relying on this carve-out bears the burden of showing that the processing qualifies.
Who Must Comply With the Washington My Health My Data Act?
The Washington MHMDA applies to three categories of entities.
Regulated Entities
These are legal entities that:
- Conduct business in Washington state, or produce or provide products or services targeted to consumers in the state
- Alone or jointly with others determine the purpose and means of collecting, processing, sharing, or selling consumer health data
This category includes businesses physically located in Washington and those outside the state that target their products or services to Washington consumers. Notably, entities that merely store data in Washington without engaging in other data processing activities are not considered regulated entities under this Act.
Government agencies, tribal nations, or contracted service providers that process consumer health data on behalf of the government agency are exempt from the definition of a regulated entity.
Small Businesses
A small business under the Washington MHMDA is a regulated entity that satisfies one or both of the following conditions:
- Collects, processes, sells, or shares consumer health data of fewer than 100,000 consumers during a calendar year
- Derives less than 50 percent of gross revenue from the collection, processing, selling, or sharing of consumer health data, and controls, processes, sells, or shares consumer health data of fewer than 25,000 consumers
Small businesses must meet the same requirements as larger entities, but they had until June 30, 2024, rather than March 31, 2024, to comply with Sections 4 to 9. Both deadlines have passed, so the same obligations now apply to all regulated entities.
Regulated entities and small businesses under the Washington MHMDA are similar in function to “data controllers” as defined in other U.S. and global data protection regulations, such as the General Data Protection Regulation (GDPR). They determine the purposes and means of processing consumer health data.
Processors
Individuals or organizations that process consumer health data on behalf of a regulated entity or small business are designated as processors under the Act. This includes out-of-state processors working for Washington-based entities.
What Are the Effective Dates for the My Health My Data Act?
The Washington MHMDA includes effective dates on a section by section basis and based on the type of entity that must comply with its requirements. The last of these dates passed in June 2024, so the Act’s requirements apply in full.
Definitions Under the Washington My Health My Data Act
The Washington MHMDA defines some key terms pertaining to data processing activities.
Geofencing Under the Washington MHMDA
Under the Act, geofencing is technology that uses any of the following to establish a virtual boundary that is 2,000 feet (609.6 meters) or less from the perimeter of a specific physical location, or to locate a consumer within a virtual boundary:
- Global positioning coordinates
- Cell tower connectivity
- Cellular data
- Radio frequency identification
- WiFi data
- Any other form of spatial or location detection
Processing Under the Washington MHMDA
The Washington MHMDA provides a broad definition of processing to include “any operation or set of operations performed on consumer health data.”
Sale Under the Washington MHMDA
The Act defines sale or sell as “the exchange of consumer health data for monetary or other valuable consideration.” It specifically excludes from this definition the sale of consumer health data that is:
- Transferred to a third party as part of a merger, acquisition, bankruptcy, or other transaction, where the third party assumes control of the regulated entity’s assets and complies with the Act’s requirements
- Exchanged with a processor, provided it aligns with the original purpose for which the data was collected and disclosed to the consumer
Sharing Under the Washington MHMDA
Under the Washington MHMDA, share or sharing means “to release, disclose, disseminate, divulge, make available, provide access to, license, or otherwise communicate orally, in writing, or by electronic or other means, consumer health data by a regulated entity or a small business to a third party or affiliate.”
The term does not include:
- Sharing data with a processor to provide goods or services, as long as it aligns with the original purpose for which the data was collected and disclosed to the consumer
- Sharing data with a third party with whom the consumer has a direct relationship, provided it is for a product or service requested by the consumer, the regulated entity retains control of the data, and the third party uses the data only as directed by the regulated entity and consistent with the consumer’s consented purpose
- The disclosure or transfer of personal data as part of a merger, acquisition, bankruptcy, or other transaction, where the third party assumes control of the regulated entity’s assets and complies with the Act’s requirements.
Consent Under the Washington MHMDA
Consent is defined under the Act as “a clear affirmative act that signifies a consumer’s freely given, specific, informed, opt-in, voluntary, and unambiguous agreement, which may include written consent provided by electronic means.”
Regulated entities and small businesses may not obtain consent by:
- A consumer accepting a general or broad terms of use agreement or a similar document that includes descriptions of personal data processing along with other unrelated information
- A consumer hovering over, muting, pausing, or closing a given piece of content
- Using deceptive designs, also known as dark patterns
Personal Information Under the Washington MHMDA
The Act defines personal information as information that identifies, or can reasonably be linked to, a particular consumer, directly or indirectly. This includes data associated with a persistent unique identifier, such as a cookie ID, an IP address, or a device identifier.
Precise Location Under the Washington MHMDA
Precise location information means data that identifies an individual’s specific location within a radius of 1,750 feet.
Restrictions on Data Processing Activities Under the Washington My Health My Data Act
Section 5 of the Washington MHMDA prohibits regulated entities and small businesses from collecting consumer health data, except in any one of the following cases:
- They obtained consent from a consumer to collect their health data for a specified purpose
- The data is necessary to provide a product or service that the consumer has requested from the regulated entity or small business
Consumer health data collected on either of these bases cannot be shared without the consumer’s separate and distinct consent, unless sharing is necessary to provide a product or service that the consumer has requested.
Consent must be opt-in and obtained before the collection or sharing takes place, and the request for consent must clearly and conspicuously disclose all of the following information:
- Categories of consumer health data collected or shared
- Purpose of collection or sharing, including specific ways in which it will be used
- Categories of entities with whom the data is shared
- How the consumer can withdraw consent
Section 9 of the Act makes it unlawful for any person to sell or offer to sell consumer health data without first obtaining valid authorization from the consumer. This authorization must also be separate from the consents obtained to collect and/or share consumer health data.
A valid authorization under the Act must be written in plain language that is easy to understand, and must contain the following information:
- Specific consumer health data concerning the consumer that the person intends to sell
- Name and contact information of the person collecting and selling the consumer health data
- Name and contact information of the person purchasing the consumer health data
- Description of the purpose for the sale, including how the consumer health data will be gathered and how it will be used by the purchaser when sold
- Statement that requiring the consumer to sign the valid authorization is not a condition to providing goods or services
- Statement that the consumer has a right to revoke the valid authorization at any time and a description on how to submit a revocation of the valid authorization
- Statement that the consumer health data sold under the valid authorization may be disclosed again by the purchaser and may lose its protection under this section.
- Expiration date for the valid authorization that expires one year from when the consumer signs the valid authorization
- Signature of the consumer and the date of signing
An authorization is invalid if:
- The expiration date has passed
- It doesn’t contain all the required information
- The consumer revokes it
- It has been combined with other documents
- It is required for the consumer to receive goods and services
The consumer must receive a copy of the signed valid authorization. Both the seller and purchaser must keep copies of all valid authorizations for sale of consumer health data for six years from the date of its signature or the date when it was last in effect, whichever is later.
Consumer Rights Under the Washington My Health My Data Act
Under Section 6 of the Washington My Health My Data Act, consumers are granted specific rights with respect to their health data. These rights include:
- Right to access: consumers can confirm whether a regulated entity or small business is collecting, sharing, or selling their health data. They can also access this data and receive a list of all third parties and affiliates who have received it, along with contact information for these third parties.
- Right to withdraw consent: consumers can withdraw their previously given consent for the collection and sharing of their health data.
- Right to deletion: Consumers can request deletion of their health data from the records of a regulated entity or small business, including data held on archived or backup systems. The business must also notify affiliates, processors, contractors, and other third parties with whom it shared the data, and they must delete it too. Deletion from archives and backups may be delayed, but by no more than six months from authenticating the request.
Obligations under the Washington My Health My Data Act
Entities within the scope of the Washington MHMDA have several obligations toward consumers and their health data.
Consumers can exercise their rights under Section 6 of the Act at any time by making a consumer rights request to the regulated entity or small business. Consumer rights requests are often referred to as data subject requests (DSR) or data subject access requests (DSAR).
Regulated entities and small businesses are required to establish a secure and reliable method for consumers to exercise their rights, which must be described in the consumer health data privacy policy. Consumers can be asked to log into an existing account to verify their identity, but they must not be required to create a new account to submit a request or otherwise exercise their rights.
If the regulated entity or small business cannot authenticate the request using commercially reasonable efforts, it is not required to comply and may ask the consumer for the additional information needed to authenticate the consumer and the request.
The regulated entity or small business must respond to a consumer request within 45 days, with an extension option of another 45 days if necessary (e.g., the entity is experiencing a high volume of requests or there are difficulties in accessing all the required information). If an extension is required, the consumer must be notified before the expiry of the initial 45-day period.
The regulated entity or small business must establish a process for consumers to appeal a refusal to act on a consumer request. This process must be similar to the process for submitting a request. The regulated entity or small business has 45 days to respond to an appeal, and it must provide a written explanation of its decision to the consumer.
If the appeal is denied, the regulated entity or small business must provide the consumer with a way to contact the Attorney General, either online or through another method, to submit a complaint.
Businesses must provide information in response to a request free of charge, up to twice a year per consumer. If requests are manifestly unfounded, excessive, or repetitive, the business may charge a reasonable fee or decline to act, but it bears the burden of showing that the request meets that description.
Privacy Policy Requirements Under the Washington MHMDA
Section 4 requires regulated entities and small businesses to maintain a consumer health data privacy policy and to publish a prominent link to it on their homepage. The Act defines “homepage” to include any web page where personal information is collected and, for mobile apps, the app’s platform or download page and a link within the app.
According to guidance from the Washington Attorney General, the link must be separate and distinct, and the policy may not contain information that the Act does not require. The consumer health data privacy policy must clearly outline:
- Categories of consumer health data collected
- Purposes for which the data is collected and how it will be used
- Categories of sources from which the data is collected
- Categories of consumer health data that are shared
- Categories of third parties and specific affiliates with whom the data is shared
- How consumers can exercise their rights under the Act
A regulated entity or small business cannot collect, use, or share additional categories of consumer health data, or use the data for additional purposes, without first disclosing them in the policy and obtaining the consumer’s affirmative consent.
It is a violation for a regulated entity or small business to contract with a processor to handle consumer health data in ways that contradict this privacy policy.
Data Security Measures Under the Washington MHMDA
Under Section 7 of the Washington MHMDA, regulated entities and small businesses must take specific steps to protect consumer health data.
First, they must restrict access to consumer health data. This means access should only be granted to employees, processors, and contractors who need it to carry out the purposes consented to by the consumer, or to deliver a product or service requested by the consumer.
They are also required to put in place comprehensive administrative, technical, and physical data security practices. The standards for these practices should at minimum meet the reasonable standard of care within the industry to protect the confidentiality, integrity, and accessibility of consumer health data, taking into account the volume and nature of the consumer health data handled.
Data Processing Agreements (DPAs) Under the Washington MHMDA
Section 8 of the Washington MHMDA requires regulated entities and small businesses to enter into a binding contract with processors before they can process consumer health data on their behalf.
This contract is known as a data processing agreement in laws such as the GDPR and the Virginia Consumer Data Protection Act (VCDPA), and must clearly outline the processing instructions and restrict the actions the processor can take with the consumer health data.
The Act explicitly requires that processors can only process consumer health data in a way that aligns with the detailed instructions provided in their contract with the business.
Processors must also assist the regulated entity or small business by implementing appropriate technical and organizational measures to help fulfill their obligations under the Washington MHMDA.
If a processor fails to follow the business’s instructions, or processes data outside the scope of the contract, it is treated as a regulated entity or small business for that data and becomes subject to all of the Act’s requirements concerning it.
Geofencing Restrictions Under the Washington My Health My Data Act
The Washington MHMDA imposes specific restrictions on the use of geofencing technology in proximity to healthcare services. It prohibits any person from implementing geofences within a 2,000-foot perimeter of locations providing in-person healthcare services if the geofence is used for:
- Identifying or tracking consumers seeking healthcare services
- Collecting consumer health data
- Sending notifications, messages, or advertisements related to consumer health data or healthcare services
This broad application means that the restriction on geofencing technology is not limited to specific types of businesses, but includes any individual or entity using such technology in the specified manner around healthcare services.
Healthcare services under the Act mean any service provided to a person to assess, measure, improve, or learn about their mental or physical health. It includes, among other things:
- Individual health conditions, status, diseases, or diagnoses
- Social, psychological, behavioral, and medical interventions
- Health-related surgeries or procedures
- Use or purchase of medication
- Bodily functions, vital signs, symptoms, or measurements of the information included under the definition
- Diagnoses or diagnostic testing, treatment, or medication
- Reproductive healthcare services
- Gender-affirming care services
Enforcement and Penalties Under the Washington My Health My Data Act
The Washington Attorney General is empowered to enforce the Washington MHMDA. Violations of the Act are treated as unfair or deceptive acts under the Washington Consumer Protection Act (CPA), which allows the Attorney General to bring actions against violators and seek civil penalties of up to USD 7,500 per violation.
Unlike many other state privacy laws, the Washington MHMDA allows consumers to sue. The Act does not create a separate cause of action. Instead, consumers sue through the CPA and must prove its elements, including injury to their business or property and a causal link to the violation.
In August 2026, the Attorney General published the state’s first Data Privacy Report. It recommended stronger protections for sensitive data, including biometric identifiers and precise geolocation data, which fall within the MHMDA’s definition of consumer health data.
Successful plaintiffs can recover actual damages, court costs, and reasonable attorneys’ fees, and a court may increase the damages award up to three times, not to exceed USD 25,000.
Committee Review Under the Washington My Health My Data Act
The Act directs a joint legislative committee to review enforcement actions brought by the Attorney General and consumers (RCW 44.28.819). The joint committee must submit a report of its findings and recommendations to the Governor and the appropriate committees of the legislature by September 30, 2030.
The provisions related to the review of enforcement actions expire on June 30, 2031.
Lawsuits Filed Under the Washington My Health My Data Act
The Washington MHMDA gives consumers a private right of action through the CPA. On February 10, 2025, the first class action based on the law was filed against an online retailer. The plaintiffs voluntarily dismissed their claims without prejudice in May 2025, and the consolidated case closed on June 6, 2025, without a ruling on the merits. The sections below summarize the allegations in that complaint.
What Violation of the Washington MHMDA Did the First Lawsuit Allege?
The complaint alleges that the advertising division of the retailer — unlawfully and unknown to the consumer — used a software development kit (SDK) on consumers’ mobile devices to collect and monetize their location data.
The SDK allegedly performs various functions for advertising purposes, including attribution, mediation, measurement, etc., and the retailer allegedly licenses it to mobile application developers. The complaint alleges that the SDK is designed to collect many individual data points from the location of a user’s mobile phone.
According to the complaint the SDK has been integrated into more than 10,000 Android and iPhone mobile applications, which millions of North American consumers have downloaded.
What Data Did the Complaint Say Was Collected, and How Was It Used?
It’s also alleged that when the user agrees to share their location with a specific mobile app, via the SDK the retailer will also have access to the collected location data, including time-stamped geolocation coordinates and mobile advertising IDs (MAIDs), which they then monetize.
The complaint alleges that this location data enables insights into consumers’ health and lifestyle, which could be sensitive information, including visits to a cancer clinic, stops at fast food restaurants, where a person lives and works, and social contacts that can influence health status, like during the COVID-19 pandemic.
The complaint contends that the retailer did not inform consumers or obtain their consent for use of these technology functions — or, indeed, about the presence of the SDK at all — or data use before collecting, sharing, and selling this data for its own targeted advertising.
Since consumers did not know about the SDK or the data processing, according to the complaint, they also didn’t have the opportunity to accept or decline consent for access to their data, separate from using the app.
What Other Laws Did the Complaint Cite?
The complaint asserts several violations of multiple laws in addition to the Washington MHMDA, including:
- Federal Wiretap Act (FWA), as amended by the Electronic Communications Privacy Act of 1986 (ECPA)
- Stored Communications Act
- Computer Fraud and Abuse Act (CFAA)
- Washington Consumer Protection Act (CPA) (through this Act consumers are provided with the private right of action under the Washington MHMDA)
To succeed under the CPA, plaintiffs must prove that the defendant engaged in an unfair or deceptive act or practice in trade or commerce that affected the public interest, and that the act caused injury to their business or property.
Regarding the Washington MHMDA, the complaint alleges these specific violations:
- Failure to obtain a consumer’s consent prior to collecting and sharing consumer health data (including biometric data)
- Failure to include a clear and conspicuous disclosure with a consent request, including:
- Categories of health data collected or shared
- Purposes of collection or sharing
- Categories of entities with whom the data is shared
- Instructions for how consumers can withdraw consent from future data processing
What Penalties Can Apply in a Private Lawsuit Under the Washington MHMDA?
Under the Washington MHMDA via the CPA, plaintiffs who prove injury from a violation can recover actual damages, court costs, and reasonable attorneys’ fees. A court may also increase the damages award up to three times, not to exceed USD 25,000.
Second Class Action Targets Website Tracking
On November 6, 2025, a second putative class action was filed in the Western District of Washington against the operators of a Seattle-area cannabis retailer. The complaint alleges that tracking pixels and cookies on the retailer’s website shared information about online purchases, including medical marijuana products, and appointment scheduling with Google and other third parties without consent. It asserts a claim under the Washington MHMDA alongside federal wiretap and common law claims.
Both complaints center on tracking technologies. Businesses that use pixels, SDKs, or similar tools on pages or apps where health-related data may be collected should review what those tools collect and when they fire.
Next Steps for Businesses Under the Washington MHMDA
The Act has applied to all regulated entities since 2024, and the lawsuits filed so far target tracking technologies rather than clinical records. Businesses within its scope can take the following steps to help meet its requirements:
- Map where consumer health data is collected, including through pixels, SDKs, and other third-party tools.
- Publish a consumer health data privacy policy with its own prominent homepage link.
- Obtain opt-in consent before collecting consumer health data, separate consent before sharing it, and a signed authorization before any sale.
- Set up a secure process for access, deletion, consent withdrawal, and appeal requests, and track the 45-day response periods.
- Put binding contracts in place with every processor that handles consumer health data.
- Check that no geofence is used within 2,000 feet of a facility that provides in-person health care services.
Because the Act’s key terms have not yet been tested in court, qualified legal counsel should review how it applies to a specific business.
Usercentrics does not provide legal advice, and information is provided for educational purposes only. We always recommend engaging qualified legal counsel or privacy specialists regarding data privacy and protection issues and operations.
