- 1Provenance is a hard gate, not a bonus: a buyer who can't verify you lawfully hold and can grant rights to the data will walk at any price, or demand a discount that erases the value.
- 2Under GDPR, consent and lawful basis are distinct paths; consent must be freely given, specific, informed, and unambiguous, and neither consent nor legitimate interest can be manufactured after collection.
- 3Clinical data only becomes a licensable training asset through HIPAA de-identification: the Safe Harbor removal of 18 identifiers or a certified expert-determination path.
- 4Copyright and web-scraping risk is live and escalating: high-profile litigation over training on copyrighted corpus data has made provenance of every source a contractual requirement.
- 5Transferability is a legal question, not a technical one. A defensible provenance and consent file is what turns an accumulated dataset into an asset a reputable buyer can actually acquire.
Most startup datasets die at the due-diligence stage, not the negotiation stage. Price rarely kills a deal. A provenance or consent gap the buyer discovers when they ask for the legal file usually does. This guide walks through the regimes that gate AI training data: consent and lawful basis under GDPR, HIPAA de-identification for clinical data, copyright and web-scraping exposure, CCPA and other state privacy laws, the contractual warranties buyers will demand, and a practical due-diligence checklist. If you're winding down or pivoting, this is the difference between monetizing your data and discovering it was never transferable in the first place.
On this page ▾
Why provenance is a hard gate, not a bonus
In data M&A, provenance works as a binary gate, not a scale of value. A buyer runs due diligence to answer one question: can you prove you lawfully hold this data and can grant the rights in the license? Yes, and the deal proceeds to pricing. No, and the deal dies at any price, because no reputable AI lab or enterprise will ingest training data whose legal history it can't verify. [4]
The stakes have risen alongside demand for proprietary, human-generated data. Epoch AI estimates the usable stock of public text at roughly 300 trillion tokens and projects models may exhaust it between 2026 and 2032. [2] As public sources drain, buyers lean harder on closed datasets, and they scrutinize provenance more, precisely because those datasets aren't governed by a clear public license. Academic audits back this up: most large AI training datasets lack documented provenance, licensing terms, and attribution. [4]
“We find that over 70% of a subset of 1,800+ datasets of interest lack clear provenance information, terms of use, or attribution information, and are therefore unverifiable by downstream users.”
Consent vs lawful basis under GDPR
Under the GDPR, consent isn't a synonym for we have permission. It's one of six lawful bases in Article 6, alongside performance of a contract, legal obligation, vital interests, public interest, and legitimate interests. [4] For AI training data involving EU or UK personal data, the seller must point to a specific, documented lawful basis that supports both the original collection and the transfer of the data to the buyer. A transfer counts as processing under the regulation, so it needs its own basis.
Relying on consent means meeting the Article 7 / GDPR standard: freely given, specific, informed, and unambiguous, evidenced by a clear affirmative act. A pre-ticked box doesn't count. [6] Consent is also narrow: it covers only what the data subject actually agreed to, so training use is often a separate purpose requiring separate consent. If the data includes health, biometric, or other special-category data, the bar rises further: Article 9 generally forbids processing unless explicit consent or another specific exemption applies. [14]
“Processing shall be lawful only if and to the extent that at least one of the following applies: the data subject has given consent... or processing is necessary for the purposes of the legitimate interests pursued by the controller.”
| Legal basis | Where it fits AI training data | Red flags for buyers |
|---|---|---|
| Explicit consent (Art. 6 / Art. 9) | User-generated content, health/biometric data | Generic “we may use your data” wording; no record of the affirmative act |
| Legitimate interests (Art. 6(1)(f)) | B2B operational data with balanced interests | No documented balancing test; training use not foreseeable at collection |
| Contract performance | Data needed to deliver the product/service | Training isn't necessary for the contract; creep into unrelated purposes |
| Anonymization | No personal data remains, so GDPR does not apply | Claims of anonymization without a defensible method |
HIPAA de-identification for clinical data
For health-tech startups and clinical data holders, the governing question isn't value. It's whether the asset is licensable at all. Under HIPAA, protected health information (PHI) can only be shared in ways that satisfy the Privacy Rule. The pathway that makes clinical data usable for AI training is de-identification, rendering the data no longer individually identifiable, through one of two recognized methods: the Safe Harbor approach (removing an enumerated list of 18 identifiers from each record) or the expert-determination approach (a qualified statistician certifies the risk of re-identification is very small). [12]
A buyer must verify de-identification directly, because once data is properly de-identified it's no longer PHI, and HIPAA's restrictions largely fall away, unlocking a far larger and more sophisticated buyer pool. [2] The rigor still matters: Safe Harbor requires every one of the 18 identifiers, names, geographic units, dates more specific than a year, phone numbers, medical-record numbers, full-face photos, and more, to be stripped. Cutting corners, or relying on pseudonymized data that could be re-linked, leaves the transfer exposed, and any clinical dataset carrying special-category personal data may also implicate GDPR Article 9 for EU touchpoints. [4]
“De-identification is a process by which identifiers are removed from a health record so that the remaining information is no longer considered protected health information, and therefore is no longer subject to the HIPAA Privacy Rule.”
Copyright and web-scraping risks
A large share of the data that trains models, and that startups accumulate, originates from copyrighted works: news, books, forums, code, images. Whether training on a protected work counts as infringement or fair use is unsettled and actively being litigated, and the U.S. Copyright Office has opened a formal inquiry into how copyright should apply to AI training inputs. [2] For a seller, the practical consequence holds regardless of how that fair-use question resolves: any inability to account for a corpus's provenance is a liability on its own.
Web-scraping compounds the risk. Scraped data may be governed by terms of service that prohibit copying or reselling, by robots.txt and technical access controls, and by underlying copyright in the scraped works themselves. A buyer acquiring a scraped corpus inherits the claim exposure, including the risk that rightsholders assert infringement over the very documents used to train the buyer's model. [8] Landmark AI copyright cases will shape this field for years, but no seller should wait on that resolution: the defensible position is to monetize only data you can trace to a lawful source.
CCPA and the patchwork of state privacy laws
Beyond the GDPR, the California Consumer Privacy Act (CCPA), strengthened by the California Privacy Rights Act (CPRA), imposes a distinct set of obligations, including rights to know, delete, correct, and opt out of sale and sharing, that constrain how a California-touching startup can collect and transfer personal data. [6] The CCPA's own definition of sale or sharing can reach what most people call a license, so granting a data license to a buyer can itself trigger notice and opt-out obligations that need to show up in your provenance file.
California anchors a growing patchwork: a wave of states have enacted or advanced comprehensive privacy laws, including Colorado, Connecticut, Utah, and Virginia, and sectoral regimes for health, financial, and children's data add further layers. [4] For a winding-down startup, the practical rule is boring but essential: assemble the privacy compliance record for each jurisdiction your data touched, because a buyer's counsel will review the most restrictive applicable regime, not the most convenient one. The higher the compliance burden on record, the harder it gets to claim a clean transfer.
| Regime | Key constraint for sellers | What buyers will ask to see |
|---|---|---|
| GDPR / UK GDPR | Documented lawful basis; consent per purpose; special-category limits | DPIAs, consent records, legitimate-interest balancing, transfer mechanism |
| CCPA / CPRA | Notice, right to delete/correct/opt-out; sale and sharing triggers | Privacy policy, opt-out records, sale/sharing logs |
| State privacy laws (CO, CT, UT, VA...) | Differing consumer rights and processing rules | Controller obligations and data inventory |
| HIPAA | De-identification or authorization to use / disclose PHI | De-identification method, BAAs, expert certification |
Contractual provenance reps and warranties
Provenance gets enforced through representations and warranties in the Data Purchase Agreement. The standard package a buyer will demand includes a title and authority warranty (you own the data or hold the rights to license it), a provenance warranty (accurate description of how the data was collected and its source chain), a consent / compliance warranty (personal data lawfully processed under applicable law, including GDPR and CCPA where relevant), an intellectual-property warranty (the data doesn't infringe third-party copyright or other IP), and indemnification for breaches of those warranties. [14]
None of this is boilerplate: a warranty breach can trigger damages, mandatory deletion, and termination, and the indemnity shifts the cost of a downstream claim onto you. Because the buyer bears the long-tail risk of a model trained on tainted data, sophisticated acquirers will often ask for a provenance appendix, a schedule documenting each source, its license or authorization, consent capture, and any de-identification method. [4] The strength of that appendix directly sets how much warranty liability you carry and how much of the price survives dilution.
“The Office's report and the public record highlight how inputs to AI, including the datasets used to train models, raise novel copyright questions about reproduction, fair use, and the provenance of training corpora.”
A due-diligence checklist for sellers and buyers
Whether you sit on the selling or buying side, the same evidence decides whether a dataset transfers cleanly. Work through this checklist before any listing or closing. It's the exact review a serious marketplace or acquirer runs. [2]
- 1Map the source chain. For every record or corpus: where it originated, how it was collected, and under what license or authorization. [4]
- 2Document personal-data lawful basis. Identify GDPR Article 6 basis (and Article 9 handling for special categories) or verify anonymization for every jurisdiction touched. [4][6]
- 3Check clinical exposure. If any health data is present, confirm HIPAA de-identification (Safe Harbor 18 identifiers or expert certification) and keep the method on file. [4]
- 4Clear third-party rights. Rule out copyrighted works, terms-of-service restrictions, and scraped content you can't trace to a lawful source. [4]
- 5Align with privacy laws. Confirm CCPA/CPRA and state-law notice, opt-out, deletion, and sale/sharing obligations are satisfied and evidenced. [4]
- 6Prepare the provenance appendix. Assemble consent records, DPAs/BAAs, transfer mechanisms, and de-identification documentation into a clean schedule the warranty can reference.
- 7Draft the warranties honestly. Only represent what the file proves. A gap here can turn a negotiation into personal liability for the seller.
Provenance is the gateway to every other value driver. You can negotiate exclusivity, term, and price all day, but none of it matters if the legal file doesn't hold. [2] Sellers who invest in a defensible provenance and consent record turn a potentially unsellable heap of rows into a licensable asset. Buyers who run this checklist protect themselves from inheriting a claim that follows the model wherever it ships.
Sell data that can actually clear due diligence.
Get a free, no-obligation provenance and compliance review from the team that brokers AI training data deals every day. We'll tell you what's defensible, what needs fixing, and whether your data is ready to list.
List your data on Dayda→