Data broker laws in California, Vermont, Texas and Oregon generally cover businesses that sell personal information about people they have no direct relationship with. A company licensing its own de-identified operational data is usually in a different position, but the line can blur. This is general information, not legal advice, so confirm with counsel.
This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.
What data broker laws are for
Data broker laws target a specific business model: companies that gather personal information about people who have never dealt with them and sell it on. The people affected usually do not know the broker exists, so they cannot exercise privacy rights against it. Registration laws make brokers visible.
The laws work mainly through registration and disclosure. A covered business registers with a state office, pays a fee, and discloses facts about its practices. Some laws add security requirements or deletion duties. Failing to register can bring daily penalties.
The policy reason matters when reading the definitions. Legislators were not aiming at ordinary companies that hold data about their own customers and staff. They were aiming at firms whose product is other people's information. The wording follows that aim, though not always precisely, and a company at the edge of a definition should not assume the purpose will rescue it.
This guide is general information, not legal advice. The four state laws described here differ in their definitions and exemptions, they have been amended more than once, and other states are considering their own. Confirm the current text with counsel.
The four state registration laws
Four states have data broker registration laws at the time of writing. The table summarizes each. The definitions are paraphrased, and the statutes carry exceptions that the summary omits.
California's law goes furthest. The Delete Act moved the registry to the California Privacy Protection Agency and created a state-run mechanism through which a consumer can ask every registered broker to delete their personal information with a single request. The agency's site lists the registry and the current compliance dates.
Registration is public. Each state publishes its list, and California's registry shows whether a broker collects data about minors, precise location or reproductive health care. A company that registers is therefore making a public statement about its business. That is worth weighing against the alternative of restructuring a deal so that registration is not required.
| State | Where brokers register | Who is covered, in summary |
|---|---|---|
| California | California Privacy Protection Agency | A business that knowingly collects and sells to third parties the personal information of a consumer with whom it does not have a direct relationship |
| Vermont | Secretary of State | A business that knowingly collects and sells or licenses to third parties the brokered personal information of a consumer with whom it does not have a direct relationship |
| Texas | Secretary of State | A business whose principal source of revenue comes from collecting, processing or transferring personal data it did not collect directly from the individuals |
| Oregon | Department of Consumer and Business Services | A business that collects and sells or licenses brokered personal data to others, with exceptions for data about its own customers, users and employees |
Who is a data broker: the direct relationship test
Three of the four definitions turn on the same idea. A broker sells personal information about people it has no direct relationship with. A direct relationship generally exists where the person is the company's own customer, user, subscriber or employee, and has dealt with the company knowingly.
Texas frames it differently, by asking where the business's revenue mainly comes from. A company whose income is from running an operating business, and not from trading in personal data, would generally not meet that description.
Two further elements matter in every state. The information must be personal information as the law defines it. And the business must sell or license it, which in California follows the CCPA's broad definition of a sale.
The word knowingly appears in the California and Vermont definitions. A company that sells a dataset it believes to be free of personal information is in a different position from one that sets out to sell personal information. That is not a safe harbor. A seller who has been told that identifiers remain, and delivers anyway, can hardly claim not to know.
Why first-party, de-identified operational data is different
A company that licenses its own operational records for AI training differs from a broker in two ways. The first is origin. The records were created in the course of the company's own work, by its own staff, in dealings with its own customers. The people in them generally have a direct relationship with the company.
The second is de-identification. Where the delivered dataset contains no personal information as the relevant law defines it, there is nothing of the regulated kind being sold. California's definition of personal information excludes information that meets its deidentified test, which includes a public commitment and contract terms as well as technical measures.
Together, these place a typical first-party seller outside the usual reading of the definitions. That is a general observation, not a conclusion about any one company. Outrich Data is a direct buyer of company data and asks sellers to de-identify before delivery for this reason among others.
A further point concerns frequency and purpose. Broker statutes are written around an ongoing activity of collecting and selling. A company that runs a logistics or software business and licenses a cleaned archive is not in the business of collecting information for sale. Courts and regulators have had little occasion to test that distinction for AI training licenses, so it should be treated as an argument, not a rule.
Where the line can blur
The distinction is less clean in practice than on paper. Counsel should look at the following situations in particular.
- People in the data who never dealt with you. A call center's records include callers who are customers of its clients. A staffing firm's records include candidates sourced from elsewhere. Those people may have no direct relationship with the seller.
- Mixed sources. California's regulations say a business can be a data broker for personal information it sells that it did not collect directly from the consumer, even if it has a direct relationship with that consumer for other purposes.
- Enriched records. Contact or company data bought from a vendor and appended to your own records was not collected from the individual.
- De-identification that falls short. If records can still reasonably be linked to people, the data is personal information and the analysis starts again.
- Regular selling. A one-time license looks different from an ongoing line of business in selling data, particularly under a revenue-based definition.
The buyer's position
The analysis runs separately for the party on the other side. A buyer that acquires personal information about people it has never dealt with and then resells or sublicenses it is much closer to the statutory description of a broker than the original seller is.
This is one reason the structure of a deal matters to a seller. Ask whether the buyer will resell the data, in what form, and to whom. Ask whether the license bars the buyer and any later recipient from attempting to re-identify individuals. A seller whose de-identified data is later re-identified downstream may not be the one in breach, but it will be part of the story.
Sellers sometimes ask whether dealing with a registered data broker is a problem. It is not unlawful, but it changes the picture. Data sold to a broker is, by design, going to be sold again, and the seller has less control over where it ends up. A direct buyer that takes the license itself and names the permitted uses is a simpler counterparty to assess.
What a seller should do
A company planning its first data license does not need to assume it is about to become a data broker. It does need to check. Write down where the records came from and who the people in them are. Identify anyone with no direct relationship to the company and exclude or de-identify their information. Confirm that the delivered dataset meets the deidentified standard of the states involved, including California's public commitment and contract clause.
Then ask counsel the direct question for each state where the people in the data live: whether this transaction, as structured, makes the company a data broker there. If the answer is yes or uncertain, registration is generally a manageable step. Selling without registering where it was required is the outcome to avoid.
Keep the analysis on file. If a regulator or a later buyer asks why the company did not register, the answer is a dated memo showing what was sold, to whom, in what form and why counsel concluded the statute did not apply. Review it again if the company licenses data a second time, since repetition can change the conclusion.