Core Terms of Service

Agreement node: core

Document key: terms

Version: 2026-08-08

Scheduled publication: 8 August 2026, 10:00 CEST

Release status

This Core Terms release replaces, before publication and before it could take effect, the unpublished omnibus version previously scheduled for 8 August 2026 at 10:00 CEST. The superseded scheduled draft was never an effective contract version. Replacing it does not migrate, amend or replace any effective contract.

The exact previous English version, published on 1 August 2026 at 15:00 CEST remains available and continues to govern every contract into which it was incorporated until the parties validly agree otherwise. Earlier versions, including the legacy English version dated 1 January 2017, also remain available.

These Core Terms apply to a new or existing contract only as part of a complete Agreement Root that was made available and expressly accepted under section 2. Publication, a displayed update, continued use, login or dismissal of a notice is not acceptance.

1. Applicability and definitions

1.1 These Core Terms govern an online service only where Coflnet GmbH is identified as provider or contracting party before conclusion and the accepted Agreement Root includes the exact version and content hash of these Core Terms as a dependency (each such offering a “Service”).

1.2 A “consumer” is a natural person who enters into a legal transaction for purposes that predominantly are outside their trade, business or profession (§ 13 German Civil Code, BGB). A “business user” is an entrepreneur within the meaning of § 14 BGB. A service or customer extension may limit an offering to a stated customer group without changing these statutory definitions.

1.3 A service-specific, customer, role or feature extension applies only if the accepted Agreement Root includes its exact document key, version and content hash. A document linked from a website but absent from the accepted tree does not become a contract term merely because it is available there.

2. Agreement Roots, assent and precedence

2.1 An “Agreement Root” or “Root” is an immutable, versioned manifest node for a service, role or offer class. It identifies its stable Root ID and type, its contractual documents by stable document key, version and cryptographic acceptance or content hash, and every child Root by stable ID and Root hash. The “Root hash” is the cryptographic digest of the canonical Root descriptor and its pinned dependency references. The schema version published in the Root defines the serialization; under schema version 1, the Root hash is the SHA-256 digest of the UTF-8 canonical JSON descriptor. The order or acceptance record separately ties that Root hash to the provider, specific Service or offer, contracting party or account, applicable customer classification and accepted language.

Every dependency must resolve to the exact immutable content accepted for that contract. A mutable URL, a document title by itself or a reference to whatever version may be current later is not a pinned dependency. Changing any dependency, version, content hash, applicability rule or declared precedence produces a different Root hash and does not alter an earlier Root.

2.2 Before a binding registration, order or amendment, we provide the complete Root and all contractual dependencies in the applicable language in a form that the other party can review, download and retain. Acceptance requires a separate, unambiguous affirmative action referring to that complete Root. A preselected control, silence, inactivity, continued use, login, technical access or dismissal of a notice does not constitute acceptance. A Root hash proves which bundle an acceptance referred to; the hash alone does not prove assent.

2.3 We record the accepted Root hash, its manifest and dependency list, the contracting account or party, language, acceptance channel and server time. We provide the contract confirmation and complete accepted bundle on a durable medium where required by law, including § 312f BGB. The confirmation permits the accepted text to be reproduced without relying on a later mutable webpage.

2.4 Contractual documents are read together. In a true conflict, the following order applies, but only to the extent the higher-level provision expressly identifies the subject and intended deviation:

1. individually negotiated terms and an order provision that expressly identifies its deviation;
2. an applicable role or optional-feature extension;
3. the service-specific extension;
4. the applicable consumer, business or organization customer schedule; and
5. these Core Terms.

Dependency order, a later publication date and a more recent version number do not by themselves create priority. The Root must declare the order between two documents at the same level if a conflict is intended; otherwise they must be interpreted consistently. Mandatory law always prevails, and an ambiguity is resolved under the applicable statutory rules.

2.5 A privacy notice, withdrawal information, security policy, product description or other information document is not a contractual dependency merely because its version is recorded alongside the Root. Separate consent or another declaration required by data-protection, consumer or other law is not bundled into acceptance of the Root.

3. Provider, contract formation and accounts

3.1 The provider is Coflnet GmbH, Dorfstraße 27a, 84163 Marklkofen, Germany (Local Court Landshut, HRB 13861), email: [email protected] (“Coflnet”, “we”, “us”).

