Datasets:

referencesource
/

state-data-privacy-applicability-thresholds

pretty_name: 'US state consumer data privacy laws: applicability thresholds by state'
license: other
license_name: source-terms-cited
license_link: https://referencesource.org/state-data-privacy-applicability-thresholds/
language:
  - en
tags:
  - reference-data
  - provenance
  - referencesource-org
configs:
  - config_name: default
    data_files:
      - split: train
        path: data/records.jsonl

US state consumer data privacy laws: applicability thresholds by state

Canonical, always-current version: https://referencesource.org/state-data-privacy-applicability-thresholds/ Machine-readable: https://referencesource.org/state-data-privacy-applicability-thresholds/data.json — this mirror is a point-in-time copy.

Last verified: 2026-08-12
Stale after: 2026-11-10 (past this date, prefer the canonical copy — it re-verifies on a cadence this snapshot does not)
Records: 18

For each US state with a comprehensive consumer data privacy law, the thresholds a business must meet for the law to apply: consumer volume (number of state residents whose data is processed), revenue from data sales (percentage of gross revenue derived from selling personal data), revenue floor (minimum annual revenue), and whether these conditions are combined with AND or OR logic — sourced from the state's own statute. Answers 'does [state]'s privacy law apply to my business', 'what are the CCPA thresholds for 2026', 'which state privacy laws have no revenue threshold', 'how many consumers triggers the Virginia privacy law', 'which states changed their privacy law thresholds in 2026' (Connecticut lowers from 100k to 35k consumers on July 1, 2026, and adds a sensitive-data trigger with no volume floor; Indiana, Kentucky, and Rhode Island took effect January 1, 2026), 'which state has the lowest privacy law threshold' (Montana: 25k consumers), and 'does Utah require both a revenue AND consumer threshold' (yes — the only state using AND logic). As of mid-2026, 20 states have comprehensive consumer privacy laws in effect. No single authority publishes the thresholds for all states — each state's statute defines its own — which is why assembled versions come from compliance-software vendors (Feroot, IAPP, MultiState, PrivacyLawMap). The thresholds spread is wide: consumer volume from 25k (Montana) to 175k (Tennessee); revenue percentage from 0% (Texas, no numeric threshold) to 50% (Virginia model); revenue floor from $0 to $26.6M (California, inflation-adjusted). The AND/OR distinction matters: most states use OR (any threshold triggers the law), while Utah requires both revenue AND consumer volume, and Connecticut (CA) requires meeting one of three distinct paths.

Provenance — what every record carries

Every record carries source (the URL the value was read from) and source_quote (a verbatim quote from that page stating it). A value you cannot check against its page is indistinguishable from an invented one; these can all be checked. Each record is also individually addressable on the canonical site at its url.

Licence position

Facts and short attributed quotes taken from each state's own statute, linking back to the official code. Facts are not copyrightable (Feist, 1991); no source statute is reproduced wholesale.

Facts are not copyrightable; what this dataset takes from each source is a fact plus a short attributed quote linking back to the page that states it.

Sources

Fields

See any record in data/records.jsonl — field names are self-describing, and the canonical page for each record renders them with labels: https://referencesource.org/state-data-privacy-applicability-thresholds/