From the journal

Software product liability for AI updates and data loss

An AI-enabled file-management service is updated. A consumer loses personal files; a business loses working records. The first legal decision is which obligation failed and which loss the applicable law protects. The developer, distributor and hosting provider may face different claims, even where they contributed to the same release.

30 min read

Software product liability is only one route. Consumer guarantees, contractual promises and negligence or other civil-wrong rules may provide a stronger claim, particularly for business records. A product claim also requires a covered loss, a legally responsible defendant and proof that the defect caused that loss.

This comparison examines fourteen countries across seven regions, with separate EU-level and United Arab Emirates (UAE) financial-free-zone analysis. It states the law as at 18 November 2026. The US discussion uses Maryland and a bounded California comparison; Canada distinguishes Ontario and Quebec; the UK private-law and procedural discussion focuses on England and Wales. Actual supply locations, contracts, customer purposes and release dates determine which branch matters.

Start with the obligation and the loss

The parties should build two linked records. The first explains what happened: the original program, the update, any model or configuration change, the instructions executed, the permissions available and the point at which the files disappeared. The second identifies the legal undertaking: a sale, licence, hosted service, storage obligation, implementation project or combination of these.

Causation requires evidence linking the update’s operation to the deletion. A destructive migration script may breach a promise to preserve existing files. An AI classification error may become actionable because the system deletes files without an adequate approval mechanism. A correctly executed deletion instruction may point elsewhere. The analysis must test the update against storage faults, compromised credentials, user commands, third-party integrations and retention settings.

Separate the claimed losses before assessing exclusions:

  • Price of the defective software or service. Question to resolve: Is the remedy repair, replacement, re-performance, price reduction, termination or damages?
  • Restoration of personal files. Question to resolve: Does the route cover data, property damage or breach of a preservation obligation, and what recovery expense was reasonably incurred?
  • Reconstruction of working records. Question to resolve: Does the claimant qualify for consumer protection; otherwise, what contract or civil-wrong duty supports the claim?
  • Business interruption and profit. Question to resolve: Was the loss caused by the breach, sufficiently foreseeable or otherwise within the duty, proved and reasonably mitigated?
  • Irreplaceable personal material. Question to resolve: Is there a legally recognised non-financial loss, rather than an assumed monetary value for emotional attachment?

These categories matter throughout the comparison. A refund for an unusable subscription does not necessarily compensate for lost files. An upstream indemnity does not itself give the customer a claim against its beneficiary. Nor does compliance with a cybersecurity rule establish every element of a civil compensation claim. The separate reporting workstream is addressed in Licentium’s analysis of Cyber Resilience Act (CRA) reporting for AI software development kits (SDKs).

When software is a product and when services provide the clearer route

The EU change has a precise date and a limited damage category

The revised EU Product Liability Directive expressly includes software. Its treatment is not confined to a program installed on a physical device: the recitals include software delivered through a network, cloud or software-as-a-service model. Related services and components have their own definitions. Non-commercial free and open-source software is excluded within the directive’s specified conditions; commercial integration requires a separate analysis.[1]

The date needs particular care. A 7 May 2026 corrigendum changes the English wording of Article 2(1) to products placed on the market or put into service after 8 December 2026, meaning from 9 December 2026. Member States must transpose the directive by 9 December 2026. The revised regime is not a uniform private claim simply because the directive exists. Earlier products remain within the relevant legacy framework, while national implementing law and the actual placement or service date must be established.[2]

For the consumer’s files, Article 6 expressly includes destruction or corruption of data not used for professional purposes. Article 5 gives the compensation right to natural persons. A company’s working records therefore fall outside this route, and a sole trader cannot convert professional data into protected personal data merely by suing as an individual. The property and data limbs are drafted differently: the property exclusion concerns exclusively professional use, while the data limb does not use that qualification.[1]

The directive covers material loss resulting from recognised damage, with non-material loss dependent on national law. It excludes damage to the defective product itself and specified damage to an integrated product. A customer who receives complete recovery without cost may have a different compensable-loss position from one who must pay for reconstruction. Contract and other liability grounds remain important, especially for business data.[1]

An update also requires more than a date check. The directive addresses manufacturer control, including authorised integration, modifications and the ability to supply updates. It limits certain later-defect defences where controlled software, updates, omitted safety updates or related services cause the defect. Substantial modification outside original control can create manufacturer responsibility and a new relevant start date. An ordinary patch does not automatically reset every limitation period or move every legacy product into the revised regime.[1]

France and the UK already have distinct digital and service remedies

In France, the digital-content and digital-service conformity regime can address a paid consumer file-management service without first winning a strict product-classification argument. Its provisions also extend specified protection to non-professionals. The trader must supply conforming content or services and the necessary updates, with separate rules for optional changes. A claim may concern failure to preserve promised functionality, compatibility or continuity. Liability for a consumer’s failure to install an update is subject to conditions, including causation and adequate information or instructions.[3]

