Crowdfunding Legal Risks Games | IT-Medienrecht

Legal Risks Associated with Long Development Times and Discontinuation of Crowd-Funded Games

Crowdfunding has established itself as a popular financing model within the games industry. Developers collect funds from supporters to pre-finance game development, utilizing platforms like Kickstarter or Indiegogo, or offering pre-order options directly on their own websites. However, significant delays in development or project abandonment pose considerable legal risks for developers. This article comprehensively examines the legal consequences and obligations developers have towards backers in such scenarios, particularly regarding terms and conditions, regulation, and compliance in computer games.

Supporters' Claims for Reimbursement

A significant risk for developers arises if a game is not completed or its development faces excessive delays: backers are generally entitled to a refund of their money. If a promised game fails to be delivered within a reasonable timeframe or is ultimately abandoned, supporters can demand their contributions back. The legal basis for such a claim depends on the specific contract type underlying the crowdfunding and the agreements made.

Refund Rights on Crowdfunding Platforms

• On crowdfunding platforms (e.g., Kickstarter, Indiegogo): The terms of use of such platforms stipulate that the financing contract is concluded directly between the developer (project initiator) and the backer. If the promised product (the game or other rewards) is not delivered, the contract is unfulfilled. Supporters generally have the right to withdraw from the contract and demand their money back. Practically, this means the developer must refund the received contributions. Kickstarter, for instance, states that project initiators must either deliver the promised rewards or repay the support funds if fulfillment fails. Indiegogo operates similarly; even with flexible financing where money is paid out regardless of reaching the funding target, the project initiator remains obligated to deliver or refund.

Pre-Order Models via Dedicated Websites

• In the case of pre-order models via dedicated websites: Here, supporters often conclude a purchase contract or a contract for future game delivery directly with the developer studio. If the studio fails to meet its delivery obligation, buyers are entitled to rescission under general contract law. Consumer protection law (e.g., in the EU) specifically states that in the event of non-delivery within an agreed or reasonable period, consumers can withdraw from the contract after setting a deadline and demand a refund. If development is excessively delayed, supporters can issue a final grace period. If this also expires without success, a statutory right of withdrawal exists (§ 323 BGB in Germany). The developer must then refund the amount paid.

These reimbursement claims exist regardless of whether delays stem from unforeseen difficulties or miscalculations. Backers contribute funds expecting a return; if this doesn't materialize, they are entitled to their money back. This carries significant financial consequences for developers, especially if invested funds are no longer available. In extreme cases, simultaneous refund demands from numerous backers can even lead to insolvency.

Allegations of Fraud and Improper Use of Funds

Accusations of fraud represent another significant risk for developers of crowdfunded games. This risk materializes if there is suspicion of improper use of collected funds or a lack of serious development intent from the outset. Legally, such actions could constitute a criminal offense of fraud (§ 263 StGB in Germany or equivalent provisions elsewhere).

• Misrepresentation of Facts

  If a developer knew at the time of the campaign that the project was not feasible, or deliberately made false promises to secure funds, this can be considered fraudulent inducement. Supporters would have contributed their money under false pretenses. Criminal investigations could follow, potentially leading to criminal proceedings for fraud in addition to civil claims. Internationally, there have been cases where initiators of failed crowdfunding projects faced legal action on such grounds.

• Misappropriation of Funds

  Even with serious initial intent, the use of funds can become problematic. Crowdfunding contributions are earmarked for the specific project's development. Diverting money for private purchases or other projects makes supporters feel deceived. While contributions aren't legally fiduciary funds (the developer gains ownership), improper use can indicate an intent to self-enrich. In some countries, consumer protection authorities have taken action. The US Federal Trade Commission (FTC) in 2015 acted against a Kickstarter project launcher for misusing funds. State prosecutors have also filed lawsuits, leading to sanctions and repayment obligations.

