Live Service Games Recht: Verträge & Modelle | IT-Medienrecht

Contractual Framework and Models for Live Service Games (Games as a Service)

The games industry is increasingly moving towards live service games or “Games as a Service” (GaaS). Unlike traditional video games, which are purchased once, GaaS models are constantly evolving. Content, functions, and even game mechanics can change or be expanded over time. This poses particular contractual challenges for providers, whether developer studios or publishers.

Contracts and general terms and conditions (GTC) must be adapted to these particularities. This is essential to avoid legal pitfalls and simultaneously meet player expectations. This blog post takes a detailed look at the contractual framework and typical models for live service games.

We differentiate between subscription models and one-off purchases with additional content. We also examine the legal requirements for ongoing services, such as updates, support, and new content. The relevance of SLA-like provisions, including availability guarantees and maintenance windows, will also be discussed.

Furthermore, we will look at termination regulations, especially in the case of continuing obligations. We will also highlight the differences in contract design between consumers and entrepreneurs. Finally, the relevant statutory provisions, such as Sections 312 et seq. and Sections 327 et seq. BGB on consumer rights for digital content, are presented and explained.

All of this is done in legal language yet practically. Our goal is to provide a comprehensible guide for founders and game developers.

Business Models for Games as a Service: Subscription vs. One-Off Purchase

Live service games can be monetized using different business models. Essentially, two models have become established: the subscription model and the one-time purchase model with additional content. Both approaches have different legal characteristics and obligations, which we explain below.

Subscription Models (Ongoing Memberships)

With the subscription model, the player pays a regular fee, such as monthly. This grants them access to the game and its ongoing content. Classic MMORPGs like World of Warcraft are examples, relying on monthly subscriptions. Modern services also purchase seasonal memberships.

Flat-rate offers such as Xbox Game Pass or PlayStation Plus can also be seen as subscriptions for a games library. However, these typically include a large number of games.

Characteristics of the subscription model:

• It is legally a continuing obligation. A continuous service (access to the game and regular updates/content) is provided in return for ongoing payment.
• As a rule, the user does not acquire an unlimited right to use the game. They only receive a time-limited right of use, linked to ongoing payment. If the subscription ends, the right to continue using the game also expires (provided there is no free-to-play mode).
• Content and updates are often included in the subscription price. The provider implicitly undertakes to keep the game functional and accessible for the duration of the subscription. They usually also commit to making it attractive with new content.
• For the provider, this means an ongoing contractual obligation. They must provide technical infrastructure (servers, etc.) and continuously make the contractually agreed game content available.

In legal terms, such a subscription is now regarded as the provision of a digital service over a period of time in the consumer relationship. Sections 327 et seq. BGB, in force since 2022, define these as contracts for digital products. An online game made available for use over a certain period is a digital product.

This can be either digital content or a digital service. A subscription typically involves a digital service. This includes the opportunity to play online, participate in a persistent virtual world, and access it.

Example: If a consumer takes out a 6-month subscription for an online game, the provider undertakes to grant access to the game for 6 months. This includes all planned updates and content during this period. In return, the user pays the subscription price (once in advance or monthly). Under the new law (Section 327 (1) BGB), this is a consumer contract for the provision of a digital product in return for payment. Both parties' obligations run over time: the provider performs continuously, and the customer pays continuously.

One-Off Purchase with Additional Content (DLCs, Season Passes, Microtransactions)

The alternative basic model is a one-off purchase of the game. This is often combined with optional, chargeable additional content. Here, the customer typically purchases a one-off license to use the basic version of the game. This business model, in turn, has various forms:

• Classic purchase + DLCs: The base game is purchased at a fixed price. Downloadable content (DLCs), such as expansions, new levels, or story packs, appear later. These can be purchased separately. Each DLC purchase is a separate contract, usually another purchase contract for digital content. The player can decide whether to invest additional money to unlock new content.
• Season Pass / Expansion Pass: This is a bundled offer. The user pays a certain amount in advance to acquire the right to a series of future DLCs or updates. A Season Pass often covers a season or a year and includes all expansions released during this period. Legally, the customer acquires several digital contents with a one-off contract. However, these are delivered at different times. This is also a continuing obligation, but with a one-off payment. The provider owes various service components spread over a certain period without further payments. Clear terms and conditions are essential here.
• Microtransactions and in-game purchases: Many modern games, especially free-to-play titles, involve small amounts spent on virtual goods, cosmetic items, loot boxes, or gameplay benefits. Each transaction is a purchase contract for digital content (e.g., virtual currency or a cosmetic skin). Although the game runs continuously as a platform, there is no subscription. The player pays as required. Legally, this results in many individual contracts for digital products, not one large permanent contract. Nevertheless, the terms of use of the game must frame these microtransactions. This includes rules for redeeming virtual currency and the availability of purchased items.

Characteristics of the one-off purchase model:

• The initial purchase of the game is a purchase agreement for digital content if distributed digitally. The buyer receives a permanent right to use the game in its version at the time of purchase. This is in the form of a license, usually unlimited in time. However, use may be effectively limited to the lifetime of the servers if it is an online-only game.
• Additional content such as DLCs or items extend the right of use. Each purchase of DLC is, in turn, a separate contract (contract for digital content).
• With a Season Pass or similar models, a contract is created with partial services over time. Here, the provider must deliver content over a defined period, similar to a subscription. The difference is no ongoing payment, but an advance payment. Nevertheless, the customer is entitled to subsequent delivery of future content once completed.
• With pure one-time purchase models, the provider is under no obligation to provide new content unless sold separately or promised. Many single-player games receive free updates or patches. However, new content packages are only delivered if the customer purchases them or has previously acquired them via a season pass.

From a legal perspective, the following also applies since 2022: If the customer is a consumer, the special rules of Sections 327 et seq. BGB for digital products apply. Once a game or DLC is purchased, it is subject to the regulations for digital content. It is worth noting that the legislator has introduced an update obligation for digital products, as we will discuss. Even a game sold once must, therefore, receive necessary updates to ensure contractual conformity.

Comparison and Legal Classification of the Models

The choice of business model significantly influences the legal classification of the contractual relationship:

• Continuing obligation vs. individual service: A subscription or season pass establishes a long-term service relationship. This entails, among other things, termination protection regulations and special warranty provisions. A one-off purchase with optional DLCs, on the other hand, consists of individual, self-contained service relationships.
• Types of contract: In the past, a one-off purchase was clearly qualified as a purchase contract (purchase of goods analogous to digital goods). A subscription was seen more as a service contract (ongoing service access to the game) or a rental contract (provision of a game for a limited period). Since the introduction of digital product law, these categories have blurred in consumer law, as a uniform framework applies to all digital content/services. Nevertheless, these types help understand the obligations. For a purchase, the focus is on the one-off transfer of a usage option. For a subscription, it's on the continued granting of usage.
• License rights: In both models, the customer generally does not acquire title to an item. Instead, they receive a license to use the software (the game). For a one-off purchase, this is usually a permanent license. For a subscription, it's a temporary license. These license conditions are defined in the EULA/AGB. It must be clearly regulated which rights of use the player receives and which they do not (e.g., no right to edit the game, resell it, etc.). This ties into ownership of software principles.
• Additional purchases in the subscription model: Even subscriptions do not exclude microtransaction-type purchases; many MMOs also have item stores. Legally, a continuing obligation (the subscription) and individual purchase contracts (microtransactions) run in parallel. The terms and conditions should clarify that access depends on the subscription. Purchased items can only be used within the active subscription. They do not give rise to a claim for compensation if the subscription ends. This must be addressed in the contractual terms and conditions.