For a one-off supply, the two-year conformity period concerns when the defect appears; it is not a complete statement of the prescription period. A continuous supply is assessed over the contracted period, and burden rules differ. Repair, price reduction or termination do not necessarily exhaust other damages. The existing French product-liability chapter and ordinary contract or fault rules remain relevant; pure software and deleted-data treatment under the legacy product provisions should not be asserted as settled merely by importing the revised directive’s definitions.[3][4]

As at 18 November 2026, the French Civil Code still contained the legacy product-liability structure.[5][6]

In the UK, the Consumer Rights Act 2015 distinguishes digital content from services. Section 46 gives a specific route where digital content supplied under a contract damages the consumer’s device or other digital content, and reasonable care and skill would have prevented the damage. It can require repair or compensation. Its scope can include contractually supplied free content through section 33(8). A hosted arrangement still needs classification: content used only as the means of supplying a service is not automatically governed by the digital-content chapter.[7]

The cap analysis is equally specific. Section 47 does not make every restriction of section 46 liability automatically void; section 47(6) directs that issue to the section 62 fairness test. Mandatory digital-quality rights and service rights have their own restrictions. Section 40 also prevents a simple assumption that every modification restarts the digital-content claim clock. Apply each of these statutory restrictions and fairness tests separately in the contract review.[7]

The Consumer Protection Act 1987 remains a separate safety-based route with its own product and private-property conditions. Standalone software classification and data-only damage remain difficult questions under that legislation. The Law Commission’s consultation opened on 8 October 2026 and, as at 18 November 2026, closes on 14 January 2027; its proposals are not enacted remedies. Licentium’s article on the consultation explains that reform workstream.[8][9]

Apply each regime’s software and remedy conditions

Japan provides a useful contrast. Its Product Liability Act defines a product as a manufactured or processed movable. The Consumer Affairs Agency distinguishes standalone software from software incorporated into a manufactured product: a software problem may make the physical product defective, but software alone does not enter the Act simply because it is commercially supplied. Contractual non-performance under Civil Code Articles 415–416 and tort under Article 709 therefore deserve direct attention for a hosted file manager. Consumer Contract Act Articles 8 and 10 restrict exclusions and unfair terms within their conditions.[10][11][12][13]

In Singapore, contractual performance and reasonable-care obligations may be more useful than asserting an automatic product-defect claim. The Consumer Protection (Fair Trading) Act’s unfair-practice route can address misleading performance or safety representations, but its non-conforming-goods provisions have a distinct scope. Section 13 applies the distinct goods and supply concepts governing the Part 3 remedies to the particular software transaction. Spandeck and the 2026 Deloitte judgment require separate analysis of duty, breach, causation and recoverable loss.[14][15][16][17]

In the United States, state law and transaction classification are central. Maryland’s enacted computer-information law expressly addresses computer-information transactions, including access arrangements and modifications. It supplies a more specific contractual starting point than assuming that every licence or hosted service is an ordinary sale of goods. Express promises, merchantability, fitness and system-integration obligations need separate analysis. For a qualifying consumer contract, Maryland restricts exclusion of both specified warranties and their remedies; commercial risk allocation differs.[18][19][20][21][22]

Maryland is not a national rule. California’s Sheen decision illustrates the separate economic-loss obstacle to a negligence claim based only on a contractual failure. It concerned mortgage servicing, not software, and does not decide every independent-duty or fraud claim. For the business customer, the practical response is to establish the relevant state’s contract, warranty and independent-duty routes before treating an upstream developer as a tort defendant.[23]

Two other regions show why the classification question cannot be answered globally. South Africa expressly includes software, data, code and specified licences in its definition of goods; a service supplier providing access to goods may also fall within the statutory product chain. Saudi Arabia’s enacted product-safety regulations expressly cover tangible and intangible products and products offered during services. These are substantive statutory starting points, but each still requires its own actor, defect or safety, causal-damage and defence analysis.[24][25]

Personal files and working records do not follow the same recovery path

A business buyer can sometimes receive consumer protection

In Australia, computer software is goods under the Australian Consumer Law (ACL). A business purchase may qualify as a consumer acquisition, including through the A$100,000 price threshold, subject to statutory exclusions; the alternative household-kind test also matters. Goods and service guarantees can therefore protect some business software purchases. Consequential damages under the guarantee remedies differ from the safety-defect provisions, whose property-damage limb has private-use conditions. The Valve litigation confirms the significance of consumer guarantees for downloaded software supplied to Australian consumers. For a hosted contract, apply the relevant goods or services classification, territorial connection and remedy conditions separately.[26][27][28]

