When a contractor hands over technical data or software under a federal contract, the deliverable itself matters less than the rights the government receives to use it afterward. The Defense Federal Acquisition Regulation Supplement spells out those rights at DFARS 227.7103-5, which sets the categories DoD uses to sort technical data by how it was funded and how freely the government — or the public — can use it later. Civilian agencies run a parallel but simpler system under the FAR. Getting the category wrong, or asserting it too late, can cost a contractor its proprietary protections or leave the government without rights it actually needs.
Background
For civilian agencies, FAR clause 52.227-14 sorts data into three buckets. Unlimited Rights let the government "use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose" — the broadest grant available, typically tied to data developed entirely at government expense. Limited Rights protect privately developed proprietary data, which the government may hold and use internally but can disclose outside the agency only under a Limited Rights Notice. Restricted Rights apply specifically to privately developed computer software: the government can run it on its own machines and make backup copies but cannot distribute it publicly or use it for other purposes.
DoD's rules track that same three-tier structure but add a fourth: Government Purpose Rights, defined at DFARS 227.7103-5 for technical data developed with a mix of government and private funding. The overall policy driving all of this sits at DFARS 227.7103-1, which instructs DoD to "acquire only the technical data, and the rights in that data, necessary to satisfy agency needs." The same section bars contracting officers from pressuring contractors to give up rights in privately developed items outside specific carve-outs, and from steering procurements away from privately developed solutions purely to avoid data-rights friction.
The category follows the funding source, not who holds the contract. A component a contractor built entirely with private funds before ever bidding on government work remains eligible for the strongest available protection even after it is embedded in a larger government deliverable, provided the contractor properly identifies and marks it under the applicable clause.
Key Details
Government Purpose Rights sit between Unlimited and Limited. Under the clause at 252.227-7013, mixed-funding technical data carries a "nominal five-year period" of Government Purpose Rights, running from execution of the contract or the relevant option. During that window, the government can use the data for any government purpose — including sharing it with other contractors doing government work — but cannot release it commercially. Once the five years run out, the data automatically converts to Unlimited Rights unless the parties agreed otherwise.
That five-year clock is not fixed in stone. DFARS 227.7103-5 explicitly allows either party to request a change to the Government Purpose Rights period "at any time prior to delivery of the technical data without consideration from either party" — meaning a contractor or contracting officer can renegotiate the period, longer or shorter, without either side having to pay for the change, as long as it happens before delivery. Miss that window and the negotiated period is locked in.
Limited Rights data carries its own release restrictions. DFARS 227.7103-5 states that Limited Rights technical data may not be used, released, or disclosed outside the government without the contractor's permission, subject to a short list of exceptions: emergency repair or overhaul situations, disclosure to covered government support contractors operating under a nondisclosure agreement, and certain foreign-government disclosures specified in the regulation. Outside those carve-outs, the default is that the data stays inside the government.
Timing matters as much as category. DFARS 227.7103-1 requires solicitations and contracts to give offerors a mechanism to identify technical data they intend to deliver with restricted rights markings before award. A contractor that waits until after award to start asserting Limited Rights or Government Purpose Rights markings on data risks losing the argument entirely — the regulation is built around pre-award identification, not after-the-fact assertions.
Restricted Rights for computer software works differently from Limited Rights or Government Purpose Rights. Because it attaches to privately developed software rather than technical data, the government's default use is narrower still: internal use on government computers and backup copying, with no outside distribution absent a separate license. Software developers negotiating a DoD contract should confirm which category — technical data or computer software — actually applies before assuming the same rules carry across.
What It Means for Contractors
The data-rights category attached to a deliverable is a business decision, not paperwork, and it needs to be made before the contract is signed. A contractor developing a component with its own R&D funds and rolling it into a government deliverable should identify that data as Limited Rights (or negotiate Government Purpose Rights if government funding was involved) in the proposal or before delivery — not after a program office has already started distributing the data to other contractors under an assumption of Unlimited Rights.
Because the Government Purpose Rights period is explicitly negotiable "without consideration from either party" prior to delivery, contractors with long-lived technology should treat the five-year default as a starting point, not a ceiling. A five-year window that expires mid-program converts proprietary technical data to Unlimited Rights automatically — including the right for the government to hand it to a competitor for follow-on production. Contractors who want a longer runway need to negotiate that explicitly, and early, since the deadline for changing the period is delivery of the data itself, not the end of the contract.
On the Limited Rights side, contractors should know exactly who can see their proprietary data and why. The exceptions — emergency repair, NDA-bound support contractors, specified foreign disclosures — are narrow. If a program office wants to share Limited Rights data with a support contractor, DFARS 227.7103-5 requires that support contractor to be under a nondisclosure agreement; a contractor that spots data moving outside those channels has grounds to raise it with the contracting officer before it becomes a bigger dispute.
Finally, DFARS 227.7103-1's policy language cuts both ways. It commits DoD to seeking only the data rights it actually needs, and it prohibits contracting officers from discouraging the use of privately developed items just to sidestep data-rights complexity — language contractors can point to if a solicitation seems to be reaching for Unlimited Rights on data that was clearly developed at private expense.
