Terms of Service & Community Guidelines

Provider / Operator (Imprint)

Felix Frenzel
Hellerstraße 9
96047 Bamberg
Germany
Phone: +49 151 59200157
E-mail: info@clean-core.io

Clean-Core.io is a private, non-commercial community project for the SAP community. It is operated by the above-named individual and is not affiliated with, endorsed by, or connected to SAP SE or Google LLC.

1. Scope and Purpose

Clean-Core.io is a free community program provided solely for research and evaluation purposes in the domain of automated code modernization (ABAP to Cloud-Native, including Node.js). By registering for or using the Platform, you accept these Terms of Service and Community Guidelines (the “Terms”). If you do not agree, you may not use the Platform.

The Platform is intended for professional and evaluation use. By participating, you help shape and improve this community utility.

Minimum age: You must be at least 18 years old to register for or use the Platform. Accepting these Terms means entering into a contract, and under German law a minor has only limited capacity to do so (§§ 106 ff. BGB), so an acceptance given without a parent or guardian would remain provisionally invalid. The Platform is a tool for professional software work and is not directed at children. We do not verify age — asking for proof would mean collecting more personal data than the service needs, not less — but we will delete an account on notice that it belongs to someone younger.

3. Nature of Generated Output; Mandatory Architect Review

All modernization analyses, source code, and related artifacts produced by the Platform — whether computed by the deterministic analysis or generated by a generative AI model (section 4.1) — are automatically produced drafts. They are illustrative only and are not fit for productive use in their delivered state.

4. AI-Generated Output, Agreed Characteristics and Limitation of Liability

4.1 Agreed characteristics of the digital product. The Platform produces two kinds of output. (a) Deterministic results — in particular the findings with their line references, the extensibility route, the Clean Core Score, the clean core levels shown for SAP objects, the process reconstructed from the source code, and the Economics calculation made from the figures you enter — are computed by rule-based analysis of the source code you submit and of published SAP data, without a generative AI model. They are evidence for your own assessment, not a guarantee: they can be incomplete or wrong, in particular where the analysis could not determine something. The clean core levels are an orientation and do not replace the ABAP Test Cockpit. (b) Model-generated output — the narrative around the findings, proposed business names and sentences, the solution design, transformed source code, the technical documentation and business blueprint, and proposed test cases and test suites — is generated automatically by generative AI models (section 5) where you use those functions. The parties expressly agree that the output owed under this contract consists of automatically synthesized draft artifacts which are illustrative only and which must be inspected, validated and approved by qualified software architects before any compilation, deployment or use in a test, staging or productive environment (section 3). The operator therefore does not owe the correctness, completeness, security, compilability, merchantability or fitness for a particular purpose of any individual output, whether deterministic or model-generated.

4.2 Consumers. Where you are a consumer within the meaning of § 13 BGB and provide personal data in connection with the use of the Platform, the deviation from the objective requirements set out in section 4.1 applies only where you have been specifically informed of it before submitting your contractual declaration and have expressly and separately agreed to it at that time (§ 327h BGB). Your statutory rights under §§ 327 ff. BGB — in particular as to conformity, updates and remedies — otherwise remain unaffected; sections 2, 4.1, 4.3 and 6 neither are intended to nor do limit those rights.

4.3 Liability of the operator.

(a) The operator is liable without limitation for damages caused intentionally or by gross negligence, for damages arising from injury to life, body or health caused by a breach of duty by the operator, for the fraudulent concealment of a defect, where the operator has assumed a guarantee, and under the German Product Liability Act (Produkthaftungsgesetz).

(b) In the case of slight negligence, the operator is liable only for the breach of an essential contractual obligation. An essential contractual obligation is an obligation whose fulfilment makes the proper performance of this contract possible in the first place, whose breach jeopardises the achievement of the purpose of the contract, and on whose observance you may therefore regularly rely. In such cases, liability is limited to the damage that is foreseeable and typical for a contract of this kind.

(c) Any further liability of the operator is excluded. In particular, the operator is not liable for slightly negligent breaches of obligations that are not essential contractual obligations.

(d) Liability for the loss of data is limited to the expense that would have been necessary to restore the data had you made backup copies appropriate to the risk. You remain responsible for retaining your own copies of the source code you submit and of the output you receive.

(e) Sections 4.3(a) to (d) apply equally to the liability of the operator's legal representatives, employees and vicarious agents, and to claims in tort.

(f) The above provisions do not alter the statutory allocation of the burden of proof. Statutory liability privileges applicable to the gratuitous provision of services (in particular §§ 521, 599 BGB) remain unaffected where they apply. Nothing in these Terms excludes or limits liability that cannot be excluded or limited under applicable mandatory law.

6. Usage Limits / Quota

