Who Owns the Data You Deliver: Technical Data Rights and the Markings That Matter

Published 2026 | TIKC NewsWire

When you deliver technical data or software to the government, you are not just handing over files. You are handing over rights, and who holds them decides whether the government can share your designs with a competitor, whether you keep your edge, and whether you are even allowed to use certain data at all. Technical data rights are among the most valuable and least understood assets in a contract. Get the markings wrong, or misuse data that belongs to someone else, and you can forfeit your intellectual property or hand the government a misuse and false-claims problem.

The rights framework in plain terms

Government contracts allocate rights in technical data and computer software based mostly on who paid to develop it. Data developed exclusively at private expense generally carries limited rights, meaning the government can use it but not freely release it to your competitors. Data developed with government funding generally carries broader, often unlimited, rights for the government. There is also a middle category of specially negotiated and government-purpose rights. The category controls what the government may do with what you deliver, which is why it is worth real attention, not a last-minute checkbox.

Markings are everything

Rights are asserted and protected through markings, the legends you place on data and software to signal the government’s rights. Here is the trap that runs in two directions. If you under-mark, or forget to assert your limited rights, you can lose protection and watch your privately funded designs become shareable. If you over-mark, slapping restrictive legends on data the government actually paid for or is entitled to use freely, you have made a false assertion, and nonconforming or unjustified markings can be challenged, stripped, and in serious cases treated as a misrepresentation. Both errors are expensive, and only careful, honest marking avoids them.

Using data that is not yours

The other half of the risk is inbound. Contractors routinely handle a competitor’s proprietary data, a former employer’s drawings, or third-party software, and using any of it without the right license is where data rights blur into trade secret theft. A new engineer who arrives with a prior employer’s design files can import a lawsuit, and your delivery of that data to the government can spread the problem. This is also why protecting controlled information from your own people, the heart of an insider-threat program, sits right next to data rights as a discipline.

Data that cannot leave

Some technical data is not just proprietary, it is controlled for national security, and then data rights and export controls collide. Defense technical data can carry both a rights category and an export restriction, so who may receive it is limited by law as well as by license. Sending a controlled drawing to the wrong recipient, even internally to a foreign national employee, can be an export violation on top of any data-rights issue. The safe habit is to know, for every significant piece of data, both who owns the rights and whether it is export controlled, before it moves.

What to do now

• Track development funding. Know whether each deliverable was developed at private expense, with government funds, or mixed, because that sets the rights.
• Mark deliberately. Apply the correct rights legends, never over-mark data the government paid for, and never forget to assert genuine limited rights.
• Vet inbound data. Confirm you are licensed for any third-party or competitor data before using or delivering it.
• Screen new hires’ materials. Keep a prior employer’s proprietary files out of your work and your deliverables.
• Flag export-controlled data. Check whether technical data is export controlled before sharing it, including internally.

Your data rights are the fence around what makes you competitive, and the government’s rights are the fence around what taxpayers funded. Respect both, mark honestly, and never deliver data you do not have the right to use, and your intellectual property stays yours while your contract stays clean. Brick by brick.

FAQ

What decides who holds rights in technical data?

Mostly who paid to develop it. Privately funded data generally carries limited rights, government-funded data generally carries broader or unlimited government rights, with negotiated and government-purpose categories in between.

Why do markings matter so much?

Markings assert and protect rights. Under-marking can forfeit protection for your private data, while over-marking data the government is entitled to use is a false assertion that can be challenged and stripped.

What is the risk of using third-party data?

Using a competitor’s, former employer’s, or licensor’s data without the right license can be trade secret misappropriation, and delivering it to the government can spread the liability.

How do export controls fit in?

Defense technical data can be both rights-restricted and export controlled, so who may receive it is limited by law. Check export status before sharing controlled data, even with a foreign national inside your company.

Sources

Defense Federal Acquisition Regulation Supplement. (2026). Subpart 227.71 and 227.72, Rights in Technical Data and Computer Software.

Federal Acquisition Regulation. (2026). Part 27, Patents, Data, and Copyrights.

This article is general information, not legal advice.