Yes, in many cases. Engineering, architecture and manufacturing firms can license design files to AI labs when the firm has the right to share them and nothing in the files is restricted by a client contract or an export rule. The two questions that decide most cases are who owns each design and whether any of it counts as controlled technical data.
This article is general information, not legal advice. Your own lawyer should review ownership, client terms and export questions before any file is approved.
Which design files qualify
Paid4Data works from the design systems a firm already uses. The data sources page lists what is typically included from each one.
| System | What is typically included |
|---|---|
| AutoCAD, Revit, Civil 3D | Drawing sets and building models with revision history |
| SolidWorks, Inventor, Creo, CATIA, NX | Parts, assemblies, drawings and engineering change records |
| Altium, KiCad, OrCAD | Schematics, board layouts and BOMs |
| PDM and PLM systems | Release history, change orders and review comments |
The records around the files count too. For engineering firms that means calculation packages, design reports and review comments with their responses. For architecture firms it means design review notes, RFI and submittal responses and meeting minutes. For industrial equipment makers it means BOMs, engineering change orders and service, warranty and field failure records. For PCB design firms it means DFM feedback from fabricators and bring-up, test and debug logs.
Why revision history matters more than the final file
A released drawing shows what was built. It does not show why. The reasoning sits in the steps before release: the markup a checker left on revision B, the change order that moved a hole pattern, the fabricator's note that a trace was too close to the board edge, the RFI that forced a detail to be redrawn.
Those steps are what the Paid4Data industry pages describe buyers wanting. Expert review cycles are a record of how a qualified person judged someone else's work. A design, its changes and how it held up in the field make a complete engineering record that is not on the open web.
In practice this means a folder of final PDFs is a weaker archive than the same projects with their native files, revision tables, change orders and review threads still attached. If your PDM or PLM system has kept the release history, say so early.
Who owns a design
You can only license what you have the right to license, so ownership comes first. Under US copyright law, the copyright in a work initially belongs to the person who created it. The main exception is a work made for hire.
The US Copyright Office describes two situations in which a work is made for hire:
- Employee work. A work created by an employee within the scope of their employment. The employer is treated as the author and the copyright owner.
- Certain commissioned work. A work that was specially ordered or commissioned, falls into one of nine categories listed in the statute, and is covered by a written agreement, signed by the parties, that expressly calls it a work made for hire. If any of those conditions is missing, it is not a work made for hire.
Two practical points follow. First, designs drawn by your own employees as part of their jobs start out belonging to the firm. Designs drawn by outside contractors or freelancers do not follow that rule automatically, so those agreements need to be read.
Second, ownership can move by contract. The Copyright Office notes that a transfer of copyright ownership generally must be made in writing and signed by the owner of the rights. If your agreement with a client assigns the deliverables to the client, or limits how you may reuse them, that agreement controls. Confidentiality clauses can restrict sharing even where the firm still holds the copyright.
Architects should know one more detail. The Copyright Office treats an architectural work, meaning the design of a building, and a technical drawing of that building as separate works.
Export controls on technical data
Some design files are regulated because of what they describe, whoever owns them. Two sets of US rules matter here.
ITAR. The International Traffic in Arms Regulations define technical data as information required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles. The definition says this includes information in the form of blueprints, drawings, photographs, plans, instructions or documentation. It does not include general scientific, mathematical or engineering principles commonly taught in schools, information in the public domain as the regulations define it, or basic marketing information about function or purpose.
EAR. The Export Administration Regulations are a separate set of rules. The EAR definition of technology says it may be in any tangible or intangible form and names blueprints, drawings, engineering designs and specifications, and computer-aided design files. The regulations state that all items in the United States and all US-origin items wherever located are subject to the EAR, apart from listed exclusions such as items controlled exclusively under ITAR and published information. Which technology is actually controlled is set out in the Commerce Control List.
Under both sets of rules, an export is not only a shipment abroad. Both definitions also cover releasing or transferring technical data or technology to a foreign person inside the United States.
Whether any of your files fall under these rules depends on the product and the customer. That is a question for your export compliance lead or lawyer, not something this article can answer.
What de-identification does and does not do
Before any buyer sees a dataset, Paid4Data removes names, emails, phone numbers, street addresses, account and invoice numbers, tax IDs and signatures, and replaces people and company names with consistent pseudonyms.
That process deals with identifiers. It does not settle who owns a design or whether an export rule applies. Client-owned designs and work covered by export controls or confidentiality terms can only be included where you have the right to share them, and that is reviewed with you on the scoping call.
What to check before listing files
- Sort projects by who owns the deliverables. Separate your own product designs from work done for clients, and pull the contract terms for the client work.
- Find contractor-made designs. Check whether those agreements assign the work to your firm in writing.
- Flag defense, aerospace and government projects. Mark anything that carried an export control or distribution marking, or that your compliance lead has classified.
- Read confidentiality clauses. Look at NDAs and master service agreements for limits on reuse of client information.
- Note what history survives. Record which systems hold revisions, change orders and review comments, and for which years.
- List exclusions. You approve every system and date range in the Data Schedule and can exclude any client, project or product line.
How to start
You do not upload files to find out whether an archive fits. The data review form asks a few questions. The advanced intake then asks you to describe each system and its data volume, and a 30-minute scoping call under a mutual NDA covers ownership, client contracts and exclusions.
The minimum to qualify is 20 or more employees, three or more years in business and 200 GB or more of data. To see whether your archive is in range, request a free data review.
Sources
Checked on November 16, 2026.
- Circular 30: Works Made for Hire, U.S. Copyright Office
- Circular 1: Copyright Basics, U.S. Copyright Office
- Circular 41: Copyright Registration of Architectural Works, U.S. Copyright Office
- 22 CFR 120.33 -- Technical data., Electronic Code of Federal Regulations (ITAR, U.S. Department of State)
- 22 CFR 120.50 -- Export., Electronic Code of Federal Regulations (ITAR, U.S. Department of State)
- 15 CFR 772.1 -- Definitions of terms as used in the Export Administration Regulations (EAR)., Electronic Code of Federal Regulations (EAR, Bureau of Industry and Security)
- 15 CFR 734.3 -- Items subject to the EAR., Electronic Code of Federal Regulations (EAR, Bureau of Industry and Security)
- 15 CFR 734.13 -- Export., Electronic Code of Federal Regulations (EAR, Bureau of Industry and Security)