Which state privacy laws apply to my app? The thresholds, as each statute words them
A state consumer privacy law binds you only if you cross its threshold, and the thresholds are not the same: the consumer counts differ, some states add a revenue test, and the way the tests combine differs too. Below is each state we have read, with the statute's own wording for each threshold, so the comparison is against the text and not against somebody's summary of it.
The answer, in the publisher's own words
Each state's thresholds and how they combine.
| State | Law | Consumer volume threshold | Revenue floor | How the tests combine |
|---|---|---|---|---|
| California | California Consumer Privacy Act of 2018 / California Privacy Rights Act (CCPA/CPRA) | annually buys, sells, or shares the personal information of 100,000 or more consumers or households | annual gross revenues in excess of twenty-five million dollars ($25,000,000), as adjusted pursuant to subdivision (d) of Section 1798.199.95 | OR — satisfies one or more of the following thresholds |
| Colorado | Colorado Privacy Act (CPA) | Controls or processes the personal data of one hundred thousand consumers or more during a calendar year | — | OR — satisfies one or both of the following thresholds |
| Connecticut | Connecticut Data Privacy Act (CTDPA) | Controlled or processed the personal data of not less than one hundred thousand consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — during the preceding calendar year met either threshold |
| Delaware | Delaware Personal Data Privacy Act (DPDPA) | Controlled or processed the personal data of not less than 35,000 consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — during the preceding calendar year did any of the following |
| Florida | Florida Digital Bill of Rights (FDBR) | — | Makes in excess of $1 billion in global gross annual revenues | AND — requires $1 billion+ in global gross annual revenues AND satisfies at least one additional criterion (50%+ revenue from online ads, operates a smart speaker with virtual assistant, or operates an app store with 250,000+ apps) |
| Iowa | Iowa Consumer Data Protection Act (ICDPA) | Controls or processes personal data of at least one hundred thousand consumers | — | OR — during a calendar year does either of the following |
| Kentucky | Kentucky Consumer Data Protection Act (KCDPA) | One hundred thousand (100,000) consumers | — | OR — control or process personal data of at least either threshold |
| Maryland | Maryland Online Data Privacy Act (MODPA) | CONTROLLED OR PROCESSED THE PERSONAL DATA OF AT LEAST 35,000 CONSUMERS, EXCLUDING PERSONAL DATA CONTROLLED OR PROCESSED SOLELY FOR THE PURPOSE OF COMPLETING A PAYMENT TRANSACTION | — | OR — during the preceding calendar year met either threshold |
| Minnesota | Minnesota Consumer Data Privacy Act (MCDPA) | during a calendar year, controls or processes personal data of 100,000 consumers or more, excluding personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — satisfies one or more of the following thresholds |
| Montana | Montana Consumer Data Privacy Act (MCDPA) | control or process the personal data of not less than 25,000 consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — applies to persons that conduct business in this state and meet either threshold |
| Nebraska | Nebraska Data Privacy Act (NDPA) | — | — | No numeric consumer or revenue thresholds — applies to any non-small-business that processes or sells personal data |
| New Jersey | New Jersey Data Privacy Act (NJDPA) | control or process the personal data of at least 100,000 consumers, excluding personal data processed solely for the purpose of completing a payment transaction | — | OR — during a calendar year either threshold is met |
| Oregon | Oregon Consumer Privacy Act (OCPA) | The personal data of 100,000 or more consumers, other than personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — during a calendar year, controls or processes either threshold |
| Rhode Island | Rhode Island Data Transparency and Privacy Protection Act (RIDTPPA) | Controlled or processed the personal data of not less than thirty-five thousand (35,000) customers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction | — | OR — during the preceding calendar year did any of the following |
| Tennessee | Tennessee Information Protection Act (TIPA) | During a calendar year, control or process personal information of at least one hundred seventy-five thousand (175,000) consumers | Exceed twenty-five million dollars ($25,000,000) in revenue | AND — requires exceeding $25,000,000 in revenue AND one of the volume thresholds |
| Texas | Texas Data Privacy and Security Act (TDPSA) | — | — | No numeric consumer or revenue thresholds — applies to any non-small-business that processes or sells personal data |
| Utah | Utah Consumer Privacy Act (UCPA) | during a calendar year, controls or processes personal data of 100,000 or more consumers | has annual revenue of $25,000,000 or more | AND — requires annual revenue of $25,000,000 or more AND one of the volume thresholds |
| Virginia | Virginia Consumer Data Protection Act (VCDPA) | control or process personal data of at least 100,000 consumers | — | OR — applies to persons that (i) during a calendar year, control or process personal data of at least 100,000 consumers or (ii) control or process personal data of at least 25,000 consumers and derive over 50 percent of gross revenue from the sale of personal data |
Where each line came from
California.
California, and that satisfies one or more of the following thresholds: (A) As of January 1 of the calendar year, had annual gross revenues in excess of twenty-five million dollars ($25,000,000) in the preceding calendar year, as adjusted pursuant to subdivision (d) of Section 1798.199.95. (B) Alone or in combination, annually buys, sells, or shares the personal information of 100,000 or more consumers or households.
Our record: /state-data-privacy-applicability-thresholds/california/. Quoted from <https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=1798.140.&lawCode=CIV>, last checked 2026-08-12, due to be re-checked by 2026-11-10.
Colorado.
(I) Controls or processes the personal data of one hundred thousand consumers or more during a calendar year; or Colorado Revised Statutes 2024 Page 142 of 320 Uncertified Printout (II) Derives revenue or receives a discount on the price of goods or services from the sale of personal data and processes or controls the personal data of twenty-five thousand consumers or more.
Our record: /state-data-privacy-applicability-thresholds/colorado/. Quoted from <https://leg.colorado.gov/sites/default/files/images/olls/crs2024-title-06.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Connecticut.
apply to persons that conduct business in this state or persons that produce products or services that are targeted to residents of this state and that during the preceding calendar year: (1) Controlled or processed the personal data of not less than one hundred thousand consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction; or (2) controlled or processed the personal data of not less than twenty-five thousand consumers and derived more than twenty-five per cent of their gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/connecticut/. Quoted from <https://web.archive.org/web/2024/https://www.cga.ct.gov/current/pub/chap_743jj.htm>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Delaware.
This chapter applies to persons that conduct business in the State or persons that produce products or services that are targeted to residents of the State and that during the preceding calendar year did any of the following: (1) Controlled or processed the personal data of not less than 35,000 consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction. (2) Controlled or processed the personal data of not less than 10,000 consumers and derived more than 20% of their gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/delaware/. Quoted from <https://delcode.delaware.gov/title6/c012d/index.html>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Florida.
Makes in excess of $1 billion in global gross annual revenues; and 6. Satisfies at least one of the following: a. Derives 50 percent or more of its global gross annual revenues from the sale of advertisements online, including providing targeted advertising or the sale of ads online; b. Operates a consumer smart speaker and voice command component service with an integrated virtual assistant connected to a cloud computing service that uses hands-free verbal activation.
Our record: /state-data-privacy-applicability-thresholds/florida/. Quoted from <https://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&Search_String=&URL=0500-0599/0501/Sections/0501.702.html>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Iowa.
This chapter applies to a person conducting business in the state or producing products or services that are targeted to consumers who are residents of the state and that during a calendar year does either of the following: a. Controls or processes personal data of at least one hundred thousand consumers. b. Controls or processes personal data of at least twenty-five thousand consumers and derives over fifty percent of gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/iowa/. Quoted from <https://www.legis.iowa.gov/docs/code/715D.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Kentucky.
KRS 367.3611 to 367.3629 apply to persons that conduct business in the Commonwealth or produce products or services that are targeted to residents of the Commonwealth and that during a calendar year control or process personal data of at least: (a) One hundred thousand (100,000) consumers; or (b) Twenty-five thousand (25,000) consumers and derive over fifty percent (50%) of gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/kentucky/. Quoted from <https://apps.legislature.ky.gov/law/statutes/statute.aspx?id=56648>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Maryland.
CONDUCTS BUSINESS IN THE STATE OR PROVIDES PRODUCTS OR SERVICES THAT ARE TARGETED TO RESIDENTS OF THE STATE, AND THAT DURING THE PRECEDING CALENDAR YEAR DID ANY OF THE FOLLOWING: (1) CONTROLLED OR PROCESSED THE PERSONAL DATA OF AT LEAST 35,000 CONSUMERS, EXCLUDING PERSONAL DATA CONTROLLED OR PROCESSED SOLELY FOR THE PURPOSE OF COMPLETING A PAYMENT TRANSACTION; OR 2. (II) (2) CONTROLLED OR PROCESSED THE PERSONAL DATA OF AT LEAST 10,000 CONSUMERS AND DERIVED MORE THAN 20% OF ITS GROSS REVENUE FROM THE SALE OF PERSONAL DATA.
Our record: /state-data-privacy-applicability-thresholds/maryland/. Quoted from <https://mgaleg.maryland.gov/2024RS/chapters_noln/Ch_455_sb0541E.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Minnesota.
This section, as added by Laws 2024, chapter 121, article 5, section 3, is effective July 31, 2025, except that postsecondary institutions regulated by the Office of Higher Education are not required to comply until July 31, 2029. Laws 2024, chapter 121, article 5, section 14. 325M.12 SCOPE; EXCLUSIONS. § Subdivision 1.Scope. (a) Sections 325M.10 to 325M.21 apply to legal entities that conduct business in Minnesota or produce products or services that are targeted to residents of Minnesota, and that satisfy one or more of the following thresholds: (1) during a calendar year, controls or processes personal data of 100,000 consumers or more, excluding personal data controlled or processed solely for the purpose of completing a payment transaction; or (2) derives over 25 percent of gross revenue from the sale of personal data and processes or controls personal data of 25,000 consumers or more.
Our record: /state-data-privacy-applicability-thresholds/minnesota/. Quoted from <https://www.revisor.mn.gov/statutes/cite/325M/full>, last checked 2026-08-12, due to be re-checked by 2026-11-10.
Montana.
apply to persons that conduct business in this state or persons that produce products or services that are targeted to residents of this state and: (a) control or process the personal data of not less than 25,000 consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction; or (b) control or process the personal data of not less than 15,000 consumers and derive more than 25% of gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/montana/. Quoted from <https://leg.mt.gov/bills/mca/title_0300/chapter_0140/part_0280/section_0030/0300-0140-0280-0030.html>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Nebraska.
Data Privacy Act applies only to a person that: (a) Conducts business in this state or produces a product or service consumed by residents of this state; (b) Processes or engages in the sale of personal data; and (c) Is not a small business as determined under the federal Small Business Act, as such act existed on January 1, 2024, except to the extent that section
Our record: /state-data-privacy-applicability-thresholds/nebraska/. Quoted from <https://nebraskalegislature.gov/laws/statutes.php?statute=87-1103>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
New Jersey.
that during a calendar 44 year either: 45 a. control or process the personal data of at least 100,000 46 consumers, excluding personal data processed solely for the 47 purpose of completing a payment transaction; or S332 [5R] SINGLETON, CODEY 12 1 b. control or process the personal data of at least 25,000 2 consumers and the controller derives revenue, or receives a discount 3 on the price of any goods or services, from the sale of personal 4 data.
Our record: /state-data-privacy-applicability-thresholds/new-jersey/. Quoted from <https://pub.njleg.state.nj.us/Bills/2022/S0500/332_R5.PDF>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Oregon.
means a person, a public corporation, including the Oregon Health and Science University and the Oregon State Bar, or a public body, as defined in ORS 174.109, other than a consumer, a controller, a processor or an affiliate of a controller or processor. [2023 c.369 §1] 646A.572 Scope and application; exclusions. (1)(a) ORS 646A.570 to 646A.589 apply to any person that conducts business in this state, or that provides products or services to residents of this state, and that during a calendar year, controls or processes: (A) The personal data of 100,000 or more consumers, other than personal data controlled or processed solely for the purpose of completing a payment transaction;
Our record: /state-data-privacy-applicability-thresholds/oregon/. Quoted from <https://www.oregonlegislature.gov/bills_laws/ors/ors646a.html>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Rhode Island.
entities that conduct business in the state or for-profit entities that produce products or services that are targeted to residents of the state and that during the preceding calendar year did any of the following: (1) Controlled or processed the personal data of not less than thirty-five thousand (35,000) customers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction. (2) Controlled or processed the personal data of not less than ten thousand (10,000) customers and derived more than twenty percent (20%) of their gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/rhode-island/. Quoted from <https://webserver.rilegislature.gov/Statutes/TITLE6/6-48.1/6-48.1-4.htm>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Tennessee.
However, the Tennessee Code Commission is requested to include the headings in any compilation or publication containing this act. SECTION 6. This act takes effect July 1, 2025, the public welfare requiring it.
Our record: /state-data-privacy-applicability-thresholds/tennessee/. Quoted from <https://publications.tnsosfiles.com/acts/113/pub/pc0408.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Texas.
APPLICABILITY OF CHAPTER. (a) This chapter 16 applies only to a person that: 17 (1)AAconducts business in this state or produces a 18 product or service consumed by residents of this state; 19 (2)AAprocesses or engages in the sale of personal data; 20 and 21 (3)AAis not a small business as defined by the United 22 States Small Business Administration, except to the extent that 23 Section 541.107 applies to a person described by this subdivision.
Our record: /state-data-privacy-applicability-thresholds/texas/. Quoted from <https://capitol.texas.gov/tlodocs/88R/billtext/pdf/HB00004F.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Utah.
This chapter applies to any controller or processor who: (a) (i) conducts business in the state; or (ii) produces a product or service that is targeted to consumers who are residents of the state; (b) has annual revenue of $25,000,000 or more; and (c) satisfies one or more of the following thresholds: (i) during a calendar year, controls or processes personal data of 100,000 or more consumers; or (ii) derives over 50% of the entity's gross revenue from the sale of personal data and controls or processes personal data of 25,000 or more consumers.
Our record: /state-data-privacy-applicability-thresholds/utah/. Quoted from <https://le.utah.gov/xcode/Title13/Chapter61/C13-61_2022050420231231.pdf>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
Virginia.
This chapter applies to persons that conduct business in the Commonwealth or produce products or services that are targeted to residents of the Commonwealth and that (i) during a calendar year, control or process personal data of at least 100,000 consumers or (ii) control or process personal data of at least 25,000 consumers and derive over 50 percent of gross revenue from the sale of personal data.
Our record: /state-data-privacy-applicability-thresholds/virginia/. Quoted from <https://law.lis.virginia.gov/vacodefull/title59.1/chapter53/>, last checked 2026-11-10, due to be re-checked by 2027-02-08.
What these statutes do not say
No statute here states a number of employees, and only one of them turns on the size of your business at all.
Checked, not asserted: none of headcount, employer, payroll, FTE appears anywhere in the eighteen provisions we hold of the state privacy statutes we have read. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
Texas is the exception, and its own sentence is in the table above: the chapter applies only to a person who is not a small business as the United States Small Business Administration defines one — a definition that agency publishes by industry, not a number the legislature wrote down. Everywhere else the number that decides is a count of consumers whose personal data you control or process, and in some states the share of gross revenue you derive from selling personal data. Virginia's record adds the trap worth reading next to it: employees and business contacts are excluded from its consumer count, so the staff you do have are not what is being counted either.
None of these statutes is written about software, a website or an API. What each one tests is the person who controls or processes the data, whatever the product is built out of.
Checked, not asserted: none of software, website, SaaS, platform, API, mobile, developer, source code appears anywhere in the eighteen provisions we hold of the state privacy statutes we have read. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
So "we are only an API", "we are a developer tool" and "we have no consumer-facing product" are not exemptions any of these texts offers. The exemptions they do offer are named in each record instead: in most of these states data already covered by GLBA or by HIPAA is carved out, and non-profits are treated separately in several. Those are the sentences to read next, and they are on the record page each row links.
What we have not read
Only the states we have read are here, and only their applicability thresholds — not what the law then requires of you, which is a much longer answer and a different dataset. Thresholds also move: at least one of these revenue figures is adjusted for inflation by the statute itself, so check the record's last-checked date before relying on it.
The same answer for a machine
- The thresholds as data — one record per state, with the statute's own sentence, the exemptions and who enforces it.
The other questions answered here
Does HIPAA apply to my app?, What does HIPAA require software to do?, Does HIPAA require encryption at rest, and which algorithm?, What must I log for HIPAA, and how long must records be kept?, What session timeout do HIPAA and NIST require?, What password rules does NIST state?, Do I need multi-factor sign-in, and under which rule?, How fast must I report a breach, by law and by state?, Which NIST 800-53 controls bear on a database, on object storage, on logs and on backups?, What is SOC 2, and what in it can and cannot be quoted for free?, Which cryptographic algorithms and TLS certificate lifetimes stop being acceptable, and when?.
All of them are listed on the question list.
What this page is
This page is assembled automatically out of the records named on it. No sentence of a rule on it is ours: every one is quoted from the publisher that wrote it, with a link to the page it was quoted from and the date we last checked that page.
SOC 2, ISO/IEC 27001 and PCI DSS are not quoted anywhere on these pages. The bodies that write those documents sell the text, and our position, written down in our constitution, is that facts plus a short attributed quote with a link are fine but republishing licensed text is not. So nothing here quotes a trust services criterion or an ISO clause. What can be quoted is the rules the public bodies publish — the HIPAA Security Rule, NIST SP 800-53, federal retention regulations, state statutes and the CA/Browser Forum's requirements — and that is what every answer here is built out of.
This is not legal advice and it is not a statement that any system complies with anything. A provision quoted here is a sentence from a published document, not a finding about your software. Who decides: your own counsel, your auditor, and the regulator.