What was the nature of the dispute between Linux and Lizeth regarding the AED 132,500 claim?
The dispute centered on a Software Development Agreement dated 15 March 2021 and an associated Non-Disclosure Agreement (NDA) dated 16 February 2021. The Claimant, Linux, sought to recover funds and damages, alleging that the Defendant, Lizeth, failed to deliver original software as promised, instead providing a third-party platform that allegedly violated copyright laws and exposed the Claimant to third-party liability.
As stated in the court record:
On 14 June 2022, the Claimant filed a claim seeking payments owed to the Claimant by the Defendant in the amount of AED 132,500 it in light of the Defendant’s alleged breach of contract.
The Claimant specifically sought a refund of AED 32,500 paid for services and an additional AED 100,000 in damages, citing losses in partnerships and potential exposure to copyright infringement claims. The Claimant’s position was that the delivered platform was a "copied" product rather than the bespoke development originally contracted for.
Which judge presided over the SCT 237/2022 proceedings and when did the hearing take place?
The matter was heard and determined by H.E. Justice Nassir Al Nasser in the Small Claims Tribunal (SCT) of the DIFC Courts. The hearing took place on 18 July 2022, with the final judgment issued on 27 July 2022.
What specific legal arguments did Linux and Lizeth advance regarding the software deliverables?
The Claimant argued that the Defendant breached the Agreement by delivering a third-party platform instead of developing original software from scratch. The Claimant further contended that this delivery violated the NDA and placed the Claimant at risk of third-party litigation.
The Claimant submits that the Defendant’s breach of the Agreement and delivery of the copied platform caused the Claimant loss of vendors, partnerships and income amounting to substantial loss.
The Defendant countered that it had informed the Claimant of the availability of common industry software solutions and that the Claimant had explicitly requested the handover of "whatever material was ready" within one month of signing the Agreement. The Defendant maintained that it delivered a beta version of the software, which was integrated with the Claimant’s requirements, and that the Claimant subsequently breached the Agreement by handing over this unfinished product to a different developer.
What were the primary legal questions the Court had to answer regarding the alleged breach of contract and NDA?
The Court was tasked with determining whether the Defendant’s delivery of the software constituted a breach of the Software Development Agreement, specifically whether the Claimant had accepted the deliverables by failing to object within the contractually mandated timeframe. Furthermore, the Court had to decide whether the Defendant’s disclosure of information—specifically the procurement of a non-objection certificate—constituted a breach of the NDA. The core issue was whether the Claimant’s conduct in requesting an early handover precluded them from later claiming that the delivered product was non-conforming.
How did H.E. Justice Nassir Al Nasser apply the doctrine of contractual acceptance to the software handover?
The Court applied a strict interpretation of the contractual notice period. The judge found that because the Claimant failed to provide written notice of non-conformity within the required three-day window following the handover, the Claimant was deemed to have accepted the product in its then-current state.
I am of the view that this means the Claimant accepted the handover of the product that was ready at that time. Therefore, I find that there is no breach of the Agreement as alleged by the Claimant.
Regarding the NDA, the Court noted that the Defendant’s actions were performed under the express direction of the Court itself. Consequently, the judge ruled that the Defendant could not be held liable for complying with judicial instructions. The Court concluded that the Claimant failed to meet the burden of proof required to establish a breach of contract.
The Claimant failed to convince the Court of any breach and failed to provide sufficient evidence to establish a breach.
Which specific DIFC statutes and procedural rules governed the SCT 237/2022 decision?
The proceedings were governed by the Rules of the DIFC Courts (RDC), specifically those pertaining to the Small Claims Tribunal. The judgment relied on the contractual terms stipulated in the Software Development Agreement and the Non-Disclosure Agreement. The Court’s authority to determine the matter was derived from the Judicial Authority Law and the established procedures for the SCT, which prioritize summary determination of disputes.
How did the Court utilize the evidence presented during the 18 July 2022 hearing?
The Court utilized the evidence—including WhatsApp communications from 16 February 2021—to establish that the Claimant was aware of the software solutions being utilized by the Defendant. The judge used this evidence to distinguish between the Claimant’s initial expectations and their subsequent conduct in requesting an early handover of the "ready" material. The Court also relied on the procedural history, noting that the Defendant had filed an Acknowledgment of Service on 20 June 2022, confirming its intent to defend the claim in its entirety.
What was the final disposition and order regarding the AED 132,500 claim?
The Court dismissed the Claimant’s claim in its entirety. The judge found that the Claimant was not entitled to the requested refund or the damages for the alleged breach of the Agreement or the NDA.
Since no breach has been found, the Claimant is not entitled to damages in the sum of AED 100,000 as claimed.
The Court made no order as to costs, meaning each party was responsible for its own legal expenses. The final order, issued on 27 July 2022, effectively closed the matter without awarding any of the monetary relief sought by the Claimant.
What are the wider implications of this ruling for software development contracts in the DIFC?
This judgment serves as a reminder to practitioners and litigants that contractual notice periods for the acceptance of deliverables are strictly enforced by the DIFC Courts. Parties in software development agreements must ensure that any dissatisfaction with a deliverable is communicated in writing within the precise timeframe specified in the contract. Failure to do so will likely result in the Court finding that the deliverable was accepted, thereby waiving the right to claim a breach of contract. Furthermore, actions taken by a party under the specific direction of the Court cannot be used as a basis for claiming a breach of a non-disclosure agreement.
Where can I read the full judgment in Linux v Lizeth [2022] DIFC SCT 237?
The full judgment is available on the DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/small-claims-tribunal/linux-v-lizeth-2022-difc-sct-237
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | N/A |
Legislation referenced:
- Rules of the DIFC Courts (RDC)
- Software Development Agreement (15 March 2021)
- Non-Disclosure Agreement (16 February 2021)