• Failure in Good Faith vs. Fraudulent Failure

  Legally, the reason for project failure is crucial. Failure in good faith—due to technical issues, misjudgments, or external circumstances—triggers civil law consequences (breach of contract, reversal) but generally no criminal law consequences, provided the developer acts transparently and without intent to deceive. The situation differs with fraudulent failure: if false information was provided during the campaign, progress faked, or risks concealed to attract backers, it can be retroactively considered fraud. Developers must, therefore, ensure truthful information and proper fund usage to avoid fraud accusations.

Contractual Obligations of the Developer

Beyond criminal law considerations, developers also bear significant contractual obligations towards their supporters. Upon successful financing, a contract forms, establishing mutual duties: the backer provides funds, and the developer owes a defined service in return. This service typically includes the finished game, often alongside additional rewards like merchandise or beta access.

• Delivery of Promised Service

  The developer's foremost contractual obligation is to deliver the announced game or rewards in the promised form. This fulfillment of contract is central. Complete non-completion constitutes non-performance. Significant delays may also be considered a breach of duty, especially if a specific delivery date or approximate period was promised. Many campaigns include an estimated delivery date (e.g., "Estimated Delivery: October 2023"). Legally, such a date can be binding or non-binding, depending on its communication. If presented as a mere estimate, the developer might argue no fixed deadline was agreed. Nevertheless, delays must not be unreasonable. What constitutes "unreasonable" varies by circumstances; a few months for a complex game might be acceptable, but several years is not.

• Secondary Obligations and Diligence

  In addition to primary obligations, secondary obligations also arise from the contract. This includes taking all reasonable steps to ensure project success. The developer owes the specific product described in the campaign, not just any product at any time. Serious content deviations or a clearly inferior end product could also breach contractual obligations, as the delivered service wouldn't match the promised one (e.g., warranty for material defects, applicable to digital goods). Furthermore, developers must not violate backers' interests, such as misusing internal backer information or making arbitrary business model changes that diminish backer rights.

• Type of Contract: Purchase or Contract for Work?

  From a legal standpoint, the exact classification of the contract is crucial. Is a backer payment a purchase contract (advance purchase of a future game) or a contract for work and services (commission to produce a specific game)? This distinction is debated in German law. A contract for work and services (Section 631 BGB) obliges the developer to produce a promised work, typically paid upon acceptance—however, crowdfunding involves advance payment, atypical for classic work contracts. A purchase contract (Section 433 BGB) obliges delivery of an item in exchange for payment, with advance payment and future delivery. Practically, the distinction mainly impacts legal details like warranty periods, not the core issue of delivery or repayment. In both cases, no delivery means no consideration; if the work isn't delivered, the customer/buyer can demand their money back. For developers, this means the contractual obligation to fulfill performance exists irrespective of exact contract qualification. The contractual framework and models for live service games also require careful consideration.

• Impossibility of Performance

  If the project ultimately fails, the legal consequences involve impossibility of performance (Section 275 BGB for Germany), meaning the developer can no longer provide the owed service. Consequently, the developer's claim to consideration lapses (Section 326 BGB), implying they cannot retain the received funds as the promised service hasn't been rendered. This reinforces backers' right to reimbursement and clarifies that developers cannot unilaterally avoid their obligation by canceling the project. They generally must reimburse contributions, unless an alternative solution is agreed individually with backers, such as conversion into voluntary donations. This is a critical aspect of avoiding common legal mistakes for start-ups.

Information and Accountability Obligations

Effective communication with supporters becomes crucial during the development phase, particularly if it extends beyond initial timelines. Legally, the question arises: to what extent are developers obligated to inform backers about progress, delays, or problems, and to account for fund usage? This transparency is key to managing expectations and mitigating legal challenges for start-ups.

• Contractual or Statutory Information Obligations

  Unlike shareholders or investors, crowdfunding backers are generally not subject to explicitly standardized statutory accountability obligations from the developer. However, information duties may arise from the principle of good faith (Section 242 BGB). If a delivery date is foreseeably missed or difficulties jeopardize completion, developers must not leave backers uninformed, at least within reasonable bounds. Platform rules or community expectations often compel project initiators to provide regular updates. Kickstarter, for example, requires initiators to keep backers informed and openly report problems. A complete lack of communication can not only erode trust but also constitute a breach of secondary obligations, especially if it prevents backers from exercising their rights (e.g., withdrawal). Such obligations are part of the broader T&Cs, regulation & compliance in blockchain & computer games sector.

