Data ownership clause examples for service contracts

What a data ownership clause does in a service contract#

A data ownership clause in a service contract allocates rights in three kinds of information: data the client provides, records the provider creates while doing the work, and deliverables made for the client. Without one, ownership falls back on general law and the rest of the contract, which often leaves the provider's operating records undefined.

Copyright rules show why the clause matters. Under US work made for hire rules, a commissioned work belongs to the commissioning party only if it falls into specific statutory categories and the parties agree in a signed writing. Many consulting and engineering deliverables fall outside those categories, so client ownership usually depends on an express assignment.

Some industries start from provider ownership. Standard owner-engineer agreements such as the EJCDC E-500 treat the engineer's documents as instruments of service, with the engineer keeping ownership and reuse rights and the owner receiving a limited license to use them for the project.

The definitions that decide the outcome#

The definitions in a service provider data rights clause do most of the work. The illustrative clauses below all assume these terms, and each is a drafting example for discussion with counsel, not recommended language.

Provider-favorable data ownership clause example#

A provider-favorable data ownership provision keeps everything except the client's own inputs with the provider and gives the provider wide reuse rights.

Illustrative clause: Client retains ownership of Client Data. Provider owns all Provider Records and all methods, know-how, tools and templates used or developed in performing the Services, and retains ownership of Deliverables subject to a non-exclusive license to Client to use them for the Project. Client grants Provider a perpetual license to use Client Data in de-identified or aggregated form for any purpose, including developing, training and licensing analytical and artificial intelligence tools, provided no Client or individual is identified.

Clients who read closely often push back on the perpetual reuse license and on retained deliverables, so this form tends to survive only in standard terms that clients accept without negotiation.

Balanced data ownership clause example#

A balanced clause gives each side what it naturally creates and allows narrow, documented reuse.

Illustrative clause: Client owns Client Data and, upon full payment, the Deliverables, excluding Provider's pre-existing materials and general know-how, which Provider retains and licenses to Client as needed to use the Deliverables. Provider owns Provider Records. Provider may use Client Data only to perform the Services, except that Provider may create and use Aggregated Data that does not identify Client, its personnel or its customers, including to improve Provider's services and to license to third parties under written confidentiality and use restrictions, provided Client's Confidential Information is not disclosed.

The balanced form is often the easiest to sign and the clearest to rely on later, because it names the records the provider keeps and spells out the reuse right in plain terms.

Client-favorable data ownership clause example#

A client-favorable client data clause treats everything that touches the engagement as the client's and bars reuse.

Illustrative clause: All Client Data, Deliverables and other information created, collected or derived by Provider in performing the Services, including Provider Records to the extent they contain or are derived from Client Data, are owned by Client. Provider shall not use such information for any purpose other than performing the Services, and shall not use it to develop, train or improve any artificial intelligence or machine learning model, whether or not de-identified or aggregated. On termination Provider shall return or destroy all such information.

Under this form, a provider's schedules and internal reviews for the engagement may be off-limits for licensing, which is why the derived from language deserves careful review before signing.

How the three positions compare#

The comparison below shows where the positions differ. Most negotiations end somewhere between the balanced and client-favorable columns, so the drafting checklist that follows focuses on the points that survive negotiation.

• 1Name the provider's record families instead of relying on a general reference to work product.
• 2Define de-identified and aggregated by a standard, not just a label.
• 3State in those words whether AI training and third-party licensing are allowed.
• 4Say whether reuse rights survive termination and how they interact with return-or-destroy duties.
• 5Align the clause with the confidentiality section and any data processing agreement.
• 6Keep dated copies of every signed form, because old contracts govern old records.

Illustrative: an engineering firm sorts projects by contract form#

Illustrative: a fictional civil engineering firm wants to license years of internal design review notes, RFI logs and project schedules kept in Deltek and Bluebeam. Its projects ran under its own standard agreement, a professional association form and a stack of client-drafted contracts.

The firm sorts projects by contract form. Projects under its own agreement and the association form, both of which keep instruments of service with the engineer, move into scope with client names and project addresses removed. Projects under client paper with derived-from ownership language are excluded. For new work, the firm adopts a balanced clause that names Provider Records and states whether aggregated data may be licensed.

How SourceX uses data ownership clauses#

SourceX reads data ownership clauses during the Rights step of the SourceX five-step transaction, sorting records by the contract form that governed them. The initial fit check asks only which forms exist and which years they cover.

The forms relied on and the projects excluded are recorded in the SourceX Evidence Packet under licensing rights, so the supplier's approval rests on a written map of its contracts rather than on assumptions about ownership.