A dispute over confidential technology or commercial information in Israel may begin with a question that precedes misappropriation: who is entitled to control the information? The person who developed a formula, software system, customer database or business method is not necessarily the only person entitled to assert rights in it. Equally, paying an employee or an external developer does not automatically establish ownership of every item of know-how created during the engagement.
Under Israeli trade secret law, the analysis turns on lawful control of the information, its origins, the relationship in which it was developed, the parties’ agreements and the resources used. Where the development also constitutes a potentially patentable invention, the rules governing employee service inventions may become relevant. These distinctions matter particularly to foreign businesses commissioning development in Israel, investors reviewing an Israeli company’s intellectual property and overseas counsel handling an Israeli trade secret dispute.
Israeli law does not require formal ownership in every case
Section 5 of Israel’s Commercial Torts Law, 5759-1999, defines the owner of a trade secret broadly, including a person who lawfully controls the secret. Protection is therefore not confined to a claimant holding a document expressly titled “Assignment of Trade Secrets”. A party with lawful control of qualifying confidential information may also be entitled to protect it.
This reflects the nature of trade secret rights. Unlike patents, trade secrets are not recorded in a public register identifying a registered proprietor. Protection depends on the information’s confidentiality, its competitive value and the steps taken to maintain secrecy. The statutory conditions are examined separately in What Qualifies as a Trade Secret in Israel?
Nevertheless, where two parties claim entitlement to the same information, possession alone will rarely settle the dispute. It is necessary to consider who developed the information, the relationship in which it was created, who financed and directed the work, what the parties agreed and what knowledge each party possessed before the relationship began.
Trade secrets developed by an employee hired to create technology
A relatively straightforward situation arises where an employee is engaged specifically to develop the technology or process in dispute. If the development falls within the employee’s responsibilities and the employer’s business, there is a stronger basis for asserting the employer’s entitlement to it.
Where the development is a patentable invention, Section 132 of the Israeli Patents Law, 5727-1967, addresses service inventions. An invention made by an employee in consequence of and during the course of employment generally becomes the employer’s property, unless the parties have agreed otherwise or the employer relinquishes its entitlement under the statutory provisions.
That statutory rule should not simply be applied to every kind of business information. Not every internal procedure, database, commercial method or body of know-how is a patentable invention. Where the information does not fall within the service-invention framework, entitlement is assessed by reference to the contractual relationship, the circumstances of development, duties of loyalty and lawful control of the information.
The employee’s actual role is therefore important. A researcher or software engineer employed to develop solutions in a defined area presents a different situation from an employee who independently develops an unrelated idea outside the company’s business without significant use of its resources. Employment alone does not resolve every ownership question.
Working hours and location do not determine ownership
Whether the work took place at the office or at home, during ordinary working hours or in the evening, is not conclusive. For a service invention under Section 132, the statutory test concerns both the invention’s connection to the employment and whether it was made during the period of service. An invention developed at home can still qualify if it arose from the employee’s work. Conversely, an idea conceived during employment does not become the employer’s property merely because of its timing.
Relevant evidence may include the employee’s job description, the employer’s field of activity, directions received, company information used in the development, equipment and other resources supplied, and whether developing the relevant solution was an expected part of the employee’s assignment.
Ownership must also be distinguished from the employee’s ability to use general professional skills after leaving. Section 7 of the Commercial Torts Law provides an exception from misappropriation liability, in the circumstances specified by the statute, where knowledge acquired through employment with the owner has become part of the employee’s general professional skills. A claim to a trade secret does not automatically prevent a former employee from using ordinary expertise and experience.
Pre-existing know-how brought by an employee
An employee may join a company with technology, source code, libraries, methods, procedures or other knowledge developed before the engagement. Using that material in the course of employment does not, by itself, transfer ownership of all pre-existing rights to the employer.
Employment agreements in technology businesses should therefore distinguish pre-existing intellectual property from developments created in the course of employment. If the employee brings significant prior software, an algorithm, a technical process or commercial know-how to the company, it is better to identify that material before it becomes integrated into the company’s product.
The agreement should address not only title but also use rights: whether the employer may incorporate the earlier technology into its product, license or supply that product to customers, transfer the relevant rights to a future purchaser of the business and use improvements produced during employment. Without such provisions, the dispute may arise only after the earlier technology has become essential to the business.
Independent contractors: payment is not necessarily an assignment
The ownership analysis can be more complicated when a company commissions an external developer or consultant to create software, a manufacturing process, a formula, a prototype or a database. Payment for the project does not necessarily establish that all know-how created or used in carrying out the project belongs to the customer.
There is a material distinction between a contractor retained to create a bespoke development for one customer and a contractor who brings existing technology, tools and methodologies used across multiple clients. The first situation offers a stronger basis for treating the specifically commissioned result as intended for the customer. In the second, an assignment of all the contractor’s technology could prevent the contractor from continuing its own business.
A development agreement should distinguish the background knowledge contributed by each party, deliverables developed specifically for the project, improvements to pre-existing technology, information supplied by the customer and the rights each party will retain or receive after the engagement ends.
When the contract does not address these matters clearly, a court may need to examine the parties’ expectations and the commercial structure of the transaction. The relevant question is not merely who wrote the code or devised the process, but what the customer paid for and what each party could reasonably have expected to receive.
A distributor may own a customer list developed for another company
The difficulty is not confined to technology. In Yedioth Ahronoth Ltd. v. Firstenberg, Israeli Supreme Court, Civil Appeal 9099/96, PD 53(5) 1 (1999), the dispute concerned, among other things, subscriber lists developed by an independent distributor. The Court upheld the conclusion that the lists belonged to the distributor rather than the newspaper, taking account of the parties’ relationship and the distributor’s independently operated business.
The significance extends to other distribution arrangements. A company engaging another business to establish a sales channel, supplier database or commercial network should not assume that the resulting information belongs to it simply because it concerns its products. The contractual structure, the parties’ respective investments and who bore the costs and risks of building the information asset may all be relevant.
A separate issue is whether a customer list qualifies for protection as a trade secret in the first place. A list does not acquire that status automatically merely because one party claims ownership of it.
Founders and business partners: ownership is different from fiduciary duties
Joint ventures can produce a different ownership problem. Founders exchange information, develop a product together and assume that the idea or technology “belongs to the venture”. After the relationship breaks down, the absence of a clear agreement may reveal that this assumption was never properly addressed.
In Integrity Software 2011 Ltd. v. Gonen, Tel Aviv District Court, Civil Case 65217-06-15 (8 February 2018), the claim that the defendants had been shown to use the earlier venture’s trade secrets was rejected, although breaches of duties of loyalty and obligations among the parties were established. The decision illustrates that a breach of a fiduciary or contractual duty is not the same question as whether specified information constitutes another party’s trade secret.
Founders’ and collaboration agreements should identify the knowledge each party contributes, what will count as a development of the venture, who will own those developments, whether a party may continue using its background technology independently and what happens to jointly developed information if the relationship ends.
Shared lawful control creates its own risks
More than one party may lawfully control or hold confidential information. A business can provide information to a licensee, distributor, manufacturer or commercial partner for a defined purpose without surrendering its own rights. In such arrangements, the permissible scope of control and use should be made explicit.
The more parties who have access, the greater the risk of disclosure and of disagreement over authorized uses. A well-drafted agreement does more than state that all information must remain confidential. It explains what each recipient may do with the information, to whom it may be disclosed, how copies and backups are handled, whether derivative developments are permitted and who may enforce the rights if a leak occurs.
A non-disclosure agreement (NDA) can help regulate the disclosure of information to an external party, but it does not replace provisions governing ownership and the scope of the recipient’s rights of use.
Contracts should distinguish ownership, permitted use and confidentiality
These are three different concepts. One party may own information while licensing another to use it extensively. A party may assign ownership while remaining bound by confidentiality obligations. A recipient may receive limited permission to use information without receiving any ownership rights. Treating these arrangements as interchangeable creates avoidable disputes.
Employment and development agreements should address each party’s background knowledge, project deliverables, ownership of improvements, assignment versus licensing, exclusivity, territorial or commercial scope, sublicensing and the duration of confidentiality obligations after the relationship ends.
Where technology may also be patentable, the agreement should be consistent with the rules governing service inventions and with the chosen strategy for protecting the development. A company may wish to patent part of a technology while preserving other know-how as a trade secret. The allocation of rights should be clear under either approach.
Clear entitlement is essential when enforcing trade secrets in Israel
When suspected misappropriation arises, a claimant that cannot explain the legal basis of its entitlement to the information begins at a disadvantage. Before asking whether a defendant copied, disclosed or used a secret, the claimant must be able to explain why it is entitled to protect the particular information.
The issue is equally important in acquisitions, investment rounds and intellectual property due diligence. An investor or purchaser assessing an Israeli technology business needs to know more than whether the company possesses source code and know-how. It must also consider whether rights created by employees, founders and independent contractors have been properly documented and allocated. An incomplete chain of rights may become a serious point of contention just as the technology begins to acquire commercial value.
The best time to resolve these questions is when the information is created, not after the relevant parties separate. Clear employment, founders’ and development agreements are part of the protection of the information itself. Where the dispute has already arisen, the ownership analysis provides a starting point for assessing claims under Israeli law and potential trade secret litigation in Israel.
