
Selling Customer Data When Selling a Business: The Merger Carve-Out in 23 State Privacy Laws (2026)
- Primary data
- SMBB coding of 23 state comprehensive privacy statutes (official texts)
- Data period
- Laws enacted 2018 to 2026, effective 2020 to 2028
- Latest release used
- 2026-11-02
- Next release
- Next check after the 2027 legislative sessions; CCPA revenue threshold adjusts in January 2027
- Geography
- United States, 23 states
- Sources
- 52 (49 Tier 1)
Selling customer data when selling a business is excluded from the definition of a 'sale' in all 23 state comprehensive privacy laws we coded as of November 2, 2026. California alone adds conditions. Of 22 laws read from statute text, 18 also cover proposed deals, and 17 of 23 can reach a business of any revenue through consumer counts alone.
Selling customer data when selling a business: all 23 laws carve it out of 'sale'
Every state comprehensive privacy law in our registry treats a transfer of customer data that is part of a merger or acquisition as something other than a 'sale' of personal data. The carve-out sits inside each law's definition of 'sale', not in its exemptions section.
We read the 'sale of personal data' definition and the applicability section of 23 state laws on 2026-11-02, from legislature or agency texts saved with this report. In each law, the definition lists things that are not a sale, and one item on every list is the disclosure or transfer of personal data to a third party as an asset that is part of a merger, acquisition or similar transaction.
Sale of personal data: In 15 of the laws, the exchange of personal data for monetary or other valuable consideration; in 7 laws (including Virginia, Utah, Iowa and Kentucky), only an exchange for monetary consideration. Alabama counts other consideration only where the seller gets a material benefit and the recipient's later use is unrestricted.
| State | Law and citation | In effect | Who is covered | Business-sale carve-out | Proposed deals covered | Conditions | Confidence |
|---|---|---|---|---|---|---|---|
| California | California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act (Cal. Civ. Code 1798.100 to 1798.199.100) | 2020-01-01 | Revenue over $26,625,000, OR 100,000 consumers or households bought, sold or shared, OR 50% of revenue from selling or sharing | yes, with conditions | no | Data must be used or shared consistently with the CCPA; a buyer that materially changes use in a way materially inconsistent with promises made at collection must give prior notice; buyer must honor opt-out directions consumers gave the seller (1798.120(a)(2)) | clear text |
| Virginia | Virginia Consumer Data Protection Act (Va. Code 59.1-575 to 59.1-585) | 2023-01-01 | 100,000 consumers, or 25,000 with over 50% of revenue from data sales | yes, unconditional | no | None in the definition | clear text |
| Colorado | Colorado Privacy Act (C.R.S. 6-1-1301 to 6-1-1313 (Senate Bill 21-190)) | 2023-07-01 | 100,000 consumers, or 25,000 with any revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Connecticut | Connecticut Data Privacy Act (Conn. Gen. Stat. 42-515 to 42-525) | 2023-07-01 | 35,000 consumers (100,000 before 2026-07-01), OR any sensitive data, OR offering personal data for sale | yes, unconditional | yes | None in the definition | clear text |
| Utah | Utah Consumer Privacy Act (Utah Code 13-61-101 to 13-61-404) | 2023-12-31 | Revenue of $25,000,000 or more AND 100,000 consumers (or 25,000 with over 50% of revenue from data sales) | yes, unconditional | yes | None in the definition | clear text |
| Texas | Texas Data Privacy and Security Act (Tex. Bus. & Com. Code ch. 541 (HB 4, 88th Leg.)) | 2024-07-01 | No consumer count; SBA-defined small businesses exempt except a ban on selling sensitive data without consent | yes, unconditional | no | None in the definition | clear text |
| Oregon | Oregon Consumer Privacy Act (ORS 646A.570 to 646A.589) | 2024-07-01 | 100,000 consumers, or 25,000 with 25% or more of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Montana | Montana Consumer Data Privacy Act (Mont. Code Ann. 30-14-2801 to 30-14-2822) | 2024-10-01 | 25,000 consumers, or 15,000 with over 25% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Iowa | Iowa Consumer Data Protection Act (Iowa Code ch. 715D) | 2025-01-01 | 100,000 consumers, or 25,000 with over 50% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Delaware | Delaware Personal Data Privacy Act (6 Del. C. 12D-101 to 12D-111) | 2025-01-01 | 35,000 consumers, or 10,000 with over 20% of revenue from data sales; 10,000 and 5,000 from 2027-01-01 | yes, unconditional | yes | None in the definition; from 2027 a buyer that acquires personal data from a controller is itself within the law | clear text |
| Nebraska | Nebraska Data Privacy Act (Neb. Rev. Stat. 87-1101 to 87-1130 (LB 1074, 2024)) | 2025-01-01 | No consumer count; SBA-defined small businesses exempt except a ban on selling sensitive data without consent | yes, unconditional | yes | None in the definition | clear text |
| New Hampshire | New Hampshire privacy law (RSA 507-H) (N.H. RSA 507-H:1 to 507-H:12) | 2025-01-01 | 35,000 consumers, or 10,000 with over 25% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| New Jersey | New Jersey consumer data privacy law (P.L.2023, c.266) (N.J.S.A. 56:8-166.4 to 56:8-166.19) | 2025-01-15 | 100,000 consumers, or 25,000 with any revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Tennessee | Tennessee Information Protection Act (Tenn. Code Ann. Title 47, Ch. 18, Part 32 as enacted by Pub. Ch. 408 (2023)) | 2025-07-01 | Revenue of $25,000,000 or more AND 175,000 consumers (or 25,000 with over 50% of revenue from data sales) | yes, unconditional | no | None in the definition | clear text |
| Minnesota | Minnesota Consumer Data Privacy Act (Minn. Stat. 325M.10 to 325M.21) | 2025-07-31 | 100,000 consumers, or 25,000 with over 25% of revenue from data sales; SBA-defined small businesses exempt except a ban on selling sensitive data without consent | yes, unconditional | yes | None in the definition | clear text |
| Maryland | Maryland Online Data Privacy Act (Md. Code, Com. Law 14-4701 to 14-4714) | 2025-10-01 | 35,000 consumers, or 10,000 with over 20% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Indiana | Indiana Consumer Data Protection Act (Ind. Code 24-15 (Senate Enrolled Act 5, 2023)) | 2026-01-01 | 100,000 consumers, or 25,000 with over 50% of revenue from data sales | yes, unconditional | unclear | None in the Attorney General's summary of the definition | interpretation needed |
| Kentucky | Kentucky Consumer Data Protection Act (KRS 367.3611 to 367.3629) | 2026-01-01 | 100,000 consumers, or 25,000 with over 50% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Rhode Island | Rhode Island Data Transparency and Privacy Protection Act (R.I. Gen. Laws 6-48.1-1 to 6-48.1-10) | 2026-01-01 | 35,000 consumers, or 10,000 with over 20% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Oklahoma | Oklahoma consumer data privacy law (Senate Bill 546) (75A O.S. (new sections) | 2027-01-01 | 100,000 consumers, or 25,000 with over 50% of revenue from data sales | yes, unconditional | yes | None in the definition | clear text |
| Alabama | Alabama Personal Data Protection Act (HB 351, 2026) (Act of 2026 (HB 351 enrolled)) | 2027-05-01 | More than 25,000 consumers, or over 25% of revenue from data sales; under 500 employees exempt if no data sales | yes, unconditional | yes | None in the definition | clear text |
| Louisiana | Louisiana Data Privacy Act (Act 502 of 2026) (La. R.S. 51:1780.1 to 1780.5 (Act 502, SB 386)) | 2027-01-01 | Revenue over $25 million, OR 75,000 consumers, households or devices, OR 50% of revenue from selling data | yes, unconditional | yes | None in the definition | clear text |
| Vermont | Vermont Data Privacy and Online Surveillance Act (Act 145 of 2026) (9 V.S.A. ch. 61A, 2415a to 2415k (Act 145, S.71)) | 2028-01-01 | 35,000 consumers, OR sensitive data of 3,000, OR offering for sale personal data of 3,000 | yes, unconditional | yes | None in the definition | clear text |
| Florida (narrow law, not counted) | Florida Digital Bill of Rights (Fla. Stat. 501.701 to 501.722) | 2024-07-01 | Only controllers with more than $1 billion in global gross annual revenue that also meet an ad-revenue, smart-speaker or app-store test | yes, unconditional | no | None in the definition | clear text |
Checked 2026-11-02. Florida is listed for reference and left out of every count. Indiana is coded from the Attorney General's guide because the statute text could not be opened. Full coding with URLs, raw files and archive flags: tables/registry_full.csv.
Source: [1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35][36][37][38][39][40][41][42][43] California Privacy Protection Agency; California Privacy Protection Agency; Virginia Legislative Information System; Virginia Legislative Information System; Virginia Legislative Information System (archived); Colorado General Assembly (archived); Connecticut General Assembly; Connecticut General Assembly; Utah State Legislature; Utah State Legislature; Texas Legislature Online; Oregon State Legislature (archived); Oregon State Legislature (archived); Montana Legislature; Montana Legislature; Montana Legislature (archived); Iowa Legislature; Iowa Legislature; Delaware Code Online; Delaware Code Online, session laws; Nebraska Legislature (archived); Nebraska Legislature (archived); Nebraska Legislature (archived); New Hampshire General Court (archived); New Jersey Legislature (archived); Tennessee Secretary of State (archived); Minnesota Office of the Revisor of Statutes; Minnesota Office of the Revisor of Statutes; Maryland General Assembly; Maryland General Assembly; Maryland General Assembly; Indiana Office of the Attorney General; Kentucky General Assembly; Kentucky General Assembly; Kentucky General Assembly; State of Rhode Island General Assembly (archived); State of Rhode Island General Assembly (archived); Oklahoma Legislature; Oklahoma Legislature; Alabama Legislature; Louisiana State Legislature; Louisiana State Legislature; Vermont General Assembly
Florida's Digital Bill of Rights also excludes a transfer 'as part of a merger or an acquisition', but it reaches only controllers with more than $1 billion in global gross annual revenue (Fla. Stat. 501.702), so it is listed for reference and left out of the counts.
California is the only state that puts conditions on the buyer
The brief for this report expected several states to attach conditions to the carve-out. The statute text supports one: California. The other 22 state the carve-out without conditions inside the definition.
Under Cal. Civ. Code 1798.140(ad)(2)(C), a transfer in a merger, acquisition, bankruptcy or other transaction is not a sale 'provided that information is used or shared consistently with this title'. If the buyer later materially changes how it uses the data in a way materially inconsistent with the promises made at collection, it must give consumers prior notice of the new practice.
A second California rule follows the data to the buyer: Civ. Code 1798.120(a)(2) requires a business that receives personal information in such a transaction to comply with an opt-out direction the consumer gave the seller. California's statute uses the same carve-out for 'sharing' (cross-context advertising) as for 'sale'.
| How the carve-out is worded | States | Laws |
|---|---|---|
| Standard wording, names proposed deals | Colorado, Connecticut, Oregon, Montana, Iowa, Delaware, Nebraska, New Hampshire, New Jersey, Minnesota, Maryland, Kentucky, Rhode Island, Oklahoma, Alabama, Vermont | 16 |
| Standard wording, completed deals only | Virginia, Tennessee | 2 |
| Merger, acquisition or bankruptcy only, proposed or actual (no catch-all) | Utah | 1 |
| 'Merger, acquisition, or similar activity', proposed or completed | Louisiana | 1 |
| 'A merger or acquisition' only | Texas | 1 |
| Standard wording plus conditions on the buyer | California | 1 |
| Attorney General paraphrase only (statute not opened) | Indiana | 1 |
Standard wording: transfer of personal data to a third party as an asset that is part of a merger, acquisition, bankruptcy or other transaction in which the third party assumes control of all or part of the controller's assets.
Source: [1][11][9][41][32] California Privacy Protection Agency; Texas Legislature Online; Utah State Legislature; Louisiana State Legislature; Indiana Office of the Attorney General
Wording differs at the edges. Texas names only 'a merger or acquisition'. Utah names a merger, an acquisition or a bankruptcy and has no catch-all for other transactions. Louisiana says 'merger, acquisition, or similar activity' and does not require the buyer to assume control of the seller's assets. A share purchase, an asset purchase of part of a business, and a transfer in bankruptcy can fall on different sides of these lines; the statutes do not define the terms.
Eighteen laws also cover a deal that has not closed
Most sellers open their books to a buyer before closing. 18 of the 22 laws read from statute text extend the carve-out to a 'proposed' transaction; four cover only a completed one. This count is SMBB's own coding and is not published elsewhere that we found.
Colorado, Connecticut, Oregon, Montana, Iowa, Delaware, Nebraska, New Hampshire, New Jersey, Minnesota, Maryland, Kentucky, Rhode Island, Oklahoma, Alabama and Vermont use the words 'proposed or actual' or 'proposed or completed'. Utah's text reads 'a proposed or actual merger, an acquisition, or a bankruptcy', and Louisiana's reads 'a proposed merger, acquisition, or similar activity'.
- California: completed merger, acquisition, bankruptcy or other transaction only (Civ. Code 1798.140(ad)(2)(C)).
- Virginia: completed transaction only (Va. Code 59.1-575).
- Texas: 'a merger or acquisition' only (HB 4, Bus. & Com. Code 541.001(28)).
- Tennessee: completed transaction only (Pub. Ch. 408 of 2023).

In these four states the statute text does not say how a disclosure to a prospective buyer during due diligence is treated. A disclosure for no consideration is not a 'sale' under any of the definitions, and Virginia and Tennessee count only monetary consideration; whether data access in a letter-of-intent stage is 'other valuable consideration' in California or Texas is a question for counsel.
Does a small business even meet the thresholds?
Coverage, not the carve-out, is where state laws differ most for a small seller. 17 of 23 laws can reach a business of any revenue through a count of state residents whose data it holds or processes.
| Coverage route | States | Laws | What it means for a small seller |
|---|---|---|---|
| consumer count only | Virginia, Colorado, Connecticut, Oregon, Montana, Iowa, Delaware, New Hampshire, New Jersey, Maryland, Indiana, Kentucky, Rhode Island, Oklahoma, Vermont | 15 | A seller of any size is covered once it holds or processes enough residents' data |
| revenue or consumer count | California, Louisiana | 2 | Revenue alone triggers coverage; so does the consumer count, at any revenue |
| revenue floor and consumer count | Utah, Tennessee | 2 | A business under $25,000,000 in revenue is outside the law |
| SBA small-business exemption | Texas, Nebraska, Minnesota | 3 | SBA-size small businesses are outside the law except for selling sensitive data |
| employee-count exemption | Alabama | 1 | Under 500 employees and no data sales: outside the law |
Coded from each law's applicability section. Counts are of state residents only; most laws exclude data processed solely to complete a payment.
Source: [4][1][9][11][40] Virginia Legislative Information System; California Privacy Protection Agency; Utah State Legislature; Texas Legislature Online; Alabama Legislature
Headline threshold, laws with no revenue floor
Source: state statutes, checked 2026-11-02; SMBB coding
Most laws count a resident once their data is controlled or processed during the year, and Connecticut's definition of processing includes storage (Conn. Gen. Stat. 42-515). A customer database built over many years can therefore count toward a threshold even in a slow sales year.
| Consumers in a year | Used by (headline or sale-of-data route) | Average distinct consumers per day |
|---|---|---|
| 3,000 | Vermont | 8.2 |
| 10,000 | Delaware, New Hampshire, Maryland, Rhode Island | 27.4 |
| 15,000 | Montana | 41.1 |
| 25,000 | Virginia, Colorado, Utah, Oregon, Montana, Iowa, New Jersey, Tennessee, Minnesota, Indiana, Kentucky, Oklahoma, Alabama | 68.5 |
| 35,000 | Connecticut, Delaware, New Hampshire, Maryland, Rhode Island, Vermont | 95.9 |
| 75,000 | Louisiana | 205.5 |
| 100,000 | California, Virginia, Colorado, Utah, Oregon, Iowa, New Jersey, Minnesota, Indiana, Kentucky, Oklahoma | 274.0 |
| 175,000 | Tennessee | 479.5 |
SMBB calculation: threshold / 365. Records already on file count when they are stored or used during the year, so a long-held customer list can meet a threshold without new sales.
Source: [7][15][19][43] Connecticut General Assembly; Montana Legislature; Delaware Code Online; Vermont General Assembly
Translated into daily terms, 35,000 consumers is about 95.9 distinct residents a day for a year and 100,000 is about 274.0. A retailer, clinic or online shop selling mostly into one state can reach the lower lines; a business-to-business firm with a few hundred client contacts usually cannot. Three states add routes with smaller numbers or none: Connecticut covers any business that controls sensitive data or offers personal data for sale, Vermont will cover sensitive data of 3,000 consumers, and Alabama covers any business deriving more than 25 percent of revenue from data sales regardless of consumer count.
Most laws also exempt data or entities covered by federal sector rules, such as financial institutions subject to the Gramm-Leach-Bliley Act and HIPAA covered entities (for example, Va. Code 59.1-576(B)). A medical practice or insurance agency should check those exemptions before relying on the thresholds.
Connecticut, Montana and Delaware have lowered the bar
The newest amendments push thresholds down, which brings more small and mid-size sellers inside the laws over time.
Headline threshold as enacted and as now written
Source: Conn. Gen. Stat. 42-516; Mont. Code Ann. 30-14-2803 and SB 384 (2023); 6 Del. C. 12D-103
Connecticut's cut from 100,000 to 35,000 consumers (65.0 percent) took effect 2026-07-01. Montana's line fell from 50,000 to 25,000 (50.0 percent) under Chapter 567, Laws of 2025. Delaware's falls from 35,000 to 10,000 (71.4 percent) on 2027-01-01, and from that date Delaware's law also applies to 'third parties who acquire personal data from a controller', which can include a buyer.
Fifteen of the 23 laws take effect in 2025 or later
Most of these laws are new. 19 were in force on 2026-11-02 and 4 enacted in 2026 take effect in 2027 or 2028, so a sale signed now can close under a different rulebook than the one in force at signing.
23 comprehensive laws; 2027 and 2028 are scheduled
Source: state statutes and session laws, checked 2026-11-02; SMBB coding
Darker tiles are newer laws
Source: state statutes and session laws, checked 2026-11-02
| Date | State | Change | Source id |
|---|---|---|---|
| 2025-09-22 | California | CCPA regulation update (risk assessments, cybersecurity audits, automated decisionmaking) approved; effective 2026-01-01 | s46 |
| 2026-01-01 | Indiana, Kentucky, Rhode Island | Three laws take effect | s32, s34, s37 |
| 2026-03-20 | Oklahoma | SB 546 approved by the Governor; effective 2027-01-01 | s39 |
| 2026-05-29 | Louisiana | Act 502 signed; effective 2027-01-01; revenue over $25 million alone triggers coverage | s42 |
| 2026-06-16 | Vermont | Act 145 signed; effective 2028-01-01; thresholds 35,000 consumers or 3,000 for sensitive data | s43 |
| 2026-07-01 | Connecticut | Threshold cut to 35,000 consumers; any business handling sensitive data or offering data for sale is covered | s7 |
| 2027-01-01 | Delaware | Threshold falls to 10,000 consumers (5,000 with over 20% of revenue from data sales); buyers that acquire personal data from a controller are covered | s19 |
| 2027-05-01 | Alabama | HB 351 takes effect; under 500 employees and no data sales exempt | s40 |
| 2027-07-01 | Kentucky | 2026 Ky. Acts ch. 118 amends definitions; merger carve-out unchanged | s48 |
Alabama's signing date is not printed in the enrolled bill and is left out. All dates read from the official documents listed.
Source: [46][39][42][43][7][19][40][48] California Privacy Protection Agency; Oklahoma Legislature; Louisiana State Legislature; Vermont General Assembly; Connecticut General Assembly; Delaware Code Online; Alabama Legislature; Kentucky General Assembly

The privacy notice travels with the customer list
The carve-out keeps a business sale out of the 'sale' rules. It does not cancel what the seller told customers when it collected their data.
The Federal Trade Commission's staff wrote in 2014 that, absent affirmative express consent, a company may not use data in a manner materially inconsistent with promises made when the data was collected, and that doing so could be an unfair practice under Section 5 of the FTC Act. California writes the same idea into its carve-out by requiring prior notice before a materially inconsistent new use.
In practice, a seller's privacy notice is part of the asset being sold. If it promised never to share customer data, the buyer inherits that promise. A buyer that meets a state's threshold, or falls within Delaware's buyer route from 2027, owes that state's consumer rights to the customers it acquires.
Points to raise with a broker or attorney before sharing the customer file
These questions follow from the coding above; they are prompts for advisers, not answers.
- In which states do our customers live, and do we pass any state's consumer count, including stored records?
- Does our privacy notice say anything about a sale or merger of the business?
- If customers live in California, Virginia, Texas or Tennessee, how will data be shared during due diligence before closing?
- Will the buyer keep using the data as described in our notice, and who sends notice if that changes?
- Is any of the data health, financial or children's data covered by a federal rule or a sensitive-data consent rule?
For where these questions fit in a sale, see how a sale moves through six stages and questions to ask a broker.
Ratios behind the comparison
Carve-out count and conditions
Formulacount of laws with a business-sale exclusion in the 'sale' definition; split by conditional vs unconditional
Inputs: derived d2 to d4 (input rows listed there) (fact sheet rows)
Result: 23 of 23 laws exclude the transfer; 22 unconditional, 1 conditional (California)
The brief expected 'some' conditional laws; the text supports one. Conditions elsewhere come from privacy promises and consumer-protection law, not the state privacy statutes' sale definitions.
Limitations: Indiana coded from Attorney General guidance; Colorado and Texas from enacted bills.
Proposed-deal coverage (signature finding)
Formulalaws whose carve-out names a proposed transaction / laws read from statute text x 100
Inputs: derived d5 to d7 (fact sheet rows)
Result: 18 of 22 = 81.8 percent
Due-diligence disclosures to a prospective buyer are expressly carved out in 18 states; in California, Virginia, Texas and Tennessee the text covers completed transactions only.
Limitations: Utah's phrase 'a proposed or actual merger, an acquisition, or a bankruptcy' may apply 'proposed' to mergers only; counted as yes.
Small-business reach
Formulalaws coded 'consumer count only' + laws coded 'revenue or consumer count'; share of 23
Inputs: derived d8 to d14 (fact sheet rows)
Result: 17 of 23 = 73.9 percent
A business's revenue does not protect it from 17 laws; only Utah and Tennessee (revenue floor) and Texas, Nebraska, Minnesota and Alabama (size exemptions) screen most small firms out.
Limitations: Thresholds count residents of each state separately; a business must check each state where its customers live.
Thresholds per day
Formulaannual consumer threshold / 365
Inputs: derived d23 to d30 (fact sheet rows)
Result: 3,000 = 8.2 a day; 25,000 = 68.5; 35,000 = 95.9; 100,000 = 274.0
Gives owners a quick sense of scale; a single-state retailer with about 96 distinct customers a day for a year meets the 35,000 line.
Limitations: Average only. Stored records and non-customers (newsletter sign-ups, leads) also count.
Timeline
Formulacount of laws by effective year; share effective on or after 2025-01-01
Inputs: derived d15 to d18 (fact sheet rows)
Result: 15 of 23 = 65.2 percent effective 2025 or later; 19 in force on 2026-11-02
Deals signed in 2026 that close in 2027 can straddle Oklahoma, Louisiana and Delaware changes.
Limitations: Effective dates only; enforcement grace (cure) periods are not coded.
Threshold cuts
Formula(new threshold minus original) / original x 100
Inputs: derived d31 to d33; fact rows for Connecticut, Montana, Delaware (fact sheet rows)
Result: Connecticut -65.0 percent; Montana -50.0 percent; Delaware -71.4 percent (2027)
Amendments since 2025 move in one direction: down.
Limitations: Three states only; other laws have not been amended on thresholds in the text we read.
Where the numbers diverge
- Every one of the 23 state comprehensive privacy laws coded on 2026-11-02 excludes a transfer of personal data that is part of a merger or acquisition from the definition of 'sale'.[1][3][6][7][9][11][12][14][17][19][21][24][25][26][27][29][32][33][36][38][40][41][43]
- 22 of 23 laws state the carve-out without conditions inside the 'sale' definition; California alone conditions it (Cal. Civ. Code 1798.140(ad)(2)(C)).[1]
- Under the CCPA text effective 2026-01-01, a California buyer must comply with opt-out directions consumers gave the seller (Cal. Civ. Code 1798.120(a)(2), statute effective 2026-01-01).[1]
- 18 of 22 laws read from statute text (81.8 percent) cover a proposed or actual transaction; Virginia, Tennessee, California and Texas cover completed transactions only.[3][26][1][11]
- Texas excludes only a transfer 'as an asset that is part of a merger or acquisition' (Tex. Bus. & Com. Code 541.001(28), HB 4 enrolled, effective 2024-07-01).[11]
- Louisiana's carve-out covers a 'merger, acquisition, or similar activity' and drops the usual test that the buyer assumes control of the seller's assets (Act 502 of 2026).[41]
- 15 laws use a consumer count with no revenue test and no size exemption, and California and Louisiana add a revenue-only trigger beside the count, so 17 of 23 laws can reach a business of any revenue.[4][1][41]
- Utah and Tennessee apply only to businesses with $25,000,000 or more in revenue that also meet a consumer count (Utah Code 13-61-102; Tenn. Pub. Ch. 408).[9][26]
- Texas, Nebraska and Minnesota exempt businesses that are small under the U.S. Small Business Administration standard, except that they may not sell sensitive data without consent.[11][22][27]
- Alabama's law, effective 2027-05-01, exempts businesses with fewer than 500 employees that do not sell personal data (HB 351 section 4).[40]
- The median headline consumer threshold across the 21 laws that use one is 100,000 consumers; 9 laws set it below 100,000.[4][7][15][30]
- Montana's 25,000-consumer threshold is the lowest in force on 2026-11-02; it was 50,000 when the law was enacted in 2023.[15][16]
- Connecticut's 35,000-consumer threshold took effect 2026-07-01, a 65.0 percent cut from 100,000.[7][8]
- 7 laws count only a cash exchange as a 'sale', while 15 count any valuable consideration, which matters for list swaps or data handed over in exchange for services.[3][7]
Summary
- All 23 state comprehensive privacy laws coded here say that transferring personal data as an asset in a merger or acquisition is not a 'sale' of personal data (statutes checked 2026-11-02).
- California is the only state that attaches conditions: the buyer must use the data consistently with the CCPA, give prior notice of a materially inconsistent new use, and honor opt-outs consumers gave the seller (Cal. Civ. Code 1798.140(ad)(2)(C) and 1798.120(a)(2)).
- 18 of the 22 laws read from statute text extend the carve-out to proposed deals; California, Virginia, Texas and Tennessee name completed transactions only.
- Texas uses the narrowest wording, 'a merger or acquisition', with no mention of bankruptcy, other transactions or proposed deals.
- 17 of 23 laws (73.9 percent) can cover a business of any revenue once it holds enough residents' data; Utah and Tennessee require $25,000,000 in revenue, and Texas, Nebraska, Minnesota and Alabama exempt most small firms.
- Thresholds are falling: Connecticut cut its line from 100,000 to 35,000 consumers on 2026-07-01, Montana from 50,000 to 25,000, and Delaware's drops from 35,000 to 10,000 on 2027-01-01.
- 15 of the 23 laws (65.2 percent) take effect in 2025 or later, and 4 enacted in 2026 (Oklahoma, Louisiana, Alabama, Vermont) are not yet in force.
- The carve-out removes a deal from the 'sale' rules only; privacy promises made at collection still bind the data, as the Federal Trade Commission's staff stated in 2014.
Questions people ask
Can I sell my customer list?
As part of selling the business, the 23 state laws coded here say a transfer of personal data as an asset in a merger or acquisition is not a 'sale' of personal data (checked 2026-11-02). Selling the list on its own, without the business, is different: the carve-out is tied to a transaction in which the buyer takes control of all or part of the seller's assets, and the statutes do not say whether a list alone qualifies. Your privacy notice still binds the data.
Is a customer list transfer a sale of personal information under CCPA?
Not when the list moves as an asset in a merger, acquisition, bankruptcy or other transaction in which the buyer assumes control of all or part of the business, provided the information is used consistently with the CCPA (Cal. Civ. Code 1798.140(ad)(2)(C)). The buyer must give prior notice before a materially inconsistent new use and must honor opt-outs consumers gave the seller (1798.120(a)(2)).
Do privacy laws apply to small businesses?
Often yes. 17 of 23 state laws can cover a business of any revenue once it holds or processes data on enough state residents; the lowest headline threshold in force on 2026-11-02 is 25,000 consumers (Montana). Utah and Tennessee require $25,000,000 in revenue, and Texas, Nebraska, Minnesota and Alabama exempt most small firms.
What do I tell customers when I sell my business?
The state privacy statutes do not require a notice for the sale itself, except that California requires prior notice if the buyer will use the data in a way materially inconsistent with the original promises. The FTC's staff has said privacy promises made at collection survive an acquisition. Confirm the wording with a privacy attorney.
For journalists and researchers
If you cite only a few, cite these
- 23 of 23 state comprehensive privacy laws carve business-sale transfers out of 'sale'; only California adds conditions (SMBB coding of official texts, 2026-11-02).[1][3][7]
- 18 of 22 laws read from statute text also cover proposed deals (SMBB coding, 2026-11-02).[6][7][12]
- 17 of 23 laws can reach a business of any revenue through consumer counts alone (SMBB coding, 2026-11-02).[4][1][41]
Most quotable statistics
- All 23 state comprehensive privacy laws coded on 2026-11-02 exclude a merger or acquisition transfer of customer data from the definition of 'sale'.[1][3][6][7][9][11][12][14][17][19][21][24][25][26][27][29][32][33][36][38][40][41][43]
- California is the only state of 23 that attaches conditions to its business-sale carve-out (Cal. Civ. Code 1798.140(ad)(2)(C)).[1]
- 18 of 22 state privacy laws read from statute text also exclude transfers in a proposed deal, covering due diligence before closing.[6][7][12][19]
- 17 of 23 state privacy laws can reach a business of any revenue size through a consumer count alone.[4][1][41]
- Montana's 25,000-consumer threshold was the lowest in force on 2026-11-02; Delaware's falls to 10,000 on 2027-01-01.[15][19]
- 15 of 23 state comprehensive privacy laws take effect in 2025 or later.[1][3][6][7][9][11][12][14][17][19][21][24][25][26][27][29][32][33][36][38][40][41][43]
Press summary
A business owner selling a company can usually hand the customer file to the buyer without it counting as a 'sale' of personal data under state privacy law, according to a Sell My Business Broker review of 23 state comprehensive privacy statutes checked on November 2, 2026. Every law excludes a transfer of personal data that is part of a merger or acquisition from its definition of 'sale'. California is the only state that attaches conditions: the buyer must use the data consistently with the CCPA, give notice before a materially inconsistent new use and honor opt-outs consumers gave the seller. 18 of the 22 laws read from statute text also cover proposed deals, the due-diligence stage. Coverage is the bigger issue for small sellers: 17 of 23 laws can reach a business of any revenue through a consumer count, and thresholds are falling, with Connecticut at 35,000 since July 2026 and Delaware dropping to 10,000 in January 2027.
Suggested headlines
- All 23 state privacy laws let a business sale move the customer list; only California adds conditions
- 18 of 22 state privacy laws also cover due diligence before a deal closes
- Revenue is no shield: 17 of 23 state privacy laws can reach a small business
- Connecticut, Montana and Delaware cut privacy thresholds, Delaware to 10,000 consumers
- 15 of 23 state privacy laws take effect in 2025 or later
How to cite this report
Sell My Business Broker. (2026). Selling Customer Data When Selling a Business: The Merger Carve-Out in 23 State Privacy Laws (2026). Retrieved from https://sellmybusinessbroker.com/research/customer-data-business-sale-privacy-laws/
Reuse license
Data and tables are licensed CC BY 4.0. Attribution: “Source: Sell My Business Broker, Selling Customer Data When Selling a Business: The Merger Carve-Out in 23 State Privacy Laws (2026)” with a link to this page.
Download the data
Every table in this report is available as a CSV under CC BY 4.0. The fact sheet lists each value with its source URL and access date.
- derived_metrics.csv (CSV)
- fact_sheet.csv (CSV)
- Registry (CSV)
- Six ways the business-sale carve-out is worded (CSV)
- What each consumer threshold means per day of trading (CSV)
- Five routes into coverage, and which ones a small business can fall into (CSV)
- Changes from September 2025 to the scheduled 2027 dates (CSV)
Frequently asked questions
How many states have comprehensive consumer privacy laws?
We coded 23 state comprehensive privacy laws enacted as of 2026-11-02, plus Florida's narrower Digital Bill of Rights, which applies only to companies with more than $1 billion in revenue. 19 were in force on that date.
Which state privacy law attaches conditions to a business-sale transfer?
California only. The CCPA's carve-out requires the buyer to use the data consistently with the law, give prior notice of materially inconsistent new uses and honor opt-outs made to the seller.
Does Texas exempt business sales from its privacy law?
Yes. The Texas Data Privacy and Security Act excludes a transfer 'as an asset that is part of a merger or acquisition' from 'sale' (HB 4, effective 2024-07-01). It does not mention bankruptcy, other transactions or proposed deals.
Is sharing customer data during due diligence a sale?
18 of 22 laws read from statute text exclude transfers in a proposed transaction from 'sale'. California, Virginia, Texas and Tennessee name only completed transactions.
What is the lowest consumer threshold?
Montana's 25,000 consumers is the lowest headline threshold in force on 2026-11-02. Delaware's falls to 10,000 on 2027-01-01, and Vermont's 3,000 sensitive-data test starts 2028-01-01.
Does revenue alone trigger any state privacy law?
Yes, in California (over $26,625,000 after the 2025 adjustment) and Louisiana (over $25 million, from 2027-01-01), whatever the number of consumers.
Are small businesses exempt in Texas and Nebraska?
Businesses that are small under the U.S. Small Business Administration standard are outside both laws, except that they may not sell sensitive data without consumer consent. Minnesota has the same rule.
When does Connecticut's lower threshold apply?
From 2026-07-01 the Connecticut law covers businesses with 35,000 consumers, any business controlling sensitive data, and any business offering personal data for sale.
Which new state privacy laws were enacted in 2026?
Oklahoma (approved 2026-03-20, effective 2027-01-01), Alabama (effective 2027-05-01), Louisiana (signed 2026-05-29, effective 2027-01-01) and Vermont (signed 2026-06-16, effective 2028-01-01).
Do HIPAA and GLBA businesses fall under these laws?
Many of the laws exempt financial institutions or data subject to Title V of the Gramm-Leach-Bliley Act and HIPAA covered entities, in different forms; Virginia's version is in Va. Code 59.1-576(B). Check the exemption section of each state.
Reproduce this analysis
Every figure comes from the files below. The scripts that pulled and computed them are kept with the report and can be re-run.
| Dataset | Publisher | Source | Query or filter | Rows used | Retrieved |
|---|---|---|---|---|---|
| California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act (California) | California Privacy Protection Agency | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Cal. Civ. Code 1798.100 to 1798.199.100; sale definition 1798.140(ad)(2)(C); buyer duty 1798.120(a)(2) | 1 registry row (8 coded fields) | 2026-11-02 |
| Virginia Consumer Data Protection Act (Virginia) | Virginia Legislative Information System | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Va. Code 59.1-575 to 59.1-585; sale definition 59.1-575; scope 59.1-576 | 1 registry row (8 coded fields) | 2026-11-02 |
| Colorado Privacy Act (Colorado) | Colorado General Assembly (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: C.R.S. 6-1-1301 to 6-1-1313 (Senate Bill 21-190); sale definition 6-1-1303(23); applicability 6-1-1304 | 1 registry row (8 coded fields) | 2026-11-02 |
| Connecticut Data Privacy Act (Connecticut) | Connecticut General Assembly | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Conn. Gen. Stat. 42-515 to 42-525; sale definition 42-515; applicability 42-516 as amended by P.A. 25-113 sec. 6 | 1 registry row (8 coded fields) | 2026-11-02 |
| Utah Consumer Privacy Act (Utah) | Utah State Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Utah Code 13-61-101 to 13-61-404; sale definition 13-61-101(31)(b)(vii); applicability 13-61-102 | 1 registry row (8 coded fields) | 2026-11-02 |
| Texas Data Privacy and Security Act (Texas) | Texas Legislature Online | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Tex. Bus. & Com. Code ch. 541 (HB 4, 88th Leg.); sale definition 541.001(28); applicability 541.002; small business 541.107 | 1 registry row (8 coded fields) | 2026-11-02 |
| Oregon Consumer Privacy Act (Oregon) | Oregon State Legislature (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: ORS 646A.570 to 646A.589; sale definition 646A.570(17); scope 646A.572 | 1 registry row (8 coded fields) | 2026-11-02 |
| Montana Consumer Data Privacy Act (Montana) | Montana Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Mont. Code Ann. 30-14-2801 to 30-14-2822; sale definition 30-14-2802(27); applicability 30-14-2803 as amended by Ch. 567, L. 2025 | 1 registry row (8 coded fields) | 2026-11-02 |
| Iowa Consumer Data Protection Act (Iowa) | Iowa Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Iowa Code ch. 715D; sale definition 715D.1(25); scope 715D.2 | 1 registry row (8 coded fields) | 2026-11-02 |
| Delaware Personal Data Privacy Act (Delaware) | Delaware Code Online | File or endpoint | Sale definition, business-sale carve-out and applicability sections: 6 Del. C. 12D-101 to 12D-111; sale definition 12D-102; applicability 12D-103 (85 Del. Laws c. 463 version effective 2027-01-01) | 1 registry row (8 coded fields) | 2026-11-02 |
| Nebraska Data Privacy Act (Nebraska) | Nebraska Legislature (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Neb. Rev. Stat. 87-1101 to 87-1130 (LB 1074, 2024); sale definition 87-1102(29); applicability 87-1103 | 1 registry row (8 coded fields) | 2026-11-02 |
| New Hampshire privacy law (RSA 507-H) (New Hampshire) | New Hampshire General Court (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: N.H. RSA 507-H:1 to 507-H:12; sale definition 507-H:1; application 507-H:2 | 1 registry row (8 coded fields) | 2026-11-02 |
| New Jersey consumer data privacy law (P.L.2023, c.266) (New Jersey) | New Jersey Legislature (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: N.J.S.A. 56:8-166.4 to 56:8-166.19; sale definition 56:8-166.4; applicability 56:8-166.5 | 1 registry row (8 coded fields) | 2026-11-02 |
| Tennessee Information Protection Act (Tennessee) | Tennessee Secretary of State (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Tenn. Code Ann. Title 47, Ch. 18, Part 32 as enacted by Pub. Ch. 408 (2023); scope 47-18-3202 as enacted | 1 registry row (8 coded fields) | 2026-11-02 |
| Minnesota Consumer Data Privacy Act (Minnesota) | Minnesota Office of the Revisor of Statutes | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Minn. Stat. 325M.10 to 325M.21; sale definition 325M.11(u); scope 325M.12; small business 325M.17 | 1 registry row (8 coded fields) | 2026-11-02 |
| Maryland Online Data Privacy Act (Maryland) | Maryland General Assembly | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Md. Code, Com. Law 14-4701 to 14-4714; sale definition 14-4701(ff); applicability 14-4702 | 1 registry row (8 coded fields) | 2026-11-02 |
| Indiana Consumer Data Protection Act (Indiana) | Indiana Office of the Attorney General | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Ind. Code 24-15 (Senate Enrolled Act 5, 2023) | 1 registry row (8 coded fields) | 2026-11-02 |
| Kentucky Consumer Data Protection Act (Kentucky) | Kentucky General Assembly | File or endpoint | Sale definition, business-sale carve-out and applicability sections: KRS 367.3611 to 367.3629; sale definition 367.3611(27); application 367.3613 | 1 registry row (8 coded fields) | 2026-11-02 |
| Rhode Island Data Transparency and Privacy Protection Act (Rhode Island) | State of Rhode Island General Assembly (archived) | File or endpoint | Sale definition, business-sale carve-out and applicability sections: R.I. Gen. Laws 6-48.1-1 to 6-48.1-10; sale definition 6-48.1-2(25); thresholds 6-48.1-4 | 1 registry row (8 coded fields) | 2026-11-02 |
| Oklahoma consumer data privacy law (Senate Bill 546) (Oklahoma) | Oklahoma Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: 75A O.S. (new sections; SB 546, 2026); sale definition section 14(28); applicability section 15 | 1 registry row (8 coded fields) | 2026-11-02 |
| Alabama Personal Data Protection Act (HB 351, 2026) (Alabama) | Alabama Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Act of 2026 (HB 351 enrolled); sale definition section 2(20); applicability section 3; exemptions section 4 | 1 registry row (8 coded fields) | 2026-11-02 |
| Louisiana Data Privacy Act (Act 502 of 2026) (Louisiana) | Louisiana State Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: La. R.S. 51:1780.1 to 1780.5 (Act 502, SB 386); sale definition 1780.1(28); applicability 1780.2 | 1 registry row (8 coded fields) | 2026-11-02 |
| Vermont Data Privacy and Online Surveillance Act (Act 145 of 2026) (Vermont) | Vermont General Assembly | File or endpoint | Sale definition, business-sale carve-out and applicability sections: 9 V.S.A. ch. 61A, 2415a to 2415k (Act 145, S.71); sale definition 2415a(46); applicability 2415b | 1 registry row (8 coded fields) | 2026-11-02 |
| Florida Digital Bill of Rights (Florida (narrow law, not counted)) | Florida Legislature | File or endpoint | Sale definition, business-sale carve-out and applicability sections: Fla. Stat. 501.701 to 501.722; controller and sale definitions 501.702(9), (29) | 1 registry row (8 coded fields) | 2026-11-02 |
| CCPA monetary thresholds (CPI adjustment) | California Privacy Protection Agency | File or endpoint | Revenue threshold effective 2025-01-01 | 1 value ($26,625,000) | 2026-11-02 |
Data quality and exclusions
- Universe: 24 laws found; Florida's Digital Bill of Rights (1) is listed for reference and removed from every count because it applies only to controllers with more than $1 billion in global revenue, leaving 23.
- Archived copies: 7 laws (Colorado, Oregon, Nebraska, New Hampshire, New Jersey, Tennessee, Rhode Island) were coded from Internet Archive captures of the official page because the state host timed out from our network; each capture URL and date is in raw/wayback_captures.log.
- Indiana (1): iga.in.gov returned an empty JavaScript shell for every code and bill URL, so Indiana is coded from the Attorney General's official guide and marked 'interpretation needed'; it is left out of the proposed-deal count, which therefore uses 22 laws.
- Texas and Colorado (2): coded from the enrolled or signed bill because the codified text was not retrievable; later amendments to the sale definition or applicability section were not checked for these two.
- California: leginfo.legislature.ca.gov returned HTTP 403; the statute was read from the California Privacy Protection Agency's posted text effective 2026-01-01.
- Enactment dates (14 rows) are shown as the session year where the approval date is not printed in a document we opened; effective dates were all read from the act or code history.
Methodology
Selection: we included every state law commonly described as a comprehensive consumer privacy law that we could confirm from an official enactment or code text as of 2026-11-02, a total of 23, and listed Florida's Digital Bill of Rights separately because its $1 billion revenue test excludes small businesses. Sector laws (health data, biometrics, children's codes) are out of scope.
Sources: each row is coded from the state legislature's code or session-law text, or an agency's posted statute text, saved in raw/. Where a state host timed out from our network we used an Internet Archive capture of the official page and labelled it. Law-firm and vendor summaries were not used as evidence for any row; three are listed as pages compared against.
Coding: for each law we recorded the effective date, the headline consumer threshold, any sale-of-data route and revenue test, any small-business exemption, whether the 'sale' definition excludes a business-sale transfer, whether that exclusion names proposed transactions, any condition attached, and the consideration that makes a transfer a 'sale'. Confidence is 'clear text' where the official text was read and 'interpretation needed' for Indiana, coded from Attorney General guidance.
Conflicts: where a later version of a section is already printed with a future effective date (Connecticut 2026-07-01, Delaware 2027-01-01, Utah 2027-01-01, Kentucky 2027-07-01), the registry shows the version in force on 2026-11-02 and notes the change.
Derived metrics: counts and shares are computed in scripts/build.py from scripts/laws_data.py; per-day figures divide each annual threshold by 365. All formulas and the fact-sheet rows used are in derived_metrics.csv.
Last update: 2026-11-02. We plan to re-check after each legislative session. Owners who want help finding a broker can use the broker match form; it is not part of this research.
This report presents published data with its limitations. It is not legal, financial or investment advice.
Sources, ranked by quality
Tier 1: primary and official sources (49)
- [1] California Privacy Protection Agency. California Consumer Privacy Act of 2018 (Civ. Code 1798.100 et seq.), statute effective 01/01/2026. Statute as in effect 2026-01-01, posted December 2025. Accessed 2026-11-02.
- [2] California Privacy Protection Agency. California Consumer Privacy Act Monetary Thresholds (CPI adjustment). Effective 2025-01-01; posted 2024-12-17. Accessed 2026-11-02.
- [3] Virginia Legislative Information System. Va. Code 59.1-575, Definitions (Consumer Data Protection Act). Law as read 2026-11-02. Accessed 2026-11-02.
- [4] Virginia Legislative Information System. Va. Code 59.1-576, Scope; exemptions. Law as read 2026-11-02. Accessed 2026-11-02.
- [5] Virginia Legislative Information System (archived). Acts of Assembly 2021 Special Session I, Chapter 35 (HB 2307), Internet Archive copy. Approved 2021-03-02. Accessed 2026-11-02.
- [6] Colorado General Assembly (archived). Senate Bill 21-190, Colorado Privacy Act, signed act, Internet Archive copy. Act as signed, 2021. Accessed 2026-11-02.
- [7] Connecticut General Assembly. Conn. Gen. Stat. Chapter 743jj, Data Privacy and Security, 2026 Supplement. Revised to January 1, 2026, with July 1, 2026 versions. Accessed 2026-11-02.
- [8] Connecticut General Assembly. Public Act No. 25-113 (Substitute Senate Bill 1295). Approved 2025-06-24. Accessed 2026-11-02.
- [9] Utah State Legislature. Utah Code 13-61-101 and 13-61-102 (Utah Consumer Privacy Act), current and 2027 versions. Law as read 2026-11-02. Accessed 2026-11-02.
- [10] Utah State Legislature. S.B. 227 Consumer Privacy Act (2022 General Session) status page. Signed 2022-03-24; effective 2023-12-31. Accessed 2026-11-02.
- [11] Texas Legislature Online. H.B. No. 4, 88th Legislature, enrolled (Texas Data Privacy and Security Act). Enrolled 2023; effective 2024-07-01. Accessed 2026-11-02.
- [12] Oregon State Legislature (archived). Oregon Revised Statutes chapter 646A (2025 edition), ORS 646A.570 to 646A.589, Internet Archive copy. ORS 2025 edition, captured 2026-10-31. Accessed 2026-11-02.
- [13] Oregon State Legislature (archived). Senate Bill 619 (2023), enrolled, Internet Archive copy. Enrolled 2023. Accessed 2026-11-02.
- [14] Montana Legislature. Mont. Code Ann. 30-14-2802, Definitions. Law as read 2026-11-02. Accessed 2026-11-02.
- [15] Montana Legislature. Mont. Code Ann. 30-14-2803, Applicability. Law as read 2026-11-02. Accessed 2026-11-02.
- [16] Montana Legislature (archived). Senate Bill 384 (2023), enrolled, Internet Archive copy. Enrolled bill, captured 2023-05-22. Accessed 2026-11-02.
- [17] Iowa Legislature. Iowa Code 2026, Chapter 715D, Consumer Data Protection. Iowa Code 2026. Accessed 2026-11-02.
- [18] Iowa Legislature. 2023 Iowa Acts, Chapter 17 (SF 262). Approved 2023-03-28. Accessed 2026-11-02.
- [19] Delaware Code Online. Delaware Code Title 6, Chapter 12D, Delaware Personal Data Privacy Act. Current text with versions effective 2027-01-01. Accessed 2026-11-02.
- [20] Delaware Code Online, session laws. 84 Del. Laws c. 197 (HB 154). Approved 2023-09-11. Accessed 2026-11-02.
- [21] Nebraska Legislature (archived). Neb. Rev. Stat. 87-1102, Terms, defined, Internet Archive copy. Captured 2026-10-18. Accessed 2026-11-02.
- [22] Nebraska Legislature (archived). Neb. Rev. Stat. 87-1103, Applicability of act, Internet Archive copy. Captured 2026-10-18. Accessed 2026-11-02.
- [23] Nebraska Legislature (archived). Legislative Bill 1074 (2024) slip law, Internet Archive copy. Approved 2024-04-17. Accessed 2026-11-02.
- [24] New Hampshire General Court (archived). N.H. RSA Chapter 507-H, Expectation of Privacy, Internet Archive copy. Captured 2026-10-18. Accessed 2026-11-02.
- [25] New Jersey Legislature (archived). P.L.2023, Chapter 266 (New Jersey), Internet Archive copy. Approved 2024-01-16. Accessed 2026-11-02.
- [26] Tennessee Secretary of State (archived). Public Chapter No. 408 (HB 1181, 2023), Tennessee Information Protection Act, Internet Archive copy. Passed 2023-04-21; effective 2025-07-01. Accessed 2026-11-02.
- [27] Minnesota Office of the Revisor of Statutes. Minnesota Statutes Chapter 325M (full text). Law as read 2026-11-02. Accessed 2026-11-02.
- [28] Minnesota Office of the Revisor of Statutes. Laws of Minnesota 2024, Chapter 121. Session law 2024. Accessed 2026-11-02.
- [29] Maryland General Assembly. Md. Code, Commercial Law 14-4701, Definitions (Maryland Online Data Privacy Act). Law as read 2026-11-02. Accessed 2026-11-02.
- [30] Maryland General Assembly. Md. Code, Commercial Law 14-4702, Applicability. Law as read 2026-11-02. Accessed 2026-11-02.
- [31] Maryland General Assembly. Chapter 455 of 2024 (SB 541). Approved 2024-05-09. Accessed 2026-11-02.
- [32] Indiana Office of the Attorney General. Indiana Consumer Data Protection: Consumer Bill of Rights and Q&A. Agency guidance on the law effective 2026-01-01. Accessed 2026-11-02.
- [33] Kentucky General Assembly. KRS 367.3611, Definitions (effective until July 1, 2027). Law as read 2026-11-02. Accessed 2026-11-02.
- [34] Kentucky General Assembly. KRS 367.3613, Application. Effective 2026-01-01. Accessed 2026-11-02.
- [35] Kentucky General Assembly. 24 RS HB 15, enrolled (Kentucky Consumer Data Protection Act). Enrolled 2024. Accessed 2026-11-02.
- [36] State of Rhode Island General Assembly (archived). R.I. Gen. Laws 6-48.1-2, Definitions, Internet Archive copy. Captured 2026-10-12. Accessed 2026-11-02.
- [37] State of Rhode Island General Assembly (archived). R.I. Gen. Laws 6-48.1-4, thresholds and controller duties, Internet Archive copy. Captured 2026-09-30. Accessed 2026-11-02.
- [38] Oklahoma Legislature. Enrolled Senate Bill No. 546 (2026). Enrolled 2026. Accessed 2026-11-02.
- [39] Oklahoma Legislature. Bill information: SB 546 (2026 session). Approved by Governor 2026-03-20. Accessed 2026-11-02.
- [40] Alabama Legislature. HB351 Enrolled (2026 Regular Session), Alabama Personal Data Protection Act. Enrolled 2026. Accessed 2026-11-02.
- [41] Louisiana State Legislature. Act No. 502 (SB 386), 2026 Regular Session, Louisiana Data Privacy Act. Act 502 of 2026. Accessed 2026-11-02.
- [42] Louisiana State Legislature. SB 386 bill history (2026 Regular Session). Signed 05/29/2026. Accessed 2026-11-02.
- [43] Vermont General Assembly. Act No. 145 of 2026 (S.71), as enacted. Signed 2026-06-16; effective 2028-01-01. Accessed 2026-11-02.
- [44] Florida Legislature. Fla. Stat. 501.702, Definitions (Florida Digital Bill of Rights). Law as read 2026-11-02. Accessed 2026-11-02.
- [45] Florida Senate. CS/CS/SB 262 (2023), enrolled. Enrolled 2023; effective 2024-07-01. Accessed 2026-11-02.
- [46] California Privacy Protection Agency. CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance Regulations. Approved by OAL 2025-09-22; effective 2026-01-01. Accessed 2026-11-02.
- [47] Federal Trade Commission. FTC staff to Facebook and WhatsApp: Privacy promises prevail (Business Blog). Published 2014-04-10. Accessed 2026-11-02.
- [48] Kentucky General Assembly. KRS 367.3611, Definitions (effective July 1, 2027). Version effective 2027-07-01. Accessed 2026-11-02.
- [52] California Privacy Protection Agency. Regulations (CCPA statute, thresholds and rulemaking index). Page read 2026-11-02. Accessed 2026-11-02.
Tier 3: journalism and expert commentary (3)
- [49] Rocket Lawyer. Is It Legal to Sell My Business's Client List?. Last reviewed 2023-11-23. Accessed 2026-11-02.
- [50] Pillsbury Winthrop Shaw Pittman. Transferring Customer Data in an Asset Sale. 2015 advisory. Accessed 2026-11-02.
- [51] Kelley Drye (Ad Law Access). Privacy vs. Bankruptcy: Case Lesson on When Customer Data is Not for Sale. Published 2011-09-23. Accessed 2026-11-02.