How to regulate intellectual property (IP) rights in body leases?

The Importance of Intellectual Property Rights in IT

Intellectual Property (IP) rights play a key role in the IT industry. They primarily include copyrights on software source code, documentation, user interfaces, and potentially patents on technological inventions, database rights, or know-how. Proper regulation of the ownership of these rights is fundamental to the ability to freely use, modify, distribute, and commercialize the software being developed.

In modern software development, where teams frequently work in distributed settings and external specialists are regularly engaged, the question of IP rights is more complex than ever. The increasing use of open-source components, integration of third-party libraries, and adoption of AI-powered development tools add further layers of complexity that must be addressed contractually.

IP Risk in Body Leasing

In the body leasing model, IT specialists (contractors) create software or other works for a client, but formally they are often not the client’s employees. This raises the question of who owns the copyright to the results of their work. According to the general principles of copyright law, the creator (i.e., the specialist) holds the original copyright to the created work.

If the issue of transferring these rights to the client is not clearly and precisely regulated in the contract, the client may face serious problems with the legal use of the software created for them in the future. The main risks include:

• Usage restrictions: Without explicit rights transfer, the client may not freely use, modify, or redistribute the software
• Contractor dependency: The client could be forced to engage the original developer for every change or enhancement
• Commercialization conflicts: When multiple parties claim rights to the same software, it can obstruct marketing and sales efforts
• Licensing limitations: Without clear IP arrangements, the client cannot license the software to third parties
• Due diligence issues: Unresolved IP can be a significant obstacle during company valuations or investor rounds

Varying Legal Frameworks Across Jurisdictions

IP regulations vary considerably across different legal systems, which is particularly relevant in international body leasing arrangements:

Jurisdiction	Basic Principle	Key Considerations
United States	Work for hire doctrine	IP can belong to the hiring party if specific conditions are met
United Kingdom	Flexible approach	Under employment, IP typically belongs to employer
Germany	Rights remain with creator	Only usage rights can be transferred; moral rights are inalienable
Poland	Rights remain with creator	Under employment contracts, economic rights transfer to employer (Art. 12 Copyright Act)
France	Rights remain with creator	Strict rules for transfer; each field of exploitation must be listed separately

These differences make it essential to clearly define the applicable legal framework in the body leasing contract and adapt IP clauses accordingly.

The Need to Regulate in the Contract

To avoid any doubts and safeguard the interests of the client, the issue of transfer of IP rights must be clearly and specifically regulated in the body leasing contract or in a separate IP agreement. The absence of such provisions or their imprecise formulation poses serious legal and business risks for the client.

A comprehensive IP agreement should be negotiated and signed before the project begins. Retroactive negotiations over IP rights when the software is already developed shift the bargaining power in favor of the contractor and can lead to suboptimal outcomes for the client.

Key Elements of IP Contractual Provisions

IP contractual provisions should include, at a minimum, the following elements:

Confirmation of Transfer of Rights

A clear statement that all economic copyrights in works (code, documentation, designs, databases, etc.) produced by the contractor as part of the contract pass to the client. This statement should precisely define what constitutes a “work,” including intermediate results, drafts, and preparatory materials.

Moment of Transfer of Rights

Precise definition of the moment when the transfer of rights takes place. Common options include:

• Upon payment of remuneration for a given stage of work
• Upon acceptance of the work by the client
• Automatically upon creation of the work (preferred from the client’s perspective)
• On a contractually specified date

Fields of Exploitation

A detailed listing of the fields of exploitation in which the customer acquires copyright. The broader the fields of exploitation, the greater the customer’s freedom to use the software. Typical fields include:

• Reproduction and copying
• Modification, adaptation, and derivative works
• Distribution and making available to the public
• Sublicensing to third parties
• Translation and porting to other platforms
• Use for development of derived products

Territory and Duration

Determination of the territory in which the transfer of rights is valid (usually worldwide) and the duration (usually indefinite). In the digital world, where software is distributed globally via the internet, a worldwide license is typically indispensable.