3.2 Using freely accessible parts of our websites does not create a contract for a paid Service. A contract is concluded when a person submits a registration or order after receiving the provider, Service, price, term, Root and other required information, expressly accepts the Root, and the identified provider accepts by confirmation or by making the Service available. The accepted Root, order and confirmation determine the contracting party and contracted Service.

3.3 If an order identifies a merchant of record or another person as seller, that person is the seller for that purchase. These Core Terms do not make Coflnet the seller or contracting party unless a separate Coflnet contract and its Root were disclosed and accepted before the order.

3.4 Registration information must be accurate and kept current. Access credentials, recovery methods and API keys must be protected from unauthorized access. Accounts are not transferable unless an applicable extension expressly permits a defined transfer.

3.5 Our Services are directed at persons at least 16 years old. A person under 18 may register, order or participate in a remunerated role only with a legal representative’s consent or representation where required by law. This eligibility rule does not change the statutory rules on contractual capacity, including §§ 106 et seq. BGB, or any higher age stated in an applicable extension.

3.6 Where a Service offers an account for a company, club or other organization, only a person authorized to represent that organization may create or order it, and the organization is the contracting party identified in the acceptance record. Its administrators may add or remove members, manage roles and seats, and view the organization’s usage and billing data. The organization must ensure its members follow the accepted agreement. Members keep their separate personal accounts; an administrator receives no access to their private credentials or unrelated personal data merely because of the organization role.

4. Service scope, availability and development

4.1 The agreed scope follows from the accepted service extension, customer schedule, order and product description pinned or preserved with the order. A product page cannot change an existing contract merely by being edited later.

4.2 Free Services are provided within the limits of our operational capacity. For paid Services we provide the availability and support promised in the applicable contract documents. Reasonable maintenance and outages beyond our control can occur; statutory conformity, remedy and availability rights remain unaffected.

4.3 For a consumer contract for a digital product, we provide and inform the consumer about updates, including security updates, necessary to maintain conformity for the period required by § 327f BGB.

4.4 For a consumer digital product supplied continuously, we may make a modification beyond what is necessary to maintain conformity only without additional cost and for one of these valid reasons: adapting to binding law; maintaining security or preventing misuse; adapting to technical environments, interfaces or third-party systems beyond our control; or improving existing or adding new functions without negatively affecting the contracted use.

We inform the consumer clearly about the modification. If it impairs access or use beyond a minor degree, we inform the consumer reasonably in advance on a durable medium about its features, timing and the consumer’s rights. The consumer may terminate free of charge within 30 days after receiving that information or, if the modification occurs later, within 30 days after the modification. This termination right does not apply if the impairment is only minor or access to and use of the unmodified product remain available without additional cost. § 327r BGB and more favourable mandatory law remain unaffected.

4.5 Outside clause 4.4, we may develop, modify or discontinue a feature only where this does not restrict contracted core functionality. We may discontinue a paid Service only under an applicable contractual or statutory termination right. We give the notice required in the individual case, enable an applicable data export and refund prepaid fees for the period after the contract ends.

4.6 A feature clearly labelled “beta”, “preview” or “experimental” remains in development and is not contracted core functionality unless the accepted order or service extension expressly says otherwise. A free Service may display advertising where the Service makes this apparent. Personalized advertising and non-essential device access require the legal basis and choices described in the applicable privacy information.

5. General customer and consumer protections

5.1 Before an order, we display the total price, term, material restrictions, available payment method, payment provider and legal seller. Prices displayed to consumers include statutory VAT. A payment processor does not become the seller merely by processing payment.

5.2 After an agreed fixed initial term, a consumer subscription continues only for an indefinite period and may then be terminated at any time with no more than one month’s notice. Cancellation is possible at least in text form. Where § 312k BGB applies, the relevant website keeps the statutory cancellation function continuously and easily accessible. The right to extraordinary termination for cause remains unaffected.

5.3 Where the law grants a withdrawal right, consumers receive the applicable instructions and model form before ordering and in the contract confirmation on a durable medium. Coflnet’s instructions and withdrawal channel are also available at coflnet.com/withdrawal. Where § 356a BGB applies, the online interface keeps the electronic withdrawal function continuously available, prominently placed and easily accessible during the withdrawal period. It supplements every other legally permitted unequivocal withdrawal statement.

