US Data Broker Registry List & Contact Leads Scraper avatar

US Data Broker Registry List & Contact Leads Scraper

Pricing

$0.005 / data broker registration

Go to Apify Store
US Data Broker Registry List & Contact Leads Scraper

US Data Broker Registry List & Contact Leads Scraper

Every registered data broker from the California (CPPA) and Oregon (DFR) state registries in one uniform table: company, DBA, contact email, phone, street address, website, privacy and opt-out contacts, plus California's Delete Act disclosures. Export all or look up by name.

Pricing

$0.005 / data broker registration

Rating

0.0

(0)

Developer

ScrapeBench

ScrapeBench

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

4

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Pain points

  • California publishes its registry as a 78-column CSV whose headers are whole sentences from the registration form, and Oregon splits its registry across three daily files with different layouts; neither lines up with the other.
  • Oregon's main file is a fixed-layout tab-delimited text file that repeats at least one licence (DATA-00325 twice on 2026-11-08) and carries no email; the opt-out email sits in a separate report keyed on the licence number.
  • Checking one vendor across states means opening each state's site and search separately.

What we solve

  • One uniform row per registration across states, with the state and registry named on each row.
  • Oregon's three files joined on the licence number, duplicates removed.
  • California's Delete Act answers turned into true/false fields and request counts you can filter and sort.
  • A state whose site refuses the run comes back as a free row naming it; the other state is still delivered.

Summary

Reads the state data broker registries live and returns one row per registration in the same shape for every state: registry, registration ID, company name and DBA, contact email, phone, street address, website, and the privacy or opt-out contacts the broker filed. California rows add the Delete Act disclosures from the CPPA's registry file: which sensitive data the broker collects (minors, precise geolocation, biometrics, sexual orientation, reproductive health and more), whether it sold data to a foreign actor, the federal government, law enforcement or a GenAI developer in the past year, which privacy laws regulate it, and how many delete, know, opt-out and limit requests it received, complied with and denied. Oregon rows add the opt-out methods and the data types the broker collects, sells or licenses, from the DFR's daily reports. Leave the names empty for the whole list (1,020 registrations on 2026-11-08), or give names, DBAs or registration IDs to look brokers up.

Who it's for

  • Privacy and data-deletion services building their broker opt-out lists
  • Compliance and vendor-risk teams checking whether a vendor is a registered data broker
  • Privacy researchers and journalists tracking who sells personal data to whom
  • Ad-tech and data-partnership teams vetting data suppliers
  • Sales teams selling privacy, consent or compliance tooling to data brokers

How to use

This actor does two jobs. Run it, then collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API).

Get a list (export): no names, just filters; returns the whole matching list.

{
"states": [
"CA",
"OR"
]
}

Check specific firms (lookup): put company names or licence numbers in queries; Inputs below says how each is matched.

{
"queries": [
"Acxiom",
"LexisNexis",
"Spokeo"
]
}

See Inputs below for every available field.

What you get

One row per record:

FieldDescription
registry_stateThe registry's state: CA or OR
registryThe registry's full name
registration_idCA broker ID or OR licence number (DATA-00447)
nameRegistered company name
dbaDoing-business-as or assumed business name
emailCA: primary contact email (every row). OR: the opt-out email filed (82% of rows)
phonePhone as the registry prints it
streetStreet address (also city, state, postal_code, country; OR adds county)
websiteCA: primary website
privacy_rights_urlCA: where consumers exercise their California privacy rights
opt_out_urlOR: opt-out website (also opt_out_email, opt_out_phone, opt_out_address, opt_out_other, opt_out_instructions)
registered_sinceOR: licence start date (registration_expires: renewal date)
ca_collectsCA: true/false for minors, account logins, government IDs, citizenship, union membership, sexual orientation, gender identity, biometric, precise geolocation, reproductive health
ca_shared_or_sold_toCA, past year: foreign actor, federal government, other state governments, law enforcement, GenAI developer
ca_regulated_byCA: FCRA, GLBA, IIPPA, CMIA, HIPAA where the broker answered yes (ca_regulation_details: what each covers)
ca_consumer_requestsCA: delete / know / opt-out / limit requests received, complied in whole or in part, denied, mean and median days to respond
or_data_collectedOR: per data type, Collect, Sell, License or Does Not Collect
or_opt_out_coversOR: whether a consumer can opt out per data type, of all activities, or by proxy
source_urlThe registry the row comes from

Sample:

{
"registry_state": "CA",
"registry": "California Privacy Protection Agency (CPPA) Data Broker Registry",
"registration_id": "1000",
"name": "01Advertising Inc.",
"dba": null,
"website": "https://www.01advertising.com",
"email": "privacy@01advertising.com",
"phone": "9496099696",
"street": "3857 Birch St, PMB 5032",
"city": "Newport Beach",
"state": "CA",
"postal_code": "92660",
"country": "US",
"privacy_rights_url": "https://www.01advertising.com/legal/dsar/",
"ca_collects": {
"minors": false,
"precise_geolocation": true,
"sexual_orientation": true,
"gender_identity": true,
"biometric": false
},
"ca_shared_or_sold_to": {
"foreign_actor": false,
"federal_government": false,
"law_enforcement": false,
"genai_developer": false
},
"ca_regulated_by": [],
"ca_consumer_requests": {
"delete": {
"received": 0,
"complied_in_whole": 0,
"complied_in_part": 0,
"denied": 0,
"days_to_respond_mean": 0,
"days_to_respond_median": 0
}
},
"source_url": "https://cppa.ca.gov/data_broker_registry/#broker-1000"
}

Inputs