The business must identify whether its claim concerns goods, services or both. Section 63’s exception for services involving transportation or storage of goods for business purposes may require analysis in a storage arrangement; it should not be applied to digital files without resolving the relevant classification. Section 64A permits only specified substitute-performance limitations for qualifying non-household supplies, subject to its conditions. A fee-based cap requires its own statutory and contractual basis; section 64A authorises only its specified limitations.[26]

New Zealand also includes computer software in goods. Its Consumer Guarantees Act uses an ordinary household-kind test, subject to the statutory exclusions, without Australia’s alternative price limb. Some business purchases may qualify; qualifying parties in trade can contract out only through the written, fair-and-reasonable mechanism in sections 43–43A. Service care, fitness and completion obligations have distinct remedies and defences. Section 33’s third-party or uncontrollable-event defence concerns specified fitness and timing failures, not the section 28 reasonable-care duty.[29]

The difference changes procurement. An Australian business should test price and statutory purpose exclusions. A New Zealand business should test the kind of acquisition and any effective written contracting-out arrangement.

Provincial and consumer-purpose distinctions matter in the Americas

In Ontario, the operative Consumer Protection Act, 2002 deems services under a consumer agreement to be of reasonably acceptable quality and protects specified rights against waiver. A hosted personal-file service may therefore have a service-quality route. The consumer definition excludes an individual acting for business purposes. As at 18 November 2026, the replacement 2023 Act was marked not yet in force in the official record; using its provisions as current remedies would be an error.[30][31]

Quebec has a different civil-law analysis. Contract performance, the provider’s care or result obligation and the Civil Code’s damages rules matter. The Supreme Court’s Prelco decision is particularly relevant: it concerned a failed business software implementation and upheld the negotiated allocation against the asserted fundamental-breach argument in its legal and factual setting. It does not make every consumer or adhesion-contract exclusion valid. Civil Code Article 1474 preserves restrictions for intentional or gross fault and specified kinds of injury; consumer and adhesion rules add further controls.[32][33][34]

Against a remote developer in common-law Canada, Maple Leaf Foods explains why economic loss requires more than foreseeable damage somewhere in a supply chain. An undertaking and reasonable reliance may support a duty within its scope, but the majority did not impose the duty claimed on the facts. Contractual protection and the allocation of commercial risk are material. The case is a duty analysis from a food-supply dispute, not a decision that business software losses are categorically irrecoverable.[35]

In Brazil, the Consumer Defence Code expressly includes immaterial products as well as services. Its product or service accident rules differ from its quality-remedy rules. Strict responsibility under Articles 12 and 14 does not dispense with the relevant defect, damage and causal connection. A business using software as an input must establish final-recipient status or the vulnerability required for exceptional consumer protection. In a 2026 Microsoft 365 subscription and maintenance billing dispute, the Superior Court of Justice upheld the fact-specific refusal of consumer treatment and applied the limits on re-examining evidence on special appeal. Ordinary Civil Code performance and damages routes remain relevant outside consumer law.[36][37][38]

Brazilian law also resists a universal cap statement. Article 51(I) contains a specific possibility of justified limitation where the consumer is a legal person. Identify consumer status, the kind of remedy and the particular restriction before deciding whether restoration cost, lost profits or an agreed allocation can be enforced.[36]

In Mexico, the Federal Consumer Protection Law recognises final recipients, including legal persons, but its special extension for business inputs is limited to specified proceedings and conditions. It does not turn every business procurement into an ordinary consumer purchase. For deficient or unprovided services within Articles 92 Bis–92 Ter, the statutory bonus has a minimum based on 20% of the price paid, alongside the separate damages framework. It is neither a valuation of deleted files nor a 20% ceiling on compensation. Federal civil and commercial rules must also be distinguished from the applicable state civil law.[39][40][41]

Express goods coverage still leaves a damage question in Africa

South Africa’s section 61 covers specified harm, including loss of, or physical damage to, property and economic loss resulting from the listed harm. The wording makes it unsafe to exclude every deleted-file claim simply because the disk is undamaged. It is equally unsafe to treat software’s inclusion as goods as proof that every lost file or unrealised profit meets the harm requirement. Contract, service-quality and warranty claims should be assessed alongside the product claim.[24]

Large juristic-person transactions can be outside ordinary Consumer Protection Act coverage at the statutory threshold, yet section 5(5) preserves sections 60–61 for goods supplied under exempt transactions. That is a material difference from the EU’s natural-person and professional-data restrictions. For a separate delict claim for pure economic loss, the Constitutional Court’s Country Cloud decision requires a justified wrongfulness basis; such a duty is not presumed from financial harm alone.[24][42][43]

In Kenya, the Consumer Protection Act’s paid-service warranty offers a direct route for a qualifying hosted-service agreement. Section 5 requires reasonable merchantable quality and prevents negation of that warranty. The Act’s consumer wording is broad, but a corporate buyer’s eligibility still needs the applicable interpretation and transaction analysis. Section 16 attaches joint responsibility to persons who engaged in the unfair practice and the contracting person, subject to the section’s requirements.[44]