• Accountability for the Use of Funds

  Many backers rightly expect their money to be dedicated solely to the project. While developers don't automatically owe every backer a detailed statement, transparency about fund usage can be vital in case of failure. Firstly, it reassures backers if funds were used for development costs, licenses, or materials, countering accusations of enrichment. Secondly, in disputes, developers may be required to explain why full repayment isn't possible and where the money went. Platform guidelines often require explanations for fund usage if a project is canceled. Legally, a backer could argue for a right to information regarding fund use in case of total failure. Although not directly statutory, this question would emerge during damage claims or fraud investigations. Thus, developers should maintain thorough records of used funds to ensure accountability.

• Communication as Prevention

  Even if not every delay leads to legal action, an open information policy is the best way to prevent escalation. Many legal conflicts arise when supporters feel deceived or abandoned. Regular project updates, honest admissions of setbacks, and outlining a revised plan can deter backers from initiating legal action. While good communication doesn't negate contractual rights—backers retain their right to withdraw if performance fails despite updates—transparency and dialogue can help reach mutually agreeable solutions, such as voluntary waiting period extensions or partial refunds, thereby avoiding immediate legal confrontation. This proactive approach can help startups avoid legal pitfalls.

Platform Conditions and Disclaimers

Crowdfunding platforms, including Kickstarter and Indiegogo, aim to establish a legal framework that limits their own liability while governing obligations between developers and backers. Developers must be fully aware of these platform terms and conditions, as they impose specific duties but do not grant complete immunity. Understanding these is crucial for contract drafting for SaaS companies or any digital service provider.

• Liability of the Platform vs. Liability of the Developer

  Generally, platforms largely exclude their own liability. Kickstarter, for example, explicitly states that no guarantee is provided for project success or reward delivery. Responsibility rests entirely with the project initiator. Backers should understand they contribute at their own risk. For developers, this means they cannot claim the platform is responsible in a dispute; backer claims are directed solely against them. Kickstarter (as referenced on Wikipedia) warns project initiators that they are liable for damage claims if they fail to deliver on promises. This highlights that while the platform isn't liable, the developer bears full responsibility.

• Terms of Use and Obligations

  Platform terms of use typically contain specific requirements. For Kickstarter, developers commit to using funds for the intended purpose and fulfilling rewards if the project succeeds. If a developer cannot complete a project, Kickstarter guidelines demand efforts to find a solution, including refunding remaining funds or presenting a partial fulfillment plan. Indiegogo has similar rules, expecting campaign initiators (especially for flexible funding) to deliver promised services or actively work with backers on solutions, often including refunds. Violations of platform T&Cs can lead to exclusion from future campaigns and, in cases of fraudulent behavior, potential reporting to authorities. These terms are critical, much like understanding prepayment in online stores and their associated T&Cs.

• Liability Clauses Vis-à-Vis Supporters

  Some developers attempt to limit liability or exclude refunds in project descriptions or their own terms (especially for pre-orders on their websites). Caution is advised: in consumer law (e.g., in Germany under Sections 307 et seq. of the German Civil Code), clauses that strip consumers of essential rights—such as blanket "refunds excluded" or "delivery dates non-binding, no claims for delay"—are often invalid if they are unreasonably disadvantageous. While platform T&Cs are not directly subject to GTC control by the developer, developers creating their own terms (e.g., on a store page) must respect statutory limits. Blanket warranty exclusions or disclaimers are ineffective in many B2C legal systems. This means even if a campaign states that delays do not grant a right of withdrawal, a court might prioritize consumer protection. Developers should not rely on their own clauses to absolve responsibility.