5.4 A request or consent to begin performance during a withdrawal period, an acknowledgement that a withdrawal right may expire, a data-protection consent and any agreement to a deviation from statutory product characteristics are obtained separately where required. They are not inferred from Root acceptance. A withdrawal right ends early only if all applicable statutory conditions are met, including the conditions in § 356 (5) or (6) BGB and the confirmation required by § 312f BGB. Statutory rules on compensation for performance supplied before withdrawal remain unaffected.

5.5 We do not change a period already paid for retroactively. A higher price for a running consumer subscription takes effect only after the consumer expressly agrees to it; silence or continued use is insufficient. If the consumer does not agree, the existing price and contract continue until validly ended. We may terminate only under an existing ordinary or extraordinary termination right and may offer a new contract at the new price.

5.6 When a paid Service ends, we continue to provide access through the effective termination date unless a lawful suspension is necessary. We enable an applicable export and refund prepaid fees for an unprovided period and purchased value made unusable by our termination to the extent required by contract or law. Access to invoices, cancellation, withdrawal, data export, erasure requests and support is not conditioned on accepting a new Root.

5.7 We may close a dormant free account only after every linked Service and contract has ended; no usable or refundable balance, paid entitlement, pending invitation, remuneration, refund, dispute, support case, legal hold or other unresolved claim remains; and three full years have passed since the last authenticated login. We give at least three months’ notice on a durable medium and a further reminder at least one month before closure. An authenticated login before the closure date cancels the inactivity closure. Closure does not extinguish claims or require deletion of records that must lawfully be retained.

6. Fair use and enforcement

6.1 A user must not:

• upload or distribute unlawful, defamatory or rights-infringing content;
• knowingly exploit or conceal a vulnerability, bug or unintended function, access, credit, item, result or benefit;
• bypass authentication, payment, eligibility, rate, usage or other technical restrictions, manipulate rankings or service economies, or use automation outside documented interfaces and permissions;
• impair the security, integrity or availability of a Service or another person’s account, data or use;
• continue conduct identified as abusive after a reasonable request to stop or remedy it;
• circumvent a suspension, block or other measure, including through another account; or
• disclose or pass access credentials or API keys to an unauthorized person.

6.2 A user who becomes aware that their use has produced unauthorized access to another person’s account or data, or a material security, payment or billing anomaly has produced value or access to which they are not entitled, must stop the affected use, not copy or retain the data or benefit, and privately report the material facts without undue delay. The user need not continue testing, expose themselves to danger, investigate third-party systems or collect unnecessary evidence. Ordinary display errors, inconvenience and minor defects are outside this duty. Statutory remedy and withholding rights remain unaffected.

6.3 Some Services interact with third-party platforms. Accounts and activity on those platforms remain subject to their independent terms, and automation can lead to sanctions there. Users must have authority for every connected account and comply with applicable third-party rules. This does not exclude our responsibility for our own statements or conduct or liability that cannot be excluded. Unless an applicable service extension states otherwise, Coflnet is not affiliated with or endorsed by Microsoft, Mojang, Discord, Hypixel or a supported marketplace.

6.4 If reasonable, documented indications of misuse exist, we may apply the least intrusive proportionate measure suitable for the risk. Measures can include rate, volume or concurrency limits, additional verification, delayed processing, revocation of a session or key, restriction of an affected feature, or temporary account suspension. A measure may restrict contracted core functionality only to the extent and for the time necessary to investigate, contain an ongoing security or financial risk, protect users or data, or prevent material harm.

6.5 Before permanently closing an account or terminating an affected Service for cause, we consider the nature, severity, scope, duration and frequency of the conduct, fault, actual or foreseeable harm, earlier violations and the user’s explanation. Where appropriate and legally required, we warn the user and give a reasonable opportunity to stop or remedy the breach. Immediate action remains possible for a sufficiently serious, intentional or continuing violation after balancing both parties’ interests. § 314 BGB remains controlling.

6.6 Within the limits of the law, we may refuse a new registration, order or other new contract, including on documented grounds of fraud, payment abuse, circumvention of a prior measure or a bad-faith pattern of orders and reversals intended to cause damage. Refusal does not alter an existing contract, balance or statutory right.