The business should itemise recovery expenses, wasted fees and proved interruption rather than request an unexplained general award. The Supreme Court’s Sundowner ruling was a certification decision concerning general damages in ordinary contract litigation. It does not abolish quantified contractual loss or express statutory remedies. A direct upstream negligence claim and remote profit claim need their own legal foundation.[45]

Map defendants by their role and control

For each release, identify who wrote the relevant code, chose the model, configured deletion permissions, approved deployment, supplied the customer-facing promise and controlled rollback or recovery. Those facts help establish responsibility, but local law determines the legal consequence.

Under the revised EU directive, manufacturer and component liability, importers or authorised representatives, fulfilment providers and distributor fallback have distinct conditions. A distributor is not automatically liable merely because it sold the product: the identification mechanism and one-month response period matter. A person making a substantial modification outside the manufacturer’s control can become responsible as a manufacturer. Joint liability and recourse do not allow the chain to contract away the injured person’s mandatory rights.[1]

Saudi Arabia’s Product Safety Law and regulations also address component makers, own branding, importation, supply-chain identification, qualifying digital modification and joint responsibility. Their wording must be applied on its own terms; the distributor formulation should not be silently narrowed to the EU model. The regulations’ express intangible-product coverage supports examining a software update. Recovery for deleted records is a reasoned application of the damage wording.[46][25]

Two Saudi reforms require a separate transition check. The Consumer Protection Law approved on 10 November 2026 is announced to commence 180 days after Gazette publication. The Commercial Transactions Law published on 13 November 2026 also has a 180-day commencement rule. As at 18 November 2026, neither is treated here as operative. The Commercial Transactions Law’s express repeal list does not name the 2020 Commercial Courts Law.[47][48]

The UAE requires separate routing. Onshore, Federal Decree-Law 25/2025 replaced the 1985 Civil Transactions Law from 1 June 2026, subject to transitional provisions. Contract and harmful-act rules sit alongside consumer protection. The consumer statute includes technological or intellectual commodities and services, and its definition is not limited to natural persons in the way the revised EU directive is. Applicable provider and territorial conditions still matter. Article 257 voids exemption from or reduction of harmful-act liability; negotiated contractual caps require a separate analysis of the claim and applicable mandatory rules.[49][50]

The DIFC and ADGM (the Dubai International Financial Centre and the Abu Dhabi Global Market) operate separate civil and commercial regimes. Dubai Law 2/2025 supplies the DIFC courts framework, including jurisdictional connections and written opt-in conditions. An agreed forum does not alone settle substantive governing law. ADGM’s enacted Consumer Protection Regulations, effective from 15 December 2025, expressly include digital products but exclude business, trade, craft and professional purchases. Covered providers are limited to the specified retail-licence or temporary-permit categories. Those provider and purchase-purpose conditions apply to natural and legal persons.[51][52]

For ordinary ADGM business cloud procurement, use the contract and the locally applicable common law and selected adopted statutes. Do not assume that the UK Consumer Rights Act applies wholesale. Detailed DIFC or ADGM damages, cap and procedural advice requires the applicable zone texts and transaction facts; treating all UAE suppliers as subject to one civil-liability code risks selecting the wrong defendant and remedy.[53][54]

Branding deserves a release review because it can affect statutory actor status in several regimes. It also creates evidence about promises and reliance. The separate CRA role analysis is explained in Licentium’s article on commercial open-source SDK suppliers. That regulatory classification should not be substituted for the civil-liability test applicable to the claim.

Proof and deadlines need their own incident plan

A strict-liability regime dispenses with proof of negligence within its scope while retaining its requirements for a defective product, covered harm and causation. The revised EU directive’s disclosure and presumptions are conditional. A claimant must establish a plausible claim for proportionate disclosure. Non-disclosure, specified safety breaches, obvious malfunction and technical complexity can matter under different provisions; complexity alone does not guarantee success. Presumptions remain rebuttable.[1]

Saudi regulations likewise identify particular unsafety and causation presumptions. Brazil’s consumer burden adjustment depends on statutory conditions and judicial assessment. Kenya’s general burden and facts-within-knowledge provisions do not create a universal AI presumption. A supplier should preserve evidence even where it believes the defect case is weak, because missing evidence may independently affect the litigation.[25][36][55]

The useful evidence set is specific: executable and model versions; hashes or other stable identifiers; release approvals; migration scripts; deletion and access logs; retention and backup settings; warnings and installation instructions; customer-facing claims; incident communications; and a reproducible account of recovery attempts. Preserve the original records before repair work overwrites them. Access to source code or model internals should be tied to the issue, with confidentiality, privilege and personal-data controls.