Developers and publishers should decide at an early stage which model, or combination, to pursue. This decision provides the framework for all further contractual arrangements. Both approaches must be carefully implemented contractually, especially in light of current consumer protection laws.

Ongoing Performance Obligations: Updates, Support, and New Content

A central feature of live service games is the ongoing support and development of the game. Players expect a dynamic experience with regular improvements, bug fixes, and new content. This results in legal obligations for the provider that go beyond the initial sale.

In this section, we examine which performance obligations must be fulfilled on an ongoing basis and the legal requirements in this regard.

Legal Obligation to Update (§ 327f BGB)

Since January 1, 2022, German law expressly requires digital products to be updated. This change is particularly important for games as a service. Section 327f BGB stipulates that the supplier (entrepreneur) must ensure the consumer is provided with updates required to maintain the contractual conformity of the digital product during the relevant period. This includes, in particular, security updates.

What does this mean concretely? A digital game must be maintained for a certain period. It must comply with the features agreed at contract conclusion and be free of defects impairing its use. Contractual conformity includes subjective requirements (e.g., specific agreed features) and objective requirements (usual standard and expectations for such a game).

This means if a security-critical error or serious bug occurs, the provider is legally obliged to provide an update to fix it. They must also provide compatibility updates. For example, if a new operating system update makes the game unusable within the relevant period. This applies to the extent reasonably expected of the game.

The “relevant period” for the update obligation is not fixed by law but depends on circumstances. For a permanent contract (e.g., subscription), it's the entire contract term. For a one-off purchase of a digital product without a limited use period, the legitimate expectation of the consumer plays a role.

Section 327f (1) sentence 3 BGB states that, unless otherwise agreed, the trader must provide updates for the period the consumer can expect. This is based on the digital product's type and nature and surrounding circumstances. In many cases, at least the statutory warranty period (2 years) can be assumed.

Practically, this means that if an online game is purchased, relevant updates (patches, security fixes) are expected for a typical period. This could be two years from release, even without a subscription. This period is often determined by the usual product lifespan or manufacturer statements (e.g., “we will support the game at least until…”).

Important: The update obligation does not include constantly providing new content or features (“upgrades”) beyond the original state. It serves to maintain the contractually owed condition. For example, a provider must close security gaps and fix game balance problems. But they don't have to add new levels for free if not part of the service commitment. A paid DLC with new content doesn't fall under the legal update obligation; this would be a voluntary additional offer.

However, the boundary can blur if new content is necessary to fix bugs or maintain playability. For example, if a game mode is removed and the multiplayer function becomes useless without new content. Legal expertise in contract design for game content is crucial here.

It should also be noted that the provider must inform the consumer that updates are available. This is usually done automatically via the game launcher or platform (e.g., Steam update notifications). The consumer, in turn, is obliged to install the provided updates. Otherwise, they may lose warranty rights regarding any resulting defects (Section 327f (2) BGB).

This means if the player ignores an important update and problems arise, they cannot hold the provider responsible.

Example: A developer sells an online action game as a one-off purchase. Eight months later, a serious security vulnerability emerges. It could allow attackers to take over accounts. Although not a subscription, the developer must provide a patch (update) to close this gap and inform players. Failure to do so constitutes a legal defect or security flaw, triggering warranty claims. The developer must also ensure server-side adjustments are made within the usual usage period. Otherwise, the game could become unplayable.

Ongoing Content Support and Enhancements

Beyond minimum legal requirements, live service game users regularly expect new content, events, and expansions. This raises the question: To what extent is a provider contractually obliged to provide such content updates?

As a general rule, there is no obligation to provide new content without an express agreement. If a game is sold “as is” or as a subscription, the provider primarily owes the maintenance of agreed functions, not constant expansions. However, many live service games advertise with statements like “constant new adventures” or “new items every month.” They also publish roadmaps with planned expansions.

Such announcements can become relevant under contract law. They shape consumer expectations and can be considered a quality agreement in individual cases. For example, if a season pass promises “four expansions within a year,” this becomes part of the contractual obligation to perform.

With subscription models, it is often implicit that something is offered continuously. Although not all content may be guaranteed in advance, basic further development is part of the contract's nature with ongoing fees. A complete standstill in development could be seen as bad fulfillment of the contract. This is especially true if the subscription was advertised with ongoing development.

In extreme cases, such as a provider continuously charging for a game but providing no maintenance or new content, users may have rights. This applies if ongoing content was expected. They could be entitled to extraordinary termination or a reduction in payment, depending on the circumstances. Providers should therefore provide clarity here:

• Transparency in communication: It is advisable not to make exaggerated promises that cannot be kept. Content that is firmly planned can be named, but always with reservations for potential changes to the development plan.
• Contractual reservations: The terms and conditions or terms of use may state that no specific number or frequency of content updates is owed. They may also state that further development is at the provider's discretion. Nevertheless, a provider offering a subscription should be aware that complete passivity is commercially and legally risky.
• Season Pass as a contract for future services: Here, you have clear promises and should fulfill them. If a promised extension doesn't materialize, there's a breach of performance obligation. This is the non-delivery of a partial service owed. It can lead to a claim for supplementary performance, compensation, or partial repayment. Contracts for future digital content should always be planned realistically. For example, include clauses for delays (“release may be postponed for development reasons”). Also address how to deal with failures (“if an announced expansion is not released, the customer will receive a replacement, e.g., another DLC or a pro rata refund”).

To summarize: Although ongoing content is essential for business in GaaS models, it is only legally binding if it has become part of the contract. The legal obligation to update only requires the maintenance of the target status and security. Everything else is a matter of contract design and product strategy. For specific contracts, consulting IT contract law experts is recommended.

Technical Support and Customer Service

In addition to software updates and new game content, users often expect support services. This includes help with technical problems, account support, and moderation for player conflicts. Legally, the question arises as to the extent of a provider's obligation to provide such support.

The consumer contract for digital products does not explicitly stipulate that support must be provided. However, a lack of support can result in a defective product. This occurs if a problem prevents use, and the provider doesn't help resolve it. For example, a bug deletes inventory items. The provider patches it but refuses to restore lost items or compensate the customer. In this case, the user could argue that the owed usage option was not guaranteed.

It is customary and advisable from a business perspective to make certain support commitments in the terms of use. However, it's also important to set limits. For example, specify that support is only offered via certain channels (ticket system, email). Clarify that it's not necessarily 24/7, and there's no guarantee of a specific response time. This allows providers to control effort and manage expectations.

It is important that providers define clear processes for dealing with support-relevant cases, for example:

• Account problems: For example, the recovery of a hacked account. The update obligation and security obligation also apply here. If many accounts are hacked, security updates must follow. The contract should stipulate that the user is jointly responsible for the security of their access data. However, the provider will take certain measures if unauthorized access is suspected (blocking, notifying the user).
• Refunds/in-game purchase problems: Users might complain that a purchase hasn't been credited. A support process must be in place. In terms of contract law, the GTC should state how such errors are corrected (crediting the item or refund). It should also specify that the user must report such cases promptly.
• Player behavior and moderation: In online games, ongoing community maintenance is also crucial. Although this primarily concerns the terms of use (e.g., community guidelines, chat moderation), it's part of the ongoing service. If a game promises "moderation" or a non-violent gaming experience, the provider must intervene appropriately in case of violations. However, there is usually no absolute obligation to moderate. Instead, there's a right to take action based on reports. More on this later under Termination (topic: Blocking in the event of violations).