6.7 We inform an affected user of a measure, its material reason, scope and expected duration or termination date unless and for as long as disclosure is prohibited by law or would materially compromise security, fraud prevention or an investigation. The user can contest a measure through [email protected]. A human reviewer considers the available information and corrects or lifts an unsupported measure. Additional statement-of-reasons and redress duties under the EU Digital Services Act remain unaffected.

6.8 We may correct records and reverse unintended access, duplicate entries or benefits that were not validly acquired. Purchased balances and prepaid value are not automatically forfeited because of a suspension or breach; any set-off, withholding, refund or damages claim requires a legal basis. Mandatory remedies, data access and export rights remain unaffected.

6.9 Good-faith security research and reporting that follows our Responsible Disclosure Policy is not misuse under this section. The policy describes the permitted scope, safe-harbour conditions and reporting channel; it does not authorize access to third-party data, service disruption or retention of an exploited benefit.

7. User content and confidentiality

7.1 Users retain their rights in content they upload or deliberately submit.

7.2 For the term of the relevant contract, a user grants us a non-exclusive right to store, reproduce and technically process their content only to the extent necessary to provide, secure and support the Service. Only where the user deliberately enables sharing does this right include transmission, display or making the content available to the intended recipients and configured community or moderation endpoints. The right ends when sharing is disabled, the content is deleted or the contract ends, as applicable, subject to a disclosed moderation or retention rule, documented backup cycle, transaction evidence or statutory retention duty.

7.3 Use beyond clause 7.2, including model training, requires a separately described legal basis and, where based on consent, a voluntary, specific opt-in that can be withdrawn for the future. Accepting these Core Terms is not that opt-in.

7.4 We treat uploaded CAD files and comparable non-public business documents as confidential. Human access is restricted to authorized personnel where necessary for support, security or error analysis. We use such documents for general product improvement only in irreversibly anonymised form or with separate permission. Anonymised output must not permit reconstruction of the confidential document, personal data, trade secrets or protected intellectual property.

7.5 If a user deliberately attaches a file or output to an error report after the submission path states the test purpose and retention, the user grants us the limited right to reproduce and use it to investigate the reported error, verify a correction and regression-test that correction while the affected function remains maintained. The user may withdraw that permission through the report or support channel; we then delete the test file once the reported error is resolved, no later than closure of the report, unless law independently requires a limited record. Clause 7.4 continues to protect confidential material, and any model-training use still requires the separate basis described in clause 7.3. Deleting the optional test file does not by itself reverse an independently approved reward.

7.6 If a user voluntarily submits a suggestion, correction or other feedback through a designated feedback path, the user grants us a non-exclusive, worldwide, royalty-free licence to store, review, use and implement it to evaluate, operate, maintain and improve our Services. The user keeps all other rights. Feedback creates no entitlement to implementation, response or reward. It must not contain another person’s personal data, credentials or confidential material that the sender is not permitted to disclose.

8. Our intellectual property

8.1 Our software, texts, graphics, databases and trademarks are protected by intellectual-property law. The user receives the non-exclusive, non-transferable right to use the relevant Service within the accepted contractual scope. Further reproduction, modification, distribution or making available to the public requires permission unless contract or law permits it. Statutory exceptions, including § 69d German Copyright Act, remain unaffected.

9. Warranty and mandatory consumer law

9.1 Statutory warranty rights apply to paid Services; for consumers this includes in particular §§ 327 et seq. BGB for digital products.

9.2 For a genuinely free Service outside §§ 327 et seq. BGB, the statutory defect rules for the applicable contract type apply. Where §§ 327 et seq. BGB apply because a consumer provides personal data as consideration, all statutory conformity, update and remedy rights remain unaffected.

9.3 Nothing in the accepted contract excludes, restricts or modifies a consumer guarantee, right or remedy under mandatory law that cannot validly be waived. Mandatory protections of the consumer’s country of habitual residence remain unaffected. For consumers in Australia, this includes the consumer guarantees and remedies under the Australian Consumer Law, including a refund for a major failure.

10. Liability

10.1 We are liable without limitation for intent and gross negligence, for damage arising from injury to life, body or health, under the German Product Liability Act, and within the scope of a guarantee we have given.