In the 2026 SS&C decision arising from Ontario, Canada’s Supreme Court required proof of intentional destruction, alteration or concealment of relevant evidence during pending or reasonably contemplated litigation, including the required intent to affect that litigation. The court retained a rebuttable adverse presumption, proportionate remedies and evidence-based damages assessment. The original update’s breach and causal role still require their own proof.[56]

Procedure differs. France permits appropriate pre-action measures under Civil Procedure Code Article 145. Japanese civil procedure provides document-production mechanisms and consequences for non-compliance. In Kenya, computer-output evidence requires attention to Evidence Act section 106B and its certification conditions. Each application must satisfy the relevant production rule, including its scope and protected-material exceptions.[57][58][55]

Warnings, user choices and backups also require causal analysis. A user’s refusal of a properly explained necessary update may affect a French conformity claim within the statutory conditions. A user’s own deletion instruction may defeat the asserted causal sequence. Failure to mitigate may reduce a recoverable amount. Assess a generic warning that “AI may make mistakes” against the supplier’s file-preservation promises, foreseeable destructive pathways and applicable mandatory obligations.[3][1]

Build the deadline calendar by claim, actor and event. Do not use a single worldwide period:

  • The revised EU product regime has a three-year knowledge-based limitation rule and a separate ten-year extinction period, with a longer rule for specified latent personal injury. Those are not a general extension for lost business data.[1]
  • Maryland’s computer-information limitation rule combines accrual and discovery elements with an outer limit and restrictions on contractual shortening. A commercial consequential-loss restriction and the statutory measure of direct damages are separate questions.[59][60]
  • Ontario generally combines a two-year discovery period with a fifteen-year ultimate period, subject to statutory qualifications. Quebec’s ordinary personal-action period is generally three years, with its own accrual and suspension rules.[61][32]
  • New Zealand’s ordinary money-claim regime starts with six years from the relevant act or omission, with conditional late-knowledge and longstop rules. The late-knowledge and longstop provisions require a separate calculation where their conditions apply.[62]
  • Kenya’s usual contract and tort periods differ. Its section 27 ignorance-of-facts extension requires a personal-injury component and should not be assumed to rescue a data-only claim.[63]
  • Saudi harmful-act rules combine three years from knowledge with ten years from occurrence of harm; special commercial rules and the statutory use of Hijri time require separate attention.[64][65]

Complaint discussions, recovery attempts and a request for logs do not safely substitute for analysing the filing deadline. Contribution and indemnity claims can have different triggers from the customer’s original claim. Record the supply, update, breach, loss, knowledge, demand and settlement dates separately.

In England and Wales, compensatory remedial work can constitute payment in kind and start the two-year contribution period before a judgment or settlement. The claim still requires the relevant parties’ liability for the same damage. An express indemnity has its own terms and accrual analysis.[66][67][68]

Make the contract support recovery and supplier recourse

The contract should describe the service that the customer needs and the controls each supplier can actually perform. A distributor promising restoration without access to the developer’s logs or the host’s backups creates a practical recourse problem even before any cap is disputed.

Define preservation and restoration. Identify which files are protected, whether deletion requires approval, who operates backups, what retention applies and how exports and rollback are tested. State recovery-time and recovery-point commitments only where the parties can support them. Separate a duty to use reasonable care from a guaranteed result. Disclose unusual business dependency so that foreseeability and the scope of the undertaking can be assessed.

Allocate update authority. Name the party that can approve, defer or stop a release and the conditions for emergency changes. Require version histories, compatibility testing, migration records, rollback criteria and notice of material changes. Distinguish developer control from a distributor’s or integrator’s independent modification. These negotiated controls support compliance and legal proof; applicable law and the service’s risks determine the required release safeguards.

Provide access and cooperation. Specify incident-notification channels, preservation holds, log formats, expert access, confidentiality and claims cooperation. Allocate the cost of recovery, defence and evidence production. Ensure relevant obligations survive termination and reach the host and subcontractors that hold the records. A right to inspect that cannot practically be exercised after the incident has limited value.

Draft recourse around the actual loss. Separate direct customer liability, contribution for the same damage and express contractual indemnity. Identify whether recovery costs, defence expenditure, third-party awards and settlements fall within the indemnity; align notice, defence control and settlement consent. Avoid circular terms under which the distributor owes restoration to customers while the developer excludes every data-related cost. Mandatory claimant protection remains external to that allocation.[1][24][25]

Australia shows why the upstream remedy needs its own calculation. ACL section 274 provides a manufacturer indemnity within its conditions. For goods outside the ordinary household kind, section 276A ordinarily limits that indemnity to the lowest replacement, equivalent-goods or repair cost, subject to the supplier proving unfairness or unreasonableness; the parties may agree greater liability. A New Zealand third-party beneficiary arrangement under Contract and Commercial Law Act sections 12–19 also requires attention to section 19’s New Zealand governing-law condition.[26][69]