To summarize: Adequate technical support is a de facto standard and expected for live service games. Legally, however, the scope can be freely defined as long as the use of the game remains guaranteed. Clear regulations in the terms and conditions can define which support services are included and in what form. The impression should never be given that the user is completely on their own, as this could lead to a breach of secondary obligations. Additionally, reliable support significantly boosts customer satisfaction and contributes to the service's success.

Service Level and Availability: SLA-Like Agreements

Live service games typically run on central servers or in the cloud. The availability of these services is crucial for players. A server outage or lengthy maintenance can lead to frustration and, in the worst case, legal disputes. For example, if paying customers are unable to play for months.

In traditional B2B contracts for IT services, detailed service level agreements (SLAs) regulate availability, response times, and compensation. These are common. In the B2C sector (contracts with consumers), such formal SLAs are rare in end-user T&Cs. However, some SLA elements should still be considered.

Availability Guarantees and Uptime Commitments

With online games, it is inherent that 100% availability cannot be guaranteed. Technical maintenance, updates, or unforeseen server problems inevitably lead to downtimes. From a legal perspective, the question arises: Does the provider have to guarantee a certain level of availability? And what happens if this is not met?

Contractually, it makes sense to clearly regulate availability. Many general terms and conditions for online games contain a clause stating: “The provider endeavors to ensure high server availability, but does not guarantee continuous availability. In particular, there may be interruptions due to maintenance work, updates, or force majeure.” Such a clause should prevent every default from automatically being considered a breach of contract. Important: In the B2C sector, such a clause must be appropriate. A complete exclusion of liability for outages could be problematic if it undermines the legitimate expectations of players. However, most players do not realistically expect 24/7 uptime without interruption, as long as outages remain within normal limits.

No express guarantee: If the provider hasn't expressly guaranteed, e.g., "99% uptime," availability is measured by the objective requirements for such a service. The law (Section 327e BGB) requires a digital product to meet objective requirements. This includes having the same durability and performance characteristics as usual. For an online game, it's objectively expected to be available most of the time monthly. A permanently unstable service, e.g., daily multi-hour outages, would likely be considered defective, even without specific clauses.

It is therefore in the provider’s interest to give at least an indicative assurance of availability. This sets a benchmark but must include sufficient exceptions. Example: “We are aiming for an availability of 98% on a monthly average. This does not include announced maintenance windows. Otherwise, there is no claim to constant availability.” Such a passage creates transparency and manages expectations effectively.

Maintenance Windows and Updates

Regular maintenance periods are common for online games. They are used to install server updates, maintain databases, or apply new patches. Legally, maintenance windows should be reserved in the terms of use.

Typically, a clause like this is included: “The provider is entitled to interrupt the service at reasonable intervals for maintenance purposes. As a rule, maintenance work is carried out during periods of low usage and, where possible, announced in advance.” This is important to clarify that such interruptions are contractually permissible and do not constitute a defect.

In practice, many game providers announce major updates or planned downtimes. They do so via their platform, email, or official website/forums. Although prior notification is not legally mandatory, it is good practice. It can be seen as a secondary obligation arising from the contractual relationship, a duty of consideration. Players should have the opportunity to prepare for these interruptions.

Emergency maintenance, such as hotfixes, naturally cannot be announced well in advance. The contract should allow flexibility, stating that an immediate interruption can occur in urgent cases. This ensures functionality or security. Since this ultimately benefits users (security, rapid troubleshooting), it is generally unproblematic.

A special feature of GaaS is that updates themselves can be part of the contract. They are included in the subscription, while individual purchases include at least the mandatory updates. The provider is, therefore, not only entitled but sometimes obliged to interrupt the service to install updates. The user must accept this but should be informed.

Dealing with Malfunctions and Failures

Despite all precautions, unforeseen disruptions can occur. These include server crashes, DDoS attacks, or software errors that render the game unplayable. The legal relevance lies in how these malfunctions are classified and what rights the user has.

In principle, if the user cannot use the game due to server issues or other provider-side problems, there is a breach of performance obligation. The provider fails to deliver the promised service (access to the game). However, the law grants the provider certain tolerances, especially if they are not at fault. A short downtime due to technical issues is likely considered an insignificant defect or temporary impossibility without liability for damages, provided it's rectified promptly.

However, if a significant part of the playing time is lost, for example, if an online game is unavailable for weeks, the user may assert warranty rights. For a subscription, the user could reduce the subscription payment (reduction for downtime) or, if recurring, terminate the contract without notice. For a one-off purchase relying on online functionality, withdrawal from the purchase could even be considered if the game permanently fails to work as promised.

The general rules apply: First, the right to subsequent performance (repair of servers, which the provider will naturally attempt). If this fails within a reasonable time, further rights like withdrawal or reduction follow. For complex cases, adapting GTCs for SaaS solutions might be necessary.

Contract drafting: To deal with such cases, GTCs should address the following points:

• Reference to force majeure: Many GTCs state that the provider is not liable for failures caused by force majeure or circumstances beyond its control (e.g., natural disasters, external attacks).
• No liability for loss of data: With online games, there's always a risk of lost progress or items due to server problems. A clause can state that the provider strives for data security but assumes no liability for lost game saves, unless due to intent or gross negligence. Caution: For consumers, liability limitations must be carefully formulated, as discussed in the section on liability and general terms and conditions for consumers.
• Compensation as a gesture of goodwill: Instead of contractually promising fixed compensation, which would be risky, many providers handle this accommodatingly. For example, they might credit subscribers with part of a free month during long outages or distribute an in-game bonus. This strengthens customer loyalty without creating a legal obligation. Contractually, it is better not to establish rigid compensation rules, as this can quickly lead to disputes over when a claim arises.

Service Level in the B2B Context

Although this article focuses on contracts with end-users, service level agreements in the true sense are primarily relevant in B2B contracts (between companies). This is conceivable, for example, if a development studio outsources server infrastructure to a service provider. In this case, an availability of 99.5%, for instance, is agreed internally with the server hoster.

Alternatively, if a company licenses a game for internal purposes, such as gamification software, specific performance parameters could be defined in the contract. For end customers, a detailed SLA breakdown (with percentages, ticket priorities, penalties for non-compliance) would be overwhelming and legally unusual in mass business. Nevertheless, partial aspects of an SLA, as described above, can be usefully incorporated into the GTC. This creates clarity and makes obligations manageable. This often requires specialized cloud contracts for startups.

Term and Termination of Continuing Obligations

A key issue with games as a service is the term of the contract and the conditions under which both parties can terminate it. Subscriptions, in particular, being typical continuing obligations, are subject to numerous consumer protection rules that have tightened recently. However, other contracts, such as season passes or the continued operation of a purchased online game, also raise the question of termination rights and contract termination.

This section explains the most important aspects: notice periods, forms of termination, extraordinary termination, and new requirements like the termination button. We also examine situations where the provider discontinues the service or excludes players for good cause.

Ordinary Termination and Contract Terms

Legislation now sets clear limits for subscription contracts with consumers. Since March 1, 2022, the Fair Consumer Contracts Act has been in force. It specifically regulates automatic contract renewal and notice periods. Game subscriptions must also meet these requirements:

• A minimum contract term of up to 24 months is permitted (Section 309 No. 9 BGB). However, many games use more flexible models (monthly termination) to avoid deterring customers. It is legally permissible, for example, to offer a discounted annual subscription.
• After the initial term, a contract may not simply be tacitly renewed for the same term without a termination option. It was common practice, e.g., 1 year + automatic renewal for another year if no notice was given 3 months in advance. This is no longer permitted for consumers. Instead, customers must have the right to terminate the contract at any time after the minimum term with a maximum of one month's notice. This means that after 12 months, for instance, the contract converts into an open-ended contractual relationship, terminable by the customer with one month's notice (Section 309 No. 9 BGB new version).
• Automatic renewal is only allowed as an indefinite extension, not as a rigid fixed renewal period. And the notice period may not exceed 1 month. This applies both for termination at the end of the initial term and thereafter.

