Your organization is probably training a model on data you don’t fully own, and you haven’t thought about what that means.

This isn’t theoretical. It’s becoming the reason some organizations can’t deploy models they spent months building, why legal is suddenly involved in product decisions, and why audits are unraveling.

Let me separate myth from reality here, because the legal landscape around training data is messy enough that most organizations are operating on assumptions.

Myth: “If it’s publicly available, we can use it for training.”

Reality: Publicly available is not the same as publicly licensed for machine learning. A dataset scraped from websites is not the same as a dataset licensed under a creative commons agreement. A corpus of text published on the internet is not automatically yours to train a foundation model on. Copyright holders have claims on their work even if it’s freely accessible. Some have already started suing. Others haven’t yet, but they have the legal standing to do so.

The practical implication: You can train a model on public data. You can’t assume you own the right to deploy it without understanding where that data came from and what licenses or claims might attach to it.

Myth: “We’ll just use public datasets that are already curated for ML.”

Reality: Curated datasets often come with documentation about where data came from, but not always with clear licensing for derivative works. And even when they do, that license might constrain how you can use the resulting model. Some licenses allow training but not commercial deployment. Some allow training but require you to make your model public. Some are clearer than others. Most organizations don’t read the license until something breaks.

The practical implication: Even “safe” datasets might not be safe for your specific use case. You need to actually read the licensing terms and understand what they mean for your deployment model.

Myth: “Synthetic data solves the problem.”

Reality: Synthetic data solves one problem—it’s generated from scratch, so you own it. But many approaches to generating synthetic data involve using real data as a seed. If you generated synthetic data by fine-tuning a model trained on licensed data, you’ve inherited the licensing problem. And if you’re using synthetic data that was generated from real data, there are legitimate questions about whether derivative rights claims apply.

The practical implication: Synthetic data is useful, but it’s not an automatic legal escape hatch. Understand how your synthetic data was generated and what licensing applies to the sources.

Myth: “Fair use lets us use any training data we want.”

Reality: Fair use is a legal defense, not a permission. It’s evaluated case-by-case on four factors: the purpose of use, the nature of the copyrighted work, the amount and substantiality of use, and the market impact. Training a commercial AI model is not obviously fair use. The amount and substantiality of use is massive—you’re using the entire work. The market impact could be significant—you might be competing with the original creator. Courts might find fair use applies. Or they might not. That’s not a risk assessment framework; that’s hoping you’re right.

The practical implication: Don’t assume fair use covers your training data. Treat it as a possible defense if you’re sued, not as a license to use whatever data you want.

Myth: “Small amounts of copyrighted data in a large training set are negligible.”

Reality: There’s no legal threshold where “small amount of copyrighted material” becomes acceptable. The question isn’t “how much?” It’s “did you use copyrighted material without permission?” Even a small amount matters legally. Whether it results in actual damages depends on other factors, but the infringement itself is the legal exposure.

The practical implication: You can’t solve attribution problems by dilution. Using a tiny amount of someone’s work without permission isn’t better than using a large amount; it’s still using it without permission.

Now, here’s what makes this complicated: The foundation models you’re fine-tuning or using were trained on data whose provenance is unclear. Major foundation model providers have trained on internet-scale data. They’ve faced legal scrutiny over it. When you fine-tune their model on additional data, you layer that risk on top of new risk.

What should you actually do?

First: Know what data you’re training on. Make a list. Document the source. If you downloaded it, document where. If someone shared it, document that. If you scraped it, document that. Get metadata about licensing and ownership.

Second: For each source, verify the rights. Can you legally use this data for commercial AI training? Not “is it publicly accessible?” but “do we have the rights to train a model on it?” This means reading license agreements. This means understanding copyright claims. This means acknowledging uncertainty when licensing is unclear.

Third: Keep records of your due diligence. If you later discover you used copyrighted material, the fact that you tried to verify rights matters. Willful infringement is worse than inadvertent infringement. Document that you made a good-faith effort to understand what you were doing.

Fourth: For models going into production, have a legal perspective on training data provenance. Not after the fact—before deployment. This is a governance gate, like model validation or safety review. Does legal sign off on the training data used for this model? If not, what’s the risk assessment?

Fifth: For foundation models, understand what you’re inheriting. The model you’re fine-tuning has training data you don’t fully own. When you fine-tune it, you’re creating derivative works of derivative works. That’s legally complex. At a minimum, understand the foundation model’s licensing terms and what restrictions they place on your use.

The organizations that are handling this well treat training data provenance as seriously as they treat model accuracy. They have someone who owns this question. They document their decisions. They don’t assume they have rights they haven’t verified. They distinguish between “we can use this data” and “we can deploy a model trained on this data.”

The ones getting in trouble treat it as a problem to solve after the model is built, or as something that legal will “figure out” later. They inherit models trained on questionable data. They deploy models trained on that data without understanding the licensing constraints. Then they’re surprised when legal gets involved.

Your model might be excellent. Your training data might be the right data for the problem. But if you can’t defend your rights to use that data, you can’t deploy the model. That’s not a legal problem you solve later. That’s a governance problem you solve now.