Skip to content

Cookie settings

With your consent we use Google Analytics and Google Ads to measure how the website is used and whether our ads work. Google sets cookies for this and also processes data in the USA. Without consent none of it loads. You can change or withdraw your choice at any time under “Cookie settings” in the footer. More in the privacy policy

Purposes
NecessaryAlways on

Stores your choice in your browser’s storage so we do not ask on every page.

Google Analytics: which pages are viewed and where visits come from, so we can improve the website.

Google Ads: whether visits from our ads lead to a sign-up or an enquiry.

Limenia
  • Features
  • How it works
  • Integrations
  • DSA
  • Guides
  • Docs
  • Pricing
DeutschDERequest a demoLog inStart free trial
  • Features
  • How it works
  • Integrations
  • DSA
  • Guides
  • Docs
  • Pricing
  • FAQ
  • Contact
Start free trialRequest a demoLog in

General Terms and Conditions for Limenia

Version 1.1, as of 27 October 2026

This is an English translation for information only. Only the German version (https://limenia.eu/agb/) is binding (§ 1(5)).

Provider: Karim Belkacem, sole proprietor, trading as “SB-Techworks”, Lilienthalstr. 38, 93049 Regensburg, Germany Phone +49 941 46395983, e-mail [email protected], VAT ID DE369343383

These Terms apply to businesses only, not to consumers. They consist of the main text (§§ 1 to 23), the Service Description (Annex 1) and the Acceptable Use Policy (Annex 2). The Data Processing Agreement (DPA, in German “Auftragsverarbeitungsvertrag” or “AVV”) is published at https://limenia.eu/avv/ (English translation: https://limenia.eu/en/dpa/).

Contents

  • § 1 Scope and contract documents
  • § 2 Definitions
  • § 3 Conclusion of the contract
  • § 4 Services of the provider
  • § 5 AI features
  • § 6 Trial
  • § 7 Prices and payment
  • § 8 Term, termination and restricted mode
  • § 9 Obligations of the customer
  • § 10 Blocking of access
  • § 11 Availability, maintenance and backups
  • § 12 Support
  • § 13 Data protection
  • § 14 Confidentiality
  • § 15 Rights in the software and in data
  • § 16 Rights in case of defects
  • § 17 Liability
  • § 18 Indemnification
  • § 19 Return and deletion of data at the end of the contract
  • § 20 Notices of illegal content and point of contact
  • § 21 Changes to these Terms
  • § 22 Use as a reference
  • § 23 Final provisions
  • Annex 1: Service Description
  • Annex 2: Acceptable Use Policy

§ 1 Scope and contract documents

(1) These General Terms and Conditions (“Terms”) apply to all contracts between the provider and its customers for the use of Limenia. Limenia is a service provided over the internet (software as a service) for content reports, moderation and sanctions in apps and online services.

(2) The provider enters into contracts only with businesses (Unternehmer) within the meaning of § 14 of the German Civil Code (BGB), with legal entities under public law and with special funds under public law. The provider does not enter into contracts with consumers within the meaning of § 13 BGB. On conclusion of the contract, the customer confirms that it uses Limenia for its commercial or independent professional activity. The provider may ask for proof, such as the VAT identification number or an extract from a commercial register.

(3) General terms and conditions of the customer do not become part of the contract. This also applies if the customer refers to them in orders, confirmations or procurement portals, if the provider does not expressly object to them, or if the provider performs services without reservation while aware of such terms. Deviating terms apply only if the provider expressly agrees to them in text form.

(4) The contract consists of the following documents, which take precedence in this order in case of conflict:

  1. individual agreements of the parties, such as an offer under § 3(5);
  2. the Data Processing Agreement (“DPA”, https://limenia.eu/en/dpa/) for all matters concerning the processing of personal data on behalf of the customer;
  3. the Service Description (Annex 1);
  4. these Terms including the Acceptable Use Policy (Annex 2);
  5. the price list valid at the conclusion of the contract (https://limenia.eu/en/#pricing).

(5) The German version of these Terms is authoritative. The English translation is for information only.

§ 2 Definitions

  • Limenia: the provider’s service, consisting of the dashboard at https://app.limenia.eu, the application programming interface (API) at https://app.limenia.eu/v1, the webhooks, the connectors and the documentation.
  • Customer account: the customer’s area in Limenia (called “tenant” in the product). It holds the customer’s apps, members, settings and data separately from other customers.
  • App: an app or online service of the customer that the customer creates in Limenia and connects through the API.
  • End users: the users of the customer’s apps, such as reported persons, reporters and complainants.
  • Members: the persons to whom the customer grants access to its customer account, with the roles owner, admin, moderator or viewer. The owner acts for the customer in the product. Only an owner can buy, change and cancel plans, set the retention periods and switch on AI features.
  • Customer data: all data that the customer, its members or its apps transmit to Limenia or create there, in particular reports, content, media, cases, decisions, appeals, review requests, user files, store reviews and settings.
  • Plan: Basis, Pro or Premium with the features and limits under Annex 1. Add-on: the AI pre-check for the Basis plan.
  • AI check: one call of the AI model under Annex 1, section 5.
  • Restricted mode: the state of the customer account under § 8(5).
  • End of the contract: the end of the trial without a plan being purchased (§ 6(4)) or the date on which a termination takes effect (§ 8). Late payment (§ 7(6)) does not end the contract.
  • Text form: text form under § 126b BGB, for example e-mail.

§ 3 Conclusion of the contract

(1) The presentation of Limenia on the website is not a binding offer.

(2) Trial. The customer can request a trial through the form on the website or by e-mail. The provider is free to decide whether to accept the request. Before the customer account is set up, the customer declares in text form that it accepts these Terms and the DPA. The contract for the trial is concluded when the provider confirms the setup in text form; the invitation of the first owner counts as this confirmation. § 6 applies to the trial.

(3) Purchase of a plan. In the dashboard, under “Settings → Plan and usage”, the owner selects a plan and, if applicable, the add-on. The owner is then forwarded to the payment page of the payment service provider Stripe (Stripe Checkout). There, the owner enters the billing details and the payment method, confirms with the mandatory checkbox that these Terms and the DPA apply, and completes the process with the button for an order with obligation to pay. With the checkbox, the customer also confirms that it acts as a business (Unternehmer) within the meaning of § 14 BGB (§ 1(2)). This is a binding offer by the customer. The contract is concluded when the provider activates the plan in the customer account.

(4) The owner who concludes a contract for the customer must be authorised to do so. By concluding it, the owner warrants this authority.

(5) Individual contracts. The customer can buy the Premium plan under paragraph 3. For more apps or AI checks than the plan provides, for yearly billing, for billing by invoice outside Stripe, or for commitments on availability and response times (service level), the provider prepares an individual offer on request. The contract is concluded when this offer is accepted in text form. Unless the offer provides otherwise, these Terms apply.

(6) The provider makes these Terms available for retrieval and storage at https://limenia.eu/agb/ (English translation: https://limenia.eu/en/terms/). It stores the acceptance of these Terms and the DPA with the version, time and ID of the purchase as evidence (privacy policy, section 8). The parties agree that § 312i(1) sentence 1 nos. 1 to 3 and sentence 2 BGB do not apply.

§ 4 Services of the provider

(1) For the term of the contract, the provider makes Limenia available to the customer for use over the internet within the scope of the plan booked. The type and scope of the services are set out in the Service Description (Annex 1). The customer receives no copy of the software and no source code.

(2) The point of delivery is the connection of the data centre used by the provider to the internet. The provider is not responsible for the internet connection of the customer and its apps up to this point.

(3) A tool, not legal advice. Limenia is a tool. With it, the customer can implement its obligations under Regulation (EU) 2022/2065 on digital services (“DSA”), under the guidelines of the app stores and under its own terms of use. The customer remains responsible for meeting these obligations, in particular for

  1. its moderation decisions and measures against end users,
  2. the statements of reasons under Art. 17 DSA, the responses to appeals and all other communications to end users, even if they are based on templates or suggestions from Limenia,
  3. its policies, reason codes and terms of use,
  4. submissions to the DSA Transparency Database and the content of its transparency reports,
  5. its replies to reviews in the app stores.

The provider does not give legal advice. Templates, checklists (such as the store checklist), standard texts and notes in Limenia and in the documentation are aids. They do not replace a legal review in the individual case. The provider does not owe that the customer meets all legal requirements merely by using Limenia.

(4) Enforcement in the apps. Limenia does not itself enforce decisions in the customer’s apps. The app enforces a decision after Limenia has reported it to the app’s backend by webhook, or Limenia carries it out through a connector that the customer has set up (Annex 1, section 4). Limenia does not contact end users. The customer’s app shows statements of reasons and responses to appeals.

(5) Third-party services. The customer uses connectors and interfaces to third-party services on the basis of its own contracts with these third parties, for example with Google (Firebase, Google Play, Play Integrity), Apple (App Store Connect, DeviceCheck), Supabase, RevenueCat and GitHub. The same applies to the DSA Transparency Database of the European Commission. The provider is not responsible for the availability, services and changes of these services. If a third party changes its interface or its terms so that a connector can no longer be operated, or only with disproportionate effort, the provider may adapt or discontinue the connector. It informs the customer without undue delay.

(6) Further development. The provider develops Limenia further. It may change Limenia if the agreed features of the plan booked are essentially preserved and the change is reasonable for the customer. If an essential feature of the plan booked is removed without equivalent replacement, the provider announces this at least six weeks in advance in text form. The customer may then terminate the contract without notice until the change takes effect. The provider may make changes required to close security vulnerabilities or due to mandatory legal or regulatory requirements immediately; it informs the customer about them. Annex 1, section 7 applies to changes to the API.

(7) Features marked as “planned”, “soon” or similar on the website, in the dashboard or in the documentation are not part of the contract until the provider releases them for the plan booked.

(8) The provider may use third parties to provide the services. The DPA applies to sub-processors.

§ 5 AI features

(1) Limenia offers an AI pre-check of reported content and review requests and an AI classification of store reviews (Annex 1, section 5). The AI features run only if the owner expressly switches them on for the customer account (opt-in). The owner can pause or switch them off at any time.

(2) The AI provides assessments and suggestions. It can be wrong, for example by classifying content incorrectly or missing violations. In Limenia, a member of the customer always decides on content, accounts and appeals. Limenia makes no automated moderation decisions. Limenia sends replies to store reviews only after a member has approved the individual reply. The customer reviews suggestions before adopting them and ensures that its members are sufficiently trained for this (cf. Art. 4 of Regulation (EU) 2024/1689, the “AI Act”).

(3) Individual incorrect assessments or suggestions are not a defect as long as the AI feature otherwise works as described in Annex 1.

(4) For the AI features, the provider currently uses Mistral AI SAS, Paris, France, as a sub-processor. Processing takes place via Mistral AI’s EU endpoint in data centres in EU and EFTA states (Annex 3 of the DPA, https://limenia.eu/en/dpa/#anlage-3). The provider may change the AI provider and the model if the feature is essentially preserved. The rules of the DPA apply to a new sub-processor.

(5) The provider uses the AI provider only as a sub-processor that processes the data on the provider’s instructions to provide the AI features (§ 9 of the DPA). The provider trains and improves its own models only with anonymised data (§ 15(5)).

(6) AI checks count against the quota of the plan or the add-on. § 7(3) applies to checks beyond the quota. AI features are not available during the trial or in restricted mode.

§ 6 Trial

(1) The trial lasts 30 days from the setup of the customer account. During the trial, the features and limits of the Pro plan are available, but without AI features. The trial is free of charge. No payment method is required.

(2) The trial ends automatically after 30 days without the need for termination. It does not turn into a paid contract automatically. Costs arise only if the customer buys a plan (§ 3(3)). The provider may extend the trial at the customer’s request.

(3) If the customer buys a plan during the trial, the trial ends immediately and the paid contract begins.

(4) If the trial ends without a purchase, the contract for the trial ends with it. The customer account remains usable in restricted mode (§ 8(5)) until its deletion under § 19. Until then, the customer can buy a plan and continue to use the customer account with all its data. The provider informs the customer in text form before the deletion.

(5) § 16(7) and § 17(4) apply to defects and liability during the trial.

§ 7 Prices and payment

(1) The prices of the price list valid at the conclusion of the contract (https://limenia.eu/en/#pricing), as shown in Stripe Checkout, or the prices of the individual offer apply. All prices are net prices plus statutory VAT. For customers established in another EU member state with a valid VAT ID, the reverse charge procedure applies.

(2) The billing period is the calendar month. The first billing period runs from the conclusion of the contract to the end of the current calendar month. The base fee for the plan and the add-on is due in advance for the respective billing period; for a shorter billing period it is charged pro rata. Payment is made through Stripe using the payment methods offered there. The customer authorises the provider to collect amounts due from the stored payment method through Stripe. The provider makes invoices available electronically, in particular in the Stripe customer portal. The customer agrees to electronic transmission.

(3) AI overage. The quota of AI checks applies per calendar month (UTC). Unused checks lapse at the end of the month. When the quota is used up, Limenia stops further AI checks until the end of the month; this is the default setting. Only if the owner switches on overage in the dashboard do AI checks continue. Each additional AI check then costs the price in the price list, currently 2 cents net. Overage is charged only while overage is switched on. It is billed monthly in arrears, usually with the next monthly invoice. The daily limit of the customer account (Annex 1, section 5) also applies to overage. The owner can switch overage off again at any time.

(4) Plan changes. In the dashboard, the owner can change the plan and add or remove the add-on at any time. Changes take effect immediately. The difference for the current billing period is settled pro rata, as a credit or an additional charge. The add-on is available only with the Basis plan; it is removed when switching to Pro or Premium. After switching to a smaller plan, features not included in that plan are no longer available. If the customer then exceeds a limit of the new plan, such as the number of apps, it cannot create further apps until it is below the limit again.

(5) Price changes. The provider may change the prices with effect for the future. It announces a price increase in text form at least six weeks before it takes effect. The customer may terminate the contract with effect from the date the price increase takes effect, up to that date (special right of termination). The provider points out this right in the announcement. The right of ordinary termination remains unaffected. Price reductions may take effect immediately. For individual contracts, the rules agreed there apply.

(6) Late payment. If a collection fails, Stripe retries it and reminds the customer. During this time, the features of the plan remain available. If payment has not been received more than 14 days after the due date and after at least one payment reminder, the provider may put the customer account into restricted mode until the outstanding amounts are paid. The features under § 8(5) no. 1 remain available. Otherwise, the statutory rules on default apply. The right of extraordinary termination (§ 8(4)) remains unaffected.

(7) The customer may set off only claims that are undisputed or have been finally established by a court. It may exercise a right of retention only on the basis of claims under this contract. Neither restriction applies to claims of the customer for defects or for partial non-performance under the same contract.

§ 8 Term, termination and restricted mode

(1) A contract concluded through Stripe runs for an indefinite period with monthly billing periods. The customer may terminate it at any time with effect from the end of the current billing period, either as owner in the Stripe customer portal or in text form to the provider. In case of ordinary termination, fees already paid for the current billing period are not refunded.

(2) The provider may terminate such a contract in text form with three months’ notice to the end of a billing period.

(3) The term and termination of individual contracts are governed by the offer. If the offer does not govern them, paragraphs 1 and 2 apply.

(4) The right of both parties to terminate for good cause remains unaffected. Good cause exists for the provider in particular if

  1. the customer is in default with the payment of an amount equal to two monthly base fees, or
  2. despite a warning in text form, the customer seriously or repeatedly violates § 9 or the Acceptable Use Policy (Annex 2). A warning is not required if it is not expected to be successful or if the violation is so serious that the provider cannot reasonably be expected to continue the contract, for example if depictions of the sexual abuse of children are knowingly uploaded.

(5) Restricted mode. The customer account enters restricted mode when the trial ends without a purchase, when a paid contract ends, or when the provider puts it into restricted mode under § 7(6). In restricted mode:

  1. Everything the customer needs for its obligations under the DSA remains possible: Limenia continues to accept reports and appeals from the apps, members can handle and decide cases and appeals, decisions continue to be reported to the apps, and the data remain readable. Reports are never rejected because of the plan or the state of the subscription, because the notice-and-action mechanism under Art. 16 DSA must remain reachable at all times.
  2. In particular, new apps and API keys, new review types and review requests, signals and rules, device checks, store reviews, all AI features and the add-on are blocked. Details are set out in Annex 1, section 6.
  3. Restricted mode itself does not lead to the deletion of data. The retention periods continue to run, and Limenia deletes expired data as usual.
  4. If restricted mode was triggered by late payment, it ends with the payment. After the end of a contract, it is a transitional arrangement until the deletion under § 19. No fees are charged for it, and § 16(7) and § 17(4) apply.

(6) Terminations require text form. Termination in the Stripe customer portal is sufficient.

(7) § 19 governs what happens to customer data at the end of the contract.

§ 9 Obligations of the customer

(1) The customer uses Limenia only within the scope of these Terms, the Acceptable Use Policy (Annex 2) and applicable law.

(2) Credentials. The customer keeps API keys, webhook secrets, credentials for connectors and the sign-in details of its members secret. API keys belong only in the backend of the app, never in the app itself, in web pages, in logs or in publicly accessible repositories. If there is a suspicion that unauthorised persons know a key or credential, the customer revokes it without undue delay in the dashboard or with the respective third party and informs the provider if Limenia may be affected. Each member uses their own account. Accounts must not be shared.

(3) Members. The customer decides who receives access to its customer account and with which role. It removes access as soon as a person no longer needs it. The customer is responsible for actions its members take through the customer account as for its own actions.

(4) Data protection towards end users. The customer is the controller within the meaning of the GDPR for the personal data in its customer account. In particular, it ensures that

  1. there is a legal basis for the transmission to Limenia and the processing there,
  2. it informs its end users about the processing in its privacy notices, i.e. about reports and moderation and, where used, about the AI pre-check, the connectors, store reviews and submissions to the DSA Transparency Database,
  3. it carries out a data protection impact assessment where required,
  4. it meets the requirements of § 25 of the German Telecommunications Digital Services Data Protection Act (TDDDG) if its app accesses information on the end device for the device connector,
  5. it responds to requests from data subjects. The provider supports it in this under the DPA.

(5) Setup. The customer sets up Limenia carefully, tests its integration before use with real end users and keeps the setup up to date. This applies in particular to

  1. the retention periods, which the owner sets as controller,
  2. policies, reason codes and templates,
  3. the webhook targets and the verification of webhook signatures in the app’s backend,
  4. the connectors, to which the customer grants only the least privileges necessary in the respective third-party system,
  5. submissions to the DSA Transparency Database. Whatever is submitted there is public. The customer switches on the submission of the facts only if they contain no personal data.

(6) Only what moderation needs. The customer transmits to Limenia only data it needs for reports, moderation, appeals, pre-moderation, signals and the other features of Limenia. Limenia is not an archive and not a storage for other purposes. The customer transmits illegal content only to the extent it is the subject of a report, an appeal or a review request.

(7) Child safety. The customer does not knowingly transmit depictions of the sexual abuse of children or adolescents to Limenia as media. In case of such a suspicion, it uses the reason codes child_safety or protection_of_minors in the report. Limenia then stores no copy of the media, only their address, deletes copies already stored for this content and marks the case as urgent. There is no separate alert. The customer itself meets obligations to preserve evidence and to inform authorities, for example under Art. 18 DSA.

(8) Store reviews and connectors. The customer remains responsible for replies in the app stores, even if they are based on a reply suggestion by the AI or a template. The check before sending is an aid. Limenia carries out actions that the customer triggers through connectors on the customer’s instruction, such as account bans, revoking entitlements or refunds through RevenueCat. Measures taken by Apple, Google or other third parties against the customer because of its replies or such actions are borne by the customer, unless they are based on a breach of duty by the provider.

(9) Own records. Limenia deletes data according to the customer’s retention periods and at the end of the contract (§ 19). If the customer needs data for longer, for example as evidence in legal proceedings, it sets a legal hold or transfers the data into its own systems, for example through the webhooks.

(10) The customer reports disruptions and defects without undue delay (§ 12, § 16) and keeps the e-mail address for notices about the contract up to date (§ 23(3)).

§ 10 Blocking of access

(1) The provider may temporarily block individual API keys, access of members or features if there are specific indications that

  1. access is being misused or has become known to unauthorised persons,
  2. the use endangers the security or operation of Limenia or the data of other customers, for example through attacks or overload, or
  3. the customer seriously violates the Acceptable Use Policy or uses Limenia for unlawful purposes.

(2) The provider chooses the least restrictive effective measure. In doing so, it takes into account that the customer’s apps must be able to accept reports under the DSA at all times. It informs the customer in advance if this does not jeopardise the purpose of the block, otherwise without undue delay afterwards. It lifts the block as soon as the reason for it no longer exists.

(3) The claim to the fee remains during a justified block.

§ 11 Availability, maintenance and backups

(1) The provider makes Limenia available with reasonable availability, as is customary for comparable services. The provider commits to a specific availability, response time or recovery time (service level) only in an individual contract (§ 3(5)).

(2) The provider may maintain and update Limenia. Where possible, it announces maintenance that leads to a significant interruption in advance in text form and schedules it, where possible, at times of low usage. Short interruptions during updates and urgent maintenance, for example to close security vulnerabilities, are permitted without announcement.

(3) Events beyond the provider’s control release it from the obligation to perform for their duration, to the extent it is not responsible for them. These include force majeure, disruptions of the internet beyond its control, attacks by third parties despite reasonable protective measures, orders of authorities and disruptions of third-party services under § 4(5). The customer’s statutory rights to a reduction of the fee remain unaffected.

(4) Backups. The provider backs up the Limenia database under Annex 1, section 10. The backups serve recovery after errors and disruptions. The customer has no claim to the recovery of individual data that it has deleted or that were deleted according to its retention periods. Media copies are not backed up separately.

§ 12 Support

(1) The provider offers support by e-mail to [email protected], in German or English, on working days (Monday to Friday except public holidays in Bavaria).

(2) The provider usually replies on the next working day. It commits to fixed response or resolution times only in an individual contract.

(3) Support covers questions about the use and integration of Limenia and the handling of reported disruptions. It does not include legal advice, programming in the customer’s systems or moderation of content.

(4) In support requests, the customer gives only identifiers where possible, such as the ID of a case, and no content or personal data of end users. The provider’s staff have no access to the customer’s cases and content in the dashboard. They access customer data only under the DPA.

§ 13 Data protection

(1) Insofar as the provider processes personal data on behalf of the customer, in particular data of end users, it acts as processor under Art. 28 GDPR. The DPA (https://limenia.eu/en/dpa/) applies to this. It is an annex to these Terms, and the parties conclude it together with these Terms (§ 3(2) and (3)).

(2) The provider processes under its own responsibility the data it needs for the conclusion of the contract and billing, for the members’ sign-in accounts (identity, sign-in, second factor, session and security logs) and for the operation and security of Limenia. By contrast, it processes memberships, roles and invitations in the customer account and the audit log on behalf of the customer under the DPA. Details are set out in the privacy policy (https://limenia.eu/en/privacy/) and in § 3(6) of the DPA. The customer refers its members to the privacy policy.

(3) The provider may use counters without personal reference, such as the number of reports, review requests and AI checks, for billing, checking plan limits, administering the platform and planning its capacity, and the further development of Limenia.

§ 14 Confidentiality

(1) The parties treat confidential information of the other party as confidential, use it only to perform the contract and protect it at least as carefully as their own confidential information, but at least with reasonable care. Confidential information includes customer data, credentials, non-public information about Limenia, for example about security measures, and all information marked as confidential or recognisably confidential from the circumstances.

(2) Information is not confidential if it is publicly known or becomes publicly known without breach of this contract, was lawfully known to the receiving party beforehand, is lawfully received from third parties without an obligation of confidentiality, or was developed independently by the receiving party.

(3) The parties may disclose confidential information to the extent required by law, court or authority. They inform the other party in advance where permitted. They may also disclose confidential information to advisers bound by professional secrecy and to third parties engaged by them, to the extent these need it and are bound to confidentiality.

(4) The obligations continue for three years after the end of the contract, and for trade secrets and credentials as long as they remain secret. The DPA remains unaffected.

§ 15 Rights in the software and in data

(1) All rights in Limenia, in the software, in the documentation and in the name “Limenia” belong to the provider or its licensors.

(2) For the term of the contract, the provider grants the customer the simple (non-exclusive), non-transferable and non-sublicensable right to use Limenia over the internet for its apps within the scope of the plan booked and to have it used by its members. If the customer operates apps on behalf of third parties, it may also use Limenia for these apps. The customer then remains the provider’s sole contractual partner. It concludes the necessary agreements with its clients, in particular on data protection.

(3) Publicly provided packages, examples and documentation, such as the Flutter packages limenia and limenia_device, are subject to the licences stated there. They grant no rights in the name “Limenia”.

(4) Customer data. Customer data remain with the customer. The provider acquires no rights in them, unless paragraph 5 provides otherwise. The customer grants the provider the rights it needs to provide the services, in particular to store, copy and process customer data and to transmit them to the sub-processors under the DPA and to the recipients designated by the customer. These rights apply for the term of the contract and until deletion under § 19.

(5) Anonymised data for own models. The provider may anonymise customer data and use the anonymised data to develop, train, test and improve its own models for detecting and assessing content. The following applies:

  1. Chat messages and reported content or content submitted for pre-moderation are used, each with the results of the check and the decision on it. Annex 5 of the DPA governs what is never used and how the provider anonymises the data.
  2. The provider does not train with personal data. If a record cannot be anonymised reliably after the checks in Annex 5, the provider discards it.
  3. The owner can object to the use in the dashboard at any time, separately for chat messages and for reported content (opt-out). The objection takes effect immediately for all data that would be anonymised afterwards. Data that have already been anonymised can no longer be assigned to any customer; they and the models trained with them remain with the provider.
  4. All rights in the anonymised data and the models belong to the provider. Insofar as rights in content are needed for the use, the customer grants them to the provider as a simple (non-exclusive), free-of-charge, perpetual and irrevocable right, to the extent that it holds them itself.
  5. The provider does not pass the anonymised data on to third parties. The models are the same for all customers; the provider uses them in Limenia and in other services of its own.

Otherwise, the provider does not analyse customer data for its own purposes; § 13(3) remains unaffected.

(6) The provider may use suggestions and feedback from the customer on Limenia without remuneration, provided they contain no customer data and no confidential information of the customer.

§ 16 Rights in case of defects

(1) The provisions of German tenancy law (§§ 535 et seq. BGB) apply to defects, unless these Terms provide otherwise. The contractual quality is set out in the Service Description (Annex 1).

(2) The customer reports defects without undue delay in text form and describes them as precisely as possible, for example with time, affected feature, error message and request ID.

(3) The provider remedies defects within a reasonable period. Until the final remedy, it may provide a reasonable workaround.

(4) The provider’s strict (no-fault) liability for damages for defects that already existed at the conclusion of the contract (§ 536a(1) alt. 1 BGB) is excluded.

(5) If the fee is reduced because of a defect, the provider refunds or credits the amount overpaid.

(6) The customer may terminate for failure to grant contractual use (§ 543(2) sentence 1 no. 1 BGB) only after the provider has had sufficient opportunity to remedy the defect and the remedy has failed, unless setting a deadline is dispensable under § 543(3) sentence 2 BGB.

(7) Disruptions caused by use contrary to the contract, by incorrect setup by the customer, by the customer’s systems or by third-party services under § 4(5) are not defects; § 5(3) remains unaffected. During the free trial and in restricted mode after the end of the contract, the provider is liable for defects only if it fraudulently concealed them.

§ 17 Liability

(1) The provider is liable without limitation

  1. for intent and gross negligence,
  2. for damage resulting from injury to life, body or health,
  3. under the German Product Liability Act,
  4. to the extent of a guarantee given and
  5. for fraudulently concealed defects.

(2) In case of simple negligence, the provider is liable only for the breach of essential contractual obligations. Essential obligations are those whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely (cardinal obligations), for example making Limenia available to the agreed extent and protecting customer data. In this case, liability is limited to the damage foreseeable and typical for the contract at the time of its conclusion, but per damaging event to no more than the higher of the following amounts: the total fees the customer paid to the provider in the twelve months before the event causing the damage, or EUR 10,000.

(3) Otherwise, the provider’s liability for simple negligence is excluded.

(4) During the free trial and in restricted mode after the end of the contract, the provider is liable only under paragraph 1.

(5) The customer makes moderation decisions, statements of reasons, replies in the app stores and submissions to the DSA Transparency Database under its own responsibility (§ 4(3), § 5(2)). The provider is liable for their consequences only to the extent they are based on its breach of duty. Contributory fault of the customer, such as adopting an AI suggestion without review, is taken into account under § 254 BGB.

(6) The limitations of liability also apply in favour of the provider’s employees, representatives and vicarious agents.

(7) Claims of the customer for damages due to simple negligence become time-barred one year after the statutory start of the limitation period. This does not apply in the cases of paragraph 1.

(8) This section also applies to claims arising from or in connection with the DPA, unless the DPA provides otherwise. Liability towards data subjects under Art. 82 GDPR remains unaffected.

§ 18 Indemnification

(1) The customer indemnifies the provider against claims asserted by third parties against the provider for an infringement of rights, to the extent the infringement is based on a breach of duty for which the customer is responsible. This applies in particular to infringements caused by

  1. content or data that the customer transmits to Limenia without a legal basis or contrary to § 9(6) and (7),
  2. the customer’s moderation decisions, statements of reasons, replies in the app stores and submissions to the DSA Transparency Database,
  3. violations of the Acceptable Use Policy (Annex 2).

(2) The indemnification includes the reasonable costs of legal defence.

(3) The provider informs the customer without undue delay of claims asserted, does not acknowledge them without the customer’s consent and gives the customer the opportunity to defend against the claims at its own expense. The provider supports the customer in this to a reasonable extent.

(4) Contributory fault of the provider reduces the indemnification accordingly.

§ 19 Return and deletion of data at the end of the contract

(1) Until the end of the contract, the customer can view its data in the dashboard and export the transparency report. The dashboard does not offer a one-click export of all customer data.

(2) Export. At the customer’s request in text form, received by the end of the contract or within 14 days thereafter, the provider makes available to the customer the customer data stored at that time, within 14 days of receipt of the request and in any case before deletion under paragraph 3: the records in JSON format and the media copies as files in their original format, with an overview of the files (manifest), as an encrypted archive through a time-limited download link. API keys (stored only as a hash), webhook secrets and stored credentials are not exported. An export at the end of the contract is free of charge.

(3) Deletion. No later than 30 days after the end of the contract, including after the end of a trial without a plan being purchased, the provider deletes the customer account with all customer data, but not before the period for requesting an export under paragraph 2 has expired and a requested export has been provided. This includes the media copies, the stored secrets and the memberships and invitations. A legal hold set by the customer does not prevent deletion. Deleted data disappear from the backups no later than 14 days after the deletion. Technical logs that contain only identifiers are deleted no later than 30 days after they are created (Annex 1, section 9). On request, the provider confirms the deletion in text form. As evidence, it keeps a deletion record without personal data (ID of the customer account, times, number of deleted records). The provider deletes the sign-in accounts of members that then belong to no customer account in accordance with the privacy policy. Data anonymised under § 15(5) are no longer assigned to any customer account and are deleted when their own period expires (Annex 5 of the DPA).

(4) Documents that the provider must retain due to statutory obligations, such as invoices and contract documents, are deleted after the statutory periods have expired.

(5) The provider cannot delete data that Limenia has transmitted to third parties on the customer’s instruction, for example to the customer’s backends, through connectors, to the app stores, to GitHub or to the DSA Transparency Database. Entries in the DSA Transparency Database are public and remain there according to the rules of the European Commission.

(6) The customer disconnects its apps from Limenia before the deletion. After the deletion, the API rejects requests with the previous API keys.

(7) The DPA additionally governs the return and deletion of personal data. It prevails in case of conflict.

§ 20 Notices of illegal content and point of contact

(1) The provider’s single point of contact for authorities of the member states, the European Commission and the European Board for Digital Services (Art. 11 DSA) and for customers (Art. 12 DSA) is the e-mail address [email protected]. The point of contact communicates in German and English.

(2) Persons and entities can send notices of illegal content stored in Limenia by e-mail to [email protected]. Content in the customer’s apps is reported through the reporting channels of the respective app; the customer decides on such reports.

(3) The provider does not monitor customer data and does not actively search for illegal content. Notices are reviewed by a person at the provider, not by an automated procedure. Limenia stores reported content for moderation. The fact that illegal content is stored for this purpose is not in itself a violation of these Terms; § 9(7) remains unaffected. If a notice is justified, the provider asks the customer to remedy the matter and may take measures under § 10 or § 8(4). It gives the customer reasons for them to the extent required by law. The customer can object to a measure by e-mail to [email protected]; recourse to the courts remains open.

§ 21 Changes to these Terms

(1) The provider may change these Terms with effect for the future if there is an objective reason and the change does not unreasonably disadvantage the customer. Objective reasons include changes in laws or case law, new features or changes in third-party services. The following procedure applies:

  1. The provider gives notice of the change in text form at least six weeks before it takes effect and shows the changed passages.
  2. The customer may object to the change in text form until it takes effect. If the customer does not object, the change is deemed accepted. The provider specifically points out the deadline, the right to object and this consequence in the notice.
  3. If the customer objects, the contract continues to apply to it on the previous terms. If that is legally impossible, for example because the change is mandatorily required by law or by an authority, the change takes effect and the customer may terminate the contract extraordinarily with effect from the date it takes effect.

(2) The provider’s right of ordinary termination under § 8(2) remains unaffected.

(3) Paragraph 1 no. 2 does not apply to changes to the main obligations, i.e. the scope of services of the plan, the prices and the term. § 4(6), § 7(5) or the express consent of the customer apply to these.

(4) The same procedure applies to changes to the DPA (§ 18(2) of the DPA); § 6(2) and § 7 of the DPA apply to changes to the technical and organisational measures and to the sub-processors.

§ 22 Use as a reference

The provider names the customer as a reference, for example with name or logo, only with the customer’s prior consent in text form. The customer may revoke the consent at any time with effect for the future.

§ 23 Final provisions

(1) The law of the Federal Republic of Germany applies, excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG).

(2) If the customer is a merchant (Kaufmann), a legal entity under public law or a special fund under public law, or has no general place of jurisdiction in Germany, the exclusive place of jurisdiction for all disputes arising from and in connection with the contract is Regensburg. The provider may also sue the customer at the customer’s general place of jurisdiction. Mandatory statutory places of jurisdiction remain unaffected.

(3) Notices. The parties make declarations concerning the contract in text form, unless these Terms provide otherwise. The provider sends notices to the e-mail address the customer gave at the conclusion of the contract, and for a purchase through Stripe to the e-mail address stored in the Stripe customer portal. The customer keeps this address up to date. Notices to the provider go to [email protected].

(4) Individual agreements take precedence over these Terms (§ 305b BGB). Amendments and additions to the contract should be recorded in text form for evidence purposes.

(5) The customer may transfer rights and obligations under the contract to third parties only with the provider’s consent in text form; § 354a of the German Commercial Code (HGB) remains unaffected. The provider may transfer the contract to a company that continues its Limenia business, for example to a company it founds. It notifies the customer of this in text form at least six weeks in advance. The customer may then terminate the contract with effect from the date of the transfer.

(6) If individual provisions of this contract are or become invalid or unenforceable, the remainder of the contract remains valid. The statutory provisions take the place of the invalid or unenforceable provision.


Annex 1: Service Description

Version 1.1, as of 27 October 2026

1. Subject matter

Limenia is a service for content reports, moderation and sanctions for one or more apps of a customer. The apps’ data stay in the apps. The backend of an app sends reports, appeals and other events to Limenia through the API. Members of the customer handle and decide them in the dashboard. Limenia reports the decisions back to the app’s backend by webhook or carries them out through a connector in the customer’s system.

2. Components

  • Dashboard at https://app.limenia.eu, in German and English. Sign-in without a password by e-mail link or with a Google account. Two-factor sign-in with an authenticator app, mandatory for the roles owner and admin. Roles: owner, admin, moderator, viewer.
  • API /v1 and webhooks (section 7).
  • Documentation at https://limenia.eu, including the integration guide and the OpenAPI specification (https://limenia.eu/openapi/v1.yaml).
  • Public packages for integration, such as the Flutter packages limenia and limenia_device on pub.dev under the Apache License 2.0 (§ 15(3)).
  • Setup: The provider sets up the customer account and invites the first owner. There is no self-registration. Limenia accepts reports as soon as the owner has completed the setup, including the retention periods.

3. Basic features in every plan

Every plan, the trial and, unless section 6 provides otherwise, restricted mode include:

  • Reports through the API (Art. 16 DSA), cases and moderation queue. Reports are never rejected because of the plan, and there is no quota for reports.
  • Decisions with a statement of reasons under Art. 17 DSA, structured and as text, with feedback to the app by webhook.
  • Internal complaint handling (Art. 20 DSA) with an appeal period of six months, and feedback to reporters (Art. 16(5) DSA).
  • Trusted flaggers (Art. 22 DSA) and measures against misuse of the notice-and-action mechanism (Art. 23 DSA).
  • Transparency report as an export of the figures, and submission of decisions to the DSA Transparency Database with the customer’s access (Art. 24(5) DSA).
  • Store checklist for Apple and Google Play.
  • Retention periods, legal hold and audit log.
  • Signed webhooks.
  • Team with roles and two-factor sign-in.
  • Child safety: for the reason codes child_safety and protection_of_minors, Limenia stores no copy of the media, only their address, deletes copies already stored for this content and marks the case as urgent. The same applies if the AI pre-check reports such a suspicion. There is no separate alert.

Whether a DSA obligation applies to the customer, for example for micro and small enterprises (Art. 19 DSA), is for the customer to check.

4. Plans

Basis Pro Premium
Apps 1 up to 5 up to 20, more by agreement
Basic features (section 3) yes yes yes
Pre-moderation (reviews before publication) – yes yes
Connectors for Firebase, Supabase, RevenueCat and devices – yes yes
Signals and rules – yes yes
Store reviews: inbox, replies, tickets, GitHub – yes yes
AI pre-check (level A), AI checks per calendar month only with add-on: 5,000 5,000 25,000
Additional AI checks only with add-on and overage switched on with overage switched on with overage switched on or by contract
Billing Stripe, monthly Stripe, monthly Stripe, monthly, or contract
  • Prices: according to the price list (§ 7).
  • Trial: the features and limits of Pro, without AI features (§ 6).
  • Planned and not part of the contract (§ 4(7)): AI automation (level B), detection of ban evasion across all apps, app health.

Connectors and store reviews (Pro and Premium, can be switched on per app):

  • Firebase: bans and unbans accounts in Firebase Authentication in the customer’s project and revokes their sessions. Access through a role that the customer grants to the provider’s service account in its project.
  • Supabase: bans and unbans accounts in Supabase Auth with the customer’s secret key.
  • RevenueCat: revokes or grants promotional entitlements, cancels web subscriptions and, on instruction, refunds the last payment. Receives events from RevenueCat to create indications of ban evasion through transferred purchases.
  • Devices: checks devices through Google Play Integrity (Android) and Apple DeviceCheck (iOS) and sets flags there on instruction.
  • Store reviews: fetches reviews from Google Play and the App Store about every 15 minutes, offers reply suggestions and templates, checks replies before sending and sends them only after a member has approved the individual reply. Groups reviews into tickets and, on instruction, creates issues in GitHub.

The connectors depend on the interfaces and terms of the respective third parties (§ 4(5)).

5. AI features

  • AI pre-check (level A): The model assesses reported content and review requests against the customer’s policies and returns a category, a suggestion, a confidence and a short rationale. It can raise the priority of a case but cannot decide. If a member adopts the suggestion, the statement of reasons marks the decision as partly automated.
  • AI classification of store reviews: classification, reply suggestions and grouping into tickets, with a separate opt-in.
  • Opt-in: The owner switches the features on expressly, chooses the areas (cases, reviews) and can pause them at any time.
  • Sent to the AI provider: the text of the content (normalised and truncated to 8,000 characters), downscaled images, the content type, the customer’s policies, the review type’s guidance and the reason codes; for store reviews, the store, the app name, the language, the stars, the title, the text and the customer’s guidance for replies. Not sent to the AI provider: user identifiers, display names, report texts, information about reporters and media with a child safety flag.
  • What counts as an AI check: each assessment of a content item or review request by the model, including a manually triggered reassessment; each classification of a store review; each run of the grouping into tickets. If Limenia reuses the result of a check of the same content from the last 30 days, this does not count.
  • Limits: daily limit per customer account, by default 1,000 AI checks, adjustable by admins between 1 and 100,000. To protect against misuse, in addition at most 10 automatic checks per hour and 50 per day per reporter, and 500 per hour and 3,000 per day per app. When a limit is reached, Limenia still accepts the report and creates the case; only the AI check is skipped.
  • Availability: not during the trial and not in restricted mode. If the AI provider cannot be reached, the assessment is skipped and the work stays with the members.
  • AI provider: currently Mistral AI SAS, Paris, France, as a sub-processor, via Mistral AI’s EU endpoint with processing in data centres in EU and EFTA states (§ 5(4)). The AI provider receives the data only to provide the AI features (§ 5(5)).
  • Own models: The provider trains its own models only with anonymised data, as long as the owner does not object (§ 15(5), Annex 5 of the DPA).

6. State of the subscription and restricted mode

State When Effect
Active running subscription, including while Stripe retries a failed payment; individual contract all features of the plan
Trial 30 days from setup, without a purchase features and limits of Pro, without AI
Restricted mode trial ended without a purchase; contract ended; late payment under § 7(6) see below

Still possible in restricted mode:

  • reports (POST /v1/reports) and appeals (POST /v1/appeals),
  • querying the status and maintaining the display names of end users (/v1/subjects),
  • handling and deciding cases, appeals and review requests already received, feedback to reporters,
  • reporting decisions back to the apps by webhook and through connectors for accounts and purchases that have been set up,
  • all read access, including to stored review requests, signals, device checks and store reviews,
  • existing API keys, settings, management of members and billing.

Blocked in restricted mode (the API and the dashboard respond with 402 subscription_required, background jobs are skipped):

  • creating new apps and new API keys,
  • pre-moderation: creating new review types and new review requests (POST /v1/reviews),
  • signals and rules: new signals (POST /v1/signals) and signal types, new rules; existing rules are not evaluated,
  • device checks (POST /v1/devices/check),
  • store reviews: no fetching of new reviews, no classification and no sending of replies,
  • all AI features (AI pre-check and AI classification), the add-on and AI overage.

Features not included in the last applicable plan are not available anyway.

Restricted mode itself does not lead to the deletion of data; the retention periods continue to run.

7. API and webhooks

  • API: REST with JSON over HTTPS at https://app.limenia.eu/v1. Authentication with one API key per app (Authorization: Bearer). The key is shown only once and stored only as a hash.
  • Rate limit: currently 10 requests per second per API key, briefly up to 50 (burst). Above this, the API responds with 429 and the waiting time in the Retry-After header. Higher limits on request.
  • Idempotency: through the Idempotency-Key header, 24 hours.
  • Limits per request: up to 10 media per content item, up to 20 MiB per medium; text up to 20,000 characters; context up to 4 KB; up to 100 signals per call.
  • Media download: Limenia downloads media from the given addresses only over HTTPS and only from public addresses, with a time limit of 15 seconds per attempt.
  • Webhooks: events decision.created, subject.status_changed, reports.resolved, appeal.resolved, review.decided and test.ping. Signature with HMAC-SHA256 and a timestamp in the Limenia-Signature header. Delivery only to HTTPS targets with public addresses, up to 12 attempts over about 20 hours. Events that occur while the webhook is switched off are not delivered later. Webhooks do not come from fixed IP addresses.
  • Versioning: The API is versioned (/v1). Within a version, the provider may extend the API in a backward-compatible way at any time, for example with new endpoints, new optional fields in requests, new fields in responses and events, new values in enumerations and new webhook events. The customer’s backend must be able to ignore unknown fields, values and events. The provider usually announces changes that break existing integrations at least three months in advance in text form and in the documentation. If security, law or changes at third parties require a shorter period, it announces them as early as possible.

8. Hosting and places of processing

  • Region: Google Cloud in the region europe-west3 (Frankfurt am Main) for the application, database, background jobs, secrets, logs, backups and the anonymised data for own models (§ 15(5)).
  • Media copies: Cloudflare R2, private storage with EU jurisdiction.
  • Exceptions:
    1. Sign-in accounts of members, which the provider processes under its own responsibility (§ 13(2)): Firebase Authentication with Identity Platform (Google), a global service; processing also in the USA possible.
    2. The address app.limenia.eu runs through Firebase Hosting (Google). Requests are passed through a worldwide network without being stored there.
    3. AI features, only after opt-in: Mistral AI SAS, data centres in EU and EFTA states, not in Frankfurt.
    4. Billing: Stripe processes the customer’s billing and payment data; processing also in the USA possible.
    5. Google stores administrative logs of the Google Cloud infrastructure about changes to the infrastructure (without customer data) globally.
    6. Services the customer connects itself: Google Play Integrity, Apple DeviceCheck, App Store Connect API, Google Play Developer API, GitHub.com, RevenueCat, Supabase, the customer’s Firebase project, its webhook targets and the DSA Transparency Database, each at the locations and under the contracts of these services.
  • Sub-processors, locations and transfer mechanisms in detail: Annex 3 of the DPA (https://limenia.eu/en/dpa/#anlage-3) and privacy policy (https://limenia.eu/en/privacy/).

9. Retention and deletion

The owner sets the periods within these ranges:

Data Default Range
Content copies and media, open cases and open review requests 183 days 183 to 1,095 days
Decisions, decided cases, appeals, user files, reporter files 365 days 183 to 1,095 days
Dismissed reports 183 days 183 to 1,095 days
Audit log 730 days 1 to 1,095 days
Content of approved review requests 30 days 1 to 365 days
Signals and device checks 30 days 1 to 90 days
Store reviews and tickets 183 days 30 to 730 days
  • Fixed periods: webhook delivery log 90 days; technical logs (identifiers only, no content) 30 days; counters without personal reference 25 months, for the transparency report 37 months after the end of the month; anonymised data for own models (§ 15(5)) 365 days from creation.
  • Changed periods apply first to newly written data. The owner can trigger a recalculation for existing data.
  • A legal hold that an admin sets per case or per store review suspends the period until it is lifted.
  • Limenia deletes expired data automatically, usually within one day; a daily job deletes media copies.
  • The dashboard does not offer targeted deletion or export of the data of individual end users before the periods expire. The provider supports the customer with requests from data subjects under the DPA.
  • § 19 applies at the end of the contract.

10. Backups

  • The database (Google Cloud Firestore) can be restored to its state at any minute within the last 7 days. In addition, there are daily backups that are kept for 14 days. Both are located in the region europe-west3.
  • Deleted data disappear from the backups no later than 14 days after their deletion.
  • Media copies are not backed up separately.
  • The backups serve recovery after errors and disruptions, not the recovery of individual data on request (§ 11(4)).

11. Security

  • Encrypted transmission (HTTPS), encryption of stored data by the operators of the infrastructure.
  • Separation of customer accounts in the application, roles and two-factor sign-in.
  • API keys only as a hash; secrets such as webhook secrets and credentials for connectors only in Secret Manager.
  • Media only through signed links valid for 5 minutes; images in the dashboard are blurred at first.
  • Logs without content, with identifiers only.
  • Details: technical and organisational measures under the DPA.

12. Not included

  • Legal advice and moderation by the provider.
  • Enforcement of decisions in the apps, except through the connectors.
  • Contact with end users and e-mail notifications from Limenia; Limenia sends only the sign-in e-mails.
  • One-click export of the entire customer account (export on request under § 19).
  • Commitments on availability and response times, except in an individual contract.

Annex 2: Acceptable Use Policy

Version 1.0, as of 10 October 2026

1. Purpose

The customer uses Limenia only to handle reports, moderation, appeals, pre-moderation, signals, sanctions and store reviews of its apps (§ 15(2)), and only in accordance with applicable law.

2. No surveillance of persons

The customer does not use Limenia to

  1. observe persons or build profiles of them beyond what is necessary for moderation, the enforcement of its terms of use and protection against misuse in its apps, for example their behaviour outside its apps,
  2. use signals, device checks, user files or report data for unrelated purposes, for example advertising, credit checks or pricing,
  3. monitor the performance or behaviour of its employees beyond what is necessary for record-keeping and security. The customer itself observes the rights of works councils and staff councils.

3. No unlawful data collection

The customer

  1. does not transmit data for which it has no legal basis,
  2. does not use Limenia to collect data about persons unrelated to its apps, for example by automated scraping of other services,
  3. does not write real names, e-mail addresses, phone numbers or other personal data into fields not intended for them, for example identifiers, context or signal values, unless moderation requires them,
  4. transmits special categories of personal data (Art. 9 and 10 GDPR) only to the extent they are contained in the reported content itself or are necessary for moderation.

4. No content outside moderation

The customer

  1. does not use Limenia as a file host, archive, delivery network or communication service,
  2. does not upload content that is not the subject of a report, appeal or review request,
  3. does not knowingly transmit depictions of the sexual abuse of children or adolescents as media and, in case of such a suspicion, uses the reason codes under § 9(7),
  4. does not transmit malware.

5. Security and integrity

The customer

  1. does not examine, decompile or disassemble the Limenia software to determine its structure (reverse engineering), unless §§ 69d and 69e of the German Copyright Act (UrhG) mandatorily permit it,
  2. does not circumvent access controls, rate limits, quotas, plan limits or the separation of customer accounts and does not attempt to access data of other customers,
  3. carries out security or penetration tests, vulnerability scans and load tests only with the provider’s prior consent in text form,
  4. does not exploit vulnerabilities it finds and reports them without undue delay to [email protected].

6. No overload

The customer

  1. observes the rate limits, waits for the time given in Retry-After and retries requests with increasing intervals,
  2. does not send artificially generated reports, signals or requests, except to an extent customary for testing,
  3. does not create additional apps or API keys merely to circumvent limits.

7. API keys and accounts

The customer

  1. does not pass API keys on to third parties, except to service providers who operate an app’s backend for it and are bound to confidentiality,
  2. does not store API keys in apps, web pages, logs or public repositories,
  3. does not share accounts and does not invite persons who do not work for it,
  4. does not provide Limenia to third parties as its own service and does not resell access, except within the scope of § 15(2) or under a separate agreement,
  5. does not systematically extract features, instructions to the AI model or outputs in order to develop a competing service.

8. Third-party services

The customer

  1. uses connectors and store interfaces only in accordance with the terms of the respective services,
  2. does not send advertising, requests for a better rating, incentives or personal data in replies to store reviews,
  3. submits only accurate information and no personal data to the DSA Transparency Database.

9. Sanctions

Persons and organisations subject to sanctions of the European Union may not use Limenia.

10. Consequences of violations

In case of violations, in particular § 10 (blocking of access), § 8(4) (extraordinary termination) and § 18 (indemnification) apply.

Back to the home page

Limenia

Content moderation and DSA notice and action for apps. Hosted in the EU.

Deutsch

Product

  • Features
  • How it works
  • Pricing
  • Data protection
  • FAQ
  • Solutions
  • Contact
  • Start free trial
  • Request a demo
  • Log in

Resources

  • Guides
  • Developer docs
  • DSA notice and action
  • DSA check
  • Integrations
  • Firebase connector
  • Supabase connector
  • Flutter apps
  • Examples on GitHub
  • Flutter package on pub.dev

Legal

  • Privacy policy
  • Terms
  • DPA
  • Legal notice
  • Report a vulnerability

© 2026 SB-Techworks

Limenia is a tool and does not replace legal advice.