Example: A game offers a 12-month subscription. Previously, T&Cs would state: "Renewed for a further 12 months if not canceled 3 months before expiry." Under the new law, it must read: "Renewed indefinitely after the minimum term. After 12 months, the contract can be terminated by the customer at any time with one month's notice." As a rule, the provider must also observe a notice period if it wishes to terminate the contract properly. This rarely happens with current subscriptions, as providers are more likely to terminate if discontinuing service or for good cause.

For monthly subscriptions without a fixed term, there is an open-ended contract. This must be terminable at any time for the next payment period. Most general terms and conditions already provide for this, e.g., termination at the end of the current month. Here, legal requirements are usually automatically fulfilled as long as no impermissible termination hurdles are included.

It is important to implement these provisions properly in the contract. A clause that does not grant the consumer a sufficient right of termination after the initial term would be invalid. In such cases, the law would apply directly, meaning the customer could terminate the contract at any time, which must be granted anyway.

Cancellation Button in Online Sales (Section 312k BGB)

In online business with consumers, the so-called cancel button has been mandatory since July 2022. This applies to all ongoing contracts concluded online, where the trader must provide a permanent service for payment. This specifically covers game subscriptions made via a website or platform.

What is the cancellation button?
In accordance with Section 312k of the German Civil Code (BGB), a trader offering such a contract online must provide a button on their website for consumers to cancel the contract. The label should be clear, e.g., “Cancel contract now.” Clicking this button leads to a confirmation page. Here, the consumer declares termination, usually via a form with details like name, email, and contract number. After submission, the provider must immediately confirm the termination electronically (e.g., by email).

For game providers, this means that anyone selling subscriptions on their own website must implement a cancel button. Failure to do so risks warnings from competitors or consumer protection associations. Early court decisions, such as from the Cologne Regional Court, have shown serious consequences for infringements.

Exceptions: The cancel button is not required for contracts only terminable in writing (rare in games) or for financial services. A games subscription does not fall under these exceptions. If the subscription is processed via an app store or platform that provides its own cancellation function (e.g., Apple App Store), the individual provider doesn't need to offer the button on its homepage. However, it must be on its own website if the subscription was concluded there. It's advisable to indicate how to cancel in FAQs and place the button prominently (legally “easily accessible”).

Extraordinary Termination (Good Cause)

In addition to ordinary termination, both user and provider always have the right to extraordinary termination for good cause. This is enshrined in the German Civil Code (Section 314 BGB for continuing obligations) and can be specified in the contract.

Good cause exists if the terminating party cannot reasonably be expected to adhere to the contract until its regular end. In online games, typical important reasons include:

• For the player (customer):
  • Prolonged downtime or significant game deterioration without improvement. For example, if the game is unusable for weeks or essential functions, like a core multiplayer mode, are discontinued.
  • Serious contract breaches by the provider, such as trust-destroying data protection scandals. Or sudden, unilateral, legally baseless changes to the GTC that harm the user. (Note: Unilateral changes to digital products are regulated in Section 327r BGB, discussed later).

• For the provider:

  • Violation of the terms of use by the player, especially in cases of significant or repeated breaches. Well-known examples include cheating (interference violating fair play) or toxic behavior (serious insults, hate speech, despite warnings). In such cases, the provider effectively terminates the user contract and blocks the account. For anti-cheat software, legal risks related to data protection also arise.
  • Default of payment for subscriptions: If the user fails to pay despite a reminder, the provider can terminate the contract for cause or block access. Most contracts stipulate that the account is temporarily frozen for late payment and can be terminated after a notice period.

The GTC should list the most important reasons for termination by example, at least on the provider's side. Providers typically initiate extraordinary termination. Players can usually terminate or let their subscription expire, so they rarely need this. A common clause is: “The provider is entitled to terminate the user relationship without notice for good cause. Good cause shall be deemed to exist in particular if the user breaches material contractual obligations or rules of conduct – such as… [list: unauthorized hacks, circumvention of copy protection, multiple insults to others, etc.] – and does not cease despite a warning (or is so serious that a warning is unnecessary).”

In the event of justified extraordinary termination by the provider, e.g., a permanent ban for a cheater, the user is not entitled to a refund of any fees already paid, unless otherwise agreed. Most general terms and conditions stipulate that any remaining credit expires, and the user loses their account, including virtual goods. However, these harsh consequences must be proportionate to the severity of the violation, which is why a prior warning is often required, except in serious cases.

Conversely, if the user terminates for cause because the provider doesn't deliver the service, they can demand compensation or reimbursement, e.g., a pro-rata payment back for the remaining term. This stems from general law on service disruptions. If a customer justifiably terminates due to poor performance, they are treated as if they terminated at that moment. No further payment is due, and advance payments for the future must be refunded. Damages may be claimed if the customer suffered loss due to the defect, e.g., costs to acquire a replacement game.

Contract Amendments and Discontinuation of the Service

A particular aspect of live service games is the possibility that the provider may change the game concept or cease operations altogether. Many reasons exist: economic failure, successor games, technical changes, or strategic realignment. From the user’s perspective, this is dramatic. They may have invested money (purchase price, subscription, microtransactions) and can now no longer use the game.

Unilateral changes to the current service:
The new law in Section 327r of the German Civil Code (BGB) contains provisions on when and how a provider may make changes to digital products. For a contract for permanent provision (i.e., subscriptions, season pass, etc.), the following applies:

• The contract must allow for changes and provide a valid reason (Section 327r (1) No. 1 BGB). Valid reasons can include technical necessities, adaptation to a changed environment (e.g., new legal requirements, safety-relevant changes), or, to a certain extent, further development to improve the product.

• The change must not result in additional costs for the consumer (Section 327r (1) No. 2). This means you cannot suddenly charge for content that was previously free, without the customer's consent.
• The consumer must be informed clearly and comprehensibly (Section 327r (1) No. 3) about the change.

Particularly critical are changes that negatively impact the user. This applies to the game's accessibility or usability (Sections 327r (2) and (3) BGB). For instance, if the provider removes a popular game mode or reduces graphics settings, making the game significantly less attractive. In such cases, the consumer has a special right of termination. They can terminate the contract free of charge within 30 days of the change (Section 327r (3) BGB), provided the impairment is not insignificant. This right can only be excluded in few cases, e.g., if the change is due to a legal obligation (e.g., legal prohibition of certain content – Section 327r (4)).

In practice, this means: If you reserve the right to make substantial changes to the game (common in online games, e.g., major gameplay revisions), you should
a) clearly formulate this reservation in the contract (including reasons like “improvement of the game experience, adaptation to player numbers, balancing…”),
b) announce changes in good time,
c) grant customers the special right of termination or point this out.

Although customers rarely cancel to avoid an unpopular change, this legal option must be available. For a subscription, they could cancel at the time of the change and claim back any overpayments if paid in advance.

Discontinuation of the game (server shutdown):
Eventually, an online game is discontinued. Legally, this is tricky, especially for free-to-play or paid games without subscriptions. Players may have invested money in in-game purchases that become worthless overnight. Contractually, you should reserve the right to discontinue the service, with reasonable advance notice. No special law applies beyond general fiduciary duties and termination rules. For subscriptions, the provider can terminate all contracts with due notice. The situation is more difficult for players who purchased permanent access (e.g., lifetime access or single player with compulsory online access) – they have a permanent right of use, not a recurring contract. Such decisions can impact exit strategies for startups.

