Answer · Manufacturing
Can you put export-controlled drawings into an AI tool?
Almost never on a hosted service. The exemption letting controlled data sit in the cloud needs encryption the tool cannot work through.
Not on an ordinary hosted service. Releasing controlled technical data to a foreign person is an export, and the exemption permitting cloud storage requires end-to-end encryption — which a tool that must read the file cannot have.
The controlling idea is the deemed export, and it is older than any of this. Under the arms regulations, releasing controlled technical data to a foreign person is an export to that person's country even if the data never leaves the United States and the person is your own employee or a vendor's system administrator. Nothing has to cross a border and nothing has to be downloaded. The question is who was in a position to see it, which is why the analysis lands on infrastructure rather than on intent.
The provision that made commercial cloud usable is a carve-out for encrypted data, at §120.54 of the arms regulations. Unclassified technical data that is secured end to end with validated cryptography, encrypted before it leaves the sender's security boundary and still encrypted when it arrives at the recipient's, is not treated as an export — provided the means of decryption is not given to any third party and no foreign person holds the keys. That is the basis on which controlled drawings sit in commercial storage today.
Every clause in that carve-out is incompatible with a hosted model doing anything useful. A tool that reads a drawing, extracts a tolerance, answers a question about a specification or generates a quote has to hold the plaintext. Which means the provider is decrypting inside their boundary, holds the means to do so, and has staff who are in a position to access it. The exemption is not narrowly missed here; it is missed on its central condition, and no configuration of an ordinary service closes the gap.
The scoping question is more useful than the prohibition, because most of a manufacturer's document set is not controlled and treating it all as though it were is a real cost. Technical data means the information required for design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of a controlled article — so a drawing, a specification, a process sheet, an inspection method. It does not mean the purchase order, the delivery schedule, the invoice, the general capability statement or the published catalogue. A shop that knows which of its documents are in the controlled set can use these tools freely on everything else, and a shop that has never drawn the line ends up either exposed or paralysed.
What remains available for controlled material is a model that runs where the data already is, under the manufacturer's own control, with access limited to the same people already authorised to see the drawings. That is a real option and it is what defence-adjacent shops are actually doing. It is also a different procurement conversation from the one that starts with a subscription, and the honest framing is that the controlled portion of the work has a higher floor of cost rather than a prohibition.
Two operational details cause most incidents and neither involves a decision anyone made. The first is a drawing arriving by email and being pasted into a general tool by somebody who did not know the part was controlled — which is a marking and training problem, not a technology one. The second is the supplier chain: a quote package sent to a subcontractor who then does exactly the same thing. A control that stops at the shop's own perimeter has covered the smaller half of the exposure.
The rule that made cloud storage workable for controlled data is the exact rule an AI tool cannot satisfy, because processing requires the plaintext the exemption forbids anyone else from holding.
Siddharth Sharma, Context Theory
Related questions
Does it help if the vendor is a United States company?
Only partly, and less than people assume. The regulation is about which persons can access the data, not about where the company is incorporated, so a domestic provider staffed in part by foreign persons — including foreign nationals working lawfully in the United States — presents the same question. What matters is whether the provider can state, and contract to, who is able to access the plaintext, and that is a specific commitment rather than a jurisdiction.
What about data controlled under the export administration regulations instead?
The general shape is similar and the thresholds are different, which makes it worse to guess. Dual-use items have their own classification and their own licence exceptions, and some technology moves freely to some destinations. The practical answer for a shop is the same either way: establish the classification for each controlled article before deciding what may be processed where, because the classification is the fact everything else depends on.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Realistic monthly lead-gen software spend | $1,500–$5,000 | Category-wide |
| Share of the buying journey completed before contacting a vendor | 60% | Category-wide |
2026 real estate operating cost survey · plus $1,000–$8,000 variable · verified
2026 B2B buyer surveys · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Regulation | Releasing controlled technical data to a foreign person is treated as an export to that person's country even where the data never leaves the United States and the recipient is an employee or a vendor's administrator, which places the analysis on who can access the material rather than on where it travels. | The definition of export covering release of technical data to a foreign person in the International Traffic in Arms Regulations. |
| Constraint | The exemption permitting controlled technical data to be stored and transmitted through commercial infrastructure requires validated end-to-end encryption with the means of decryption withheld from any third party, conditions a hosted model that must read the file cannot meet. | §120.54 of the International Traffic in Arms Regulations, read against the vendor's description of where decryption occurs. |
| Workflow | Controlled technical data covers the information required to design, produce, assemble, operate, repair, test or modify a controlled article, and excludes commercial paperwork such as purchase orders, schedules, invoices and published capability material. | Classifying a sample of the shop's document types against the technical data definition, and recording which fall inside it. |
| Software | The two most common incidents involve no decision at all: an unmarked drawing pasted into a general tool by somebody unaware the part was controlled, and a quote package sent to a subcontractor who does the same thing outside the shop's perimeter. | Checking whether controlled drawings carry markings at the point of receipt, and what the subcontractor terms say about processing them. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one