IOT News
Washington State's Latest IoT Policy Moves and What They Mean for Local Businesses
Published by IOT Washington Research & Editorial Team

- Right to Repair Takes Effect for Connected Devices
- Health Data Rules Now Reach Far Beyond Traditional Healthcare
- A Modernized State Privacy Office and Growing AI Oversight
- What Businesses Should Actually Do
- Why This Matters More for Washington-Based IoT Companies Specifically
- What to Watch Next
- Practical Takeaway for Local IoT Businesses
Washington's 2026 legislative session produced one of the busiest stretches of technology policy activity the state has seen in years, spanning privacy, cybersecurity, artificial intelligence, and device repair rules. For any business building, selling, or deploying connected devices in Washington, from a Kirkland startup shipping a fitness wearable to a Spokane manufacturer instrumenting its shop floor, several of these changes carry direct, practical consequences. This article walks through the policy developments that matter most for IoT-related businesses and what to actually do about them.
Right to Repair Takes Effect for Connected Devices
Washington's Right to Repair Act, signed into law in May 2025, took effect on January 1, 2026, and it applies directly to the kind of digital electronics that make up much of the IoT hardware market. The law requires original manufacturers to make parts, tools, and repair documentation available to independent repair providers and product owners on fair and reasonable terms, covering digital electronic products first sold or used in Washington on or after July 1, 2021.
The law also restricts a practice called parts pairing, where manufacturer software blocks a replacement part from working properly, or triggers persistent warnings, unless the part is verified as an original manufacturer component. For companies building connected hardware, from smart home devices to industrial sensors, this means product design and software architecture decisions now carry direct legal weight. A device that locks out third-party replacement parts through software, a common design choice in the past to protect margins on parts and accessories, may now run afoul of state law. The Attorney General's office can enforce violations under the Consumer Protection Act, giving the requirement real teeth rather than functioning as a symbolic gesture.
Health Data Rules Now Reach Far Beyond Traditional Healthcare
Washington's My Health My Data Act has quietly become one of the most consequential privacy laws for IoT device makers in the country, precisely because its definition of covered health data has expanded well beyond what most companies would intuitively consider medical information. Newly clarified categories now explicitly include fitness tracker data, purchase histories tied to supplements, and wellness app information, even from general mindfulness or activity-tracking apps that never touch a clinical record.
For any Washington-based or Washington-serving company building wearables, health-adjacent smart devices, or apps that collect biometric or activity data, this means data practices that might seem like ordinary consumer analytics elsewhere in the country can trigger obligations under one of the strongest health privacy laws in the nation. The law is enforceable both by the state Attorney General and through private lawsuits, a combination that has made it a focal point for compliance planning well beyond companies that consider themselves part of the healthcare industry.
A Modernized State Privacy Office and Growing AI Oversight
Governor Bob Ferguson signed House Bill 2606 into law in March 2026, modernizing the state's Office of Privacy and Data Protection and mandating stricter AI oversight for state agencies. While the law is primarily focused on how state government handles personal data and deploys AI systems, it signals where Washington's broader regulatory posture is heading: toward more prescriptive rules around algorithmic decision-making, more transparency requirements, and a legislature that has grown comfortable regulating digital platforms and connected technology in ways it was not five years ago.
The bill passed with overwhelming bipartisan support, 89 to 6 in the House and unanimously in the Senate, a signal that data governance and AI oversight have become an area of rare cross-party agreement in Olympia. For IoT businesses watching where state policy is trending, that bipartisan momentum is worth tracking closely, since it often precedes broader rules extending into the private sector.
What Businesses Should Actually Do
| Policy Area | Practical Business Action |
|---|---|
| Right to Repair (effective January 1, 2026) | Audit device software for parts-pairing restrictions and prepare repair documentation and parts access processes |
| My Health My Data Act expansion | Review whether wearable, fitness, or wellness data collection practices trigger health data obligations, even without a clear clinical angle |
| State AI oversight momentum | Build internal AI governance and transparency practices ahead of likely future rules extending beyond state agencies |
| Ongoing privacy legislation (HB 1671 and similar) | Monitor comprehensive privacy bill progress, since Washington has moved closer than ever to passing broad consumer privacy legislation |
Industry groups like the Washington Technology Industry Association have been vocal that a patchwork of overlapping data rules risks raising compliance costs disproportionately for startups and small companies, compared to larger firms with dedicated legal teams. That advocacy has not stopped the overall regulatory trend, but it does suggest the details of how these rules get implemented and enforced remain an active, ongoing conversation rather than a settled matter.
Why This Matters More for Washington-Based IoT Companies Specifically
Washington occupies an unusual position nationally: it is home to some of the largest technology companies in the world, yet it has repeatedly failed to pass a single comprehensive consumer privacy law like California's or Virginia's. Instead, the state has built up its regulatory framework through targeted, sector-specific statutes, several of which happen to hit particularly hard for connected device makers, including the health data expansion and biometric identifier protections already on the books.
This approach creates a genuinely different compliance landscape than operating in a state with one comprehensive law. A Washington IoT company needs to track several distinct, sometimes overlapping statutes rather than a single unified privacy framework, which increases the practical burden of staying current even when no single law looks especially onerous in isolation.
The state's biometric identifier protection statute adds another layer worth flagging specifically for IoT hardware makers. Devices that rely on fingerprint sensors, facial recognition, or voiceprint authentication, increasingly common in everything from smart locks to workplace access systems, can trigger consent and disclosure obligations distinct from the general privacy rules that apply to less sensitive data types. A company building a connected security camera or biometric access panel for the Washington market needs to treat this statute as a separate compliance track, not an afterthought folded into general privacy policy language.
What to Watch Next
- The People's Privacy Act (HB 1671), which has advanced further than any prior comprehensive Washington privacy bill and could fundamentally reshape data collection rules if it eventually passes.
- Further guidance on how the Right to Repair Act's parts-pairing restrictions apply to specific IoT hardware categories, since enforcement details are still developing in the law's first year.
- Whether the bipartisan appetite for AI oversight demonstrated in HB 2606 extends into private-sector AI regulation in future sessions.
- Federal-level IoT policy activity, since state lawmakers nationally introduced more than 600 AI-related bills in 2026 alone, a volume that shapes how multistate companies approach Washington-specific compliance.
Practical Takeaway for Local IoT Businesses
None of these developments individually reinvents how a Washington IoT business operates, but together they represent a meaningful tightening of the regulatory environment around connected devices, data collection, and repairability. Companies that treat compliance as an ongoing, actively monitored function, rather than a one-time checklist, are best positioned to adapt as Washington continues its trajectory toward more comprehensive technology regulation, a trajectory that shows no sign of slowing given the bipartisan support these measures have attracted so far.
