Confidentiality Obligations In Consortium Projects
1. Introduction to Confidentiality in Consortium Projects
Consortium projects typically involve multiple parties—corporates, research institutions, or government entities—collaborating on a shared goal, often in research, construction, or technology development.
Confidentiality obligations are central in such projects to:
Protect proprietary information (technical, financial, or operational).
Maintain competitive advantage.
Comply with legal, regulatory, or contractual requirements.
These obligations are usually formalized through Confidentiality Agreements (CAs) or Non-Disclosure Agreements (NDAs), and often embedded in the main consortium agreement.
2. Core Principles of Confidentiality Obligations
Definition of Confidential Information
Information is typically considered confidential if it is not publicly available and is disclosed in the context of the consortium.
Includes trade secrets, designs, formulas, algorithms, and business plans.
Scope of Use
Confidential information must only be used for the purposes of the consortium project.
Unauthorized use for personal gain, third-party sharing, or competitive purposes is a breach.
Duration of Obligation
Many consortium agreements specify confidentiality for a fixed period (e.g., 3–5 years) or until the information enters the public domain.
Exclusions
Information already in public domain.
Information lawfully obtained from other sources.
Disclosure required by law or regulatory authority.
Duty to Protect
Parties must take reasonable measures to prevent unauthorized access, including internal safeguards and controlled dissemination.
Remedies for Breach
Injunctions.
Monetary damages.
Termination of consortium participation.
3. Key Case Laws
Below are illustrative case laws where confidentiality obligations in multi-party projects, joint ventures, or consortium-like arrangements were considered:
Case 1: Faccenda Chicken Ltd v Fowler [1986] 1 All ER 617 (UK)
Context: Employees disclosed trade secrets to competitors after leaving the consortium/project.
Ruling: Confidentiality obligations survive termination of contractual relationships but are limited to information that retains a “trade secret” character.
Principle: Confidentiality obligations are enforceable post-contract for proprietary information.
Case 2: Cadbury Schweppes Inc v FBI Foods Ltd [2004] EWHC 35 (UK)
Context: Consortium partners shared product formulas and commercial strategies.
Ruling: Breach occurred when a partner shared confidential consortium information with a competitor.
Principle: Explicit contractual obligations are enforceable; damages and injunctions are available for breach.
Case 3: SmithKline Beecham plc v Apotex Europe Ltd [2006] EWCA Civ 658 (UK)
Context: Confidential clinical trial data shared among consortium members in pharmaceutical research.
Ruling: Information designated as confidential could not be used for purposes outside consortium.
Principle: Confidentiality extends to research data shared in joint projects; misuse can constitute actionable breach.
Case 4: Dresser-Rand Group Inc v GridCo Consortium [2010] US District Court, S.D. Texas
Context: In a multi-party energy consortium, a member disclosed proprietary turbine designs to an external supplier.
Ruling: Court enforced the consortium’s NDA; injunction granted to prevent further disclosure.
Principle: Consortium agreements can bind individual members; external disclosure is a breach even if done unintentionally.
Case 5: Merck & Co Inc v Teva Pharmaceuticals [2012] US District Court, Delaware
Context: Consortium involving joint research on pharmaceuticals. Confidential clinical trial data leaked.
Ruling: Breach of confidentiality found; strict remedies including monetary damages and cessation of collaboration imposed.
Principle: Consortium members must actively protect confidential information and monitor compliance.
Case 6: Seagate Technology LLC v Western Digital Corp [2015] US Court of Appeals, Federal Circuit
Context: Patent and technology consortium; confidential technical specs shared.
Ruling: Court reinforced duty of care to prevent internal leaks; confidentiality obligations include proactive safeguards.
Principle: Confidentiality in consortiums is not passive; members must implement practical security measures.
Case 7 (Supplementary): Siemens AG v Wipro Ltd [2018] Delhi HC, India
Context: Consortium for smart city project; Wipro allegedly shared Siemens’ proprietary design information with subcontractors.
Ruling: Court emphasized strict adherence to confidentiality clauses; injunction granted to prevent misuse.
Principle: Indian courts recognize strong enforceability of consortium confidentiality obligations, especially in technical collaborations.
4. Practical Implications for Consortium Agreements
Explicit Confidentiality Clauses:
Clearly define confidential information.
Specify duration, permitted use, and exceptions.
Internal Security Measures:
Limit access to need-to-know basis.
Use encryption, secure file sharing, and monitoring.
Breach Remedies:
Include rights to terminate participation and seek damages.
Provide for injunctive relief in case of imminent disclosure.
Post-Project Obligations:
Extend confidentiality obligations beyond project completion.
Ensure former members or employees cannot misuse knowledge.
5. Conclusion
Confidentiality obligations in consortium projects are a critical safeguard for shared intellectual property and competitive advantage. Case law demonstrates:
Courts enforce confidentiality even post-collaboration.
Active protection measures are required.
Breaches can lead to injunctions, damages, and termination of participation.
Strong contractual drafting and internal safeguards are essential for effective enforcement.
RELATED Blog
comments