In the three state laws covered here, de-identified data is carved out of the definition of personal information. The carve-out has conditions. In California, Virginia and Colorado, data only counts as de-identified if the business holding it takes reasonable measures, makes a public commitment not to re-identify it, and binds recipients by contract. This is general information, not legal advice, and your lawyer should review how these laws apply to your records.
How California defines "deidentified"
The California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act, defines the term in Civil Code section 1798.140(m). "Deidentified" means information that "cannot reasonably be used to infer information about, or otherwise be linked to, a particular consumer," provided that the business that possesses it:
- takes reasonable measures to ensure that the information cannot be associated with a consumer or household;
- publicly commits to maintain and use the information in deidentified form and not to attempt to reidentify it, except to test whether its deidentification processes meet the definition; and
- contractually obligates any recipients of the information to comply with the same subdivision.
Section 1798.140(v)(3) then says "personal information" does not include consumer information that is deidentified or aggregate consumer information.
The statute treats pseudonyms separately. Section 1798.140(aa) defines "pseudonymize" as its own term, and section 1798.140(aj) lists a "unique pseudonym" among its examples of a unique identifier. Which definition a particular dataset meets is a legal question, not a labeling choice.
The CCPA also applies only to a "business" as section 1798.140(d) defines it: broadly, a for-profit entity doing business in California that had annual gross revenues above $25 million (as adjusted), or buys, sells or shares the personal information of 100,000 or more consumers or households, or derives 50 percent or more of its annual revenues from selling or sharing personal information.
What "sale" means under the CCPA
Section 1798.140(ad) defines a sale widely. It covers "selling, renting, releasing, disclosing, disseminating, making available, transferring, or otherwise communicating" a consumer's personal information to a third party "for monetary or other valuable consideration."
That definition is written around personal information. Because section 1798.140(v)(3) takes deidentified information out of "personal information," the question for a license of de-identified records becomes whether the data actually meets subdivision (m). That is why the three conditions matter more than the word on the label.
Records are still personal information before they are de-identified. The statute defines a "service provider" in section 1798.140(ag) as a person that processes personal information on behalf of a business under a written contract that, among other things, prohibits selling or sharing it, and section 1798.140(ai) excludes service providers from the definition of "third party." How a handover of raw records for processing is classified therefore depends on the contract terms, which is something to ask your lawyer to check.
How Virginia and Colorado treat de-identified data
Virginia's Consumer Data Protection Act defines "de-identified data" in Code of Virginia section 59.1-575 as "data that cannot reasonably be linked to an identified or identifiable natural person, or a device linked to such person," and says "personal data" does not include it. Section 59.1-581(A) requires a controller in possession of de-identified data to take reasonable measures, publicly commit not to re-identify, and contractually obligate recipients to comply with the chapter. Section 59.1-581(E) adds that a controller that discloses de-identified data must exercise reasonable oversight of those contractual commitments.
The Colorado Privacy Act, as enacted by Senate Bill 21-190, uses wording close to California's. Section 6-1-1303(11) defines de-identified data as data that cannot reasonably be used to infer information about, or otherwise be linked to, an identified or identifiable individual, if the controller meets the same three kinds of condition. Section 6-1-1303(17)(b) excludes it from "personal data," and section 6-1-1307(2) requires reasonable oversight of contractual commitments.
| California | Virginia | Colorado | |
|---|---|---|---|
| Where defined | Civ. Code 1798.140(m) | Code 59.1-575, 59.1-581 | C.R.S. 6-1-1303(11), 6-1-1307 |
| Reasonable measures | Yes | Yes | Yes |
| Public commitment not to re-identify | Yes | Yes | Yes |
| Contract terms for recipients | Yes | Yes | Yes |
| "Sale" requires | Monetary or other valuable consideration | Monetary consideration | Monetary or other valuable consideration |
| People in an employment or commercial context | Covered | Not "consumers" | Not "consumers" |
The FTC test these definitions echo
The three-part structure appears in the Federal Trade Commission's March 2012 report, "Protecting Consumer Privacy in an Era of Rapid Change." The report says data is not "reasonably linkable" to a consumer or device where a company takes reasonable measures to ensure the data is de-identified, publicly commits to maintain and use it in a de-identified fashion and not to attempt to re-identify it, and contractually prohibits any company it gives the data to from attempting re-identification.
The report adds that "the standard is not an absolute one," and that what counts as reasonable depends on the circumstances, including the nature of the data and whether it is published externally. It also says that a company that re-identifies data after making the public commitment could face action under Section 5 of the FTC Act.
Employee and business contact data
This is where the three states differ most for a company's internal records.
In California, the Attorney General's CCPA guidance states that the exemptions for employment-related personal information and for personal information reflecting business-to-business transactions expired on December 31, 2022. The California Privacy Protection Agency's FAQ says California residents with CCPA rights include employees, job applicants, and contacts for business customers, vendors or independent contractors. It also says a California resident is a person, not a corporation or other business entity.
Virginia's definition of "consumer" in section 59.1-575 excludes a natural person acting in a commercial or employment context. Colorado's definition in section 6-1-1303(6) excludes an individual acting in a commercial or employment context or as a job applicant, and the Colorado Attorney General's guidance says the same.
So a purchasing manager's name in a CRM is personal information under the CCPA if that person is a California resident, while the same contact falls outside the Virginia and Colorado definitions of "consumer." Separately from any statute, Paid4Data always excludes payroll and HR records.
What these definitions do not settle
- Re-identification risk. All three laws use a reasonableness standard, not a guarantee. As our post on how de-identification works explains, unusual details can sometimes point back to a specific business, which is why buyers are contractually barred from re-identification.
- Who carries the conditions. The public commitment and the contract terms are written as duties of the business or controller that possesses the data.
- Your other commitments. A privacy statute's definition does not change what a customer contract or your own privacy notice says. Those are covered in five questions to answer first.
- Other laws. This article covers three state statutes. Other states, sector-specific laws and non-US law are outside it.
How this fits the licensing process
Two of these ideas show up directly in Paid4Data's process. Identifiers are removed and samples are reviewed by hand, as the security page describes, and buyers sign contracts that bar re-identification. The data license, with its Data Schedule of approved systems and exclusions, is a document your lawyer can review before anything is exported. Whether a given dataset meets a statutory definition remains a legal question for your own counsel.
The how it works page lists each step and document. To see whether your records are in range, request a free data review.
Sources
Checked on November 16, 2026.
- California Code, CIV 1798.140 (Definitions), California Consumer Privacy Act of 2018, California Legislative Information (leginfo.legislature.ca.gov)
- § 59.1-575. Definitions, Code of Virginia, Virginia Legislative Information System (law.lis.virginia.gov)
- § 59.1-581. Processing de-identified data; exemptions, Code of Virginia, Virginia Legislative Information System (law.lis.virginia.gov)
- Senate Bill 21-190, Concerning additional protection of data relating to personal privacy (Colorado Privacy Act), signed act, Colorado General Assembly (leg.colorado.gov)
- Colorado Privacy Act (CPA), Colorado Attorney General
- California Consumer Privacy Act (CCPA), State of California Department of Justice, Office of the Attorney General
- Frequently Asked Questions (FAQs), California Privacy Protection Agency (CPPA)
- Protecting Consumer Privacy in an Era of Rapid Change: Recommendations for Businesses and Policymakers (FTC Report, March 2012), Federal Trade Commission