• Governing Law and Place of Jurisdiction

  Platforms often specify the governing law (e.g., New York state law for Kickstarter) and jurisdiction for contractual relationships. However, these clauses usually only apply between the platform and developer, or platform and user. The actual contractual relationship between developer and backer may be unaffected, particularly if both are based in the same country. For example, a German backer supporting a German developer on Kickstarter might find German law applicable, despite the platform's US base. This means developers might not always be sued in the US under American law; a consumer could pursue legal action in their home country if consumer protection rules permit (e.g., EU consumer jurisdiction). Therefore, it's essential not just to accept platform terms and conditions but to understand their content and limitations.

German and European Legal Framework for Crowdfunded Games

While crowdfunding often operates globally, developers based in Germany or the EU, and their supporters, are subject to specific consumer protection regulations. The legal classification of supporter contributions and their associated rights are particularly relevant under German and European law. Understanding this framework is crucial, especially concerning new EU product liability directives for digital products.

Classification of Support: Gift, Purchase, or Contract for Work?

Under German law, the legal qualification of a supporter's contribution is a decisive factor, as many obligations and rights hinge on this classification:

• Gift (Donation)

  If a contribution is gratuitous, without expectation of consideration, it could be classified as a gift (Section 516 BGB). Some crowdfunding supporters deliberately contribute without rewards, simply to promote a project. Legally, such a supporter would not be entitled to anything in return; they have explicitly made a gift. However, pure donations are rare on major platforms, as donors typically expect at least symbolic consideration (e.g., credit mention, T-shirt). As soon as any consideration is promised, it ceases to be a donation and becomes a synallagmatic (mutual) contract.

• Purchase Contract

  Very often, the crowdfunding scenario aligns with a purchase with advance payment. The supporter "buys" a future product (e.g., the game as a download or boxed edition) and pays immediately, with delivery scheduled for the future. This can be summarized under Section 433 BGB (purchase contract): the developer, as seller, must deliver the purchased item at the agreed time, and the buyer has already paid or will pay upon successful campaign. Other rewards (figures, artbooks) are also ultimately purchase objects. Most courts would likely view such a contract as a purchase, as a finished product is owed, even if it still needs production. This applies particularly to understanding prepayment in online stores.

• Contract for Work and Services

  In some instances, it could be argued that this constitutes a contract for work and services (Section 631 BGB), as the developer specifically produces a "work" (the game) and the supporter, as the customer, somewhat places the order. The distinction from a purchase is nuanced: work and services contracts are typical for individually produced items for a customer (e.g., custom software). However, crowdfunded games are identical for many users, not personalized. Therefore, a purchase contract is often more fitting. Nonetheless, a contract for work and services imposes similar obligations: the manufacturer must create the promised work. If such a contract is assumed, the legal consequences for failure would be the same—the claim for remuneration would lapse, and any payments made would need repayment.

• Hybrid Forms and Uncharted Legal Territory

  Crowdfunding often sits between a gift and a purchase, frequently described as hybrid in nature. Developers sometimes argue that backers are "supporters," not buyers, to emphasize outcome uncertainty. Legally, however, promises of consideration constitute a contract for consideration. In Germany, no supreme court decision has definitively classified a crowdfunding contract, but literature tends to treat it as a standard pre-sale contract. This means developers cannot claim in court that the money was merely a voluntary donation, at least not if a specific delivery was promised.

Consumer Protection in Distance Selling: Right of Withdrawal and Delayed Delivery

Within the European and German contexts, consumer protection laws are particularly relevant for crowdfunding transactions. This is because distance selling contracts are regularly formed between an entrepreneur (the developer studio) and consumers (the backers). This framework influences developers' obligations, aligning with principles seen in GDPR compliance for the self-employed.

