Civil Law And Software-As-A-Service Licensing Breach Claims In Europe

1. Introduction

Software-as-a-Service (SaaS) licensing breach claims arise when a customer and a software provider disagree about the contractual or legal rights and obligations connected with cloud-based software.

Unlike traditional software licensing, SaaS usually involves:

access to software + cloud hosting + subscription + maintenance + updates + data processing + service levels + technical support.

Therefore, a SaaS dispute may involve both contract law and intellectual-property law, together with data protection, cybersecurity, consumer/digital-content law and, in some circumstances, competition law.

Typical claims include:

unauthorised use of SaaS;

use beyond the permitted number of users;

account sharing;

unauthorised copying;

reverse engineering;

unauthorised modification;

breach of licence restrictions;

failure to pay subscription fees;

wrongful suspension of access;

failure to provide promised availability;

failure to provide updates;

failure to meet service levels;

misuse of customer data;

unauthorised sublicensing;

termination disputes;

post-termination access;

excessive licence charges;

vendor lock-in;

failure to return/export customer data;

cybersecurity failures;

infringement of intellectual-property rights.

A crucial preliminary point is that there is still relatively little European case law specifically about modern SaaS contracts. Consequently, established CJEU software-licensing and copyright authorities must often be applied by analogy to SaaS arrangements. The distinction between a direct SaaS authority and an analogous software-licensing authority is therefore important.

2. Meaning of SaaS Licensing

In a traditional software sale:

Customer → receives software copy → installs it → uses it.

In SaaS:

Provider → operates software in cloud → customer receives contractual access → customer pays subscription → provider continuously operates/updates service.

For example:

A company subscribes to cloud accounting software for 100 employees.

The agreement provides:

100 authorised users;

€10,000 annual subscription;

business-use only;

no sublicensing;

no reverse engineering;

99.9% availability;

customer data remains the customer's property;

provider may suspend access for serious payment default.

If the customer allows 250 employees to use the system, the provider may claim a licensing breach.

If the provider shuts the service down for several weeks despite payment, the customer may bring a contractual non-performance claim.

3. Legal Character of a SaaS Agreement

A SaaS agreement is usually a mixed contract.

It can contain elements of:

licence;

service contract;

hosting agreement;

maintenance agreement;

data-processing arrangement;

support agreement;

subscription agreement;

cloud-computing agreement.

This classification matters because different legal rules can apply to different parts of the relationship.

Example

A SaaS provider promises:

software access;

data storage;

technical support;

updates;

99.9% uptime.

The customer's claim that the provider failed to maintain 99.9% availability is primarily a contract/service-performance dispute, while unauthorised copying of software may engage copyright and software-protection law.

4. Main European Legal Framework

A. Contract law

The primary source is usually the applicable national contract law.

Issues include:

formation;

interpretation;

breach;

material breach;

termination;

damages;

limitation of liability;

force majeure;

good faith;

mitigation;

restitution.

For international SaaS contracts, Rome I Regulation can determine the applicable law, subject to its rules and contractual choice-of-law provisions.

B. Software Copyright

Computer programs receive special protection under Directive 2009/24/EC on the legal protection of computer programs.

It regulates, among other things:

reproduction;

adaptation;

distribution;

lawful acquisition;

decompilation;

interoperability.

This is particularly important when a contractual licence breach also amounts to copyright infringement.

C. Copyright Enforcement

Directive 2004/48/EC provides an EU framework for enforcement of intellectual-property rights.

Possible remedies can include:

injunctions;

damages;

corrective measures;

evidence preservation;

information orders.

D. Digital Content

For B2C SaaS arrangements, Directive (EU) 2019/770 on contracts for the supply of digital content and digital services is particularly relevant.

It addresses:

conformity;

updates;

remedies;

modification of digital services;

termination;

consumer protection.

Its scope is primarily consumer contracts, so it should not automatically be applied to a purely B2B SaaS contract.

E. GDPR

SaaS platforms frequently process:

employee information;

customer information;

financial data;

health information;

behavioural data.

Consequently, the GDPR may operate alongside the SaaS contract.

A breach can therefore potentially create:

contractual liability + data-protection consequences.

5. Case Law

Case 1: IT Development SAS v Free Mobile SAS

C-666/18, EU:C:2019:1099

This is one of the most directly relevant CJEU cases for software-licence breach claims.