10.2 In cases of slight negligence, we are liable only for breach of essential contractual obligations whose fulfilment makes proper performance possible and on whose observance the other party may regularly rely. Liability is then limited to the foreseeable damage typical for the contract.

10.3 Any further liability is excluded. These limitations also apply in favour of our legal representatives and vicarious agents. Mandatory liability and claims that cannot validly be limited by standard terms remain unaffected.

11. Data protection and third-party data

11.1 Information about our processing of personal data is provided in the applicable Privacy Policy and product notices. Those notices are information, not acceptance-based contract terms.

11.2 A user may upload or connect third-party personal data only where their collection, use and instructions to us are lawful and required information has been given. Where Coflnet is to process personal data on a business customer’s documented instructions, that processing begins only after an agreement meeting Article 28 GDPR and the applicable subprocessor information are in force. Coflnet’s own account, billing, security and legal-compliance processing remains subject to its separately identified controller responsibilities.

12. New versions and changes to an accepted contract

12.1 A new document or Root version applies to a new contract only if provided and accepted before that contract is concluded. Publishing a new version never mutates an earlier dependency or Root.

12.2 A change to an existing contract requires express agreement to a new complete Root, except to the extent mandatory law applies directly without agreement. Before requesting assent, we provide the proposed Root, changed documents, reasons and intended effective date individually on a durable medium. Acceptance uses the process in clause 2.2 and is recorded under clause 2.3.

12.3 If the other party does not agree, the existing contract and accepted Root remain in force until validly ended. Refusal is not a breach and is not by itself cause for extraordinary termination. We may condition a genuinely new order, upgrade or optional contract on acceptance of the Root offered for that new contract. An existing entitlement can be stopped only under an applicable contractual or statutory termination right.

12.4 Activating an optional feature does not require a new Root only if the accepted tree already identifies and fully contains every term applicable to that feature and activation does not materially change rights or obligations. Adding or changing a contractual dependency, applicability rule or material right requires a new Root and express assent. Consumer digital-product modifications remain separately governed by clause 4.4 and § 327r BGB.

13. Consumer dispute resolution

13.1 Coflnet is neither willing nor obliged to participate in dispute-resolution proceedings before a consumer arbitration board within the meaning of the German Consumer Dispute Resolution Act (VSBG).

14. Final provisions

14.1 The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). For consumers, this choice applies only insofar as it does not deprive them of mandatory protection under the law of their habitual residence.

14.2 If the user is a merchant, legal entity under public law or special fund under public law, the exclusive place of jurisdiction for disputes arising from the contractual relationship is Coflnet’s registered seat.

14.3 These Core Terms and their extensions can be offered in German and English. The Root pins the available language variants and their hashes; the order or acceptance record identifies the contractual language used. Where both language versions are incorporated and differ, the German version prevails for business users; for consumers, the version in the language in which the contract was concluded applies.

14.4 A transfer of shares in or change of control over Coflnet does not by itself change the contracting party. We may use affiliates and subcontractors to perform a Service while remaining responsible for contractual performance.

If a contract or Service passes to another entity through merger, division, spin-off or another statutory universal succession, mandatory law governs the succession and creditor protections. We inform the affected party individually on a durable medium as early as reasonably possible of the successor, affected Service, effective date and applicable rights.

For another transfer, the other party agrees that we may transfer the contract for a specified Service as a whole to a legal entity established in the European Economic Area that acquires or operates that Service, but only if it assumes all rights and obligations. The transfer does not alter price, scope, term, paid entitlement, balance, warranty rights, claims or defences. We give at least 30 days’ individual advance notice on a durable medium, naming the transferee, affected contract and effective date. The other party may terminate the affected contract free of charge before transfer through the same readily available electronic termination channel used for the Service. We refund advance payments for the period after termination and purchased value made unusable by our termination to the extent required by law.

Any disclosure or transfer of personal data must independently comply with data-protection law. A transfer clause does not authorize a new processing purpose or waive data-subject rights.

14.5 If a provision is invalid, the remaining provisions remain valid and the statutory rule replaces the invalid provision. This does not reverse the statutory burden of proof or interpretation rules.

14.6 Mandatory statutory rights, in particular mandatory consumer rights, remain unaffected by every contractual document without needing to be repeated in each provision.