Securafy | Knowledge Hub

State Privacy Law Thresholds 2026: Is Your SMB In Scope?

Written by Ric Hall | Nov 17, 2026, 1:00:00 PM

We have 60 employees and no national footprint, so do state privacy laws really apply to us? We hear that question from growing businesses more than any other privacy question, and in 2026 the honest answer changed for many of them. State privacy law thresholds are not measured in headcount or, in most states, revenue. They are measured in how many residents' personal data you handle and what kind of data it is, and several states lowered those numbers sharply this year.

Rhode Island's law, effective January 1, 2026, applies to for-profit businesses that controlled or processed the personal data of at least 35,000 Rhode Island customers in the preceding calendar year, excluding data processed solely to complete a payment. An e-commerce brand, a regional healthcare practice, or a membership organization can cross that line without ever thinking of itself as a large data business.

Why business size is the wrong way to read state privacy law thresholds

The common belief is that comprehensive privacy laws are written for big tech and large enterprises, and that a small company is safe until it reaches some revenue figure. That belief is wrong in most states, and it is getting more wrong each year. Coverage under most state laws turns on three things: how many state residents' personal data you control or process in a year, whether you process sensitive data, and whether you sell or share personal data. A company with 40 employees and a popular website or loyalty program can meet the first test before a company with 400 employees and a handful of industrial customers.

Connecticut shows how fast the ground can move. Under amendments that took effect July 1, 2026, Connecticut's law now reaches businesses that process the personal data of at least 35,000 Connecticut consumers, down from 100,000, or that process any amount of sensitive data, or that offer any personal data for sale. The sensitive-data and sale triggers have no minimum at all. Foley's analysis also notes that "sale" can include tracking pixels that send device IDs and browsing history to an ad network in exchange for audience insights, which brings ordinary marketing activity into the scoping question.

For a compliance leader, the practical takeaway is that scoping is now a data exercise, not a size exercise. Our overview of cybersecurity and compliance for SMBs in 2026 covers the wider regulatory picture; this article focuses on the narrower question of whether the state privacy laws reach you.

What consumer thresholds apply to small businesses in 2026 and 2027?

Most state laws apply once you process personal data of 100,000 state residents a year, or a lower number such as 25,000 when you also earn a large share of revenue from selling data. A growing group of states sets the bar lower, at 35,000 consumers or at any sensitive-data processing. A few, like Texas, use the federal small-business definition instead of a count.

That is the direct answer. The details matter because the differences decide whether you are in or out. The table below summarizes the thresholds for the laws most relevant to growing SMBs right now, including the four states that enacted laws in 2026 with effective dates in 2027 and 2028.

StateEffectiveMain consumer thresholdOther triggers worth noting
Rhode IslandJan 1, 202635,000 customers10,000 customers plus more than 20% of gross revenue from selling data
Connecticut (amended)July 1, 202635,000 consumersAny sensitive data processing; any offer of data for sale
IndianaJan 1, 2026100,000 consumers25,000 consumers plus more than 50% of gross revenue from selling data
KentuckyJan 1, 2026100,000 consumers25,000 consumers plus 50% of gross revenue from selling data
TexasJuly 1, 2024No numeric count; SBA small businesses generally exemptSmall businesses still need consent before selling sensitive data
LouisianaJan 1, 202775,000 consumers, households, or devicesAnnual gross revenue over $25 million
OklahomaJan 1, 2027100,000 consumers25,000 consumers plus more than 50% of gross revenue from selling data
AlabamaMay 1, 2027More than 25,000 consumersBusinesses under 500 employees exempt if they do not sell personal data
VermontJan 1, 202835,000 consumersSensitive data of 3,000 consumers, or selling data of 3,000 consumers

The sources for these rows are primary where possible. Indiana's statute applies to businesses that control or process personal data of at least 100,000 Indiana consumers, or 25,000 if more than 50% of gross revenue comes from selling personal data. The Kentucky Attorney General's guidance describes the same structure and adds that the office may seek civil penalties of up to $7,500 per violation after a 30-day cure window. The four 2026 enactments are summarized in Benesch's review of the Alabama, Louisiana, Oklahoma, and Vermont laws, which also notes that Louisiana's cure period sunsets on July 31, 2027.

How do I count consumers for a state privacy law?

Count every state resident whose personal data you control or process in a calendar year, across every system, not just your customer database. That includes newsletter subscribers, loyalty members, patients, event registrants, and website visitors whose identifiers you collect, minus any category a given statute excludes, such as data processed only to complete a payment in Rhode Island and Connecticut.

