Rights and contracts
Dataset broker or principal? How to verify who your data counterparty is
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
To verify whether a data counterparty is a broker, a platform or a direct licensor, read the documents rather than the website: who is named as licensor in the grant clause, who warrants the rights, where those rights came from, who invoices and on whose behalf, who delivers the data and whose terms govern use. Each answer points to a role, and mixed answers mean counsel should review before you sign.
Checklist
Dataset broker principal
Key takeaways
- A counterparty's role is set by the contract it signs, not by whether its website says marketplace, broker or partner.
- A principal grants the license in its own name and stands behind it; an agent or platform arranges or hosts a license someone else grants.
- The grant clause, the rights warranty, the invoice and the governing terms are the four documents that most often settle the role.
- Statutory labels such as California's data broker or the EU's data intermediation service carry their own tests and are not interchangeable with commercial usage.
- Treat every role statement as a provider claim until a signed document, a public register or an upstream agreement extract supports it.
How do you verify whether a data deal counterparty is a broker, platform or direct licensor?
You verify the role from the transaction documents. Find the clause that grants the license and see which legal entity grants it, then check who gives the warranty that the rights exist, who issues the invoice and in what capacity, who controls delivery and whose usage terms you accept. Four or five consistent answers settle the role; conflicting answers are the finding.
The distinction matters because it decides whose rights you are relying on. If the counterparty is the principal, its own grant and warranty are what you negotiate, and its upstream rights must be wide enough to cover yours. If it is an agent, a platform or a service provider, the license comes from someone else, and that other party is the one whose rights, consent basis and restrictions you need to see.
This article is general information, not legal advice. The role map below is a working tool for buyers and their counsel; the conclusions for a specific deal depend on the documents and the governing law.
Five roles a data counterparty can hold
Commercial usage blurs these roles, so it helps to fix working definitions before reading any contract. The labels below are editorial categories for this map, not statutory terms. Privacy law adds its own vocabulary on top: under the GDPR a controller determines the purposes and means of processing while a processor acts on the controller's behalf, and the CCPA's service provider processes personal information for a business under a contract that bars it from selling or sharing that information.
| Role | What it does in the deal | Who grants your license | What you verify first |
|---|---|---|---|
| Direct licensor | Holds the records or the rights in them and licenses them itself | The counterparty | Its ownership or source of rights, consent basis and internal approvals |
| Principal reseller | Acquires rights from others and relicenses in its own name | The counterparty, within its upstream grants | That each upstream grant allows the resale and your intended use |
| Agent or arranging broker | Introduces or negotiates for one side but is not party to the grant | The underlying rights holder | Its written mandate and the identity of the party it represents |
| Platform or venue | Hosts listings, access control or payment while providers set terms | The listing provider, under terms it supplies | The provider entity behind each listing and its terms |
| Service provider or processor | Holds data only to process it for its client | Usually nobody; it cannot license what it processes for others | Whether its contract permits any onward use at all |
Why the name on the website does not settle the role
Statutes define their terms narrowly, and a company can match one definition while marketing itself under another. California's Delete Act defines a data broker as a business that knowingly collects and sells to third parties the personal information of a consumer with whom it has no direct relationship, and the California Privacy Protection Agency runs the registration program built on that definition. A firm that calls itself a data broker may not meet that test, and a firm that calls itself a marketplace may.
The EU uses yet another frame. Under Article 12 of the Data Governance Act as currently in force, a provider of data intermediation services may not use the data for purposes other than putting it at the disposal of data users, and must offer the service through a separate legal person. The Commission's digital omnibus proposal would replace that legal separation with a functional one, a change the EDPB and EDPS addressed in a 2026 joint opinion, so check the text in force on the day you sign. That neutrality condition is close to what this map calls a platform role, and a provider that also sells data on its own account is not acting neutrally for that data.
The FTC's 2014 study of nine data brokers described firms that combine and analyze consumer data to draw inferences. That is a description of an industry, not a contract role. For a specific deal, the statutory label tells you which obligations may apply; only the documents tell you who is granting your license.
The transaction role and evidence map
Work through these nine questions with the draft agreement, the order form, the invoice template and any platform terms in front of you. Each row lists the evidence to request and what the answer usually signals. Platform documentation is a useful check on the platform row: AWS Data Exchange, for example, offers providers a standard data subscription agreement template that they can edit or replace with their own, and Hugging Face lets dataset authors gate access so that users share contact details with the authors.
At a glance
The transaction role and evidence map
Record the result as one line per question: the answer, the document and clause it came from, the evidence grade from the next section and the date you checked it. Keep the file with the deal record. When the agreement is amended or renewed, rerun the nine questions against the new text, because a change in the party block or the warranty clause can move the counterparty from one role to another without any change in how it markets itself.
| Question | Evidence to request | Points to principal | Points to agent, platform or processor |
|---|---|---|---|
| Who grants the license? | The grant clause and the party block of the agreement | The counterparty grants in its own name | A named third party grants, or the counterparty signs as agent for it |
| Who warrants the rights? | Rights, non-infringement and privacy warranties and the indemnity | The counterparty warrants without reference to another party | Warranties pass through or are disclaimed in favor of the provider |
| Where did the rights come from? | Upstream agreement extracts, data source list, collection notices | Counterparty generated the records or holds a written upstream grant | Counterparty cannot produce an upstream grant because it holds none |
| Who invoices, and on whose account? | Invoice template, payment terms, any statement of collection on behalf | Invoices in its own name for the license | Invoices a fee or collects for the provider |
| Who controls and delivers the data? | Delivery clause, storage location, access mechanism | Counterparty holds and delivers the data | Provider delivers, or data stays in the provider's storage |
| Whose usage terms govern? | License terms, platform terms, listing terms | One agreement with the counterparty governs use | You accept the listing provider's terms through the platform |
| Who can change scope or fields? | Change and amendment clauses, correspondence | Counterparty agrees changes alone | Counterparty must ask the provider or its client |
| Is it on a data broker register? | State registry entries for the counterparty's legal name | Registration supports a resale role for personal information | No entry is not proof of any role; check the definition applies |
| What is its privacy role? | Data processing terms, privacy notice, controller statements | Acts as controller for the data it licenses | Acts as processor or service provider for a client |
Which statements are provider claims, and which are substantiated?
Grade every answer in the map by the strength of the evidence behind it. A role is substantiated only when the higher grades agree. The grades are editorial; adjust them with counsel for your own approval process.
In practice, a buyer can usually reach Grade 4 for the counterparty's own role early, because the draft agreement is already on the table. Grade 5 takes longer and depends on the counterparty's willingness to share upstream terms. Decide in advance which rows must reach Grade 5 before signature; the grant and warranty rows are the usual minimum when personal information or third-party content is involved.
- Grade 1, provider claim: website copy, sales decks, verbal answers and questionnaire responses. Useful leads, never sufficient.
- Grade 2, self-issued document: the counterparty's own policies, data source list or privacy notice. Binding on the counterparty in some respects but not proof of upstream rights.
- Grade 3, public record: a state data broker registry entry, a company registry filing or a published regulatory decision naming the entity.
- Grade 4, executed agreement: the signed license or platform terms naming the parties and the grantor.
- Grade 5, upstream evidence: extracts of the upstream grants or the source company's written confirmation that the counterparty may relicense for your use.
- Unknowns: record every question the counterparty declines to answer. A refused upstream extract is information, not a gap to fill with assumptions.
Illustrative case: the marketplace that held the license itself
This case is illustrative and invented. A model team finds a call-transcript dataset listed on a site that describes itself as a marketplace. The listing names a provider, so the team first assumes a platform role and asks for the provider's terms.
The draft agreement says otherwise. The site's own operating company is the only party granting the license, it gives the rights warranty in its own name and it invoices in full for the license. In the map, six of nine rows point to a principal reseller. The data source list names 4 contact-center operators, and the site produces upstream agreement extracts for 3 of them.
The team's decision follows from the map rather than the label. It negotiates the grant and warranty with the site as principal, narrows scope to the 3 sources with Grade 5 evidence, and records the fourth as an unknown until an upstream extract arrives. Had the site instead signed only as agent, the team would have needed a direct agreement with each operator.
Mixed roles: the exception that breaks a simple label
The same company can hold different roles for different datasets, or for different parts of one deal. A platform may host third-party listings and sell its own first-party data alongside them. A broker may arrange one deal as agent and buy and resell the next. A processor may hold one client's records under a service contract and license its own operational logs separately.
So fill in the map per dataset, not per company. If the rows split, for example a counterparty that grants the license in its own name but disclaims every rights warranty in favor of an unnamed provider, treat that as the main risk in the deal. The grantor and the warrantor should normally be the same party or be expressly linked.
Mixed roles also change over the life of a contract. A platform that starts by hosting a provider's listing may later buy that provider's rights and relist the same data under its own license. If renewal paperwork arrives from a different entity, or the warranty language changes, treat the renewal as a new counterparty review rather than a formality.
Signals that the role question needs counsel before signature
Some answers in the map are routine; others mean the role cannot be settled by procurement alone. Send the file to counsel, or narrow the scope, when you see any of these.
- The grantor named in the agreement is not the entity you have been dealing with, or is not named at all.
- The counterparty describes itself as a processor or service provider for the records it is offering to license.
- Personal information about consumers is involved and the counterparty has no direct relationship with them, which may bring state data broker duties into play.
- The deal crosses into the EU and the counterparty presents itself as a neutral intermediary while also licensing the data in its own name.
- Upstream grants are refused, redacted beyond use, or cover a narrower purpose than training models.
Where SourceX sits in this map
SourceX works on the rights-holder side: it licenses business data directly from companies and handles sourcing, rights review, contracting, preparation, delivery and payment. Delivery waits for the source company's signature on scope and terms; from then on SourceX may use, sublicense and distribute the de-identified dataset only as that agreement allows. For a buyer, that means the upstream agreement is a document that exists and can be discussed, not an assumption.
Buyers describe what they need through a request, and the data is sourced from U.S. businesses for that request rather than taken from inventory.
Frequently asked questions
Is a data marketplace the licensor of the datasets it lists?
Not necessarily. Many marketplaces let each provider supply its own license terms, and the buyer accepts those terms from the provider. Others grant the license in their own name. Read the party block and grant clause of the agreement you will actually sign.
What is the difference between a data broker and a data reseller?
In commercial usage a reseller buys rights and relicenses them as principal, while a broker may only arrange deals. Statutes use their own tests: California, for example, defines a data broker by knowingly selling personal information about consumers it has no direct relationship with. Check which definition applies to your deal.
Can a service provider license me data it processes for a client?
Generally it cannot do so on its own authority. Under the CCPA, a service provider's contract must bar it from selling or sharing the client's personal information and from using it outside the contracted purposes. Any license would have to come from the client that controls the data.
Does registering as a data broker prove the company owns the data?
No. Registration signals that the company believes a statutory definition applies to some of its activity. It says nothing about whether it holds upstream rights broad enough for your use, so you still need the grant, warranty and upstream evidence.
What should I ask a counterparty for before signing?
Ask for the draft agreement with the grantor named, the rights warranty and indemnity, a data source list, extracts of upstream grants for each source and the invoice template. Record any request it declines as an unknown in the evidence map.
Sources
- California's Delete Act defines a data broker as a business that knowingly collects and sells to third parties the personal information of a consumer with whom it has no direct relationship. Source
- The California Privacy Protection Agency publishes guidance for data brokers and runs the registration program built on the statutory definition. Source
- A CCPA service provider processes personal information on behalf of a business under a written contract that prohibits it from selling or sharing that information or using it outside the contracted business purposes. Source
- Under GDPR Article 4, a controller determines the purposes and means of processing, and a processor processes personal data on the controller's behalf. Source
- Article 12 of the Data Governance Act bars data intermediation service providers from using the data for purposes other than making it available to data users and requires a separate legal person. Source
- The FTC's May 2014 report studied nine data brokers and described how they combine and analyze consumer data to make inferences. Source
- On AWS Data Exchange, subscribing to a product means accepting the provider's offer terms, including its data subscription agreement. Source
- AWS Data Exchange offers providers a standard data subscription agreement template that they can edit or replace with their own terms. Source
- Hugging Face lets repository owners set a license in the repository card and asks users to respect a project's license. Source
- Hugging Face dataset authors can enable access requests, and users must share their contact information with the authors to get access. Source
- EDPB-EDPS Joint Opinion 2/2026 on the digital omnibus proposal includes a section on functional instead of legal separation of data intermediation services from other services. Source
Tell us what data you need
Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.