Contents:

Free course: “Quick start in Python"
Find out more
Mikhail Stetsenko
Associated partner of Legit. Legal consultant with more than 15 years of experience in the field of law. We offer professional legal services, including consultations and support in complex legal matters. Our experience allows us to effectively resolve client issues, ensuring a high level of satisfaction. Contact us for qualified legal assistance.
Specializes in intellectual property, IP and IT law, commercial and antitrust dispute resolution, and the legal design of processes and documents. Experts in these areas provide effective legal support and protection of clients' rights, offering innovative solutions to complex legal issues.
The issue of ownership of the results of developers' work remains relevant in the professional community. Many professionals wonder whether employers or clients truly have full rights to all the products they create. This aspect is important and requires careful analysis, as it affects not only the financial but also the legal relations between the parties. The legal framework in this area may vary depending on the country and type of contract, so developers should carefully review the terms of agreements to protect their interests and intellectual property rights.
- The first piece of news is good: of course not! Hallelujah, the civil and labor codes in Russia are still in effect, and developers haven't become slaves to IT corporations!
- The second piece of news: the employer still owns the rights to the developments you create for them. And this news is also good, I think.
The company most likely hired you not because of sympathy, but because of your skills, which allow you to create valuable solutions. Frankly, the organization doesn't focus on paying you for your time, but on the final result of your work. If you are a developer, then the main result of your work will be the written code.
The company has a clear interest in acquiring exclusive rights to all the code you write. This right is protected by current legislation, which guarantees the company full control over the software you develop.
In Russia, code, both object and source, is recognized as copyrighted material related to programs for electronic computers. Furthermore, even if you develop or manage a database, it can also be protected as intellectual property. A key aspect in this context is determining who owns the exclusive rights to the created materials. Proper understanding and formalization of copyright for software and databases are essential for protecting your interests and preventing potential legal disputes.
Broadly speaking, there are two main scenarios for interacting with a company during the development process. The first scenario involves active collaboration, where both parties work closely together, exchange ideas, and make decisions jointly. This approach allows for optimal results, as the client can make changes and adjustments at every stage of development. The second scenario involves more remote interaction, where the company carries out work based on previously agreed-upon requirements and specifications. In this case, it's important to carefully draft the terms of reference to avoid misunderstandings and errors later. Both scenarios have their pros and cons, and choosing the appropriate one depends on the specific goals and objectives of the project.
- You're an employee—you have an employment contract;
- You're a contractor—a freelancer, self-employed individual, or sole proprietor.
There are two scenarios, each offering unique approaches to legal regulation. These scenarios differ in their principles, methods, and consequences, making them important to understand in the context of legal practice. Legal regulation plays a key role in ensuring justice and order in society, and each of the presented scenarios has its own characteristics that must be taken into account for the effective application of legal norms.
Copyright of Code for Employees
According to Article 1295 of the Civil Code of the Russian Federation, there is a general rule that exclusive property rights to the results of intellectual activity created by an employee in the course of performing work duties belong to the employer. This rule can be modified by contract, but in practice, situations where the parties deviate from this principle are rare. It is important to keep in mind that employers and employees can discuss and record the terms and conditions regarding intellectual property rights in the employment contract in advance, which helps avoid misunderstandings and protect the interests of both parties.
However, there are important nuances that require careful consideration.
The developer always retains the copyright's non-property rights, including the right to be recognized as the author. These rights are inalienable and protect the creator's identity, guaranteeing the ability to claim authorship.
The employer is obligated, within a specified period of time, which is three years for software, to either begin using the results of intellectual activity (RIA), transfer the exclusive right to these results to another person, or notify the author of the intention to keep the RIA secret. If the employer fails to comply with these requirements within the specified period, the exclusive rights automatically revert to the employee. In this case, the employer retains the right to use the RIA under a simple (non-exclusive) license, which requires payment and agreement of terms of use with the employee, or determination of the terms through litigation. Therefore, it's important to discuss all aspects of RIA use in advance to avoid misunderstandings and protect your interests.
Companies must be able to control what their employees create and when to protect their interests in a timely manner. Effective management of content development and creation processes allows organizations to avoid legal risks and ensure compliance with corporate standards. This also contributes to increased productivity and improved quality of the final product. It's important to establish clear rules and procedures so that employees understand their responsibilities and work restrictions. In this way, companies can ensure the protection of their rights and interests, minimizing potential conflicts and problems.
It's important to notify the employer of the progress of work and adhere to established deadlines. It's often tempting to hide development results from the company, but this is not the best approach. Transparency and openness in work help build trust and improve team effectiveness. Avoid bad habits such as concealing information, as this can negatively impact the overall atmosphere and results of the project.
Even if the exclusive rights to a work made for hire have been transferred to the employer and the employee begins to use it, the employee retains the right to receive royalties. This right ensures that the employee will be rewarded for their creative work, even if the rights to use the work belong to the employer. Therefore, it is important to consider not only the transfer of rights but also fair compensation for authors, which helps maintain employee motivation and creativity.
Good news for developers: royalties are not part of your salary. They must be negotiated and paid separately. This is because the agreement on royalties is a civil law agreement, not an employment agreement. Thus, developers can expect additional compensation for their intellectual achievements, which provides them with greater opportunities for financial growth.
Companies often use payments to incentivize programmers to document their developments, accurately track their time, and promptly inform their employer. As a result, the employee receives the compensation they deserve, and the company ensures proper accounting of intellectual property and associated costs. This approach promotes greater efficiency and improves interaction between employees and management, which ultimately leads to increased overall productivity and innovation in the company.
The employee has the right to demand payment of compensation through the courts in the event of non-payment. In Russia, cases of recovery of significant sums are not so common, but there are precedents. For example, in the ruling of the Supreme Court of the Russian Federation dated June 5, 2020, No. 78-KG20-1 in the case of A. Kukin v. Scientific and Technical Center of Thin-Film Technologies in Energy, the issue of remuneration for service patents was considered. The court in this case developed universal approaches that can be applied in similar situations.
It's important to understand that not every program developed by an employee is a work for hire. Even if you're a full-time developer, say, at a senior level, and your primary task is programming, the situation may not be so straightforward. If you created code for yourself during work hours, using your employer's computer, and posted it to the corporate repository, this doesn't guarantee that your company owns the exclusive rights to that code. As the classic quote goes, "Was there a boy?" This is reminiscent of the plot of the TV series "Silicon Valley," where the main character faced the threat of losing the rights to his program simply because he once deployed it from his work computer. It's important to be aware of legal nuances and company policies regarding intellectual property to avoid misunderstandings and potential conflicts.
The law, in particular paragraph 1 of Article 1295 of the Civil Code of the Russian Federation, relies on the criterion of job responsibilities. If the development of a specific program was part of an employee's job responsibilities, the rights to that program transfer to the company. Otherwise, if performing this task was not part of their responsibilities, the rights remain with the developer. This important provision helps determine who owns the copyright to the software products created and regulates the relationship between employers and employees in the area of intellectual property.
Job responsibilities are defined by several key documents, including the employment contract, job title, and job description. These documents clearly define the employee's role in the organization and their primary duties in the workplace. The employment contract establishes the terms of work and the rights of the parties, the job title defines the level of responsibility, and the job description specifies the duties and requirements for completing tasks. It is important that all these elements are aligned, as they form the basis for understanding the work process and ensure the effective performance of job functions.
The employer is obliged to demonstrate that a specific result of intellectual activity (RIA) was created within the scope of the employee's job responsibilities. In this process, the company often faces a difficult situation where it is necessary to balance the employee's rights and the interests of the business. It is important to clearly define which tasks fall within the employee's direct responsibilities to avoid legal disputes and protect the company's interests. Proper documentation and the presence of clear internal regulations will help the employer confirm the official nature of the created RIA.
- On the one hand, job responsibilities should not be described too abstractly. For example, theoretically, you could write something like "a programmer programs": yes, that seems true, but what exactly, where, how, and why does he program? And most importantly, what if he designed something, but didn't write the code himself?
- On the other hand, you shouldn't get too specific. For example, the wording: "Ivanov Ivan Ivanovich writes the interface code for the 'Knee Joint' module of the 'Horns and Hooves' program in Python" doesn't seem very viable and works only until Ivanov I. I. completes his module. And, God forbid, he switches to Java!
Companies should regularly update important documents, such as employment contracts and staffing schedules. A key element of successful HR management is the creation of clear job descriptions for each position. Developing a system for setting tasks and monitoring results is also an important aspect. When employee responsibilities are clearly defined in a matrix, and specific job assignments are assigned by management, this simplifies the process of documenting completed work. For example, if an employee is developing the "Knee Joint" module and then switches to debugging the "Heart" module, and all of this is recorded, proving that the program was created within the scope of their job responsibilities becomes much easier. Regularly updating documents and clearly assigning tasks contribute to increased company efficiency and minimize potential legal risks. Effective team management requires clearly defined work processes. It is important to discuss key aspects of collaboration with employees in advance: who performs tasks and how, how goals are set, how and when to report on achieved results, and how royalties will be calculated and paid. This is not only done by good companies, but also by truly smart companies, which helps create a transparent and productive work environment. Some companies offer contracts with wording that can be misleading, for example: "Exclusive rights to any intellectual property created by I. I. Ivanov belong to Horns and Hooves LLC." However, such wording is not compliant with the law and may be deemed invalid. This is especially true if Ivan Ivanovich is a security guard under an employment contract. In some cases, even more intricate schemes are encountered, where the CEO or owner of the company unexpectedly becomes the author of all the developments in the documents. If you encounter such language in a contract, it's worth considering whether it really benefits you. Before signing, it's important to carefully review the terms of the contract and assess the potential risks.
In Russia, two striking examples illustrate this topic.
The case of Anton Mamichev vs. Veeam illustrates an important aspect of the legal nature of intellectual property. In this case, it can be said that neither party emerged victorious, and both suffered losses. The essence of this case is that not every program developed by an employee is automatically considered proprietary. This underscores the need to discuss all terms and rights to created products in advance. Misunderstandings and the absence of clear agreements can lead to serious legal consequences and conflicts.
The second important case involves Nginx. The issue of software rights can arise unexpectedly even years after you've been fired, and in some cases, you may face criminal liability. Fortunately, this case has not yet resulted in a court decision, but its history underscores the seriousness of the issue. It's important to be mindful of the legal aspects associated with intellectual property to avoid potential trouble in the future.
Copyright of Code for Freelancers or Contractors
The situation is quite simple. If you don't have an employment relationship with the company, none of your developments can be considered a work made for hire. Therefore, all legal aspects are governed solely by the contract, and in some cases, by a number of related factual circumstances. Regardless of your status in relation to the client company (an individual, self-employed, a sole proprietor, or a legal entity), you will most likely need to enter into a copyright contract. This will clearly define the rights and responsibilities of the parties and protect your interests during the collaboration.
Russian civil law is based on the principle of discretion, allowing parties to independently determine the terms of their agreements. In accordance with Article 1288 of the Civil Code of the Russian Federation, which pertains to the contract for the commission of a copyright, the client has the option of obtaining both exclusive rights to the development and limited rights to use, i.e., a license. This provides flexibility in establishing legal relations between the parties and allows for the client's individual needs to be taken into account.
Agreement on the terms of ownership of exclusive rights to the development must be clearly recorded. This is necessary to ensure the legal protection of all parties involved in the project. Clearly agreeing on such terms helps avoid potential conflicts and disputes in the future, and also ensures that intellectual property rights are properly formalized and protected.
It is important that the contract clearly states what exactly will be created as a result of the development. The problem is that at the time of signing the contract, the product is not yet ready (for example, the code has not yet been written). Nevertheless, both parties should have a common understanding of the final result of the development and who will own the rights to the created product. This will help avoid misunderstandings and protect the interests of both parties.
The main difference between a commissioned author's contract and other types of contracts lies in the specific nature of its content and objectives. Under a commissioned author's contract, the author creates a work at the request of the client, who in turn receives the rights to use this work. This creates unique conditions for interaction between the author and the client, which distinguishes this contract from standard civil law agreements. It is important to keep in mind that a custom order implies a creative component, which makes it more flexible and individual.
- an agreement on the alienation of exclusive rights refers to an existing object;
- a contract for work on the creation of certain entities that are not objects of intellectual property;
- a contract for the provision of services refers to the consumption of a service (but not an object) immediately at the time of its provision.
A description of the future development and the requirements for it are usually included in the terms of reference or specification, which are drawn up as an appendix to the contract. These documents must be sufficiently detailed and clear to allow for the identification of a specific development as the result of the contract. Properly drawn up terms of reference help avoid misunderstandings and ensure the successful implementation of the project. It is important that the description takes into account all key aspects, including functional requirements, deadlines, and expected results.
It is important to define the moment of transfer of rights to the development in the contract. This may be related to the actual creation of the product, the moment of payment, the signing of the acceptance certificate, or another pre-agreed date, but not earlier than the date of actual completion of development. Clearly indicating this point will help avoid misunderstandings and ensure the protection of the interests of the parties.
Care must be taken when drawing up the transfer of rights certificate. It is important that the certificate clearly specifies all aspects and elements of the development that are transferred under the contract. If you miss any detail or do not reflect it in the certificate, this may lead to a situation where you are unable to document the development of a specific software module and its transfer to the customer. It is important to remember that the presence of correct documentation plays a decisive role in the event of litigation.
Instead of a conclusion
Development in the field of information technology, especially in the context of official activities, is a complex task for lawyers. For programmers, the process may seem simpler: if new functionality is created, this means that working code appears. As a rule, it shouldn't be changed as long as it functions correctly. However, it's precisely during the development stage that it's important to consider legal aspects to avoid potential risks and ensure compliance with all regulations and standards.
A lawyer, analyzing the situation, perceives it through the prism of legal aspects and asks specific questions. What is the code, who exactly developed it, and under what conditions? Who owns the rights? What is the situation with royalties? If the lawyer doesn't receive clear answers to these questions, they may feel insecure: "Boss, everything is lost! The cast is being removed, the client is leaving!" To minimize risks, the lawyer may offer an extreme recommendation: "Use of this development is not recommended!" This approach emphasizes the importance of legal due diligence when using software and the need for a clear understanding of legal relations in the field of intellectual property.
Undoubtedly, this is an example of a less than effective approach on the part of a lawyer. Nevertheless, it is important to consider the opinion of your lawyer and follow their recommendations before starting project development. Proper interaction with a legal advisor will help avoid potential problems and ensure compliance with all necessary requirements, which will ultimately have a positive impact on the success of your business.

