Compliance team mapping state privacy laws compliance requirements into one program

June 12, 2026 | Compliance

The Rise of State-Level Privacy Laws: A Compliance Roadmap

State privacy laws keep multiplying. Build one program on shared requirements instead of tracking each law alone. Here is the roadmap.

A growing number of US states now have their own comprehensive privacy laws, and each one defines personal data, consumer rights and enforcement a little differently. If your company sells across state lines, you are probably covered by several of them at once, whether or not you have mapped them.

The answer is not to write one policy per state. It is to build a single privacy program around the requirements that nearly every law shares, then add small state-specific overlays where the laws genuinely differ. This post lays out how to do that and where to start.

Why a patchwork is a program problem, not a legal-reading problem

California started the trend with the CCPA, later amended by the CPRA. Virginia, Colorado, Connecticut and a growing number of other states followed with their own statutes, many modeled on a similar framework. There is still no single federal privacy law that replaces them, so the state laws are what you work with.

Reading each statute one by one does not scale. Thresholds, definitions of "sensitive data," exemptions and cure periods vary, and states keep amending their laws. If your compliance work depends on one person tracking every change by hand, it will fall behind.

A better approach treats the laws as variations on a common core. You build the core once, run it consistently, and review the differences on a schedule.

The common core most state laws share

Despite the differences, the major state laws keep returning to the same building blocks. Design your program around these and you will cover most of the ground.

  • Consumer rights. Access, deletion, correction and portability requests, plus the right to opt out of the sale or sharing of personal data, targeted advertising and certain kinds of profiling.
  • Notice. A clear, current privacy notice that says what you collect, why, who receives it and how people can exercise their rights.
  • Sensitive data rules. Many laws require consent, or at least heightened handling, for categories such as health data, precise geolocation, biometrics and data about children.
  • Data protection assessments. A documented risk assessment for higher-risk processing, such as targeted advertising, sale of data, profiling and sensitive data.
  • Processor contracts. Written agreements with vendors that handle personal data on your behalf, setting out instructions, security duties and deletion or return at the end of the relationship.
  • Reasonable security and purpose limits. Collect what you need, use it for stated purposes, and protect it appropriately.

Set your program to the strictest reasonable standard

The practical way to avoid maintaining dozens of variants is to apply the stricter requirement everywhere you can, and only branch when the cost of doing so is high. This is often called a "high-water mark" approach.

For example, if some states require opt-in consent for sensitive data and others only require notice and an opt-out, collecting opt-in consent from everyone is simpler than running two flows. Honoring opt-out preference signals from browsers, which some states require, is easier to build once for all visitors than to detect by location.

There are exceptions. A rule that would damage a core business function in every market may be better handled as a targeted overlay. Make that call deliberately, write down why, and review it when the laws change.

Know what you hold before you promise anything

Every rights request and every assessment depends on knowing what personal data you have and where it goes. This is the step most teams skip and later regret.

Build a data inventory that covers:

  • The categories of personal data you collect and the systems that store them.
  • The purpose and legal basis for each use.
  • Which vendors and partners receive the data.
  • How long you keep it and how it is deleted.

Keep it light enough that people will actually update it. A shared register that is reviewed quarterly beats a perfect diagram that is out of date within a month. Every compliance program benefits from this step, because the inventory feeds every other deliverable.

Make rights requests a repeatable process

Most laws set a response window for consumer requests, and many require you to verify the requester and offer an appeal. A mailbox that one person checks when they have time will not hold up.

Define the process end to end: where requests come in, how identity is verified, who searches which systems, how deletion reaches backups and vendors, and how the response is recorded. Assign an owner and a backup, and keep a log of every request and outcome. That log is the evidence a regulator or auditor will ask to see.

Watch the exemptions

Several state laws exempt certain entities or data, such as data already covered by HIPAA or the Gramm-Leach-Bliley Act, or limit coverage by revenue or volume thresholds. Exemptions differ by state and are often narrower than people assume, for example applying to the data but not the whole company. Confirm your position with counsel rather than assuming you are out of scope.

Do not forget the laws that bite differently

Some statutes sit outside the general framework and carry sharper enforcement. Illinois' Biometric Information Privacy Act (BIPA) gives individuals a private right of action over the collection of biometric identifiers. Washington's My Health My Data Act covers consumer health data that falls outside HIPAA and also allows private lawsuits. If you handle biometrics or health-adjacent data, treat these as their own workstreams.

Children's and teen data, data broker registration and automated decision-making are other areas where states are adding rules. Track them in the same review cycle so they do not surprise you.

Keep it current without rebuilding it

A privacy program is a living system. Set a quarterly review that covers new or amended laws, changes to your products and data flows, new vendors, and the volume and type of requests you received. Update the notice, the inventory and the assessments from that single review rather than reacting to each headline.

Tie the program into the rest of your governance. The same vendor reviews, access controls and retention rules that support SOC 2 or ISO/IEC 27001 also support privacy compliance, so run them together instead of in separate silos.

Where to start

  1. Find out where you are covered. List the states where you have customers, employees or meaningful data subjects, and check applicability thresholds with counsel.
  2. Build the data inventory. Start with your highest-risk systems and sensitive data, then widen out.
  3. Pick your baseline. Choose the strictest practical standard for notice, consent and opt-outs, and document any overlays.
  4. Stand up the rights-request process. Assign owners, build the log and test it with a dummy request.
  5. Review vendor contracts. Make sure processors are bound by the terms these laws expect.

If you want help turning this into a working program, our privacy team can help, or get in touch.

Written By: Ken Pomella