The dispute concerned unauthorised modification of software source code by a licensee in breach of the software licence agreement.

The central issue was whether the software owner could bring an intellectual-property infringement action against the licensee for breach of contractual licence restrictions.

The CJEU held that the EU software-protection and IP-enforcement framework does not prevent a national court from treating a breach of a software licence agreement as an infringement claim where the applicable national law allows that route. (InfoCuria)

Principle

A software licence breach can potentially have two dimensions:

Contractual breach

and

intellectual-property infringement.

SaaS significance

Suppose a SaaS customer:

modifies protected software;

accesses prohibited source code;

circumvents licence restrictions;

uses the software beyond contractual permissions.

The provider may potentially pursue both contractual and IP remedies, depending upon national law.

Exam formula

Software licence breach may simultaneously constitute contractual non-performance and an IP infringement.

6. Case 2: UsedSoft GmbH v Oracle International Corp.

C-128/11, EU:C:2012:407

This is one of the most important European software-licensing cases.

Oracle supplied software through downloads and granted customers user rights under licence agreements. UsedSoft marketed so-called “used” Oracle licences.

The CJEU held that, under particular circumstances, where a copyright holder has authorised downloading of a copy of software and granted a right to use it for an unlimited period in return for a fee corresponding to the economic value of that copy, the distribution right in that copy can become exhausted. (EUR-Lex)

Important limitation

UsedSoft concerned a perpetual software licence involving a downloadable copy.

It should not be mechanically treated as a rule that SaaS subscriptions are freely transferable.

A modern SaaS arrangement may involve:

continuous hosting;

recurring subscription payments;

account authentication;

cloud infrastructure;

ongoing updates;

continuous services.

Those features can make SaaS materially different from the perpetual software transaction in UsedSoft.

SaaS principle

A perpetual software licence and a SaaS subscription are not automatically legally equivalent.

This distinction is extremely important.

7. Case 3: SAS Institute Inc. v World Programming Ltd

C-406/10, EU:C:2012:259

The dispute involved SAS software and a competing program designed to reproduce certain functions of the SAS system.

The CJEU held, among other things, that the functionality of a computer program and the programming language are not protected by copyright as such. It also examined the rights of a lawful acquirer to observe, study or test the functioning of software in order to determine underlying ideas and principles. (InfoCuria)

SaaS significance

Imagine a SaaS customer develops an interoperable system.

The provider cannot automatically argue:

“Our software performs this function, therefore the function itself is copyrighted.”

However, the customer must still respect:

contractual restrictions;

protected source code;

confidential information;

trade secrets;

database rights;

other IP rights.

Principle

Software functionality is not automatically equivalent to protected software expression.

This can become important in disputes involving:

API interoperability;

competing cloud services;

migration;

data integration;

reverse engineering.

8. Case 4: Top System SA v État belge

C-13/20, EU:C:2021:811

The CJEU examined the rights of a lawful acquirer of computer software to correct errors.

The Court interpreted the software-protection framework and recognised circumstances in which a lawful acquirer can carry out acts necessary for correcting errors, subject to the relevant legal conditions. (InfoCuria)

SaaS significance

This is relevant to a difficult SaaS question:

Can a customer modify or interfere with software to correct a defect?

Normally, a SaaS customer does not receive unrestricted control over the provider's source code.

But contractual terms cannot necessarily be treated as giving the provider unlimited power to override mandatory rights under applicable EU software law.

Principle

Mandatory software-law rights can restrict the practical effect of contractual licence restrictions.

9. Case 5: Bezpečnostní softwarová asociace v Ministerstvo kultury

C-393/09

The CJEU considered copyright protection for a graphical user interface associated with computer software.

The Court distinguished the protected computer program itself from other elements such as a graphical interface and considered whether those elements constitute an expression of the author's own intellectual creation.

SaaS significance

Modern SaaS systems include:

dashboards;

interfaces;

visual designs;

workflows;

icons;

screen layouts.

A customer or competitor copying an interface may therefore raise a different legal question from merely implementing the same functionality.

Principle

Functionality, interface design and protected software expression must be legally distinguished.

This is useful where a SaaS provider alleges that a customer has copied part of its cloud platform.

10. Case 6: Nintendo Co. Ltd and Others v PC Box Srl and 9Net Srl

C-355/12, EU:C:2014:25

This case concerned technological protection measures and copyright.

The CJEU examined the relationship between technological protection measures and copyright enforcement.