FieldRequiredTypeDefaultDescription
statesnoarray["CA", "OR"]Two-letter codes or names of the state registries to read: CA (California Privacy Protection Agency) and OR (Oregon Division of Financial Regulation). Empty = both. VT and TX are accepted and answer a free row saying why they are not included yet.
statenostring—One state code; kept alongside 'states' for saved tasks.
queriesnoarray[]Leave empty to export every registration. Otherwise each entry is a company name or DBA (matched if contained, case and punctuation ignored) or an exact registration ID (CA broker ID such as 1000, OR licence such as DATA-00447). A name with no match returns a free row.
querynostring—One name or registration ID; kept alongside 'queries' for saved tasks.
maxResultsnointeger5000Run-wide cap on billed rows (a spend cap, not per query). Both registries together hold about 1,020 registrations (2026-11-08).
proxyConfigurationnoobject{"useApifyProxy": false}Off by default. Turn on if a registry answers 'blocked' from your run: California's site is behind an F5 firewall that refuses some IP ranges.

Pricing (Pay Per Event)

You pay per result (data-broker) — no charge for empty runs. Example: 1020 registrations at $0.005/result ≈ $5.10.

$5 per 1,000 registrations, no start fee: half the only other registry actor's $10 per 1,000 list price (2026-11-08). The whole two-state list (1,020 registrations on 2026-11-08) is about $5.10.

Use cases

  • Opt-out target list: every registered broker in both states with its contact email, privacy-rights page or opt-out website, for a deletion service's request queue (states empty, no names).
  • Vendor check: is a supplier a registered data broker, and in which state (queries: the vendor names).
  • Sensitive-data audit: California brokers that collect precise geolocation (116 of 625 on 2026-11-08) or sold data to a GenAI developer in the past year (32 of 625), filtered from ca_collects and ca_shared_or_sold_to.
  • Request-handling league table: sort California brokers by delete requests received and denied (ca_consumer_requests).
  • Outreach list for privacy tooling: company, email, phone and street address for every registered broker.

Why this actor

  • Two state registries in one run and one row shape, with each state's own disclosures kept as add-on fields.
  • Read live from each state's own file on every run, so a new registration shows up as soon as the state publishes it.
  • A refused or changed state is a free row, never a silent gap and never a failed run.

Limitations & updates

Covers the California and Oregon registries only; Vermont and Texas answer a free notice until they can be read. Rows are what each state publishes, as filed by the brokers: California's request counts and yes/no answers are the broker's own declarations for the prior year, and some fields are blank where a broker left them blank. No registration history: each run returns the current registrations.

FAQ

Which states are covered?

California (the California Privacy Protection Agency's Data Broker Registry, 625 registrations on 2026-11-08) and Oregon (the Division of Financial Regulation's Data Broker Registry, 395 registrations). Vermont and Texas also keep registries: Vermont's is searchable only behind a reCAPTCHA (its downloadable list is due by law from 2027-01-01) and Texas's is an interactive portal with no file, so neither is read yet. Asking for VT or TX returns a free row saying so.

How fresh is the data?

Every run downloads each state's current file: California's registry.csv and Oregon's data broker file and reports, which the DFR says are updated daily. Nothing is cached between runs.

Why do California and Oregon rows have different extra fields?

Each state asks brokers different questions. California's Delete Act registration asks about sensitive data, sales to governments and GenAI developers, regulating laws and consumer request counts; those are the ca_ fields. Oregon asks for opt-out methods and which data types the broker collects, sells or licenses; those are the or_ fields. The contact fields (name, DBA, email, phone, address) are the same on every row.

Why does an Oregon row have no email?

Oregon's main registry file carries no email; the email on an Oregon row is the opt-out email the broker filed in the DFR's opt-out report, present for 323 of 395 brokers on 2026-11-08.

How am I charged?

$0.005 per registration row returned. A company registered in both states is two rows, one per registry. Rows that explain something (a state that could not be read, a name with no match, a reached cap) are free. Set Maximum registrations to cap spend.

Guides & use cases

Written up on scrapebench.dev — the bench that runs and verifies this actor against the live source every night:

More actors, coverage and nightly verification results: scrapebench.dev

Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the MCP tab on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

"Look up Acxiom, LexisNexis and Spokeo in the US data broker registries and give me each one's contact email, phone and opt-out page per state."

That input returned 8 registrations across California and Oregon on 2026-11-08 (Acxiom 2, LexisNexis 4, Spokeo 2). Leave the names empty for the whole list. Runs started this way bill exactly like any other run.

Data & lawful use

This actor collects publicly available information that the California Privacy Protection Agency (CPPA) and the Oregon Department of Consumer and Business Services, Division of Financial Regulation (DFR) publishes for public lookup — licence records, business listings and the contact details professionals list there. Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the controller of that data and we act only as your processor (Apify Standard Actor Contract). You need a lawful basis for your use, must honour opt-out and deletion requests, and must follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar). Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and don't sell or share them.

Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by the California Privacy Protection Agency (CPPA) and the Oregon Department of Consumer and Business Services, Division of Financial Regulation (DFR). Names and marks are used only to describe the data source. Records are provided as published by the source and may be out of date or incomplete. For anything consequential (hiring, a permit, a legal decision), confirm the record with the issuing agency. You are responsible for making sure your use complies with applicable law and the source's terms.

Need help?

Open an issue on this actor's Issues tab and we'll respond there. Bug reports, missing fields and feature requests are all welcome. Guides and examples: scrapebench.dev.

If you are a person named in this data and want your record removed from our copy, email apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: Apify Console → Settings → Security → Share run data with developers. It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.