• Right of Withdrawal

  In traditional online retail, consumers possess a 14-day right of withdrawal (Section 312g BGB, EU Consumer Rights Directive 2011/83/EU). This allows consumers to cancel a contract within 14 days of its conclusion or goods receipt, without stating reasons, and reclaim their money. Applied to crowdfunding, this creates a volatile situation: if an EU-based developer sells a game via pre-order or accepts Kickstarter-funded pre-orders, consumers could theoretically cancel their contribution within 14 days of payment. Practically, this is rarely integrated into platform processes; Kickstarter, for example, doesn't actively inform backers about an EU right of withdrawal, and many backers are unaware. Legally, however, such a right of withdrawal may exist. Developers would essentially need to properly inform every EU supporter about this right. Failure to do so extends the right of withdrawal beyond 14 days (up to 12 months in Germany). This poses a significant risk: a backer could revoke their contribution weeks or months post-campaign, demanding repayment, thus disrupting the financing plan. Developers should at least recognize this rule. Some try to circumvent it by arguing that digital content negates the right of withdrawal once fulfillment begins; but this requires explicit backer agreement to immediate digital delivery and waiver of the right. This exception doesn't apply to future games, as there's no immediate delivery. In short: the right of withdrawal always applies in crowdfunding, and ignoring it risks legal issues with consumer protection organizations or individual backers.

• Delayed Delivery and Reasonable Deadlines

  Timely delivery is another consumer protection aspect. The EU directive states that without a fixed delivery date, traders must deliver within 30 days; otherwise, consumers can send a reminder, set a grace period, and withdraw from the contract if the deadline is missed. For crowdfunding projects, 30 days is clearly insufficient, with months or years often separating financing from planned completion. An estimated delivery date is usually provided. If this is significantly exceeded, it constitutes a delivery delay. Under German law, the debtor (developer) is in default once the creditor (backer) sends a reminder after the due date (Section 286 BGB). Practically, backers could send a reminder after the announced delivery month, demand delivery within a period, and withdraw if that deadline passes. This largely mirrors the right of withdrawal for non-performance, emphasized in consumer protection. For developers, excessive development times automatically increase the risk of contract termination and repayment requests. Even without a "hard" contractual delivery date, protection against claims is not unlimited; at some point, a waiting period becomes unreasonable. What is "unreasonable" depends on circumstances, but doubling or tripling the forecast development period will likely raise critical questions.

• Warranty Law for Digital Products

  Recent EU regulations, such as the Digital Content Directive (EU 2019/770, implemented in Germany in Sections 327 et seq. of the German Civil Code), bolster consumer protection for digital services. Accordingly, a digital product (e.g., a video game) must be provided at the agreed time and in the agreed condition. Failure to do so grants consumers warranty rights, ultimately including the right to withdraw if grace periods prove futile. Applied to crowdfunding, this means legally recognized warranty rights could apply if the delivered game significantly deviates from promises (qualitative defect) or is not delivered at all (legally, non-performance, treated similarly). While crowdfunding may be considered a special case, legal texts make no distinction between a pre-purchased game and a game bought normally in a shop. This is vital when considering the new concept of defects in software development.

Special Features of German Law: GTC Control and Legal Consequences of Failure

Beyond general contract and consumer law, several specific German legal issues are particularly relevant for crowd-funded games:

• GTC Control of Risk Exclusions

  As mentioned, clauses in general terms and conditions that unilaterally restrict liability or obligations are subject to judicial review. For instance, a developer stating in their terms, "The game will be delivered if possible. There is no entitlement to delivery; the backer accepts the risk of failure," would likely not succeed in German courts. Such a clause would practically undermine the contract, stripping the backer of rights, which is deemed unreasonably disadvantageous. Consequently, the clause would be null and void, and the developer could not invoke it. The same applies to clauses generally excluding refunds or legal recourse. Therefore, developers in Germany must draft their contractual terms fairly and in compliance with the law. Transparency about risks is permissible and sensible, but it does not supersede consumers' minimum legal rights. This also impacts the amendment of GTCs.

• Legal Consequences if a Project is Canceled

  It's worth considering whether a crowdfunding contribution could be reinterpreted as a gift agreement if the project fails, allowing the developer to keep the money. Developers might argue: "You supported us knowing the risks, effectively gifting us the money." However, this contradicts the actual agreement if rewards were promised. German law recognizes the frustration of contract (Section 313 BGB) for adjusting contracts due to unforeseeable circumstances. A developer might claim, "Development was more complex than expected; the contract assumed budget X. This is no longer valid, so we can't fulfill the contract as is." Practically, this would unlikely prevent backers from getting refunds; rather, it might lead to adjustments like deadline extensions or additional funding. If the project is canceled, the principle remains: no money without performance. If the developer becomes insolvent, backers are regular insolvency creditors, registering claims and potentially receiving only a quota or nothing. This insolvency risk is borne by the backer, an inherent disadvantage of crowdfunding. However, as long as the developer is solvent, the law will compel them to refund received funds rather than retain them without delivery.

