Beware of Impersonation Scams. Dilendorf Law Firm communicates only through @dilendorf.com email addresses. Ransomware attack or data breach? Call +1 (212) 457-9797 immediately.
Home/Tech & AI Startups/IP, Training Data & Open Source
Technology, AI & Robotics · New York

IP, Training Data & Open Source

Who owns the model, the output and the code. Where the training data came from and under what terms. Which open-source licenses are in your stack and what they require.

These are the first questions an investor or acquirer asks an AI company. We help you have the answers, and the documents behind them, before anyone asks.

Ownership  ·  Training data  ·  Copyright and trade secrets  ·  Open source  ·  Assignments
Why It Matters

An AI company’s value is its IP. Its IP is only what it can prove.

The Copyright Office has said that purely machine-generated output is not protected by copyright, while human contributions can be. Ownership between you and your model provider is set by the provider’s terms. Training data carries whatever license it came with.

None of that is a problem until a financing, an acquisition or a claim. Then every gap becomes a price adjustment or an indemnity.

We build the record as you go: assignments from everyone who writes code, a provenance log for training data, a license inventory for the stack, and copyright and trade secret protection for what matters most.

The Landscape

The lines the IP statutes draw.

Figures from the Copyright Act, the Patent Act and the Defend Trade Secrets Act.

$150,000
Maximum statutory damages per work for willful copyright infringement, available only if the work was registered in time
1 year
Grace period after an inventor’s own public disclosure to file a U.S. patent application before the disclosure counts as prior art
3 years
Time to bring a federal trade secret claim after the misappropriation was or should have been discovered
3 reports
Copyright Office reports on AI: digital replicas, copyrightability of AI output, and the use of copyrighted works in training

Under 17 U.S.C. § 411, registration generally must be made before an infringement suit can be filed. Statutory damages run from $750 to $30,000 per work before the willfulness increase. Sources: 17 U.S.C. § 504, Copyright Office; 17 U.S.C. § 411, Copyright Office; USPTO, MPEP § 2153, AIA 35 U.S.C. 102(b)(1); 18 U.S.C. § 1836, Defend Trade Secrets Act; U.S. Copyright Office, Copyright and Artificial Intelligence.

What We Do

What we do on IP for technology companies.

Ownership

Assignments and chain of title

Founder, employee and contractor IP assignments, confirmatory assignments for past work, and the records investors ask for in diligence.

Training data

Provenance and licensing

Where the data came from, under what license, what it permits, and the agreements for data you license in or out.

Output

Model and output rights

What your model provider’s terms say about inputs and outputs, what you can claim as your own, and what you pass through to your users.

Protection

Copyright and trade secrets

Registering the code and content that matter, and the access controls, confidentiality terms and policies that make a trade secret a trade secret.

Open source

License compliance

An inventory of the open-source components in your stack, what each license requires, and remediation before a financing or sale finds the problem.

Patents

Patent strategy and coordination

When a patent filing makes sense for an AI or software invention, the one-year clock after public disclosure, and coordination with patent counsel.

How We Work

How an IP review runs.

Done once properly, then maintained as the product grows.

01

Inventory

Who wrote what, what data trained what, and what licenses govern what.

02

Gaps

Missing assignments, unlicensed data, incompatible open-source terms and unregistered works that matter.

03

Cure

Confirmatory assignments, license negotiations, component replacement and registrations.

04

Record

A diligence-ready IP file and templates that keep it current.

Two Sides of the Practice

We draft it. We also defend it.

Counsel

Fintech and digital assets since 2017.

Max Dilendorf has advised fintech, payments and digital-asset companies since 2017, through the growth of the sector and the regulation that followed. The questions founders ask today about AI, we have worked through before with crypto.

Disputes

More than 130 arbitrations since 2019.

Software liability, platform and payment disputes, cybercrime losses and AI-related claims before the AAA, JAMS and NAM, and emergency relief in New York courts. What we learn in those rooms shapes how we draft.

Before a Financing or a Sale

Fix the chain of title before someone else checks it.

Every gap found in diligence costs more than the same gap fixed earlier.

Do
  • Get a signed IP assignment from every founder, employee and contractor
  • Keep a log of training data sources and the license for each
  • Read your model provider’s terms on output ownership before you rely on them
  • Run an open-source license scan and keep the inventory current
  • Register the copyright in your core code and content before you need to sue
Do not
  • Assume contractor work belongs to you without a written assignment
  • Train on data you do not have the right to use because it was publicly available
  • Describe AI-generated output as proprietary without knowing what you can claim
  • Ship a product on copyleft code without understanding the obligations
  • Disclose an invention publicly and wait more than a year to file
Insights

From the firm’s writing.

Founders

AI Startup Attorney: Legal Guide for Founders & Seed Funding

The documentation investors ask AI founders for, including IP and data.

Read the article
Domains

Domain Account Takeover: What Victims Must Do in the First 48 Hours

When a company’s domain, the front door to its brand, is taken.

Read the article
Founders

Asset Protection Lawyer for Tech Founders & Crypto Trusts

How founders separate personal wealth from company risk.

Read the article
FAQ

Frequently asked.

Between you and the provider, the provider’s terms decide, and they vary. As against the world, the Copyright Office’s position is that purely machine-generated output is not protected by copyright, while human-authored contributions can be. We document the human contribution and protect the rest through contracts and trade secret measures.

Publicly available is not the same as licensed. Websites have terms, datasets have licenses, and copyrighted works are copyrighted whether or not they are online. The Copyright Office’s third report addresses training on copyrighted works. We help you document what you used, under what terms, and where the risk is.

Not automatically. Unless the contractor signed a written assignment, the contractor may own the copyright and you may hold only a license. A confirmatory assignment can cure it if the contractor cooperates. Every contractor agreement should include one from the start.

Not open source itself; most of your stack is open source. The problem is license terms you did not read. Some licenses require you to release your own source code if you modify and distribute, or offer over a network. Acquirers and investors scan for this. We inventory and remediate before they do.

Sometimes. Software and AI inventions can be patentable, but the cost and disclosure must be weighed against trade secret protection. One clock matters regardless: a public disclosure starts a one-year period to file in the United States. We help decide and coordinate with patent counsel.

Tech & AI Startups Practice

Other areas of the practice.

Six services for technology companies, from ongoing counsel to the dispute. Back to the overview.

Know what you own before someone asks you to prove it.

A confidential review of your IP chain of title, training data and open-source stack, with a diligence-ready file at the end.

Dilendorf Law Firm PLLC · 115 Broadway, 5th Floor, New York, NY 10006 · info@dilendorf.com
Call us now Request consultation