Remuneration for the Transfer of Rights

Indication that the remuneration for the transfer of copyrights is included in the remuneration for the provision of services, or specification of a separate remuneration. Including the IP transfer fee within the service remuneration is the more common and practical approach.

Derivative Rights

Regulation of rights to modify the work and exercise dependent rights. This is especially important when the software is intended for ongoing development and enhancement.

Supplier Commitment

A provision that obligates the body leasing provider to ensure that it has appropriate agreements with its specialists (contractors) to guarantee that they effectively transfer copyright first to the provider and then to the end customer.

Special Aspects of IP Regulation

Open-Source Compliance

When contractors integrate open-source components into the developed software, IP provisions must also govern compliance with the respective open-source licenses. Certain licenses such as the GPL can trigger copyleft effects that place the entire software under the same license. The contract should:

• Require approval for the use of open-source components
• Define a list of acceptable and unacceptable licenses
• Establish responsibilities for open-source compliance
• Include provisions for license violation scenarios

Pre-Existing Intellectual Property

The contract should clearly regulate how to handle pre-existing intellectual property that the contractor brings into the project. This includes reusable libraries, frameworks, or methodologies the contractor has developed. Typically, the contractor retains rights to their pre-existing works and grants the client a license for use within the project context.

AI-Generated Code

With the increasing adoption of AI coding assistants such as GitHub Copilot, ChatGPT, and similar tools, IP provisions must also address the question of who owns rights to AI-generated code and how the use of such tools is regulated within the project context. The legal status of AI-generated works remains unsettled in many jurisdictions, making explicit contractual provisions even more important.

B2B Cooperation and IP

Special attention should be paid to situations where the contractor works with the supplier on the basis of a B2B contract. In such cases, it is crucial that the B2B contract between the supplier and the specialist contains appropriate provisions for the transfer of economic copyrights to the supplier, which will enable them to further transfer these rights to the customer.

The contractual chain must be seamless:

1. Specialist to supplier: Clear transfer of all rights arising from the project
2. Supplier to customer: Passing of acquired rights to the end customer
3. Warranties: The supplier warrants that it is authorized to transfer the rights

Any gap in this chain can result in the customer not receiving effective rights to the software.

IP Protection and Enforcement

Beyond the transfer of rights, the contract should also contain provisions for the protection of confidential information and trade secrets:

• Non-Disclosure Agreement (NDA): Protection of trade secrets, algorithms, and proprietary methods
• Non-compete clauses: Limiting the contractor’s ability to develop similar solutions for competitors
• Warranties: Assurance that the developed software does not infringe the rights of third parties
• Indemnification: Clear responsibilities and financial coverage in case of IP infringement claims
• Audit rights: The client’s right to verify compliance with IP provisions

IP Management with ARDURA Consulting

ARDURA Consulting, as an experienced body leasing provider, places great emphasis on transparent and comprehensive regulation of IP rights. ARDURA Consulting’s contracts include detailed IP clauses as standard, protecting the client’s interests and ensuring clear transfer of rights. Collaboration with experienced legal advisors ensures that IP provisions comply with the relevant national legal frameworks and are internationally enforceable.

The company’s approach involves proactive IP risk assessment at the beginning of each engagement, ensuring that all potential IP issues are identified and addressed before development begins. This preventive approach saves clients from costly disputes and legal uncertainties down the line.

Summary

Precise and comprehensive regulation of intellectual property rights in a body leasing contract is absolutely essential for the customer’s legal and business security. It provides them with the full right to use and develop the software created on their order by external specialists. The IP agreement should cover all aspects, from the transfer of copyrights through open-source compliance to the protection of confidential information. Consideration of different legal frameworks in international arrangements and a seamless contractual chain from the specialist through the provider to the customer are of decisive importance. Neglecting this aspect can lead to serious legal and business complications that can significantly diminish the value of the developed software.