• Distance Selling Information Obligations

  Developers operating their own online store for pre-orders must also observe statutory information obligations. These include providing a legal notice, clear product information, and instructions on the right of withdrawal. Failure to comply can result in warnings from consumer protection associations or competitors. The "button solution" (Section 312j BGB) requires order buttons to clearly indicate payment obligation (e.g., "order with obligation to pay"). Crowdfunding platforms like Kickstarter use buttons such as "Back this project," which is borderline by German standards; however, Kickstarter operates outside the direct German legal area. A German developer with their own store must meticulously adhere to such formal requirements to avoid both content-related non-compliance issues and formal legal disadvantages. This is critical for e-commerce start-ups.

International Perspectives: USA, UK, Australia

The legal treatment of crowdfunding risks varies significantly by jurisdiction. Several countries have already accumulated experience with disputes concerning delayed or failed games, highlighting the importance of understanding international publishing contracts for indie developers.

USA

In the United States, there's no specific crowdfunding law for reward-based crowdfunding; general contract and fraud principles apply. Most platforms (Kickstarter, Indiegogo) are US-based and apply US law in their terms. Important for developers:

• Contract Law and Lawsuits

  Backers in the USA can file civil lawsuits for breach of contract if promised rewards aren't delivered. However, the expense of individual lawsuits often deters those with smaller claims. In some cases, groups of supporters have banded together or initiated class actions for projects involving numerous claimants and substantial sums. US courts have consistently affirmed that a binding contract forms once a campaign is successfully funded and the backer charged, leading to enforceable obligations.

• Regulatory Intervention

  As previously mentioned, the FTC has intervened in at least one prominent case, involving a board game creator who used Kickstarter funds for private purposes. The FTC secured a cease and desist order and refunds. State-level prosecutors have also intervened in individual cases. The general consumer protection law in the USA, which protects against "unfair or deceptive acts or practices," is applicable here. If a crowdfunding project appears to be a fraudulent deception, it can be prosecuted as an unfair practice.

• Mail Order Rule

  An interesting aspect is the FTC's Mail Order Rule (or "Mail, Internet, or Telephone Order Merchandise Rule"). This rule dictates that ordered goods must be delivered within the promised time or, if none is specified, within 30 days. Otherwise, sellers must notify customers and offer refunds if necessary. Theoretically, this rule could apply to pre-order crowdfunding if viewed as a sale of goods. However, its application to crowdfunding is ambiguous due to the specific nature of such projects, often involving announced long delivery times. Nonetheless, developers, especially those accepting pre-orders from US customers, should be aware of this rule. Long delays could lead consumers to argue a violation of this rule.

• Criminal Law (Fraud)

  The threshold for criminal prosecution (e.g., for wire fraud at the federal level) is met in the USA if it can be proven that the project initiator acted with fraudulent intent—for example, never intending to deliver or making false promises to obtain money. US authorities have taken selective action in cases involving millions or obvious audacity. For developers, this means that even in the USA, they are not immune to prosecution if they abuse backers' trust.

United Kingdom (UK)

In the UK, EU law applied until the end of 2020, and many of those consumer protection principles remain enshrined in national law. Crowdfunding in the UK context involves the following aspects:

• Contract and Consumer Law

  Similar to the EU, a crowdfunding contribution aimed at a reward is likely considered a purchase contract or order. The Consumer Rights Act 2015 and the Consumer Contracts Regulations 2013 (implementing the EU Directive) also grant UK consumers rights of withdrawal and rights in cases of non-delivery. A UK supporter could therefore cancel within 14 days or withdraw from the contract due to severe delays. Practical enforcement in crowdfunding cases remains rare in the UK, often due to consumer unawareness or complex international project constellations where applicable law is unclear.