Although not a SaaS contract case, it is relevant where a provider uses technological mechanisms to control access to software.

SaaS relevance

Cloud providers commonly use:

authentication;

licence keys;

user limits;

API keys;

technical access restrictions;

digital rights management;

account suspension.

A provider may therefore argue that bypassing those mechanisms constitutes unlawful circumvention.

But the legality of a technological restriction must still be analysed under applicable EU and national law.

Principle

Technical access controls can have legal significance, but technological enforcement cannot be analysed independently of the underlying IP and statutory framework.

11. Case 7: SAS Institute — Lawful Acquirer and Software Observation

A particularly important aspect of SAS Institute is the treatment of the lawful acquirer's ability to observe, study and test software operation.

The CJEU recognised that contractual software use does not mean that every act connected with understanding software automatically becomes copyright infringement. (InfoCuria)

SaaS application

A customer may need to understand:

API behaviour;

data formats;

system interactions;

software outputs;

interoperability.

A provider cannot simply label every interoperability investigation as copyright infringement.

But contractual restrictions, confidentiality obligations and trade-secret law may remain relevant.

12. Case 8: IT Development v Free Mobile — Importance of Contractual Terms

The most important feature of IT Development for SaaS disputes is the recognition that the licence agreement itself matters.

A customer might have a right to use software for:

100 users;

but not:

1,000 users.

It may have permission to:

use software internally;

but not:

resell access.

It may have permission to:

access an API;

but not:

reproduce or modify protected software.

The precise licence terms therefore determine the contractual boundary.

13. Direct vs Analogous Case Law

This distinction is particularly important for SaaS litigation.

Important: There is not yet a large, unified body of CJEU jurisprudence specifically deciding modern disputes over cloud SaaS subscription contracts. Therefore, traditional software cases should not be presented as if they were all direct SaaS decisions.

14. What Constitutes a SaaS Licensing Breach?

A breach can arise from either side.

Customer-side breaches

1. Exceeding user limits

Contract permits:

100 users

Actual use:

500 users.

Potential claim:

licence overuse + additional fees + damages/injunction.

2. Account sharing

A contract may restrict access to named users.

Sharing credentials may breach the agreement.

3. Unauthorised sublicensing

Customer may allow another company to use the SaaS platform without permission.

4. Reverse engineering

Customer attempts to reproduce protected software architecture.

This may involve:

copyright;

contract;

trade secrets;

interoperability exceptions.

5. Unauthorised modification

Customer modifies code or deploys unauthorised components.

IT Development is particularly important here.

6. Commercial resale

A business licence may permit internal use only.

The customer then sells access to third parties.

This can constitute a serious licence breach.

15. Provider-Side Breaches

SaaS providers can also breach the agreement.

Examples include:

unjustified suspension;

failure to provide access;

prolonged downtime;

failure to provide contracted updates;

failure to maintain promised functionality;

failure to meet SLA;

wrongful termination;

failure to return customer data;

cybersecurity failure;

unauthorised data use;

material service degradation.

Thus:

SaaS licensing litigation is not necessarily provider-versus-customer copyright litigation.

It can equally be:

customer-versus-provider contract litigation.

16. Service-Level Agreement Breaches

A SaaS contract might promise:

99.9% monthly availability.

Suppose the service is unavailable for several days.

Potential legal questions include:

Was the SLA contractual?

Was it an obligation of result or best efforts?

Were scheduled maintenance periods excluded?

Was the outage caused by force majeure?

Did the customer suffer legally recoverable loss?

Is there a service-credit mechanism?

Does the contract make service credits the exclusive remedy?

Is the limitation clause enforceable?

17. Suspension of SaaS Access

One of the most important modern disputes concerns account suspension.

Suppose:

customer misses one payment;

provider immediately disables the entire platform;

customer loses access to business records;

business suffers €1 million in losses.

The provider may rely on the contract.

The customer may argue:

suspension was disproportionate;

contractual notice was required;

the breach was minor;

suspension caused disproportionate harm;

essential data remained inaccessible;

termination/suspension clause is unfair or invalid.

The result depends heavily on the governing national law and contract wording.

18. Material vs Minor Breach

Not every breach justifies termination.

Minor breach

Example:

Customer exceeds 100 users by 2 users for one week.

Material breach

Example:

Customer deliberately copies and commercially redistributes the provider's software.

Similarly:

Minor provider breach

One short, contractually permitted maintenance interruption.

Serious provider breach

Repeated prolonged outages that make the SaaS system unusable.

The right to terminate depends upon the applicable law and contract.

19. Cure Periods

Many SaaS agreements provide:

“The breaching party has 30 days to cure.”

This can become decisive.

If a customer exceeds its licence:

Provider notice

↓

Customer cure period

↓

Customer reduces users

↓

No termination

unless the contract/law provides otherwise.

Courts generally examine the actual contractual mechanism rather than treating every breach as automatically terminating the relationship.

20. Damages

Potential SaaS damages include:

Direct losses

additional licence charges;

restoration costs;

technical remediation;

replacement service costs.

Consequential losses

business interruption;

lost contracts;

lost profits;

reputational damage.

Whether consequential loss is recoverable depends heavily on:

governing law;

foreseeability;

causation;

contractual exclusions;

limitation clauses.

21. Limitation-of-Liability Clauses

SaaS contracts frequently state:

“Provider's total liability shall not exceed fees paid during the preceding 12 months.”

This can become one of the central litigation issues.

Courts may consider:

mandatory national law;

consumer protection;

gross negligence;

intentional misconduct;

personal injury;

data-protection liability;

fraud;

unfair contract terms;

reasonableness/proportionality.

A contractual cap is therefore not automatically valid in every situation.

22. Unfair Terms in B2C SaaS

Where the customer is a consumer, EU unfair-terms law becomes particularly important.

Potentially problematic terms can concern:

unilateral modification;

automatic renewal;

excessive termination fees;

broad suspension powers;

exclusion of all liability;

unilateral price increases;

forced arbitration where legally restricted;

automatic loss of customer data.

B2B SaaS contracts generally receive greater contractual freedom, although national mandatory law can still restrict certain terms.

23. Digital Content and SaaS

For consumer contracts, Directive 2019/770 is highly relevant.

A consumer can potentially have remedies where a digital service:

does not conform to the contract;

lacks required functionality;

is not supplied properly;

is not updated as required.

Possible remedies can include:

bringing the service into conformity;

price reduction;

termination;

refund.

Therefore:

Consumer SaaS litigation is increasingly moving beyond traditional copyright law into digital-content conformity law.

24. Updates and Patches

SaaS is fundamentally different from a one-time software sale because software changes continuously.

Updates can involve:

security patches;

functionality changes;

bug fixes;

AI model updates;

API changes;

user-interface changes.

A contractual dispute may arise where:

Provider changes the software so substantially that the customer's business process no longer works.

The court may need to determine whether the provider had a contractual right to make the change.

25. Data Ownership and Data Access

A SaaS customer may own or control:

customer records;

transaction data;

employee information;

business documents.

But the SaaS provider may own:

software;

databases;

system architecture;

platform code;

proprietary algorithms.

This creates an important distinction:

Customer data ≠ SaaS software.

A licensing dispute should therefore identify exactly what property is allegedly being misused.

26. Data Portability

At termination, the customer may demand:

“Give me my data.”

Important questions include:

What data must be returned?

In what format?

Within what period?

At what cost?

Can the provider retain backups?

Can the provider delete data immediately?

Is migration assistance included?

These issues are increasingly important under European digital regulation.

27. Vendor Lock-In

A SaaS provider may technically make it difficult for a customer to move to another provider.

Examples:

proprietary data formats;

expensive export charges;

restricted APIs;

artificial technical barriers;

refusal to provide migration assistance.

The dispute may potentially involve:

contract law;

competition law;

data-access legislation;

interoperability principles.

28. Cybersecurity Breach

Suppose the provider's cloud system is hacked.

Customer data is stolen.

Potential claims may involve:

Contract

Failure to comply with security obligations.

GDPR

Failure to comply with controller/processor obligations.

Tort/delict

Negligence causing loss.

Regulatory law

Possible supervisory enforcement.

IP/confidentiality

Unauthorised disclosure of protected information.

Therefore:

One cybersecurity incident can generate several independent legal claims.

29. Reverse Engineering

Reverse engineering is a particularly difficult area.

The customer may argue:

“I needed to study the software to make it interoperable.”

The provider may respond:

“You violated the licence prohibition.”

European software law contains specific rules concerning lawful acquirers, error correction and interoperability.

SAS Institute and Top System are therefore particularly important.

30. API Access Disputes