To keep the Platform available to the community, usage without your own API key is subject to a quota: currently a total of 5 transformations per user account. One transformation is counted when a new ABAP source object is submitted for analysis. All subsequent stages of that transformation — solution design, code transformation, documentation, testing, TCO and delivery — as well as the glossary assistant are not counted, and re-analysing the same source object does not count again. The starter examples supplied with the Platform are the exception in both directions: each of them may be analysed once per user account without being counted, and every further analysis of the same example is counted, including where its source is unchanged. An example you have modified is your own source object and is counted as one. A transformation is counted only once the analysis has completed; an analysis that is aborted or fails is not counted. This is a one-time allotment and is not reset on a daily or monthly basis. When you provide your own Google Gemini API key (BYOK, see section 5), no quota applies. Fair-use rate limits apply to all accounts. The operator may adjust, introduce or remove quotas with effect for the future in order to protect the stability and fair use of the Platform. A one-time allotment already granted to your existing account and not yet used will not be reduced retroactively. A reduction with effect for the future will be notified in text form at least 30 days in advance; section 2.5 applies accordingly.

7. Community Guidelines and Code of Conduct

As a participant in the Free Community Edition, you agree to constructive and respectful rules of engagement:

• Do not upload malicious software, illegal scripts, or proprietary source code that violates intellectual property rights or confidentiality obligations.
• Do not upload personal data of third parties — section 8 says what to strip out of your code before you submit it.
• Maintain a respectful, collaborative, and professional tone in all community spaces.
• Report system hallucinations, security vulnerabilities, or compilation errors to help continuously refine the engine.

The operator may remove content and restrict, suspend or terminate access where there is an objective reason for doing so, in particular a breach of these Terms or of the Code of Conduct. Any such measure follows section 2.4: the operator will inform you of the reason for it without undue delay in text form, you will be given an opportunity to respond, and the measure will be lifted as soon as the reason for it ceases to apply. Your statutory rights, and your right to object to the measure and to have it reviewed, remain unaffected.

9. Data Protection

Personal data is processed in accordance with the EU General Data Protection Regulation (GDPR) and applicable German data-protection law. Details on the nature, scope, and purpose of processing are set out in the separate Privacy Policy (Datenschutzerklärung) available on the Platform at clean-core.io.

This section is about the personal data we process about you as a user of the Platform. Personal data that ends up inside the content you upload is a different question, and section 8 answers it: it does not belong on the Platform.

10. Changes to These Terms

10.1 These Terms can be amended only by agreement between the parties. The operator will notify you of a proposed amendment in text form to the e-mail address associated with your account at least six weeks before the date on which it is proposed to take effect. The notice will contain the amended text, a clear indication of the provisions that are changing, and the reason for the amendment.

10.2 An amendment becomes binding on you only if you accept it expressly, for example by confirming it in the dialogue displayed at your next sign-in. Your silence, and your continued use of the Platform, do not constitute acceptance of an amendment.

10.3 If you do not accept a proposed amendment, you may continue to use the Platform on the basis of the Terms as they stood before the proposed amendment. Your right to terminate at any time under section 2.3 remains unaffected. The operator may in that case terminate the contract in accordance with section 2.3 by giving at least 30 days' notice in text form, where continuing the contract on the existing Terms cannot reasonably be expected of the operator.

10.4 Valid reasons for proposing an amendment are: (a) changes in the applicable law, or binding decisions of a court or a public authority; (b) changes to the third-party services on which the Platform depends (section 5), including changes to their terms, their technical interfaces or their availability; (c) the introduction of new functions, or the discontinuation of existing functions, of the Platform; (d) closing a gap in these Terms which has become apparent after their conclusion and which cannot be resolved by interpretation; and (e) amendments which are purely advantageous or neutral for you. Amendments affecting the essential content of the contract — in particular the scope of the service owed under sections 1 to 3 and the liability provisions in section 4, to your detriment — are never implemented unilaterally and always require your express acceptance under section 10.2.

10.5 The operator publishes the current version of these Terms, together with all previous versions and their effective dates, at clean-core.io/terms.

11. Governing Law and Jurisdiction

These Terms and any dispute arising out of or in connection with them are governed by the laws of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). Mandatory consumer-protection provisions of the country in which a consumer has their habitual residence remain unaffected.

To the extent permitted by law, the place of jurisdiction for all disputes is Bamberg, Germany. This choice of jurisdiction does not apply to consumers where prohibited by mandatory law.

12. Severability

Should any provision of these Terms be or become invalid or unenforceable, the validity of the remaining provisions shall not be affected. In place of an invalid or unenforceable provision, the statutory provisions apply.

Contact

Questions regarding these Terms can be directed to:
Felix Frenzel
Hellerstraße 9, 96047 Bamberg, Germany
Phone: +49 151 59200157
E-mail: info@clean-core.io