Test each cap locally. Quebec’s Prelco decision supports careful negotiated allocation within its boundaries. France’s Faurecia II decision and Civil Code Article 1170 show why an essential obligation and a cap must be analysed together; a failed obligation does not by itself answer the gross-fault question. The UK Supreme Court’s Triple Point decision shows how a negligence carve-out can include contractual duties of care under the wording used. Its application to another contract requires analysis of that contract’s words and the relevant duty of care.[34][70][71][72]

A reasonable-care exclusion also needs the applicable unfair-terms statute. In Singapore and the UK, provisions concerning intellectual-property rights and international supply can affect the reach of the Unfair Contract Terms Act. Australian and New Zealand consumer-guarantee restrictions are different again. Classify the transaction, obligation, claimant and limitation, then apply the relevant mandatory restrictions and unfair-terms rules before relying on the signed clause.[73][74][26][29]

Review insurance against the pleaded exposure. For software product liability insurance, identify the policy provision that covers the particular loss and insured role. Ask the insurer or broker to explain how the wording addresses data restoration, technology errors, customer financial loss and business interruption. Examine electronic-data and professional-services exclusions, contractual-liability treatment, defence costs, deductibles, territorial and jurisdiction limits, notification obligations and aggregation. Product, professional-indemnity and cyber policies may address different parts of the event; coverage depends on the actual wording and facts.

Response to the two claims

For the consumer, identify the paid or free contractual basis, the supplied digital product or service and the specific personal files lost. Preserve the release and deletion record, attempt proportionate recovery, and distinguish the refund claim from restoration expense and any separately recognised non-financial harm. Check mandatory protections before offering a settlement based on a standard disclaimer.

For the business, first test whether the local consumer regime applies. If it does not, assemble the contractual promises, communicated dependency, breach, causal loss and mitigation evidence. Quantify restoration, reconstruction and net interruption loss separately. Identify any independent duty owed by a non-contracting developer instead of assuming that every actor in the technical chain owes the same obligation.

For the suppliers, preserve evidence and identify the party that controlled each relevant step. Check claims-notification and recourse deadlines while recovery proceeds. Before the next release, align customer promises with upstream access, update authority, indemnities and insurance. The decisive result is a supportable claim and a workable allocation of responsibility under the law actually connected to the supply.

Review distribution and update terms

To review software distribution, update control and claims-cooperation terms for the markets in which your product is supplied, contact Licentium.

