Technical Data Rights in Government Contracts
When you develop technology, software, or technical data under a government contract, who owns it? The answer depends on who paid for the development. Understanding data rights is critical for protecting your intellectual property while meeting your contractual obligations.
DFARS 252.227-7013 (technical data) and DFARS 252.227-7014 (computer software) establish the framework for data rights in DoD contracts. Civilian agencies follow similar principles under FAR 52.227-14. Getting data rights wrong can mean losing control of your most valuable IP — or facing breach of contract claims.
100M+ government records · 300+ gov/news sources · Updated hourly
Types of Data Rights
Unlimited Rights
Unlimited rights give the government the broadest possible rights to technical data and software. The government may use, modify, reproduce, release, perform, display, or disclose the data in any manner and for any purpose — including releasing it to the public or providing it to competitors.
When they apply: Unlimited rights attach to data developed exclusively with government funds, data in which the government has been granted unlimited rights through a negotiated license, form, fit, and function data, data necessary for installation, operation, maintenance, and training (IOMT), and data that is publicly available or has been released without restriction.
Impact: Once the government has unlimited rights, you have no control over how the data is used. The government can share it with your competitors for reprocurement or include it in a solicitation package. This is why documenting private investment is essential.
Government Purpose Rights
Government Purpose Rights (GPR) are a middle ground between unlimited and limited rights. The government can use the data for any government purpose, including competitive procurement, but cannot release it for commercial purposes. GPR data can be shared with other government contractors for government work.
When they apply: GPR applies to data developed with mixed funding — both government and private investment. This is one of the most common categories because many developments involve some level of government funding combined with the contractor's own IR&D, B&P, or other private investment.
Duration: GPR is not permanent. After 5 years from the date of delivery, government purpose rights automatically convert to unlimited rights unless the parties negotiate a different period. This 5-year clock is important for strategic planning — if you need longer protection, negotiate before award.
Limited Rights (Technical Data) / Restricted Rights (Software)
Limited rights provide the strongest protection for contractor IP. When technical data is developed exclusively at private expense, the government receives only limited rights — it can use the data within the government but cannot release it to third parties (including other contractors) without the contractor's permission.
For computer software: The equivalent is “restricted rights” under DFARS 252.227-7014. The government can use the software on government computers but cannot modify, reproduce, release, or disclose it outside the government.
Proving private expense: The contractor bears the burden of proving that the data was developed exclusively at private expense. This requires maintaining clear records of funding sources, development timelines, and cost allocation. If you cannot prove private funding, the government may assert unlimited rights.
SBIR Data Rights
Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs provide enhanced data rights protections. Under the SBIR/STTR data rights framework, data developed under SBIR/STTR contracts receives protection for 20 years from the date of contract completion — significantly longer than the 5-year GPR period.
Protection period: During the 20-year period, the government may not release or disclose SBIR data outside the government without the contractor's permission. After 20 years, the rights convert to unlimited. This extended protection is designed to allow small businesses to commercialize their innovations.
Limitations: The government retains unlimited rights to SBIR data for government purposes during the protection period. The restriction is on release outside the government — not on internal government use.
Key DFARS Clauses
The primary clause governing technical data rights in DoD contracts. Establishes the unlimited, government purpose, and limited rights categories based on funding source. Requires contractors to mark deliverable data with appropriate legends and to assert restrictions prior to delivery. Includes provisions for the government to challenge restrictive markings.
The companion clause for computer software and documentation. Follows the same funding-based framework but uses “restricted rights” instead of “limited rights” for privately funded software. Addresses source code, object code, and documentation separately. Important: this clause does not apply to commercial software, which is governed by DFARS 252.227-7015.
Requires contractors to identify all technical data and software for which they intend to assert restrictions. The assertion must be submitted to the Contracting Officer prior to delivery, ideally as part of the proposal. Failure to assert restrictions can result in the government treating the data as having unlimited rights.
Gives the government the right to challenge contractor markings and restrictions within 6 years (3 years for commercial data). The contractor must justify its markings within 60 days. If the contractor fails to respond or provides an inadequate justification, the government may remove the restrictive markings.
Marking Requirements
Proper marking of technical data and software is your first line of defense in protecting data rights. DFARS requires specific legends on all deliverable data that is subject to restrictions. Unmarked data may be treated as having unlimited rights.
Must include the contract number, contractor name, and a statement that use, duplication, or disclosure is subject to the restrictions in DFARS 252.227-7013. Apply to all technical data developed exclusively at private expense.
Must include the contract number, contractor name, the expiration date (5 years from delivery), and a statement that the government may use the data for government purposes only. Include the specific date when rights convert to unlimited.
Must include the SBIR contract number, SBIR protection period expiration date (20 years from completion), and a statement restricting release outside the government during the protection period.
Correction of omitted markings: If you inadvertently deliver data without markings, you can request the Contracting Officer to add or correct markings within 6 years of delivery. Act quickly — the government may have already released unmarked data in reliance on the absence of restrictions.
Asserting Restrictions and Protecting Pre-Existing IP
The best time to protect your data rights is before contract award. Once you have signed a contract with unfavorable data rights provisions, your options are limited. Here are the key steps to protect your IP.
Assert Restrictions in Your Proposal
Use DFARS 252.227-7017 to identify all technical data and software for which you intend to assert restrictions. List each item, the basis for restriction (e.g., developed at private expense), the asserted rights category, and the name of the person asserting restrictions. Submit this with your proposal.
Document Private Investment
Maintain detailed records showing that specific technologies, software, or data were developed using private funds. This includes IR&D records, B&P expenditures, internal development logs, and cost accounting records. The burden of proof is on the contractor.
Segregate Pre-Existing IP
Clearly identify pre-existing intellectual property — technology developed before the contract — in your proposal and contract. Pre-existing IP developed at private expense retains limited/restricted rights regardless of how the contract work is funded. Use configuration management to track which components are pre-existing vs. newly developed under the contract.
License vs. Ownership
The government receives a license to use technical data — it does not acquire ownership of the underlying intellectual property. You retain ownership of your inventions, copyrights, and trade secrets. The data rights clauses define the scope of the government's license, not a transfer of ownership. This distinction is important for commercialization and licensing to other customers.
Related Guides
Frequently Asked Questions
What are the different categories of technical data rights?
There are four main categories: (1) Unlimited rights — the government can use, modify, reproduce, release, perform, display, or disclose the data in any manner and for any purpose without restriction. (2) Government Purpose Rights — the government can use the data for government purposes only (not commercial), including competitive procurement, but cannot release it to the public. These rights convert to unlimited after 5 years. (3) Limited Rights — apply to technical data developed exclusively at private expense; the government can use the data internally but cannot release it outside the government without the contractor's permission. (4) SBIR Data Rights — special protections for small businesses under SBIR/STTR programs, providing 20 years of protection before converting to unlimited rights.
What determines which data rights category applies?
The funding source determines the data rights category. Data developed exclusively with government funds receives unlimited rights. Data developed with mixed funding (government and private) receives government purpose rights. Data developed exclusively at private expense receives limited rights (for technical data) or restricted rights (for computer software). The key is documenting the funding source for each data item — if you cannot prove private funding, the government may assert unlimited rights by default.
What happens if I fail to mark technical data with the correct legend?
Failure to properly mark technical data with restrictive legends can result in the government treating the data as having unlimited rights. DFARS 252.227-7013 and 252.227-7014 require contractors to mark all deliverable data with the appropriate restrictive legend. However, the regulations provide a remedy: if a contractor inadvertently fails to mark data, it can request that the Contracting Officer correct the markings within 6 years of delivery. The government must honor a timely correction request unless it has already released the data based on the lack of markings.
Can the government challenge restrictive markings on technical data?
Yes. Under DFARS 252.227-7019 (Validation of Asserted Restrictions on Technical Data), the government has the right to challenge restrictive markings within 6 years of delivery (3 years for markings on commercially available data). The contractor must justify its restrictive markings within 60 days of a challenge. If the contractor cannot justify the markings, the government can remove or replace them. The contractor can appeal an adverse decision to the appropriate Board of Contract Appeals or the Court of Federal Claims.
Research Contract Data Rights with Bureauify
Review historical contract clauses, identify data rights patterns by agency, and prepare stronger IP protection strategies with comprehensive contract intelligence.