• Regulatory Perspective

  The British Advertising Standards Authority (ASA) has previously addressed crowdfunding, particularly regarding campaign advertising. Advertisements or project descriptions must not be misleading. If a developer downplays risks or makes unsustainable promises, this could violate advertising standards. While the ASA doesn't issue refunds, a negative finding damages reputation and increases regulatory pressure.

• Practical Cases

  A notable UK crowdfunding failure was the "Zano" drone project, where thousands of backers lost money. Although no collective legal action was taken at the time (2015), the incident sparked discussions. British authorities focused more on clarification: Kickstarter commissioned a journalist to investigate instead of involving courts. This highlights the gap between legal theory and reality: backers could have held Zano's inventors liable for non-fulfillment, but the company went bankrupt, making practical legal enforcement difficult.

• Unfair Terms

  Similar to German courts, UK courts would critically assess overly broad liability exclusions in general terms and conditions (unfair contract terms). A developer serving UK customers should therefore avoid attempting to completely shift risk in their terms and conditions.

Australia

Australia has also been active in regulating crowdfunding, particularly through its strong consumer protection authority (ACCC) and stringent consumer laws:

• Australian Consumer Law (ACL)

  The ACL safeguards consumers against misleading and deceptive commercial practices. Developers targeting Australian consumers (e.g., Australian backers in a campaign) are subject to these rules. If a project fails, the ACCC may investigate whether false promises were made. The ACCC has investigated crowdfunding projects, for example, ordering a company that crowdfunded a product but never delivered it to repay contributions and cease misleading statements about progress.

• Enforcement

  In Australia, authorities can demand enforceable undertakings from companies—written assurances to take specific measures (like making refunds) to rectify legal violations. For developers, this means that if they receive funds from Australian consumers who complain, they could face regulatory requirements exceeding what an individual backer might achieve. Australian courts would also consider such contracts consumer contracts, similar to the UK/EU, with corresponding rights in case of non-delivery.

• Criminal Prosecution

  Fraud cases could also be prosecuted in Australia. While no known criminal proceedings relating to crowdfunding games exist in Australia, the legal framework (fraud, possibly unlawful procurement of financial benefits) would allow prosecution of particularly egregious cases.

Conclusion of International Perspectives

Globally, no jurisdiction leaves crowdfunding entirely unregulated. Everywhere, either general laws apply, or initial precedents establish that developers cannot simply dismiss failures with "tough luck, it was crowdfunding." While consumer rights are particularly robust in some countries (EU, UK, Australia), others focus more on governmental enforcement (USA). Developers raising funds internationally must therefore adhere to the strictest common denominator, often meaning EU consumer protection requirements and the potential for official intervention, as seen in the USA.

Conclusion: Professional Handling of Risks Required for Crowdfunded Games

Excessive development times or the failure of a crowdfunded game present not only business disappointments but also significant legal pitfalls. Developers have a duty to ensure their backers retain their rights. Refund claims, contractual fulfillment obligations, and consumer protection rights clearly limit the extent of delay and risk backers are expected to accept. Developers also face the risk of personal liability in case of failure, potentially leading to accusations of fraud. This underscores the need for robust confidentiality strategies for startups.

To effectively manage these risks, developers should implement proactive legal safeguards. These include communicating realistic schedules, ensuring risk transparency, planning financial buffers for potential repayments, and drafting legally compliant contractual documents. During development, maintaining open communication and, if necessary, offering voluntary partial reimbursements or compromises is advisable if targets are foreseeably unmet. Ultimately, legal considerations confirm that crowdfunding is not a legal vacuum. Contractually promised deliverables must either be supplied or reimbursed. Developers, publishers, and their legal advisors are therefore urged to approach crowdfunding projects with the same diligence and responsibility as traditional business models. The "crowd's" support generates legally binding expectations that demand professional fulfillment. This aligns with advice on drafting contracts for AI-based services, where clear expectations are paramount.