An API allows one software system to communicate with another.

Suppose a SaaS provider changes its API and stops the customer's integration.

Potential issues:

Was API compatibility contractually promised?

Was the API proprietary?

Was the change permitted?

Did the customer have a migration period?

Does interoperability law apply?

Was the change discriminatory?

Did the customer suffer foreseeable losses?

The exact legal answer depends upon the agreement and applicable law.

31. SaaS Termination

Termination may occur because of:

non-payment;

unauthorised use;

repeated security violations;

insolvency;

material breach;

expiry;

convenience clause.

The legal consequences may include:

immediate loss of access;

data export;

deletion;

continuing confidentiality obligations;

payment of outstanding fees;

return/destruction of materials;

transition services.

32. Post-Termination Use

Suppose a licence ends on 31 December.

Customer continues using the platform until March.

Potential claim:

unauthorised post-termination use.

The provider may seek:

licence fees;

damages;

injunction;

account termination;

restitution;

potentially IP remedies.

The exact remedy depends on national law and the contractual structure.

33. SaaS Licence Breach and Copyright

A contractual breach is not automatically a copyright infringement.

This distinction is extremely important.

Example

Contract says:

“Customer may not use the software for external commercial purposes.”

Customer does so.

That may be:

contractual breach.

But it does not automatically mean:

copyright infringement.

The provider must identify a relevant exclusive copyright act or other IP right.

IT Development is useful because it demonstrates the potential interaction between contractual licence restrictions and software-IP enforcement. (InfoCuria)

34. SaaS Licence Breach and Trade Secrets

Cloud providers may also protect:

source code;

algorithms;

system architecture;

technical documentation;

security methods.

A customer obtaining confidential technical information may create claims under:

contractual confidentiality;

trade-secret law;

copyright;

unfair competition law.

35. Good Faith

Civil-law systems frequently recognise some form of good faith in contractual performance.

This may become relevant where:

provider exercises termination rights opportunistically;

customer exploits a technical loophole;

provider changes pricing immediately before renewal;

customer deliberately circumvents licence restrictions;

one party frustrates the commercial purpose of the contract.

However:

Good faith does not normally allow a court simply to rewrite an otherwise valid commercial contract.

Its exact legal effect differs among European jurisdictions.

36. Force Majeure

Cloud outages can be caused by:

natural disasters;

war;

major cyberattacks;

power-grid failure;

internet backbone failure;

government action.

A provider may invoke force majeure.

But a provider generally cannot simply label every technical failure as force majeure.

Questions include:

Was the event external?

Was it unforeseeable?

Was it unavoidable?

Could reasonable redundancy have prevented the loss?

Did the contract define force majeure?

Was notice required?

37. Multi-Party SaaS Architecture

Modern SaaS frequently involves:

Customer

↓

SaaS provider

↓

Cloud infrastructure provider

↓

Subprocessor

↓

Third-party API

A service failure may therefore have several potential causes.

The customer may nevertheless have a contractual claim against the principal SaaS provider even where the provider relies upon subcontractors, depending upon the agreement.

38. Causation

Causation is often harder than proving breach.

Example:

Provider suffers a four-hour outage.

Customer claims:

“We lost €5 million.”

The court must ask:

Was the loss actually caused by the outage?

Would the transaction have occurred anyway?

Was the loss foreseeable?

Was there another cause?

Did the customer have backup systems?

Did the customer mitigate the loss?

Thus:

Breach ≠ automatic entitlement to all claimed losses.

39. Evidence in SaaS Litigation

Important evidence can include:

SaaS agreement;

licence schedules;

order forms;

SLA;

technical documentation;

audit logs;

user records;

API logs;

server logs;

uptime records;

emails;

support tickets;

incident reports;

cybersecurity reports;

source-code records;

invoices;

access-control records.

Cloud disputes are therefore heavily dependent upon digital evidence.

40. Audit Rights

Many enterprise SaaS contracts allow providers to audit:

number of users;

usage volume;

geographic use;

licence compliance;

unauthorised access.

A dispute may arise over whether an audit itself violates:

confidentiality;

data protection;

proportionality;

trade secrets.

The contract should therefore define the scope and method of audit.

41. Over-Licensing and Under-Licensing

Under-licensing

Customer uses:

500 users

but pays for:

100 users.

Provider claims additional fees.

Over-licensing

Customer pays for:

500 users

but actually uses:

50 users.

Customer may seek reduction or challenge automatic renewal depending on the contract.

42. Automatic Renewal

SaaS subscriptions often renew automatically.

Possible disputes include:

inadequate notice;

unclear renewal clause;

unreasonable renewal period;

increased price;

consumer unfairness;

failure to cancel correctly.

The validity of such clauses depends heavily on the applicable law and whether the customer is a consumer or business.

43. Competition-Law Dimension

Large SaaS providers may sometimes raise competition issues.

Examples:

tying SaaS with other services;

refusal to provide interoperability;

discriminatory access;

excessive switching barriers;

exclusive arrangements;

technical restrictions designed to prevent competitors.

However:

An ordinary SaaS licence breach is normally a contract/IP issue, not automatically a competition-law violation.

44. Remedies

A claimant may seek:

Contractual remedies

damages;

specific performance;

termination;

price reduction;

restitution;

service credits.

IP remedies

injunction;

cessation of infringement;

damages;

account of profits where available;

destruction/removal of infringing copies.

Data-related remedies

access;

correction;

deletion;

restriction;

portability where applicable.

Emergency remedies

interim injunction;

preservation of evidence;

temporary restoration of access where legally available.

45. Provider's Possible Remedies

If customer breaches the SaaS licence, the provider may seek:

unpaid licence fees;

additional usage charges;

damages;

injunction;

suspension;

termination;

deletion of unauthorised copies;

cessation of unauthorised access;

IP remedies.

But suspension and termination must comply with:

contract + mandatory law + applicable proportionality/unfair-term rules.

46. Customer's Possible Remedies

If provider breaches the agreement, the customer may seek:

continued service;

restoration of access;

damages;

service credits;

price reduction;

termination;

refund;

data export;

migration assistance where contract/law provides;

compensation for proven losses.

47. SaaS and Consumer Contracts

Where a consumer uses SaaS—for example:

cloud storage;

personal accounting;

online productivity software;

consumer AI service—

consumer protection law can become particularly important.

The provider cannot necessarily rely on every clause merely because:

“The user clicked I Agree.”

Mandatory consumer protections may override contractual terms.

48. SaaS and B2B Contracts

Enterprise SaaS contracts generally provide greater contractual freedom.

The parties can negotiate:

governing law;

jurisdiction;

arbitration;

liability caps;

SLA;

service credits;

licence metrics;

audit rights;

termination;

data return;

confidentiality;

cybersecurity;

indemnification.

Therefore, contract drafting is particularly important in B2B SaaS litigation.

49. SaaS Licensing and Arbitration

Large SaaS agreements often contain arbitration clauses.

A dispute may concern:

whether the arbitration clause covers IP claims;

whether termination invalidates arbitration;

confidentiality;

interim injunctions;

emergency relief;

governing law.

The scope of the arbitration agreement must therefore be analysed separately from the substantive SaaS licence.

50. Important Distinction: SaaS vs Software Sale

51. Major Legal Issues in a SaaS Breach Claim

A court should usually ask:

Step 1 — What is the contract?

Identify:

master agreement;

order form;

licence terms;

SLA;

DPA;

acceptable-use policy.

Step 2 — What right was granted?

For example:

100 users + internal business use + Europe.

Step 3 — What happened?

For example:

400 users accessed the platform.

Step 4 — Is there a contractual breach?

Step 5 — Is there also an IP infringement?

Step 6 — Is the term legally enforceable?

Step 7 — What loss occurred?

Step 8 — Was the loss caused by the breach?

Step 9 — Does a liability cap apply?

Step 10 — What remedy is available?

52. Hypothetical Example

Facts

A German company purchases SaaS software from a French provider.

Contract:

500 users;

internal business use;

no sublicensing;

99.9% uptime;

€100,000 annual fee.

The German company allows its subsidiary to use the platform.

The provider discovers this and immediately terminates the account.

Issues

Issue 1 — Was subsidiary use permitted?

Depends upon the licence definition of:

“Customer”, “Affiliate”, “Authorised User”.

Issue 2 — Was sublicensing prohibited?

If yes, potential contractual breach.

Issue 3 — Could provider immediately terminate?

Depends upon:

materiality;

notice;

cure period;

termination clause;

applicable national law.

Issue 4 — Can provider claim copyright infringement?

Not automatically.

There must be a relevant protected act.

Issue 5 — Can provider claim additional fees?

