Programs are listed alphabetically, every acquirer figure is a dated claim, and not licensing is a valid outcome. No deal by a named agency is in the DataPacts deal tracker as of 2026-11-17, and agency records are one segment of AI training data licensing.
DataPacts Editorial Team checked the program pages and rules cited here on 2026-11-09 and 2026-11-17, following how we source, date and check every figure.
What an Agency Holds: Deliverables, Working Files, Campaign Data and Its Own Records
An agency's archive holds six families of records, and only the last is the agency's own by default: final client deliverables, working files, briefs and client feedback, campaign data and client reports, websites and code built for clients, and the agency's own process records.
HUMXN states, read 2026-11-17, that it lists "Marketing & agencies: Campaign briefs, copy, ad performance, client reporting" and "Creative & design: Briefs, drafts, revisions, final assets and client feedback", and Regulr states "Agencies & Consulting: Briefs, project plans and how your team runs the work." Each line is that party's own statement.
The table compares the six record families, who names each and the first owner or limit, as of 2026-11-17.
| Record family | Typical contents | Named by (stated by) | First owner or limit | Source |
|---|---|---|---|---|
| Final client deliverables | campaigns, ads, brand identities, shipped sites and products | Mercor Design & Web Agency ("A portfolio of shipped sites or products over 3+ years") | client, where the MSA or SOW assigns them | Mercor feed /design-agency |
| Working files | layered PSD, AI or Figma sources, drafts, iterations, design systems | Mercor Design & Web Agency; Mercor Consumer Brand or Photo Studio (re-read 2026-11-17) | client or agency, by contract; licensed-in fonts and stock | Mercor feeds /design-agency, /consumer-brand |
| Briefs, revisions and client feedback | briefs, iterations, client feedback, presentation decks | Mercor ("Briefs, iterations and client feedback"); HUMXN Creative & design (read 2026-11-17) | client confidential information | Mercor feed; humxn.io/sell-company-data |
| Campaign data and client reports | campaign briefs, copy, ad performance, client reporting | HUMXN Marketing & agencies (read 2026-11-17) | client records; ad platform terms not stated here | humxn.io/sell-company-data |
| Websites and code built for clients | front-end code with history, repositories | Mercor Design & Web Agency; Pangea agency page | client, unless owned or cleared | Mercor feeds; pangea.ai/code-licensing/agency |
| The agency's own process records | procedures, playbooks, checklists, blank templates, project and task histories, own CRM and accounting | Regulr (read 2026-11-17) | agency; de-identified copy only | regulr.ai |
Before any license talk, the inventory records the client and the contract for each project.
Who Owns Client Work: Work for Hire, Freelancers and the Client Contract
Ownership of client work turns on who made it and what the client contract says; this section is information, not legal advice.
Work Made by the Agency's Employees and Freelancers
An agency owns what its employees make in the course of their work, in the United States as works made for hire and in the United Kingdom as first owner of the copyright, subject to any agreement to the contrary. 17 U.S.C. 201(b) makes the employer the author of a work made for hire, owning all rights unless a written instrument signed by both parties says otherwise, and CDPA 1988 s.11(2) makes the employer first owner of copyright in a work made by an employee in the course of employment (both in force as of 2026-11-17).
Freelancers and subcontracted studios are a separate case. Under 17 U.S.C. 101, commissioned work is made for hire only in nine listed categories and only with a signed written agreement, and contractor work otherwise needs a written assignment. The file-by-file check belongs to the rights audit before licensing data.
What the MSA and SOW Say About Deliverables and Working Files
Between agency and client, the master services agreement (MSA) and each statement of work (SOW) decide who owns deliverables and whether working files, drafts and the agency's tools follow them, and the agency reads those clauses rather than assuming. Four questions structure the read:
- Does an assignment clause pass deliverables to the client, and at what point?
- Are pre-existing materials, templates and tools carved out of the assignment?
- Do drafts, rejected concepts and layered sources count as deliverables?
- Does a reuse or portfolio clause reach a license to a third party?
Mercor's software listing, read 2026-11-17, lists "Client work an agency doesn't own" as not a fit. Authorship of employee and contractor code is covered under who owns the code a company wants to sell.
An earlier exclusive grant can block a new license, and Mercor's scoping question for consumer-brand and photo archives, read 2026-11-17, is "Has any of it been licensed before?"
Client Confidentiality, Unreleased Campaigns and Clients' Customer Data
An agency holds client information it owes a duty to keep confidential, such as unreleased products, campaign plans, budgets and results, and delivering that material to an AI acquirer is a disclosure even where the agency owns the copyright in the files.
Under the Defend Trade Secrets Act, 18 U.S.C. 1839(5), misappropriation includes disclosure by one who acquired a trade secret under a duty to maintain secrecy (in force 2016-05-11, Pub.
L. 114-153), and UK SI 2018/597 reg. 2 (in force 2018-06-09) defines a trade secret as information that is secret, has commercial value because it is secret and has been subject to reasonable steps to keep it secret.
The page on the Defend Trade Secrets Act and licensed training data sets out the statute for sellers.
Clients' customer data, such as email lists, CRM exports, audience files and ad-account data, is held for the client's purposes and is not the agency's to license. This page does not state any ad platform's terms on reusing campaign or audience data.
Four kinds of client material need the client's clearance first:
- unreleased products and launch dates;
- budgets, media plans and results in client reports;
- client customer lists and audience files;
- strategy documents received from the client.
Contract clauses and notice rules sit on the consent page. The same notice and consent logic is set out under confidentiality clauses and customer consent before licensing data.
What an Agency May License and What Stays Out
An agency may license records about its own business and work it owns outright or has cleared, and two intermediaries that name agencies state the same split on their own pages.
Regulr states, read 2026-11-17, "Owning a record and having the right to license it are different things.", and Pangea's agency page, read the same day, answers "But I can't share client code" with "Client work, NDAs, and confidential data stay out of it."
The table sets out what may be licensed and what stays out, as of 2026-11-17, each entry being the stating party's own wording or a close reading of it.
| May be licensed (own or cleared) | Stays out |
|---|---|
| Procedures, playbooks, checklists and training the team wrote (Regulr) | Client work the agency cannot license (Mercor, "Client work you can't license") |
| Blank templates and forms the agency authored (Regulr) | Client work, NDAs and confidential data (Pangea) |
| Project, task, scheduling and operations histories (Regulr) | Anything a contract, NDA or court order bars from sharing (Regulr) |
| CRM and accounting records about the agency's own business, de-identified (Regulr) | Data licensed from others (Regulr); stock or licensed imagery (Mercor) |
| R&D, internal tools and projects that have wound down, where owned (Pangea) | Client-owned, previously public or forked code (Pangea) |
| Client work the client has cleared (Mercor, "either your own or cleared with clients") | Images without usage rights (Mercor) |
Each entry is the party's own statement, read on the date shown; this split is a reading aid, not legal advice.
Own records still name clients, staff and customers, so they leave only as a de-identified copy, and Regulr states that it licenses only de-identified copies (checked 2026-11-09). The methods for removing names and personal data are set out under PII removal and de-identification before licensing.
Programs and Intermediaries That Name Agencies or Creative Records
Seven listings and pages from five companies name agencies, agency code or creative records on their own pages, and none of the six that state a client-work line takes client-owned work without the rights to it. HUMXN and Pangea are marketplaces, Regulr is a sell-side advisory, and Mercor and Polyshares license data themselves.
The table compares what each program or page names for agencies, in alphabetical order, as of 2026-11-17.
| Program or page | Role | What it names for agencies or creative records | Client-work line | Source |
|---|---|---|---|---|
| HUMXN company data licensing | marketplace (licenses to buyers bound by confidentiality) | "Marketing & agencies: Campaign briefs, copy, ad performance, client reporting"; "Creative & design: Briefs, drafts, revisions, final assets and client feedback" (read 2026-11-17) | company must own the data | humxn.io/sell-company-data |
| Mercor Consumer Brand or Photo Studio listing | company-data program | industries including "ad and creative agencies"; original images with model and usage releases; layered source files (re-read 2026-11-17) | "Stock or licensed imagery" and "Images without usage rights" are not a fit | api.data.mercor.com listings /consumer-brand |
| Mercor Design & Web Agency listing | company-data program | design files and production code for the same projects; briefs and revisions; industries including "web and front-end agencies, branding agencies" (re-read 2026-11-17) | own work or "cleared with clients"; "Client work you can't license" is not a fit | api.data.mercor.com listings /design-agency |
| Mercor Software Company listing | company-data program | private repositories, 50,000+ lines owned outright | "Client work an agency doesn't own" is not a fit (re-read 2026-11-17) | api.data.mercor.com listings /software-company |
| Pangea code licensing, agency page | marketplace (licenses code to AI labs on the owner's behalf) | "Your agency's old code"; R&D, internal tools, projects that have wound down (read 2026-11-17) | "Client work, NDAs, and confidential data stay out of it"; uncapped ownership warranty | pangea.ai/code-licensing/agency |
| Polyshares data licensing | licenses data directly (calls itself the counterparty) | "design files" among data wanted; any company with operating history, any sector | not stated | polyshares.com |
| Regulr | sell-side advisory (intermediary) | "Agencies & Consulting: Briefs, project plans and how your team runs the work." (read 2026-11-17) | "Anything a contract, NDA, or court order bars you from sharing" stays out | regulr.ai |
Design files as a data type, design-led ranges and design-tool AI terms are covered on the page about design files as AI training data.
No license by a named agency is in the deal tracker as of 2026-11-17, and a listing is no promise to accept every archive.
Clearing Client Work Before an Agency Licenses It
Client work enters a license only after the client clears it in writing or the contract already allows it, because acquirers ask the question directly and make the licensor stand behind the answer.
Mercor's design listing asks "Can you license client work, or only your own?" and requires "The right to license the work, either your own or cleared with clients" (read 2026-11-17), and it lists "Briefs, iterations and client feedback" as nice to have. HUMXN lists client feedback and client reporting too, and both carry client material.
Pangea states on its agency page, read 2026-11-17, that if the ownership warranty is incorrect the owner may need to return payments and cover resulting claims, and that this obligation is uncapped. Warranty wording is compared in indemnities and warranties in AI data licenses.
A clearing sequence has four steps: list client work by project, read each MSA and SOW, ask for written permission that names AI training, and drop or de-identify the rest. An older client consent covers AI training only if its wording does, so it is read rather than assumed.
Benefits, Risks, Downsides and Alternatives for an Agency
Licensing can earn income from records an agency already keeps, but client ownership, confidentiality and warranties that survive payment carry risks a fee does not offset, and not licensing is a valid outcome.
Benefits
- Acquirers name an agency's own records: Regulr lists procedures, templates and project histories, and Mercor lists "Proprietary design systems and component libraries, with code" (read 2026-11-17).
- One program states a range for design and web agencies, given in the FAQ below as a claim, not a price.
- Ownership stays with the agency under Pangea's non-exclusive terms (checked 2026-11-09).
Risks
- Licensing client-owned work is rejected by Mercor ("Client work you can't license") and by Mercor's software listing ("Client work an agency doesn't own").
- Delivering client confidential information is a disclosure that 18 U.S.C. 1839(5) can treat as misappropriation.
- Pangea's ownership warranty is uncapped and can require repayment.
Downsides
- Clearing work project by project takes time before any sample leaves.
- Mercor states thresholds of 3+ years of shipped work and 10 to 200 employees for its design listing (checked 2026-11-09).
- The agency's own records may be a small share of the archive, which the inventory shows.
Alternatives
- Licensing own business records only, as Regulr describes.
- Licensing own design systems or internal tools only, as Mercor and Pangea describe.
- Using the archive in-house.
- Not licensing at all, as covered under alternatives to selling data, including not selling at all.
Where Agency Licensing Meets Design Files, Studios, Code and the Seller Path
Agencies share the client-ownership question with production studios and software companies and the working-file question with individual artists, and the industry index sets out how each sector's limit differs.
The data licensing by industry index sits beside production studios licensing footage and images, software companies licensing code and product data, visual artists and illustrators and consulting firms licensing client deliverables, whose Mercor listing asks for "The right to license deliverables once anonymized" (read 2026-11-17).
Working files in design tools are covered under Figma file export and licensing. Agency pipeline and client contact records are covered under HubSpot data export and selling CRM records for AI training.
An agency that decides to proceed follows seven steps:
- Check data sale readiness for the agency as a whole.
- Build a data inventory for an AI data sale that separates own, cleared and client-owned records.
- Sign NDAs before sharing data with an AI buyer before any sample.
- Describe the records in the data manifest without handing them over.
- Work through choosing a buyer for your data.
- Compare terms in evaluating an offer for your data.
- Negotiate under AI data licensing agreements.
This page is information, not legal advice.
Program and Intermediary Pages Named on This Page
Each program and intermediary above has its own page with dates and sources.
- HUMXN (marketplace)
- Mercor
- Pangea.ai (marketplace)
- Polyshares
- Regulr (sell-side advisory)
Frequently Asked Questions
Who owns the work an agency makes for a client?
The client contract decides: employee work belongs to the agency first (17 U.S.C. 201(b); CDPA 1988 s.11(2)), but an MSA or SOW can assign deliverables to the client, and freelance work needs a written assignment.
Can a marketing agency license campaign data to AI companies?
Only its own records: campaign results, client reports and audience files are client information, and HUMXN's list of ad performance and client reporting (read 2026-11-17) does not change who owns them.
How much do AI companies pay agencies for their archives?
The DataPacts deal tracker holds no agency deal price; Mercor states USD 20,000 to 890,000 for a design and web agency, "Depends on archive size and rights" (checked 2026-11-09, re-read 2026-11-17).
The valuation methods are compared under what company data is worth to AI companies.
Can designers and copywriters get paid to train AI?
Individuals can do paid tasks for human-data platforms, a separate route from licensing the agency's archive.
The platforms are compared under AI training jobs and platforms compared.