Some general terms and conditions of online games contain clauses such as: “We reserve the right to discontinue the online operation of the game at our own discretion. We will inform you at least X weeks/months in advance. Any subscriptions still running will be refunded on a pro rata basis from the date of discontinuation.” Such clauses are permissible if they comply with reasonable deadlines. The consumer must have the opportunity to use up their credit balance or mentally adjust.

For online-only games without a subscription, it is legally disputed whether deactivation shortly after purchase constitutes a defect. With the Digital Content Directive, one could argue the product no longer meets objective quality (no access), leading to a warranty case. Deactivation without replacement within the first 12-24 months after purchase is likely problematic. Therefore, a provider selling a server-dependent game should clearly state that unlimited availability is not guaranteed. Nevertheless, the provider must comply with the update obligation and maintain service for a reasonable period to avoid a defect of title. Ultimately, service can be discontinued after a few years, ideally by contractually limiting service or through transparent communication.

Right of Withdrawal vs. Termination

A brief digression on the right of withdrawal, often confused with termination: The right of withdrawal per Sections 312g, 355 BGB allows consumers to cancel an online contract within 14 days without cause. This applies to digital content and services, like game purchases or subscriptions, unless the consumer has validly waived this right.

There are special features for digital products:

• Digital content (download games, DLCs): The right of withdrawal expires if the trader has begun contract execution after the consumer expressly agreed to immediate execution and confirmed loss of their withdrawal right (Section 356 (5) BGB). Practically, when buying a download, the customer must check a box like “I expressly request immediate provision of content and understand I lose my 14-day right of withdrawal” before downloading. If not, the customer could theoretically download and cancel within 14 days, opening avenues for abuse as digital goods cannot be "returned" traditionally.
• Digital services (online subscription): The situation is similar but not identical. For services, the right of withdrawal expires if the service is fully provided and the consumer's consent and knowledge of losing the right were obtained beforehand (Section 356 (4) BGB). However, a subscription is not "fully provided" within 14 days. Theoretically, a consumer could subscribe, use it for 10 days, and cancel. They would then owe compensation for services already provided if immediate start was requested (Section 357 (8) BGB). Many providers take precautions, treating subscriptions like digital content for revocation. This means obtaining consent for immediate activation and waiver of the right. Legally, this is complex as a subscription isn't immediately fully provided. A consumer-friendly approach would be to allow withdrawal but charge pro-rata, though this is organizationally complex. Many platforms (Steam, PlayStation Store) have more accommodating refund policies, e.g., Steam's 14-day return for <2 hours playtime.

For the provider, this means providing correct information about the right of withdrawal in sales (website or launcher). If desired, obtaining the waiver must be done properly to ensure legal certainty. However, the right of withdrawal concerns contract conclusion, not ongoing termination. After 14 days, only normal contract termination rules apply.

Conclusion on this point: Termination ends an ongoing contract for the future, while revocation cancels a contract shortly after conclusion. Both must be observed. When drafting terms of use, our law firm ensures correct integration of the cancellation policy and proper implementation of the waiver of the right of cancellation if immediate service provision is desired. This also extends to aspects of T&Cs and compliance in blockchain games.

Differences in Contract Design: Consumer vs. Entrepreneur

When planning contractual documents—be it general terms and conditions, license agreements, or terms of use—it is essential to differentiate the target audience. Is the offer aimed at consumers (Section 13 BGB) or entrepreneurs (Section 14 BGB), or possibly both? Consumers enjoy far-reaching legal protection that cannot be overridden to their disadvantage. In B2B business (business-to-business), there is much more freedom in contract drafting. Here we summarize the most important differences and obligations when drafting contracts with consumers versus entrepreneurs.

Contractual Clauses and GTC Control

The AGB control according to §§ 305 ff. BGB (German Civil Code) applies strictly to consumer contracts. Many clauses permissible in B2B contracts are invalid for consumers. Examples:

• Limitations of liability: Liability towards consumers for bodily injury or gross negligence and intent may not be excluded or limited. Liability for slight negligence must also be accepted for breaches of material obligations. In B2B, liability can be limited more comprehensively (e.g., exclusion for indirect damage, for slight negligence generally, capping to a certain amount). Although extremely far-reaching exclusions could still fail under Section 307 BGB, courts are more reluctant to invalidate clauses between two entrepreneurs.
• Warranty exclusion: For consumer goods purchases or digital products for consumers, it is prohibited to exclude or shorten statutory warranty rights. The warranty period for consumers for digital products is generally 2 years (for permanent provision: for the entire period, see Section 327j BGB). Any attempt to shorten this or exclude defect liability in GTC is invalid. In B2B, the warranty period can be shortened to 1 year or certain defects excluded. For example, license agreements between entrepreneurs often state: “The software is provided as is, warranty for material defects is excluded, unless fraudulently concealed.” Such clauses are generally permissible between entrepreneurs but unthinkable for consumers.
• Notice periods and contract term: As explained, rigid renewal clauses and long commitment periods are invalid only in the consumer sector per Section 309 BGB. In B2B contracts, a 36-month contract with an automatic 12-month extension and 3-month notice period could be agreed. Section 309 BGB does not directly apply. However, a residual risk exists that courts may classify such clauses as unreasonably disadvantageous to companies (Section 307 BGB), but the hurdles are high. Generally, B2B has more freedom to create planning security through longer terms.
• Fictitious consent and communication: Some GTC clauses attempt to force or assume user behavior. For example, "If the user remains silent after a change, this is deemed consent." Such fictitious clauses are often inadmissible for consumers unless legally permitted. For example, Section 308 No. 5 BGB prohibits fictitious declarations by the contractual partner. In B2B transactions, such constructions are more likely if the other party accepts them. Here, the law relies more on the contracting parties' own responsibility.

Tip: If your game can be used by both consumers and entrepreneurs (e.g., an educational game licensed to private customers and schools), consider creating separate contractual terms for both groups. Alternatively, differentiate between them within a single set of GTC. For example, use clauses like: “The following provisions apply additionally/exceptively to consumers…; the following provisions apply instead to entrepreneurs…” This way, a shortened warranty can be ordered only for entrepreneurs, while consumers receive statutory regulation.

Information Obligations and Transparency

A large number of statutory information obligations apply when dealing with consumers. Some important ones are:

• Imprint obligation: A commercial online offer (website, app) must have an imprint with mandatory information (name, address, contact, authorized representative, registration number, etc.), per Section 5 TMG. This would also make sense for business customers but isn't legally mandatory as it's a consumer protection standard. In practice, every reputable company has an imprint, regardless of B2C or B2B.
• Provider identification in the contract: For consumer contracts, the customer must be clearly informed of the contractual partner's identity, contact options, etc., before contract conclusion (Section 312d BGB in conjunction with Art. 246a EGBGB). This is similar to the legal notice, but it should also be clear in the ordering process who the contract is with. This is crucial for fair pricing for startups.
• Product information and contract content: Especially for digital content, Art. 246b EGBGB (information requirements for consumer contracts for digital products) requires detailed pre-conclusion information. This includes product description, functionality, interoperability, provision duration, update conditions, contract duration, termination terms, payment modalities, and if applicable, the right of withdrawal or its expiration circumstances. These extensive, legally prescribed information obligations are often covered by "pre-contractual information" pages or in the general terms and conditions. These legal obligations don't apply to pure B2B sales, but for transparency, clear information is always advisable.
• Linguistic comprehensibility: T&Cs must be clearly and comprehensibly formulated for consumers (Section 307 (1) sentence 2 BGB). Unclear or surprising clauses may be invalid. In B2B, comprehensibility is still important, but more technical or legally formulated texts are tolerated. It's assumed entrepreneurs have understanding or legal counsel. For consumers, legal terms should be avoided or explained, and sentences kept clear.