Potentially, if contract or applicable law supports the calculation.

Issue 6 — Can customer recover damages?

Potentially, if termination was wrongful and loss is proven.

53. Another Example: Provider Breach

A Dutch company pays €500,000 annually for a SaaS platform.

The provider promises:

99.95% availability.

The system experiences repeated outages.

The customer loses important transactions.

The customer can potentially argue:

contract

→ SLA breach

→ failure to perform promised service

→ causation

→ financial loss

→ damages/service credits/termination depending upon contract and applicable law.

This is primarily a contract/service-performance dispute, rather than a copyright case.

54. Key Case-Law Table

The strongest authorities for an actual licensing-breach question are IT Development and UsedSoft, while SAS Institute and Top System help determine the boundaries of lawful software use. The latter cases should not be described as ordinary SaaS contract cases.

55. Direct vs Analogical Authority

For exam or litigation analysis, the following distinction is safest:

Direct/very strong

IT Development v Free Mobile

→ software licence breach.

Strong software-licensing authorities

UsedSoft

→ licence/use/distribution.

SAS Institute

→ lawful software use and copyright boundaries.

Top System

→ lawful acquirer/error correction.

Related software/IP authorities

Bezpečnostní softwarová asociace

→ interface protection.

Nintendo v PC Box

→ technological protection.

SaaS-specific limitation

There is no general CJEU rule saying that every SaaS contractual breach constitutes copyright infringement.

That would be legally incorrect.

56. Ultra-Basic Revision Notes

SaaS

Software delivered as an online service.

Licence breach

Customer uses the software beyond the rights granted.

Provider breach

Provider fails to deliver the contracted digital service.

Main legal areas

Contract + copyright + digital-content law + GDPR + data/access law + competition law where relevant.

Important case

IT Development v Free Mobile

→ software licence breach can intersect with IP infringement.

UsedSoft

→ perpetual downloaded software licence ≠ automatically same as SaaS subscription.

SAS Institute

→ functionality ≠ automatically copyright.

Top System

→ lawful-acquirer rights can limit overly broad restrictions.

Main evidence

Contract + licence + SLA + logs + invoices + access records + technical evidence.

Main remedies

Damages + injunction + termination + restoration + licence fees + service credits.

57. One-Line Case Formulas

IT Development: A breach of a software licence can have both contractual and IP-enforcement consequences.

UsedSoft: Certain perpetual software licences can be subject to exhaustion, but this does not automatically make SaaS subscriptions transferable.

SAS Institute: Software functionality and programming languages are not automatically protected in the same way as copyright-protected program expression.

Top System: A lawful software acquirer may have legally protected rights concerning error correction.

Bezpečnostní softwarová asociace: Software interfaces require separate analysis of whether they contain protected expression.

Nintendo: Technological restrictions protecting software can interact with copyright law.

Ranks and Vasiļevičs: The resale of software licences must be analysed through the specific exhaustion rules and conditions.

VOB: Digital-use arrangements demonstrate that traditional copyright concepts must be adapted carefully to digital environments.

58. Exam-Ready Conclusion

Software-as-a-Service Licensing Breach Claims in Europe are fundamentally mixed technology-contract disputes. The starting point is the SaaS agreement: what software access was granted, to whom, for how many users, for what purpose, for what period and subject to what restrictions?

The second layer is European software copyright law. IT Development v Free Mobile is particularly important because it demonstrates that violation of software licence conditions can interact with intellectual-property enforcement. UsedSoft v Oracle establishes important principles concerning certain perpetual software licences, but its reasoning must be applied cautiously to SaaS because SaaS is normally a continuing service rather than a one-time transfer of a software copy. SAS Institute and Top System help define the boundaries of lawful software use. (InfoCuria)

The third layer is contractual remedies: damages, termination, service credits, injunctions, restitution and licence fees. The fourth layer includes GDPR, digital-content protection, cybersecurity, data portability and potentially competition law.

The central legal formula is:

SaaS contract + defined licence right + breach of that right + causation + legally recognised loss = potential contractual liability.

Where protected software rights are also violated:

Licence breach + relevant protected IP act = potential contractual + intellectual-property liability.

Most important exam point:
A SaaS licence breach is not automatically a copyright infringement, and a software copyright infringement is not automatically a breach of every contractual term. The court must separately identify the contractual obligation, the statutory/IP right, the breach, causation and the appropriate remedy.