Primary authorities

  1. Revised Product Liability Directive. Directive (EU) 2024/2853; Arts 1–18,21–24; recitals 13–20,30,39–42,50.
  2. Corrigendum correcting the product application date. OJ L 2026/90364, 7 May 2026; CELEX 32024L2853R(01); Correction to Article 2(1).
  3. Consumer conformity of digital content and services. Code de la consommation; Arts L224-25-1–3,12–21,24–32.
  4. Civil Code product liability provisions. Code civil; Arts 1245–1245-17.
  5. EUR-Lex national transposition register. National implementing measures for Directive (EU) 2024/2853; France entry; register explanatory qualification.
  6. Government answer on revised product liability transposition. Assemblée nationale, question écrite 11448; Government answer published 12 May 2026, paragraphs on planned dedicated instrument.
  7. Digital content and service consumer remedies. Consumer Rights Act 2015; Ss 2,33–47,49–57,62,65.
  8. Legacy strict product liability. Consumer Protection Act 1987; Part I ss 1–7, especially 2–5.
  9. Product liability reform consultation. Law Commission Consultation Paper 279, Product Liability; Project status; CP paras 1.29–1.32,2.20,5.86–5.97.
  10. Product Liability Act. Act No 85 of 1994; arts 2–6; Supplementary Provisions.
  11. Overview of Product Liability Act: Questions and Answers. Consumer Affairs Agency; Q1, Q3–Q14, Q16–Q22, Q24–Q26.
  12. Civil Code. Act No 89 of 1896; arts 85, 90, 166, 415–420, 548-2, 562–566, 632, 644, 656, 709–710, 715, 719, 722, 724.
  13. Consumer Contract Act. Act No 61 of 2000; arts 2, 8, 8-2, 10; amendment transitional provisions.
  14. Consumer Protection (Fair Trading) Act 2003. 2020 Revised Edition; ss 2–7, 12–18, 35, 41; Second Schedule.
  15. Sale of Goods Act 1979. 2020 Revised Edition; ss 2, 13–15, 53–55, 61.
  16. Spandeck Engineering (S) Pte Ltd v Defence Science & Technology Agency. [2007] SGCA 37; [2007] 4 SLR(R) 100; [21], [69], [73]–[85], [108]–[115].
  17. Deloitte & Touche LLP v Hin Leong Trading (Pte) Ltd (in compulsory liquidation). [2026] SGCA 33; [6]–[7], [37], [44]–[69], [81]–[82], [146]–[149].
  18. Commercial Law Title 22: Definitions. Md. Code, Com. Law §22-102; (a)(1),(10)–(16),(25),(34),(43)–(46).
  19. Commercial Law Title 22: Scope and mixed transactions. Md. Code, Com. Law §22-103; (a)–(d).
  20. Commercial Law Title 22: Program merchantability. Md. Code, Com. Law §22-403; (a)–(c).
  21. Commercial Law Title 22: Fitness and system integration. Md. Code, Com. Law §22-405; (a)–(d).
  22. Commercial Law Title 22: Warranty disclaimers and consumer restrictions. Md. Code, Com. Law §22-406; (h)–(l), read with (a)–(g).
  23. Sheen v. Wells Fargo Bank, N.A. 12 Cal.5th 905 (2022), S258019; slip pp. 1–3, 12–18; particularly pp. 13–15.
  24. Consumer Protection Act. Act 68 of 2008; ss 1, 5–6, 48–49, 51, 53–56, 60–61, 65, 69, 115–117.
  25. Product Safety Executive Regulations. SASO Product Safety Executive Regulations, adopted 15 November 2024, published 22 November 2024; arts 1–5, 8–15, 56–64.
  26. Competition and Consumer Act 2010, Schedule 2: Australian Consumer Law. Compilation 168, C2026C00486; ss 2–3, 7, 9, 18, 23–27, 54–64A, 67, 138–148, 150, 236, 259–276A.
  27. Competition and Consumer Regulations 2010. Compilation 100, F2026C00856; r 77A; relevant commencement/application notes.
  28. Valve Corporation v Australian Competition and Consumer Commission. [2017] FCAFC 224; [83], [96]–[116], [135]–[153]; orders.
  29. Consumer Guarantees Act 1993. 1993 No 91; ss 2, 6–8, 13, 16–18, 25–33, 41, 43–43A, 46A.
  30. Consumer Protection Act, 2002. S.O. 2002, c.30, Sched. A; ss.1–2,6–9,14,18,100–101.
  31. Consumer Protection Act, 2023: commencement status. S.O. 2023, c.23, Sched. 1.
  32. Civil Code of Québec. CQLR c.CCQ-1991; arts.899,907,1435–1437,1457–1458,1465,1468–1479,1525–1537,1607,1611,1613,1726–1730,2098–2100,2803–2804,2880,2884,2925–2926,3117,3149.
  33. Loi sur la protection du consommateur. CQLR c.P-40.1; ss.1–2,8–11.2,16–19,34,37–43,51,53–54,261–272.
  34. 6362222 Canada inc. v. Prelco inc. 2021 SCC 39, [2021] 3 S.C.R. 3; paras.1–5,21–30,39–56,63–70,84–104.
  35. 1688782 Ontario Inc. v. Maple Leaf Foods Inc. 2020 SCC 35, [2020] 3 S.C.R. 504; majority paras.18–23,29–40,41–47,59–68,88–96; dissent 97–100,164–168.
  36. Código de Defesa do Consumidor. Lei 8.078/1990; arts.2–3,6,12–14,17–20,24–27,50–51,101.
  37. AgInt no AREsp 2.954.356/PR. STJ, Quarta Turma, reg. 2025/0202657-8, Rel. Min. Raul Araújo; Voto: passages beginning “No tocante à aplicação do CDC” and “Quanto às caracterizações”; term of judgment dated 1 June 2026.
  38. Código Civil. Lei 10.406/2002; arts.186–189,205–206,389,393,402–403,421–424,927,931,944–945.
  39. Ley Federal de Protección al Consumidor. LFPC, DOF 24 December 1992; arts.1–2,7,13–14,37,41–42,76 Bis,82,85,90,92–95,99,105,117.
  40. Código Civil Federal. CCF; arts.1,6–7,1910,1913,1915–1917,1934,2104,2106,2108–2111,2117.
  41. Código de Comercio. Código de Comercio; arts.2–4,75,89 Bis,1040–1047,1049–1050,1194–1198,1298-A.
  42. Juristic-person threshold determination. GN 294, Government Gazette 34181, 1 April 2011; determination and Schedule paras 1–4.
  43. Country Cloud Trading CC v MEC, Department of Infrastructure Development. [2014] ZACC 28; CCT 185/13; 2015 (1) SA 1 (CC); paras 20–25, 26–32, 39–50, 51–69.
  44. Consumer Protection Act. Cap. 501; Act 46 of 2012, revised 2022; ss 2–5, 12–16, 84–88.
  45. Sundowner Lodge Ltd v Kenya Tourist Development Corporation. [2023] KESC 100 (KLR), Application E039 of 2023; paras 7, 9(i)–(vi), 10.
  46. Product Safety Law. Royal Decree M/36, 29 Muharram 1446 / 4 August 2024; arts 1, 3, 7, 14–15, 31–32, 37.
  47. Consumer Protection Law approval and commencement announcements. Ministry of Commerce official approval/transition pages; Cabinet approval 10 November 2026; Approval page commencement paragraph; transition page three replacement instruments; Gazette Cabinet-news approval item.
  48. Commercial Transactions Law 2026 and promulgation. Royal Decree M/132 dated 21/5/1448H; Cabinet Decision 411 dated 16/5/1448H; Gazette publication 13 November 2026; arts 269–271; promulgation and Cabinet decision.
  49. Civil Transactions Law. Federal Decree-Law No. 25 of 2025; Promulgation arts 2–3; attached arts 4, 6–10, 19–22, 29–30, 111, 114–115, 219–223, 245–258, 266–271, 334–340, 429, 434, 437, 439–444.
  50. Consumer Protection Law. Federal Law No. 15 of 2020, amended by Federal Decree-Law No. 5 of 2023; arts 1, 3–4, 10–12, 16–17, 21, 24–26, 38.
  51. DIFC Courts Law. Dubai Law No. 2 of 2025; Official Gazette 705; arts 14–15, 28, 43–44.
  52. Consumer Protection Regulations. Consumer Protection Regulations 2025; ss 1–4, 7–15, 18–23, 26.
  53. Application of English Law Regulations. Application of English Law Regulations 2015, consolidated rulebook with 2016, 2020 and 2022 amendments; ss 1–2, 7–8; Schedule entries for UCTA 1977, contribution 1978, Sale of Goods 1979, Limitation 1980, Supply of Goods and Services 1982.
  54. Financial Free Zones Law. Federal Law No. 8 of 2004; arts 1–3, 7–8.
  55. Evidence Act. Cap. 80; Act 46 of 1963, version of 11 December 2023; ss 106A–106B, 107–112, 119.
  56. SS&C Technologies Canada Corp. v. Bank of New York Mellon Corp. 2026 SCC 29; SCC file 41543; Paras. 80–95, 135–138 and 161–162.
  57. Pre-action preservation and establishment of evidence. Code de procédure civile; Art 145, including 2025 venue amendment.
  58. Code of Civil Procedure. Act No 109 of 1996; arts 220–225, 247–248.
  59. Commercial Law Title 22: Time for bringing contract action. Md. Code, Com. Law §22-805; (a)–(f).
  60. Commercial Law Title 22: Licensee damages. Md. Code, Com. Law §22-809; (a)–(b).
  61. Limitations Act, 2002. S.O. 2002, c.24, Sched. B; ss.4–7,15,18–19,22–24.
  62. Limitation Act 2010. 2010 No 110; ss 10–14, 34, 40–48, 55–56, 59.
  63. Limitation of Actions Act. Cap. 22; Act 21 of 1968, revised 2022; ss 3–5, 22–27, 39.
  64. Civil Transactions Law. Royal Decree M/191, 29 Dhu al-Qadah 1444 / 18 June 2023; arts 1–2, 19–20, 27, 120–143, 168–180, 295–305, 721.
  65. Commercial Courts Law. Royal Decree M/93, 2020; arts 16, 24; subsequent Evidence Law art 128.
  66. Economic loss, scope of duty, remedial work and contribution accrual. URS Corporation Ltd v BDW Trading Ltd [2025] UKSC 21; Majority paras. 12, 27–33, 61 and 162–164; adopted contribution reasons at paras. 212, 225–238 and 262–266.
  67. Contribution between parties liable for the same damage. Civil Liability (Contribution) Act 1978; Ss 1,2,6,7.
  68. Contract, tort and product time limits. Limitation Act 1980; Ss 2,5,10,11A,14A–14B.
  69. Contract and Commercial Law Act 2017. 2017 No 5; ss 12–19, 34–37, 49–58.
  70. Faurecia II software liability cap decision. Cass. com., 29 June 2010, no 09-11.841; Operative reasons on first and third grounds; disposition.
  71. Civil Code contract and damages rules. Code civil; Arts 1170,1171,1217,1231-1–1231-4.
  72. Software contract negligence carve-out. Triple Point Technology Inc v PTT Public Company Ltd [2021] UKSC 29; Majority paras. 50–68 and 99–122; dissent paras. 123–147; paras. 30 and 73 on scope.
  73. Unfair Contract Terms Act 1977. 2020 Revised Edition; ss 1–4, 6–7, 11–13, 26–27; First Schedule para 1(c).
  74. Controls on commercial exclusions and limits. Unfair Contract Terms Act 1977; Ss 1–3,11,13,26; Schedule 1 para 1(c); Schedule 2.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.