Especially for startups and developers new to the market, fully complying with legal information obligations is a challenge. Our experience shows that withdrawal instructions, ODR Regulation information, and data protection details are often incomplete or incorrect. Legal support ensures all necessary elements are in place to avoid warnings.

Warranty and Liability in the B2B Context

While consumers have comprehensive warranty rights, as mentioned, these can be largely controlled contractually in B2B relationships. For example:

• Duty to inspect and give notice of defects: Section 377 of the German Commercial Code (HGB) applies between merchants. If an entrepreneur buys a digital product, like a software license, from another entrepreneur, they must inspect it immediately after delivery and report any defects. Failure to do so deems the product approved, and obvious defects can no longer be claimed. This principle can analogously apply to digital content. In general terms with entrepreneurs, this defect notification obligation can be specified or extended. For example, requiring regular inspections for continuing obligations. There's nothing similar for consumers; no early defect notification obligation exists. However, under new law, the burden of proof reversal for defects is reduced to 12 months, which is a different matter. This is a common point in SaaS company contracts.
• Exclusions of liability: In purely commercial contracts, clauses like: “Liability for loss of profit is excluded. Liability is limited to the fees paid by the customer within 12 months.” are common. Such limitations are usually effective in B2B contracts, provided they don't undermine core obligations. For consumers, such a limitation would be ineffective, at least for slightly negligent breaches, concerning core obligations.
• Shortening the limitation period: The limitation period for warranty claims in sales contracts between entrepreneurs is legally 2 years. However, this period can be shortened in general terms and conditions with entrepreneurs, e.g., to 1 year from software delivery. This is common in software license agreements. For consumers, shortening the warranty period is not permitted. They have at least 2 years, and even longer for ongoing performance (the period starts after provision ends and runs for at least 12 months, see Section 327j BGB).

Data Protection and User Accounts

There are also differences in handling personal data and user accounts, depending on whether consumers or companies are involved:

• Data protection consents: For data collected in or around the game (tracking, marketing consents, newsletters), consumers are particularly protected by GDPR and TTDSG (for cookies). Informed consent and opt-ins are required. These laws also apply to company employees using software, but B2B data is often processed under a different legal basis (contract fulfillment with the company). From the game provider's perspective, GDPR must be complied with in both cases. The difference lies more in the relationship's nature. For end consumers, there's a direct obligation to fulfill all information rights (GDPR Art. 13). For company contracts, information often goes to the company, which then informs its users. Gaming companies should always have data protection declarations ready for all users, private or business. This is also relevant for data protection in esports.
• User account registration: For consumers, the registration process must ensure proper inclusion of terms and conditions and revocation information. For companies, separate admin accounts might exist. This isn't a legal distinction, but practical. B2B customers often have different account structures (e.g., a main account with multiple employees). These differences must be reflected in the terms of use. For example: “The customer may assign user accounts to its employees to the agreed extent, but remains responsible for their compliance with terms of use”—a typical clause in a B2B software contract.

Summary of the Differences

Contracts with consumers are heavily regulated. Many clauses are only possible to a limited extent, statutory rights may not be undermined, and numerous mandatory information and protection mechanisms exist (revocation, termination button, update obligation, warranty provisions). Contracts with entrepreneurs can be negotiated more individually and may sometimes disadvantage one side, as the assumption is both parties negotiate equally.

For a game startup planning to serve both private individuals and corporate customers, drawing up two sets of T&Cs is ideal. However, most entertainment games target consumers. In this case, T&Cs must be formulated in a consumer-friendly way and comply with mandatory rules. If the game is solely for companies (rare for entertainment, perhaps for gamification software or B2B training platforms), the wording can be freer. Still, remember that clear rules avoid misunderstandings and strengthen business relationships.

Our law firm always checks the GTC to ensure the target group is correctly considered. We adapt the wording to prepare you for both scenarios.

Integration into License Agreements, Terms of Use, and Platform Guidelines

The points described above, from business models to update obligations and termination rules, must be incorporated into specific contractual documents. Several levels of contractual terms are typically relevant for games as a service:

1. End User License Agreement (EULA) or general terms of use for the game.
2. Platform conditions if the game is distributed or operated via third-party platforms (Steam, Epic, app stores, console networks).
3. Possible license agreements with partners (publisher-developer, or between developer and engine provider, etc.). These play a marginal role here but can influence background obligations, e.g., if a publisher demands certain service commitments from the developer. For more on this, see international publishing contracts.

The focus here is on the T&Cs/EULA for players and how to incorporate the content points explained above, as well as coordination with platform guidelines.

Design of the End User License and Terms of Use

An EULA (End User License Agreement) is essentially the contract that grants the end-user rights to use the game and defines usage rules. For online games, the EULA and online terms of use are often combined. This is because it covers both the software license and the use of the service (account, online world).

We have already addressed important content that must be regulated in such terms and conditions throughout this article. Here we summarize what should be included from a licensing and contractual perspective:

• Scope of license: It must be clearly defined what the user is allowed to do. E.g.: “The provider grants the user the simple, non-transferable right to download and install the client software for the game and to use the game for personal use.” For a subscription, the license is granted for a limited period (duration of the subscription). For a purchase, the license is unlimited, but often with restrictions (e.g., “as long as we offer the online service” or unlimited for offline games). Duplications (e.g., backup copies) or modifications must also be addressed. As a rule, mods are either prohibited or only permitted to a limited extent. This connects to modding and user-generated content legalities.
• Account and obligations of the user: Since live service games generally require an account, it should be regulated how registration works. Users must provide truthful information, keep account data secret, and avoid multiple accounts if undesirable. Minimum age requirements (often 13 or with parental consent) are also crucial for age verification. Additionally, behavioral obligations are important: Code of conduct, netiquette, ban on cheats/bots, and no commercial use without permission (e.g., gold selling, account sales, usually prohibited in terms and conditions).
• Provider’s services: Here, you briefly describe which services are provided—access to the game, forums if applicable, support—and what is not guaranteed (e.g., success in the game, permanent availability, certain player numbers, etc.). This is where the SLA aspects come into play: subject to maintenance, efforts to ensure security, but no guaranteed feature level except as agreed. If there are paid packages (subscription vs. free tier), it must be clear which services are included in the free tier and what paying customers get additionally.
• Terms of payment: Subscriptions must regulate payment methods, due dates, and consequences for non-payment (default, blocking). For microtransactions: how billing works, whether virtual currencies are used, and that they have no real monetary value and are not redeemable. This also includes whether prices include VAT (always show gross prices in B2C!). Any refund exclusions (no refunds for used subscriptions except for statutory revocation) can also be placed here. This also involves considering Play to Earn models.
• Term and termination: Important, as previously discussed: ordinary notice periods, the form (online via the termination button or in writing/email—the button is mandatory per Section 312k), and extraordinary grounds for termination. In particular, it should state that the provider can block or terminate the account if the user violates the rules. Ideally, the process should also be described: e.g., first a warning, then a temporary ban, then a permanent ban. This deters violations and shows fairness by not banning immediately, except for very serious offenses.
• Consequences of contract termination: The user loses access and can no longer use the game. For subscriptions: Remaining terms expire from termination date. Already paid amounts won't be refunded if termination is user-initiated or for good cause by the provider due to user behavior. If the provider terminates without user fault (e.g., service discontinuation), any advance fees should be refunded pro rata. Additionally: virtual goods and progress are lost upon account deletion. No compensation claims for this; this should be clearly stated in T&Cs to avoid future claims.
• Reservation of the right to amend the T&Cs or the game: Especially with live service games, adapting rules (e.g., new features require new provisions) and further developing the game is desired. A GTC amendment clause for consumers must be very carefully formulated to be effective. Often, an email announcement and an opt-out option are used: the user can object within a period, otherwise the change is approved. For objections, providers often reserve the right to terminate. This is common but carries legal risk, as Section 308 No. 5 BGB sets strict limits. Alternatively, changes might require express consent, which is impractical for thousands of players. Limiting changes to necessary cases and transparent communication is important. Additionally, as discussed, changes to the digital product (game updates, content changes) are only permitted under certain circumstances per Section 327r BGB. These should also be reflected in terms of use. For example: “The game is constantly being improved and changed. We will give you at least 30 days’ notice of any significant changes negatively impacting usability. In case of significant deterioration, you have the right to terminate the contract extraordinarily at the time of the change.” This clause fulfills the legal information obligation and grants the user their right.
• Warranty and liability: Careful wording is required for consumers. Statutory warranty law applies. Attempts to restrict it are ineffective and can erode trust. Conversely, you can clarify that the game's functionality on every hardware configuration is not guaranteed if minimum requirements are unmet. For online-only games, mentioning that gameplay decisions (e.g., balance changes) are not defects but part of ongoing operation helps manage expectations.
  Regarding liability, a standard clause might state: “The provider is liable without limitation for intent and gross negligence as well as for personal injury. In the event of slight negligence, the provider is only liable for breaches of material contractual obligations (cardinal obligations), limited to foreseeable, typical damage. Liability for data loss is limited, where permitted by law, to restoration costs using existing backups. Further liability is excluded.” This wording is common and effective for consumers. It excludes core obligations and limits liability for others. In B2B, stricter terms are possible, but mixed users are common. This is a core element in software license agreements.