This is where most self-assessments go wrong. Businesses count active customers in the CRM and stop. In practice, the same resident may appear in an email platform, an e-commerce system, a scheduling tool, and your website analytics, and older records that were never deleted still count if you continue to hold and process them. Most state laws also define consumers as residents acting in a personal or household capacity, and Byte Back notes that the California Consumer Privacy Act is the only state law without a B2B or employee-data exemption. A firm that sells only to other businesses may therefore be out of scope in one state and squarely in scope in California, which is why counting has to be done state by state.

Exemptions for HIPAA- or GLBA-regulated organizations also differ from state to state, with some laws exempting the whole entity and others exempting only the regulated data. If you are a healthcare practice, a financial services firm, or a vendor to either, do not assume your federal obligations take you out of state scope. Confirm it with counsel for each state where you have meaningful volume. Our Ohio compliance basics guide is a useful companion here, since breach notification duties apply regardless of whether a comprehensive privacy law does.

What happens when a business gets the scoping question wrong?

The first enforcement action ever brought by a state attorney general under a comprehensive privacy law shows the risk. In January 2025, Texas sued Allstate and its subsidiary Arity, alleging they collected and sold precise location and driving data through software embedded in third-party mobile apps without notice or consent, in violation of the Texas Data Privacy and Security Act. Allstate is not a small business, but the theory of the case is one every SMB should notice: the alleged violation came from sensitive data flowing through embedded technology that end users did not know about.

Texas is also the state where SMBs most often assume they are exempt. The Texas Attorney General's guidance confirms that small businesses as defined by the SBA are generally exempt, but a small business that sells a consumer's sensitive data must first obtain that consumer's consent. The exemption has a hole in it exactly where the risk is highest.

The cost of getting scoping wrong is rarely a single fine. It is the scramble when a customer, a partner's procurement team, or an insurer asks which state laws you comply with and you discover you should have had a privacy notice, an opt-out process, and data protection assessments in place for months. Gaps like that are what we describe in the compliance blind spot that costs SMBs thousands.

How to check your exposure before the 2027 effective dates

With Louisiana and Oklahoma taking effect on January 1, 2027, and Alabama on May 1, 2027, the window to scope your obligations calmly is the next few months. A practical review takes five steps.

  1. Build a resident count by state. Pull records from every system that holds personal data and de-duplicate by person, then total by state of residence for the last full calendar year.
  2. Flag sensitive data separately. Health, precise location, biometric, financial account, government ID, and children's data can trigger coverage on their own: at any volume in Connecticut, and at just 3,000 consumers in Vermont.
  3. Map every sale or share. List each place personal data leaves your control, including ad pixels and data-sharing partnerships, and decide with counsel whether any of it is a "sale" under each state's definition.
  4. Match obligations to the strictest state that applies. Many businesses find it simpler to meet the highest common standard for notices, rights requests, and opt-outs than to run state-by-state processes.
  5. Document the decision. Record which states you are in scope for, the counts behind each decision, and the date. Recheck annually, because thresholds are measured over each preceding calendar year.

If you already work toward international standards, much of this will feel familiar; our guide to GDPR compliance for US-based companies covers the overlapping controls. State privacy laws are also starting to intersect with AI rules, a collision our AI Lab maps in which AI regulations actually apply to your business.

How Securafy helps growing SMBs answer the scope question

When a client asks us whether a new state law applies, we treat it as a data inventory problem first and a legal problem second. Our compliance team works with your systems to produce the resident counts by state, identify where sensitive data lives, and map the data flows that could count as a sale or share. That gives your counsel facts to apply the statute to, instead of estimates.

From there, we help you build the operational pieces the laws require: rights-request handling, opt-out processing that actually works, data protection assessments, and retention controls that keep your counts from growing with stale records. We also schedule the annual recount, so a growth year does not silently move you into a new state's scope. If you are evaluating outside support, our guide to choosing a compliance-focused provider lays out what to look for.

Where To Go From Here

The privacy map will keep changing, but the question that decides your obligations stays the same: how many residents' data do you hold, and what kind? Answer that with real numbers before the 2027 effective dates, and the rest of the compliance work becomes manageable.

If you want a structured program that keeps your state privacy scope, controls, and evidence current as you grow, Securafy's Comply-CARE compliance and vCISO program is built for exactly that.

If you would rather talk through your specific environment first, book a strategy call with Securafy and we will walk through your data footprint, the states that likely apply, and the fastest path to documented compliance.