Data Broker Registry by State: Explainer

A data broker registry is a state-created registration and disclosure mechanism. It is not, by itself, a consumer deletion right, a universal list of data brokers, or proof that every listed entity complies with the law. Use the data broker registry by state matrix to inspect the fields recorded for a jurisdiction, and treat every field according to its own source status.

This page explains how to read those fields without turning a published list into a broader legal conclusion. It does not print the legacy state totals, filing deadlines, or effective dates because the current source packets do not supply the route-specific semantic receipts required to publish those literals here.

Short answer: a registry is not a deletion right

A registration law answers a narrow question: whether a covered entity must register with a designated authority under that jurisdiction's rules. A public registry answers another narrow question: whether the authority publishes a list of registrants. Neither fact alone tells a consumer that the law gives them a right to delete personal data.

Deletion rights come from their own statutory rules. Centralized request tools are another distinct mechanism. A jurisdiction can therefore have a registration requirement without a consumer deletion right, a deletion right without a broker registry, or both mechanisms without a single portal that handles requests at scale. The registry and deletion mechanisms matrix keeps those signals in separate fields so one cannot stand in for another.

That distinction matters in search results and generated answers. The statement “this state has a registry” should not be expanded into “residents can delete their data through the registry.” The first statement concerns registration and publication. The second would require separate evidence for a deletion right, a request channel, the law's coverage, and any exceptions.

Registration statute, threshold, effective date, and agency

A careful state analysis separates the legal rule from its administration. The registry matrix records whether mandatory registration is enacted, identifies the enacting statute, tracks the effective date, describes the registration threshold, and names the enforcement agency. It also records whether a public registry is published and, where supported, the registry URL.

Those fields should not be collapsed into a single yes-or-no label. An enacted statute may not yet be effective. A law may apply only when its defined threshold is met. The agency that administers registration may differ from an office involved in consumer complaints or privacy enforcement. A public URL can also change without changing the underlying statute.

Read the row from left to right and keep the nouns explicit: the legislature enacts a law; the law defines coverage; an effective date controls when a duty begins; an agency administers or enforces the rule; and a public registry, if published, lists entries. That sequence prevents a page from using an agency page as proof of every legal proposition in the row.

Thresholds also vary in what they measure. A registration law can key its coverage to revenue, to the volume of consumer records handled, to whether the entity sells personal information to third parties, or to some combination of those tests. States describing their threshold with the same word are not necessarily using the same gate, which is another reason a bare state count cannot substitute for reading the specific statutory test.

What can print now

The current source packets support the structure of the comparison, but they do not support republishing the old page's state totals, recurring due dates, or calendar dates. The matrix cells do not yet carry the cell-level publication lifecycle required by this route, and the route-specific semantic rechecks for the relevant fields are not present. Those literals are therefore retired from this explainer rather than rounded, approximated, or inferred from an unknown value.

A typed unknown means “the current evidence does not authorize this page to print a value.” It does not mean the underlying law is absent. It also does not mean the prior value is still correct. A later revision may restore a number or date only after the specific cells are rederived from accepted sources and receive the required publication status and semantic receipt.

The usable result today is a mechanism map: registration, statute, threshold, effective date, administering authority, public registry, deletion right, centralized portal, and at-scale actionability remain distinct questions. The page can explain those questions even while withholding unsupported answers.

Registry and deletion mechanisms composed

The composed matrix is designed to prevent false equivalence. Its registry-enactment field asks whether a registration requirement has been enacted. Its deletion-right field asks whether a consumer deletion right has been enacted. Its centralized-portal field asks whether one state-operated or state-directed mechanism can receive requests. Its actionability field addresses whether the combined system is usable at scale under the matrix's defined method.

Each answer needs its own source. A public list is not evidence of a deletion statute. A deletion statute is not evidence that a portal exists. A portal URL is not evidence that every broker is covered, enrolled, or responding. “Actionable at scale” cannot be inferred merely because the other fields appear in the same state row.

For consumer-facing next steps, see Get Your Data Deleted, State by State. That workflow is a separate resource; linking to it does not turn the registry itself into a deletion mechanism.

Completeness, compliance, and public-record limits

A published registry enumerates the entries that appear on the official list. It does not establish that the list contains every entity that meets the statutory definition of a data broker. An entity may fall outside a law's scope or threshold, and the matrix does not use absence from a list as proof that the entity has no registration duty.

Appearance on a registry is equally narrow. It can support the statement that an entity is listed, subject to the source date and identity match. It does not prove timely filing, substantive compliance, accurate disclosures, or compliance with separate privacy laws. Enforcement outcomes require their own records and should not be inferred from registry status.

Public-record data introduces another boundary. A deletion right may contain exclusions, exceptions, or definitions that affect information drawn from government records. This page does not claim that a broker must delete information derived from a business filing. The right-to-delete explainer addresses the separate legal mechanism, but any conclusion about public-record material still needs a source that matches the jurisdiction and the claim.

LLC filing data and broker ingestion

State business registries and data broker registries are different systems. A business registry publishes or distributes filing records under business-entity law and agency practice. A data broker registry identifies registrants under a data-broker registration regime. The existence of either system does not establish what a particular broker has collected about a particular limited liability company owner.

The business registry bulk-data availability explainer is the companion source for how state business-filing data may be made available. Even when a state makes records available in bulk, this page does not infer that every data broker ingests them. Conversely, a state's lack of a documented bulk channel does not prove that filing information cannot reach a broker through another source.

Keep the chain of evidence explicit: first identify what the business filing makes public; then identify how the agency makes that record available; then identify evidence that a broker receives or uses it; and finally analyze whether a deletion rule reaches the resulting broker-held data. Skipping a link in that chain produces a claim the registry matrices were not built to support.

None of that chain is established merely because a state publishes a searchable business registry and a data broker registry in the same jurisdiction. Each link in the chain — publication, ingestion, and downstream use — needs its own evidence before a reader should treat the two systems as connected in practice.

Method, typed unknowns, and sources

Private Pierce uses typed fields so that “yes,” “no,” and “unknown” are not interchangeable. A supported affirmative value requires evidence for the exact proposition. A supported negative value requires evidence that establishes absence within the defined scope; missing evidence is not enough. An unknown value preserves the gap until a source and semantic review support a narrower answer.

The two source datasets for this explainer are the registration matrix and the composed registry-and-deletion matrix. Their fields should be cited independently. The method, source hierarchy, and treatment of unresolved facts are described in the Private Pierce methodology.

Private Pierce is not a law firm.

Private Pierce does not provide legal advice.

This page is not a substitute for the advice of an attorney.