• Final provisions: These include applicable law (usually German law, with mandatory consumer protection regulations of the country of residence remaining unaffected for consumers). They also cover place of jurisdiction (for B2C, exclusive jurisdiction cannot be specified elsewhere; for B2B, the provider's registered office can be agreed). A severability clause is standard. There's also a reference to dispute resolution. Per Section 36 VSBG, you must state participation in consumer arbitration, and a link to the EU online dispute resolution platform (ODR) should be in the legal notice and terms. Many forget this, but it's required even if not participating (explicitly state: “We do not participate in dispute resolution proceedings before this dispute resolution body.”).

As you can see, such a GTC/EULA catalog covers all essential legal points discussed in this article. It is crucial that these documents are individually tailored to the game. Simply copying from another game is dangerous. As the game.de Start-up-Guide correctly warns, this can result in clauses from US terms or legally outdated texts invalid in Germany. For example, US EULAs often contain a complete warranty disclaimer (“AS IS, no warranty”) which is ineffective for German consumers. They might also violate data protection and other local regulations.

Our law firm develops general terms and conditions for games in close consultation with the developer. This ensures that the clauses are legally sound and suitable for the game and monetization strategy.

Coordination with Platform Guidelines

Many developers distribute their games not just via their own website, but through distribution platforms like Steam, Epic Games Store, GOG, console marketplaces (Sony PlayStation Network, Xbox Live, Nintendo eShop), or mobile app stores (Apple App Store, Google Play). Each platform has its own guidelines and contractual conditions that influence end-user terms:

• Inclusion of own terms and conditions on platforms: Some platforms allow publishers/developers to include their own EULAs. For example, Steam may display a separate EULA upon first game launch. Others have stricter rules. On consoles, the entire contract is concluded within the ecosystem, and platform T&Cs take precedence. When using a platform, users often agree to its terms, which include basic rules (e.g., PSN Terms). Developers should adapt their terms to avoid contradictions. For example, if Sony prohibits excluding certain liabilities, the EULA must comply.
• In-app purchase guidelines: On Apple iOS and Google Play, in-app digital purchases must be processed via the respective payment system. This mainly affects technical and economic aspects (commissions). However, it also has legal implications. In the App Store, Apple handles the withdrawal policy, informing users that no right of withdrawal exists after purchase, but offering its own refund rules. Developers cannot independently communicate different refund or subscription termination rules that conflict with the App Store. Apple also requires that users manage and cancel subscriptions via the App Store; a separate cancel button on the developer website is unnecessary as Apple manages subscriptions. Therefore, terms of use for mobile apps should clarify that purchases are processed via the platform and that terms of use of the App Store take precedence regarding payment/cancellation. This also affects prepayment in online stores.
• Age ratings and content: Platforms often have requirements for minor protection and content classification. While more of a compliance issue, terms of use are relevant. For example, they may address user obligations to provide correct age information or prohibit user-uploaded content (community, chat). Consistency between platform policy and your own policy is important.
• Online service ecosystem: Especially on consoles, developers enter an existing ecosystem. The network operator (Sony, Microsoft, Nintendo) has its own rules of conduct and sanctions. A player violating PSN guidelines can be excluded from the entire network by Sony. They would then lose access to your game, even if you, as the provider, haven't terminated the contract. Your terms and conditions could include a note: “The use of our online game requires a valid PlayStation™Network account. If this account is blocked by Sony, their terms and conditions apply; we accept no responsibility for this.” This clarifies that your liability does not apply to such platform-side measures.

As a provider, you should carefully study the developer agreements and guidelines of platform partners. In some cases, they even stipulate certain formulations in end-user agreements or prohibit certain clauses. For example, Steam prohibits limiting its own liability in the EULA. Some platforms have model EULAs or recommended clauses. Nevertheless, having your own rules adapted to the platform is beneficial, especially for aspects not covered by the platform (e.g., specific game rules, cheating bans, Season Pass benefits).

Contracts with Publishers or Service Providers

Finally, a quick note: end-users don't see this, but live service games often involve contracts between the developer studio and other companies. This includes a publisher distributing the game or technical service providers (server hosting, payment providers). These contracts should mirror the obligations owed to the end-user. For example, a hosting contract should ensure agreed uptime, allowing you to keep promises to gamers.

The contract with a payment service should clarify refund handling for withdrawals/chargebacks. This ensures correct referencing in player terms and conditions. Especially in a publisher-developer relationship (publishing contract), topics like monetization models, update obligations, and support distribution must be contractually defined. A publisher will require the developer to comply with certain update obligations to prevent legal infringements. The contract can also specify who drafts the terms and conditions (often the publisher) and how liability risks are distributed for warnings due to incorrect terms and conditions.

For founders, it is important that all levels—end-user T&Cs, platform conditions, B2B contracts—are consistent. In the worst-case scenario, a contradiction can leave you contractually exposed. For example, if the publisher demands something prohibited for end-users, or vice versa. Therefore, it is advisable to plan legally from the outset. Determine who assumes which responsibilities and how contracts interact. This is key for founding a game development studio.

Relevant Legal Provisions at a Glance

Numerous laws relevant to live service games have already been mentioned. Here, we summarize the most important standards and legal bases. This “mini-compendium” serves as a checklist for founders and developers to avoid overlooking anything critical:

• §§ 312 ff. BGB – Consumer contracts and distance selling: These sections regulate when a contract is a consumer contract and which special rights apply. Particularly relevant:
  • § Section 312a BGB: General obligations for consumer contracts (e.g., no overpriced hotlines for customer service).
  • § 312b ff. BGB: Definition of distance contracts (typical for online game subscriptions or downloads) and off-premises contracts.
  • § 312d BGB in conjunction with Art. 246a EGBGB: Information obligations for distance selling (as explained: price, features, duration, right of withdrawal, etc.).
  • § 312g BGB: Right of withdrawal for consumers in distance selling. Exceptions are important: No right of withdrawal for fully delivered digital content after proper instruction (Section 312f in conjunction with Section 356 BGB), and the right of withdrawal for services expires under certain conditions.
  • § Section 312k BGB: Termination of consumer contracts in electronic commerce, specifically the aforementioned termination button.

• §§ 327 ff. BGB – Contracts for digital products: This section is new and highly relevant for games:

  • § Section 327 BGB: Scope of application – applies only to consumer contracts. It covers payment of a price (including data) for digital content or services. Digital games are explicitly mentioned as an example of digital content.
  • § Section 327a BGB: Exceptions to the scope of application (e.g., merely providing telecommunications lines is not digital content).
  • § Section 327b BGB: Obligation of the contractor to provide. Important: What does “make available” mean? (Provide access, offer download, etc.).
  • § Section 327c BGB: Rights of the consumer if provision does not take place (e.g., if a purchased download doesn't work or server access is denied, the consumer can demand fulfillment or, if necessary, withdraw).
  • § Section 327d BGB: Conformity with the contract – the entrepreneur must provide the digital product free of defects.
  • § Section 327e BGB: Material defect concept for digital products. It distinguishes between subjective and objective requirements, plus integration requirements. For games, this means they must have promised properties (subjectively agreed, e.g., system requirements, features). Second, they must objectively provide what an average user expects (e.g., for multiplayer games, stable online experience; for downloads, running on standard hardware).
  • § Section 327f BGB: Duty to update – as discussed, the obligation to provide updates to maintain contractual conformity, including security updates, during the relevant period.
  • § Section 327g BGB: Defects of title – e.g., the game must not infringe third-party copyrights; otherwise, it's defective. The user should be able to use it without infringing third-party rights, which the provider must ensure. This is part of building a clean chain of rights.
  • §§ 327h-327m BGB: Warranty rights in the event of defects. These essentially reflect general warranty rights: subsequent performance (Section 327l BGB – consumer can choose rectification or new delivery, if possible for digital products; usually rectification/patch), withdrawal or reduction (Section 327m), compensation (Section 327m (3) refers to normal compensation rules). A special feature: For continuing obligations, withdrawal corresponds to termination ex nunc (for the future) – you can withdraw, but only for the future; services already rendered (past subscription months) can at best be reduced.
  • § Section 327j BGB: Statute of limitations and burden of proof. The reversal of the burden of proof for consumers is newly regulated. If a defect appears within one year of provision (or during the term for ongoing products), it's presumed present from the beginning. The provider must prove the problem was user-caused. Warranty claims expire at earliest 12 months after the update obligation period ends. If the update obligation runs for 2 years, you still have 1 year to assert claims if a defect occurs within those 2 years. For ongoing contracts, this can be very long. It prevents providers from evading responsibility.
  • § Section 327k-327p BGB: Further details, e.g., consumer's duty to cooperate (e.g., installing updates), consequences of non-cooperation (loss of claims if update not installed, Section 327l (2)).
  • § Section 327q BGB: Relationship to data protection – the provider may not impose contractual disadvantages on the consumer for exercising data protection rights. Example: If a player requests data deletion (under GDPR), the provider cannot simply terminate the contract unless further performance is impossible because the data was absolutely necessary (Section 327q (2) allows termination if data was necessary and performance impossible without it). Otherwise, consumers should not fear exercising data protection rights.
  • § Section 327r BGB: Changes to the digital product – as discussed, requirements for permissible changes during an ongoing contract, information obligations, consumer's special right of termination for significant changes.
  • § 327t-327u BGB: Recourse of the entrepreneur in the supply chain – relevant if a developer delivers to a publisher, who delivers to the end customer. The publisher can take recourse if the developer is responsible for the defect. This affects inter-company contracts, not end-user T&Cs.

• Youth protection law: Although not a direct contract for the user, providers must be aware of the Interstate Treaty on the Protection of Minors in the Media (JMStV) and the Youth Protection Act. This includes age ratings (USK) for games, labeling online offers with age levels, or technical means to prevent children from accessing 18+ content. For GaaS with online elements like chat or user-generated content, moderation is relevant to prevent harmful content. New since 2021 in DE: Gambling-like mechanisms (e.g., loot boxes) might influence age ratings. This is a separate topic, but founders often need to implement solutions (age verification, filters), which can be included in terms of use (e.g., “Account holder confirms meeting required age per USK rating”).

• Data protection (GDPR, BDSG): Every online service must be data protection compliant. A privacy policy is mandatory but separate from GTC. However, data protection is embedded in contracts: if personal data is processed for a subscription, it must be contractually permitted. T&Cs can state that certain data is stored (e.g., player data, chat logs for abuse control), but the legal basis is GDPR. Important for GaaS: often international players. If you offer outside the EU, terms and privacy must be globally coordinated. See also: GDPR reporting and damage limitation.
• Competition and consumer protection laws: Failure to provide mandatory information (e.g., imprint, revocation) or unfair practices (misleading advertising, e.g., about in-game purchases) can lead to warnings under the UWG (Unfair Competition Act). Since May 28, 2022 (implementation of the Modernization Directive), certain practices in games have been explicitly declared consumer deception. This includes manipulating ratings or opaque personalization of prices. Although these topics only peripherally touch on contract law, it's good to be aware of them. This is especially true given the legislator's focus on dark patterns.

This is not an exhaustive catalog of all conceivable legal norms, but it covers those most important for live service games and their contracts. The innovations of 2022, particularly digital products and fair consumer contracts, have changed the landscape. Therefore, existing GTCs and contracts created before these changes should be urgently updated to be current.

Conclusion

Live service games (games as a service) offer enormous potential for long-term player loyalty and continuous revenue. At the same time, however, they place high demands on a clean contractual structure. From the right business model (subscription or sales with DLC) to update and support obligations, availability commitments, termination rules, and consumer protection-compliant design, numerous legal aspects need consideration. The latest legislative changes, especially in digital contract law, bring additional obligations. These should definitely be accounted for in contracts and general terms and conditions, including keywords like update obligation, termination button, right of withdrawal for digital goods, and special rules for changes.

For founders and developers launching a live service game, this regulatory complexity can be overwhelming. Early legal advice is therefore crucial. A specialist games law firm, like ours, understands the pitfalls and industry standards. I can help draft trustworthy and legally compliant terms of use that protect your business interests and meet legal requirements. This often aligns with the professionalism valued in contracts.

Well-drafted contracts are not just a formality. They also shape the relationship with your players. Clear rules build trust and reduce potential conflicts. When players understand their rights—how to cancel, what happens during server downtime, what recourse they have for problems—long-term satisfaction increases. Simultaneously, you protect yourself from unjustified claims and have a solid contractual basis to rely on in disputes.

In conclusion, games as a service combine technology, community, and law excitingly. If you manage the legal framework, you can focus on continuously improving your game. This will make both players and investors happy. If you have questions or need support with contractual implementation, I will gladly provide my expertise. Your success in the live service game sector should not be hindered by legal hurdles; we can help pave the way.