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

Data Processing Agreement (DPA) for Limenia

Agreement on the processing of personal data on behalf of a controller under Art. 28 of the General Data Protection Regulation (GDPR)

Version 1.1, as of 27 October 2026

This is an English translation for information only. The German version (Auftragsverarbeitungsvertrag, https://limenia.eu/avv/) is binding and prevails.

Parties

Controller: the customer who has concluded an agreement with the Processor on the use of Limenia, with the details given in the order or in the declaration of acceptance (hereinafter “Controller”).

Processor: Karim Belkacem, sole trader (Einzelunternehmer) trading as “SB-Techworks”, Lilienthalstr. 38, 93049 Regensburg, Germany, phone +49 941 46395983, e-mail [email protected], VAT ID DE369343383 (hereinafter “Processor”).

Contents

  • § 1 Subject matter, conclusion and term
  • § 2 Nature and purpose of the processing
  • § 3 Types of data and categories of data subjects
  • § 4 Instructions
  • § 5 Obligations of the Processor and confidentiality
  • § 6 Technical and organisational measures
  • § 7 Sub-processors
  • § 8 Connections set up by the Controller
  • § 9 AI pre-check and AI classification
  • § 10 Assistance with data subject rights
  • § 11 Assistance with the obligations under Art. 32 to 36 GDPR
  • § 12 Notification of personal data breaches
  • § 13 Retention, deletion and return
  • § 14 Evidence and audits
  • § 15 Place of processing and transfers to third countries
  • § 16 Obligations of the Controller
  • § 17 Liability
  • § 18 Final provisions
  • Annex 1: Description of the processing
  • Annex 2: Technical and organisational measures
  • Annex 3: Sub-processors
  • Annex 4: Special functions
  • Annex 5: Anonymisation for own models

§ 1 Subject matter, conclusion and term

(1) The Processor provides the Controller with the software Limenia as a service over the internet: the dashboard at https://app.limenia.eu and the programming interfaces (hereinafter “Service”). The basis is the agreement on the use of Limenia under the General Terms and Conditions (https://limenia.eu/en/terms/) with the chosen plan (https://limenia.eu/en/#pricing) or under an individual agreement (together the “Main Contract”). In providing the Service, the Processor processes personal data on behalf of the Controller. This agreement governs the rights and obligations of the parties in doing so.

(2) This agreement is concluded together with the Main Contract:

  1. when a plan is purchased, by the Controller accepting it together with the General Terms and Conditions in the order process (Stripe Checkout) using the check box provided for this purpose;
  2. for a trial, by the Controller accepting the General Terms and Conditions and this agreement in text form (e.g. by e-mail) before its tenant is created;
  3. for an individual agreement, by concluding it, unless it provides otherwise.

Conclusion in electronic form satisfies Art. 28(9) GDPR. The Processor stores the acceptance with the version and time as evidence.

(3) This agreement applies for the term of the Main Contract. It cannot be terminated separately. It continues to apply after the end of the contract until the Processor has deleted the data completely under § 13, in particular to restricted mode until deletion, in which the Service continues to accept reports and appeals (§ 8(5) of the General Terms and Conditions).

(4) In all matters of data protection, this agreement takes precedence over the General Terms and Conditions and any other agreements of the parties. Annexes 1 to 5 form part of this agreement.

(5) Terms have the meaning given in Art. 4 GDPR. In addition:

  • Tenant: the Controller’s separate area in the Service.
  • Apps: the Controller’s applications whose backends send data to the Service.
  • End users: the users of the Apps.
  • Team members: the persons the Controller invites to its tenant, with the roles Owner, Admin, Moderator or Viewer.
  • Trial, restricted mode and end of the contract: as defined in the General Terms and Conditions (§ 2, § 6 and § 8). The end of the contract is the end of the trial without a plan being purchased or the date on which a termination of the Main Contract takes effect. Late payment does not end the Main Contract.
  • Text form: text form under § 126b of the German Civil Code (BGB), e.g. e-mail.

§ 2 Nature and purpose of the processing

(1) The Service supports the Controller in handling reports about content and users of its Apps, in moderation decisions and sanctions and in the related obligations, in particular under Regulation (EU) 2022/2065 (Digital Services Act, DSA). Depending on the functions the Controller uses, the processing comprises:

  1. receiving reports, appeals, requests for review before publication (pre-moderation), signals and device checks from the backends of the Apps via the programming interface;
  2. storing a copy of reported or submitted content including images and videos for review and preservation of evidence;
  3. grouping into cases, display in the dashboard, handling and decision by team members, the statement of reasons under Art. 17 DSA, the internal complaint-handling system under Art. 20 DSA, feedback to reporters under Art. 16(5) DSA, handling of reports from trusted flaggers and protection against misuse under Art. 22 and 23 DSA, and counts for the transparency report under Art. 15 DSA;
  4. user files per App with sanction status, earlier decisions and flags from the Controller’s rules;
  5. reporting decisions back to the Controller’s systems by signed webhook and, where the Controller sets it up, actions in its systems via connectors (§ 8, Annex 4);
  6. after the Controller opts in, assessment of content and classification of store reviews by a language model as a suggestion (§ 9);
  7. where the Controller sets it up, retrieval, classification and answering of the reviews of its Apps in Apple’s App Store and on Google Play, and tickets and issues in GitHub (Annex 4);
  8. the log of actions in the tenant (audit log) and the delivery log;
  9. storage, backup and deletion on schedule;
  10. as long as no Owner objects, the anonymisation under Annex 5 of chat messages and of reported or submitted content with the results of the check and the decisions.

(2) The nature of the processing comprises in particular collection by receipt, storage, organisation, retrieval, consultation, display, disclosure to the recipients determined by the Controller, alignment, restriction and erasure.

(3) The Processor processes the data solely to provide the Service to the Controller under the Main Contract. It does not use the data for its own purposes. In particular, it does not train or improve AI models with personal data. It does not analyse the data across tenants and does not pass them on to third parties except under this agreement. This does not affect:

  1. counts without personal reference that the Service derives from the processing (e.g. the number of reports, pre-moderation requests and AI checks per month). The Processor may use them for billing, checking plan limits, administering the platform and planning its capacity, and developing the Service further.
  2. technical logs that contain only identifiers and error codes, no content. The Processor processes them under its own responsibility for secure operation and troubleshooting (Art. 32 GDPR), as described in its privacy policy (https://limenia.eu/en/privacy/), and keeps them for no more than 30 days.
  3. the anonymisation under Annex 5. By this agreement, the Controller instructs the Processor to anonymise the data named there, as long as no Owner has objected in the dashboard. The Processor may use the anonymised data for its own models (§ 15(5) of the General Terms and Conditions).

(4) Annex 1 describes the details.

§ 3 Types of data and categories of data subjects

(1) The following categories of persons are affected:

  1. reported end users and authors of reported content;
  2. reporting end users; the Service stores them only under a pseudonym (hash of App and user ID);
  3. end users who appeal against a decision;
  4. authors of content that an App has reviewed before publication;
  5. end users about whom an App sends signals or whose device it has checked; if an App checks at every login, nearly all active users of that App are affected;
  6. third parties named or depicted in content, report texts, appeals or reviews;
  7. persons who review the Controller’s Apps with text in the App Store or on Google Play;
  8. team members and persons invited to the tenant;
  9. holders of personal GitHub accounts on which the Limenia GitHub App is installed (numeric account ID only).

(2) The following types of personal data are processed:

  1. Identifiers: external user IDs of the Apps, display names, IDs of content, reports, appeals and pre-moderation requests assigned by the Apps, the pseudonym of reporting persons;
  2. Content data: texts (up to 20,000 characters), context data (up to 4 KB), links, images and videos, free text of reports and appeals;
  3. Moderation data: cases, decisions with facts and reasons, sanctions and their end, user status, violations, appeals and their outcome, files of reporting persons with counters, warnings and suspensions;
  4. Behavioural and device data: signals of the Apps (type, value, context, time), summarised results of device checks (flag, device integrity), refund counters from RevenueCat;
  5. AI assessments: categories, suggestion, risk, confidence and a short rationale of the model;
  6. Store reviews: stars, title, text, language, country (Apple), app version, Android version and device class (Google), times, reply; without the name or nickname of the reviewer;
  7. Team member data in the tenant: membership with identifier (UID), role, time of admission and admitting person; invitations with the e-mail address and role of the invited person and the inviting person; the identifier as handling or acting person in cases, decisions, the audit log and other records; the display of e-mail address and display name in the tenant’s member list;
  8. Configuration with personal reference, e.g. who created an API key or a rule.

(3) Content, report texts, appeals and reviews may, without the Processor’s influence, contain special categories of personal data under Art. 9 GDPR and data relating to criminal offences under Art. 10 GDPR and may concern minors. The Service is designed for this (Annex 2). The Controller checks whether its legal basis covers this processing and whether a data protection impact assessment is required.

(4) Child protection: For reports with the reason codes child_safety or protection_of_minors, the Service stores no copy of the media, only their address (URL). It deletes copies of the same content that were already stored. The case is marked urgent; there is no separate alert. If a decision on a pre-moderation request relies on a policy on the protection of minors, the Service deletes its media copies immediately. Media with this flag are never sent to a language model. Review, preservation of evidence, reports to law enforcement (e.g. under Art. 18 DSA) and cooperation with reporting hotlines are the Controller’s responsibility. The Processor does not view content and does not file reports.

(5) The Service is not intended to process e-mail addresses, phone numbers, IP addresses, device identifiers or location data of end users. The Controller does not send such data (§ 16(2)). The Service does not technically enforce this.

(6) Team members: Responsibility for their data is shared:

  1. The Processor processes the identity, sign-in, second factor and session of the sign-in accounts and the related security logs as a controller in its own right. One sign-in account may apply to several tenants; the Processor sets the sign-in methods, the mandatory second factor for Owners and Admins, the session length and the retention periods of the accounts uniformly for all tenants. Its privacy policy (https://limenia.eu/en/privacy/) describes this processing; it is not subject to this agreement. The sign-in measures also serve to protect the data in the tenant (Annex 2).
  2. The Processor processes memberships, roles and invitations in the tenant and the audit log on behalf of the Controller under this agreement (paragraph 2 no. 7).

§ 4 Instructions

(1) The Processor processes the data only on documented instructions from the Controller, including with regard to transfers to a third country, unless required to do so by Union or Member State law to which the Processor is subject. In such a case, the Processor informs the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest (Art. 28(3)(a) GDPR).

(2) Instructions are:

  1. this agreement and the Main Contract;
  2. the settings in the dashboard and the actions of team members within their roles, e.g. retention periods, policies, Apps, webhooks, connectors, the opt-in to AI functions, the objection to anonymisation under Annex 5, decisions, legal hold, the approval of a reply to a store review or the creation of an issue in GitHub;
  3. calls to the programming interface with an API key of one of the Controller’s Apps;
  4. individual instructions in text form from an Owner of the tenant or a person named in the Main Contract.

The Controller decides whom it grants which role and who receives API keys. Actions through these accesses count as its instructions.

(3) The parties treat individual instructions that go beyond the agreed scope of services as change requests. The Processor may make their implementation subject to an agreement on effort and remuneration. This does not apply to services the Processor owes under this agreement anyway.

(4) If the Processor considers that an instruction infringes the GDPR or other data protection provisions, it informs the Controller without undue delay (Art. 28(3) subparagraph 2 GDPR). It may suspend execution until the Controller confirms or changes the instruction. It does not execute instructions that are manifestly unlawful.

(5) The Service logs settings and write actions of team members in the tenant’s audit log (Annex 2). Both parties document individual instructions in text form.

§ 5 Obligations of the Processor and confidentiality

(1) The Processor ensures that all persons it authorises to process the data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Art. 28(3)(b), Art. 29 and Art. 32(4) GDPR). Currently only the owner of the business processes the data. The Processor engages further persons only after a written commitment to confidentiality and data protection and only as far as necessary for their task. The confidentiality obligation continues after the end of the agreement.

(2) The Processor’s platform administration has no access in the dashboard to the Controller’s cases, content and user files. Via the infrastructure, the Processor accesses data in the tenant only as far as necessary to carry out an instruction (e.g. export or deletion under § 13, assistance under § 10), to remedy a fault or to avert a threat to the security of the Service. It limits such access to what is necessary.

(3) The Processor has not appointed a data protection officer. The contact for data protection is Karim Belkacem, [email protected]. If the Processor appoints a data protection officer or the contact changes, it gives notice in text form.

(4) The Processor keeps a record of processing activities under Art. 30(2) GDPR and cooperates with the supervisory authority on request (Art. 31 GDPR). It informs the Controller without undue delay of inspections and measures by a supervisory authority insofar as they concern this agreement.

(5) If an authority or other third party requests information about or disclosure of the Controller’s data from the Processor, the Processor refers it to the Controller and informs the Controller without undue delay, where legally permitted. It discloses data only if legally obliged to do so.

(6) The Processor keeps the Controller’s data technically separate from the data of other customers (tenant isolation, Annex 2).

§ 6 Technical and organisational measures

(1) The Processor takes the technical and organisational measures under Art. 32 GDPR described in Annex 2. The parties consider them appropriate to the risks of the processing under § 3.

(2) The measures are subject to technical progress. The Processor may develop them further and replace them with equivalent or better measures, provided the level of protection does not decrease. It documents material changes and includes them in Annex 2. The Controller receives the current version on request; it is also published at https://limenia.eu/avv/#anlage-2 (English translation: https://limenia.eu/en/dpa/#anlage-2).

(3) The Controller is responsible for the security of its own systems, in particular for keeping API keys, webhook secrets and stored credentials secret and for assigning roles carefully.

§ 7 Sub-processors

(1) The Controller gives the Processor general authorisation to engage other processors (sub-processors) (Art. 28(2) sentence 1 GDPR). Annex 3 lists the sub-processors engaged when this agreement is concluded. They are deemed approved.

(2) If the Processor intends to add or replace a sub-processor, it informs the Controller in text form at least 30 days in advance. The information is sent by e-mail to the addresses under § 16(5) and, where the dashboard offers this, additionally as a notice in the dashboard. At the same time, the Processor publishes the updated list at https://limenia.eu/avv/#anlage-3 (English translation: https://limenia.eu/en/dpa/#anlage-3).

(3) The Controller may object to the change in text form within 30 days of receiving the information on important data protection grounds. The parties then seek an amicable solution. The Processor may refrain from the change or switch off the affected function for the Controller (e.g. the AI pre-check). If no solution is found, the Controller may terminate the Main Contract extraordinarily with effect from the date the change takes effect. The Processor refunds pro rata any fees paid in advance for the period thereafter. If the Controller does not object in time, the change is deemed approved.

(4) If the Processor must replace a sub-processor at short notice to maintain the operation or security of the Service (e.g. because it ceases its service or a serious security breach has occurred), it may shorten the period under paragraph 2. It then informs the Controller without undue delay. Paragraph 3 applies accordingly.

(5) The Processor imposes on each sub-processor by contract the same data protection obligations as set out in this agreement, in particular sufficient guarantees for appropriate technical and organisational measures (Art. 28(4) GDPR). Where sub-processors offer their services only on standard terms (e.g. Google, Cloudflare, Mistral AI), their data processing terms suffice insofar as they meet Art. 28(3) and (4) GDPR. The Processor remains liable to the Controller for its sub-processors’ compliance with their data protection obligations.

(6) The following are not sub-processors within the meaning of this agreement:

  1. the bodies under § 8 to which the Service transfers data on the Controller’s instruction;
  2. service providers that the Processor uses only for its own processing as a controller, in particular Firebase Authentication (Google) for the team members’ sign-in accounts (§ 3(6) no. 1), the payment service provider Stripe for billing and the service providers of the website limenia.eu. They receive no data that the Processor processes under this agreement.

§ 8 Connections set up by the Controller

(1) Where the Controller sets this up, the Service transfers data to, and retrieves data from, systems and services that the Controller selects, operates itself or uses under its own contract. These are:

  1. the webhook receivers (backends) of its Apps;
  2. the servers from which the Service retrieves media at the addresses provided by the Controller;
  3. its Firebase project, its Supabase project and its RevenueCat project (connectors for accounts and purchases);
  4. Google Play Integrity and Apple DeviceCheck in its developer accounts (device connector);
  5. Apple’s App Store Connect API and the Google Play Developer API for its Apps (store reviews);
  6. GitHub, if it installs the Limenia GitHub App in its account;
  7. the DSA Transparency Database of the European Commission with its access token.

(2) Setting up and using these connections are instructions under § 4. The bodies named are not sub-processors of the Processor; the Processor has not concluded a contract with them for this processing. They are systems of the Controller, its own processors or independent controllers (e.g. Apple and Google for their stores, the European Commission for the Transparency Database). The Controller is responsible for the legal relationship with these bodies, for the legal basis of the transfer and, where they process outside the European Economic Area, for meeting the requirements of Chapter V GDPR.

(3) The Processor transfers only the data described in Annex 1 and Annex 4, only to the destinations the Controller has set up and only with the safeguards in Annex 2. It stores credentials provided by the Controller only in Secret Manager and deletes them when the Controller disconnects the connection or deletes the App, and at the latest under § 13.

(4) Data held by these bodies are not subject to the retention periods and deletion obligations of this agreement, e.g. webhook events in the Controller’s backend, replies in the stores, issues in GitHub, entries in the Transparency Database and the device bits held by Google and Apple. Entries in the Transparency Database are public.

(5) Annex 4 sets out the specifics of individual connections.

§ 9 AI pre-check and AI classification

(1) The Service offers two functions using a language model: the assessment of reported content or content submitted for pre-moderation (AI pre-check) and the classification and grouping of store reviews (AI classification). Both remain switched off until an Owner expressly switches them on in the dashboard (opt-in). The Service logs the opt-in with time and person. The AI classification requires a separate opt-in. The Controller can choose the areas (cases, pre-moderation), pause or switch off the functions at any time and set a daily limit. A plan with the AI function is required; the functions are not available during the trial or in restricted mode.

(2) For the AI functions, the Processor 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).

(3) Only the data needed for the assessment are sent to the model:

  1. AI pre-check: the text of the content after technical normalisation, shortened to at most 8,000 characters, downscaled images, the type of content, the Controller’s policies, the review hints of the pre-moderation type, the codes of the report reasons and the language of the rationale;
  2. AI classification: store, name of the App, language, stars, title and text of the review, the Controller’s hints for replies and the allowed link domains; for grouping into tickets only titles and short summaries, no review texts.

User IDs, display names, report texts, information about reporting persons, media flagged for child safety, names of reviewers and device data are never sent to the model.

(4) The Processor uses the AI provider only as a sub-processor that processes the data on the Processor’s instructions to provide the AI functions (§ 7(5)). Under its terms, Mistral AI may store inputs and outputs for up to 30 days for abuse detection. The Processor does not train AI models with personal data; it trains its own models only with data that are anonymised under Annex 5 (§ 2(3) no. 3).

(5) The results are suggestions. The model decides nothing: a team member decides every case, every pre-moderation request and every reply to a review. No automated decision within the meaning of Art. 22 GDPR takes place. The AI can raise the priority of a case. If a team member adopts the suggestion, the statement of reasons under Art. 17 DSA marks the decision as partly automated.

(6) The Service limits the number of checks per reporting person, per App and per day and, for identical content within the tenant, reuses the result of an earlier check from the last 30 days. It compares nothing across tenants.

(7) The Controller remains responsible for the use of the functions, including its obligations as a deployer under Regulation (EU) 2024/1689 (AI Act), where applicable.

(8) A change of the language model provider is a change under § 7.

§ 10 Assistance with data subject rights

(1) The Processor assists the Controller by appropriate technical and organisational measures in responding to requests from data subjects under Chapter III GDPR (Art. 28(3)(e) GDPR).

(2) For this purpose, the Service offers the following functions:

  1. Access: searching a user file by App and external user ID with cases, decisions, signals and device checks in the dashboard; querying the sanction status via the programming interface;
  2. Rectification: changing the display name via the programming interface; removing flags set by rules; lifting warnings and suspensions of reporting persons;
  3. Erasure: automatic deletion after the Controller’s retention periods; deleting individual store reviews with a block against renewed retrieval; resetting the device flag at the next check of the device;
  4. Preservation: legal hold per case or per review, which prevents deletion.

(3) Where these functions are not sufficient, in particular for providing the data of an end user in machine-readable form, deleting the data of an individual end user before the retention periods expire or searching for the reports of a reporting person, the Processor assists on request in text form. The Controller states the App and the external user ID or other identifiers. The Processor carries out the measure without undue delay, at the latest within ten working days of receiving the request, or states within this period why it is not possible, or not fully possible. The Service stores no names of reviewers; a review can only be found by store, time and text.

(4) If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without undue delay, at the latest within three working days, insofar as it can attribute it to the Controller. It does not answer the request itself unless the Controller instructs it to.

(5) Assistance under paragraphs 3 and 4 is included in the fees for individual requests. For assistance that goes considerably beyond this, the Processor may, after prior notice, charge reasonable remuneration based on effort, unless the assistance is required because of a breach of duty by the Processor.

§ 11 Assistance with the obligations under Art. 32 to 36 GDPR

(1) Taking into account the nature of the processing and the information available to it, the Processor assists the Controller with the security of processing (Art. 32), notifications and communications following personal data breaches (Art. 33 and 34), data protection impact assessments (Art. 35) and prior consultation of the supervisory authority (Art. 36 GDPR).

(2) For this purpose, it provides in particular:

  1. this agreement with the description of the processing and of the technical and organisational measures;
  2. the public integration guide with guidance on data minimisation (https://limenia.eu/docs/integration.md);
  3. on request, templates for a data protection impact assessment for the device connector and for store reviews with AI classification, and text modules for the privacy notices on store reviews and on the anonymisation under Annex 5;
  4. information on the sub-processors and their guarantees.

(3) It answers the Controller’s questions within a reasonable period, as a rule within ten working days. § 10(5) applies accordingly.

§ 12 Notification of personal data breaches

(1) The Processor notifies the Controller of a personal data breach affecting the Controller’s data without undue delay after becoming aware of it (Art. 33(2) GDPR). It aims to notify within 48 hours. The notification is sent by e-mail to the addresses under § 16(5).

(2) The notification contains, as far as known:

  1. a description of the nature of the breach, where possible with the categories and approximate number of data subjects and records concerned;
  2. the name and contact details of the contact person;
  3. the likely consequences;
  4. the measures taken or proposed to address the breach and to mitigate its possible adverse effects.

The Processor provides information not yet known without further undue delay.

(3) The Processor takes the necessary measures without undue delay to contain the breach and secure the data, documents the breach and assists the Controller with its notifications and communications. It does not notify the supervisory authority or data subjects on behalf of the Controller unless the Controller instructs it to.

(4) The Processor likewise informs the Controller without undue delay of serious disruptions of the Service that endanger the Controller’s data and of any suspected breaches of this agreement.

(5) A notification under this section is not an acknowledgement of fault or liability.

§ 13 Retention, deletion and return

(1) During the term, the Controller sets the retention periods in the dashboard within the limits in Annex 1. They also apply in restricted mode until deletion under paragraph 4. The Service deletes data automatically when they expire: database records as a rule within 24 hours of expiry, media copies with the daily deletion run. A legal hold set by the Controller suspends deletion until it is lifted. If the Controller deletes an App, the Service revokes its API keys and deletes its secrets and credentials immediately; it deletes the cases, content and decisions of that App according to the retention periods.

(2) Backups: The Processor backs up the database in the region europe-west3 (Frankfurt am Main) with recovery to its state at any minute within the last 7 days (point-in-time recovery) and with daily backups kept for 14 days. Deleted data therefore remain in the backups for up to 14 days and then disappear automatically. Backups serve only to restore the Service after an error or loss. If the Processor restores a backup, the Service again deletes data whose retention period has expired automatically; the Processor repeats other deletions made since the time of the backup insofar as they appear in the audit log. Media copies are not backed up.

(3) Export: At the Controller’s request in text form, received by the end of the contract or within 14 days thereafter, the Processor provides the data of its tenant stored at that time, within 14 days of receipt of the request and in any case before deletion under paragraph 4: 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. There is no export function in the dashboard.

(4) Deletion after the end of the contract: No later than 30 days after the end of the contract, including after the end of a trial without a plan being purchased, the Processor deletes the tenant with all data under this agreement, but not before the period for requesting an export under paragraph 3 has expired and a requested export has been provided. This comprises all records, media copies, stored credentials and secrets, the entries in cross-tenant assignments and the memberships and invitations. It also deletes data under legal hold; the Controller secures them beforehand via the export. Deleted data disappear from the backups no later than 14 days after deletion. Technical logs that contain only identifiers are deleted no later than 30 days after they are created. On request, the Processor confirms the deletion in text form. As evidence, it keeps a deletion record without personal data (ID of the tenant, times, number of deleted records). The Processor deletes the sign-in accounts of team members that then belong to no tenant in accordance with its privacy policy (§ 3(6) no. 1).

(5) Paragraph 4 does not apply insofar as the Processor is obliged to store the data under Union or Member State law (Art. 28(3)(g) GDPR). This agreement does not cover data that the Processor processes as a controller in its own right, in particular contract and billing data, the counts and technical logs under § 2(3) and the sign-in accounts under § 3(6) no. 1; its privacy policy and the statutory retention periods apply to them. Data that are anonymised under Annex 5 cannot be assigned to any tenant; paragraph 4 does not apply to them, and they are deleted under Annex 5 no. 7. The Processor may keep documents evidencing proper processing (e.g. this agreement and documented instructions) for the statutory periods.

(6) § 8(4) applies to data held by the bodies under § 8.

§ 14 Evidence and audits

(1) The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR (Art. 28(3)(h) GDPR). This includes this agreement with its annexes and, on request, the current description of the technical and organisational measures, the list of sub-processors and their published evidence (e.g. ISO/IEC 27001 certificates or audit reports). The Processor answers the Controller’s questionnaires within a reasonable period, as a rule within 15 working days.

(2) The Controller may audit compliance with this agreement itself or through an auditor bound to confidentiality who is not a competitor of the Processor. The following applies to audits:

  1. The Controller announces them in text form at least 30 days in advance. In the case of a personal data breach, concrete indications of a violation or at the request of a supervisory authority, a reasonably shorter period suffices.
  2. Audits take place at most once per calendar year, unless one of the occasions named in no. 1 sentence 2 applies.
  3. They take place during normal business hours, primarily by reviewing documents and holding interviews, including by video, without disrupting operations and without access to other customers’ data.
  4. The Processor does not operate its own data centres. The certificates and audit reports of the sub-processors take the place of an audit of their data centres.

(3) Each party bears its own costs of an audit. The Processor may charge reasonable remuneration for its effort exceeding one working day per audit. This does not apply if the audit reveals a not insignificant breach by the Processor of this agreement or of data protection law.

(4) The Processor supports audits by a supervisory authority to the extent necessary.

§ 15 Place of processing and transfers to third countries

(1) The Processor stores the Controller’s data in the European Union: the database, the backups, the secrets and the logs at Google Cloud in the region europe-west3 (Frankfurt am Main), the media copies at Cloudflare R2 with EU jurisdiction. The language model processes in data centres in EU and EFTA states (§ 9). For Switzerland, an adequacy decision of the European Commission exists.

(2) Annex 3 lists exceptions, in particular:

  1. routing of traffic to app.limenia.eu through worldwide edge nodes of Firebase Hosting without storage;
  2. global services of Google Cloud for monitoring and administrative logs that contain no content;
  3. access by sub-processors and their group companies from third countries for support and maintenance, insofar as their terms provide for it;
  4. e-mail communication via Google Workspace.

The Processor processes the team members’ sign-in accounts at Firebase Authentication under its own responsibility (§ 3(6) no. 1); its privacy policy states their location.

(3) Transfers to third countries take place only with appropriate safeguards under Art. 44 et seq. GDPR, in particular on the basis of the EU standard contractual clauses (Art. 46(2)(c) GDPR) in the sub-processors’ terms or of an adequacy decision of the European Commission (Art. 45 GDPR, e.g. on the EU-US Data Privacy Framework), insofar as the recipient is certified under it. Annex 3 states for which sub-processors transfers to third countries are possible. If a basis ceases to apply, the Processor informs the Controller without undue delay and switches to another basis or replaces the sub-processor under § 7.

(4) § 8(2) applies to transfers to the bodies under § 8.

(5) The Processor makes further transfers to third countries only on documented instructions from the Controller (§ 4(1)).

§ 16 Obligations of the Controller

(1) The Controller is responsible for the lawfulness of the processing, in particular for the legal basis, informing data subjects (Art. 13 and 14 GDPR), safeguarding their rights and, where necessary, a data protection impact assessment. For the device connector, it also assesses § 25 of the German Telecommunications Digital Services Data Protection Act (TDDDG).

(2) The Controller sends only data required for moderation and follows the guidance on data minimisation in the integration guide. It sets the retention periods according to its legal obligations; the Service’s defaults are only suggestions.

(3) The Controller protects access to its tenant: it assigns roles as needed, removes team members who leave, keeps API keys, webhook secrets and credentials secret and renews them if misuse is suspected. The Processor recommends the second factor for Moderators and Viewers as well.

(4) The Controller informs the Processor without undue delay if it detects errors or irregularities in the processing.

(5) The Processor sends notices under this agreement by e-mail to the Owners of the tenant and to the address for notices under § 23(3) of the General Terms and Conditions. The Controller keeps these addresses up to date. Notices sent to these addresses are deemed received.

§ 17 Liability

(1) Art. 82 GDPR governs liability towards data subjects. Internally, each party is liable according to its share of responsibility for the damage (Art. 82(2), (4) and (5) GDPR).

(2) Otherwise, the liability provisions of the General Terms and Conditions (§ 17 of the Terms) also apply to claims under this agreement, unless mandatory law provides otherwise. This applies in particular to the limitation for simple negligence under § 17(2) of the Terms: liability only for breach of essential contractual obligations, limited to the foreseeable damage typical for the contract, per damaging event at most the higher of the fees of the last twelve months and EUR 10,000.

(3) The Controller indemnifies the Processor against third-party claims based on the Controller culpably having given an unlawful instruction or having transmitted data to the Service without a legal basis.

§ 18 Final provisions

(1) Amendments and additions to this agreement require text form. § 6(2) applies to changes to Annex 2 and § 7 to changes to Annex 3.

(2) The Processor may amend this agreement if changes in legislation, case law, requirements of the supervisory authorities or new functions of the Service require it and the level of protection for the data does not decrease. The same procedure applies as for changes to the General Terms and Conditions (§ 21 of the Terms):

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

(3) If the Controller’s data at the Processor are endangered by attachment, seizure, insolvency proceedings or other events or measures of third parties, the Processor informs the Controller without undue delay and informs the third parties that the power of disposal over the data lies with the Controller. Any right of retention in respect of the data is excluded.

(4) If a provision of this agreement is invalid, the remaining provisions remain valid. The statutory provision takes the place of the invalid provision.

(5) § 23(1) and (2) of the General Terms and Conditions apply to the applicable law and the place of jurisdiction.

(6) The German version is authoritative. The English translation is for information only.


Annex 1: Description of the processing

1.1 Overview

Item Content
Controller Customer under the Main Contract
Processor Karim Belkacem, sole trader trading as “SB-Techworks”, Lilienthalstr. 38, 93049 Regensburg, Germany
Service Limenia: dashboard at https://app.limenia.eu and programming interface at https://app.limenia.eu/v1
Duration Term of the Main Contract and thereafter until deletion under § 13
Storage location Google Cloud, region europe-west3 (Frankfurt am Main); media copies at Cloudflare R2, EU jurisdiction; exceptions under § 15 and Annex 3
Source of the data Backends of the Controller’s Apps via the programming interface; team members in the dashboard; services connected by the Controller (Annex 4)

1.2 Processing by function

Function Purpose Data Data subjects Precondition
Reports and cases Notice and action mechanism (Art. 16 DSA), grouping, prioritisation Report reason, free text of the report, pseudonym of the reporting person, reported user (external ID, display name), content reported and reporting end users, third parties in the content always
Content copies and media Review and preservation of evidence Text, context, link, creation time, images and videos (at most 10 per content item, each at most 20 MB) authors, third parties in the content always; media only if the App sends addresses
Decisions Moderation, statement of reasons under Art. 17 DSA, feedback to the App Action, policies, facts, reasons, end of a suspension, handling team member reported end users, team members always
Appeals Internal complaint-handling system (Art. 20 DSA) The person’s reasons, reply, outcome appealing end users always
Reporters and flaggers Feedback to reporters (Art. 16(5) DSA), trusted flaggers (Art. 22 DSA), protection against misuse (Art. 23 DSA) Pseudonym, counters, warnings, suspensions with internal note; organisations of the flaggers reporting end users always
User files Overview of sanctions and repeat behaviour per App External user ID, display name, status, end of suspension, counters, flags, device check status, refund counters end users always
Pre-moderation Review of content before publication As content copies, author (external ID, display name), outcome authors plan with pre-moderation
Signals and rules Indications of behaviour; the Controller’s rules create cases or set flags External user ID, signal type, value, context, time end users plan with signals
Webhooks Feedback to the App’s backend Event, decision with reasons, external user and content IDs, status, reply to appeals end users set up by the Controller
Connectors for accounts and purchases Banning and unbanning in the Firebase or Supabase project, effect on purchases at RevenueCat External user ID, action, entitlements end users plan with connectors, set up by the Controller (Annex 4)
Device connector Ban that survives reinstallation, without fingerprinting Device token (only passed on, never stored), summarised result end users with a checked device plan with device connector, set up by the Controller (Annex 4)
AI pre-check Suggestion for team members, priority See § 9(3); stored: assessment with short rationale end users, third parties in the content Owner opt-in (§ 9)
Store reviews and tickets Handling and answering reviews, grouping bug reports Review without name, classification, reply suggestion, reply, tickets reviewers, third parties in reviews plan with store reviews, set up by the Controller (Annex 4)
GitHub Issues for tickets in the Controller’s repository Title, summary, figures, versions; numeric account ID of the installation holders of personal GitHub accounts, indirectly reviewers set up by the Controller (Annex 4)
Transparency Database Submission of statements of reasons under Art. 24(5) DSA Statement of reasons without user IDs and content; facts only after express setting as a rule none; personal reference only if the facts contain it set up by the Controller (Annex 4)
Transparency report Figures for Art. 15 DSA Counts only none always
Memberships and invitations Access to the tenant by role, invitations Identifier (UID), role, time of admission, admitting person; invitations with e-mail address, role and inviting person; display of e-mail address and display name in the member list (sign-in accounts themselves: § 3(6) no. 1) team members, invited persons always
Audit log and delivery log Evidence of who decided or changed what; troubleshooting deliveries Identifier of the acting person, action, target, time; delivery status as a code team members, indirectly end users always
Anonymisation for own models Training of the Processor’s own models with anonymised data (§ 2(3) no. 3) under Annex 5: flagged and blocked chat messages, a sample of unremarkable messages, texts of decided content with check result and decision; raw text only until masking authors, third parties in the content without objection by an Owner, separately for chat and reports (Annex 5 no. 10)

1.3 Retention periods

The Owner sets the adjustable periods in the dashboard. The defaults are suggestions.

Data Default Adjustable Start
Content copies and media, open cases, open pre-moderation requests 183 days 183 to 1,095 days last report or latest decision
Decisions, decided cases, appeals, user files, files of reporting persons 365 days 183 to 1,095 days decision, resolution or last update
Dismissed reports 183 days 183 to 1,095 days decision
Content copies of approved pre-moderation requests 30 days 1 to 365 days approval
Signals, device checks 30 days 1 to 90 days time of the signal or check
Store reviews, tickets 183 days 30 to 730 days submission or reply; tickets from last change
Audit log, blocks after an objection to a review 730 days 1 to 1,095 days entry
AI assessments as the content copy – –
Delivery log 90 days fixed creation
Invitations 7 days fixed creation; deleted on acceptance
Idempotency keys 24 hours fixed creation
Hashes of checked content (AI) 30 days fixed check
Counters of the AI limits 1 day after the end of the hour or day fixed –
Counts without personal reference (usage, AI agreement, transparency report) 25 or 37 months after the end of the month fixed end of month
Technical logs (identifiers only) 30 days fixed entry
Anonymised data for own models (Annex 5) 365 days fixed creation
Database backups 7 days (point-in-time recovery), 14 days (daily backup) fixed backup

A legal hold suspends the retention periods of a case with its reports, decisions, content and appeals, or of a store review. Changed periods first apply to newly written data; the Owner can apply them to existing data. Memberships and configuration (Apps, policies, pre-moderation types, rules, templates) have no retention period; they remain until the Controller deletes them or until § 13(4). The Processor’s privacy policy governs the retention periods of the team members’ sign-in accounts and profiles (§ 3(6) no. 1).

1.4 Storage locations

Data Service Location
Database, backups, background tasks, secrets, logs Google Cloud (Firestore, Cloud Tasks, Cloud Scheduler, Secret Manager, Cloud Logging) europe-west3 (Frankfurt am Main)
Execution of the Service Google Cloud Run europe-west3
Media copies Cloudflare R2 EU jurisdiction
Routing for app.limenia.eu Firebase Hosting worldwide edge nodes, no storage
AI pre-check and AI classification Mistral AI data centres in EU and EFTA states
Anonymised data for own models and training (Annex 5) Google Cloud (dedicated storage in Cloud Storage) europe-west3

Annex 2: Technical and organisational measures

As of 27 October 2026. The measures apply to the Limenia Service including the sub-processors under Annex 3. Their own measures and evidence apply to their data centres.

2.1 Confidentiality

Physical access

  • The Processor operates no servers of its own. The Service runs entirely on managed services of Google Cloud and Cloudflare. These providers control access to data centres and hardware under their certifications.

Access to the dashboard

  • Sign-in via Firebase Authentication with Identity Platform using an e-mail link without a password or a Google account.
  • A second factor (TOTP via an authenticator app) is mandatory for Owners, Admins and the platform administration; without it, the Service refuses access. For Moderators and Viewers it is optional. SMS is not used.
  • After sign-in, the dashboard exchanges the token for a session cookie (HttpOnly, Secure, SameSite=Lax) that is valid for 12 hours and is not extended. The sign-in may be at most 5 minutes old at the exchange. The Service checks the cookie on every request, including revocation. Signing out revokes the sessions on all devices.
  • The dashboard stores no sign-in tokens in the browser.
  • Invitations are valid for 7 days, only for the invited, verified e-mail address; the token is stored only as a hash and does not reach any server logs.

Access for App backends

  • API keys per App, stored only as a SHA-256 hash and shown exactly once. Tenant and App are derived only from the key.
  • Rate limit per key (10 requests per second, briefly 50).
  • Revoked keys are rejected after at most 30 seconds.

Access to the infrastructure

  • Service accounts with minimal rights and without key files. Automated builds and deployments sign in via Workload Identity Federation.
  • The infrastructure is described as code (Terraform). Changes are traceable.

Authorisation

  • Roles Owner, Admin, Moderator and Viewer with an access table per operation; if an entry is missing, the Service refuses access.
  • Roles and tenant membership are kept in the database and checked on every request.
  • Media and user files only from the Moderator role; legal hold, audit log and team from Admin; retention periods only Owner.
  • The Processor’s platform administration has no access in the dashboard to cases, content and user files and cannot become a member of a tenant.
  • Media only via signed links valid for 5 minutes after an authorisation check; images in the dashboard blurred at first.

Separation

  • Tenant isolation: every data access goes through a layer that requires a tenant ID. Automated tests rule out access to other tenants for every method.
  • Direct access to the database from browsers is completely blocked by security rules.
  • Media are stored under keys containing the tenant, App and content ID.
  • Automated tests run against a separate test database.

Pseudonymisation and minimisation

  • Reporting persons only as a hash of App and user ID.
  • Store reviews without the reviewer’s name; device data from Google reduced to Android version and device class.
  • Device checks without tokens and without device identifiers.
  • AI inputs without user IDs, names and report texts.

Encryption

  • Transport only via HTTPS (TLS), HSTS; outgoing connections only via HTTPS.
  • Data at rest encrypted according to the providers’ standard (Google Cloud, Cloudflare R2).
  • Webhook secrets, connector credentials and provider keys only in Secret Manager in the region europe-west3; the database stores only references. No secrets in the code.

2.2 Integrity

Transfer

  • Webhooks are signed with HMAC-SHA256 over timestamp and content, with one secret per App.
  • Protection against server-side request forgery: outgoing requests to webhook destinations and media addresses only via HTTPS, only to public addresses (checked against the IP address actually connected), with time and size limits and checked redirects. Media at most 20 MB, 15 seconds per retrieval.
  • Calls to providers (Mistral AI, Apple, Google, GitHub, RevenueCat, Transparency Database) only to fixed addresses in the code.
  • Incoming webhooks (Stripe, GitHub, RevenueCat) are verified by signatures or hashes.

Input control

  • Audit log per tenant for write actions with acting person, action, target and time, without content.
  • Google logs changes to the infrastructure in administrative logs with a fixed retention of 400 days.
  • Decision, retention periods, status and delivery jobs are written in one transaction.

Protection of the web interface

  • CSRF token and origin check for all write requests, Content Security Policy, X-Frame-Options: DENY, no caching of API responses.
  • Container runs as a non-root user on a minimal base image.

2.3 Availability and resilience

  • Managed, automatically scaling services (Cloud Run, Firestore, Cloud Tasks) in one region.
  • Retries via queues: media retrieval up to 10 attempts, webhooks up to 12 attempts over about 20 hours.
  • Decision and delivery jobs are stored together so that no feedback is lost.
  • Reports, appeals and decisions do not depend on billing, plan, AI or connected services.
  • Monitoring: availability every 5 minutes, alert rules for outages, error rates, failed deliveries and background jobs; alerts are sent by e-mail to the Processor.

2.4 Recoverability

  • Database: recovery to its state at any minute within the last 7 days and daily backups kept for 14 days, each in the region europe-west3.
  • The infrastructure can be rebuilt from code (Terraform).
  • Media copies are not backed up separately.

2.5 Data protection by design and by default

  • Logs contain only identifiers, route patterns and error codes, no content, e-mail addresses, IP addresses of end users or media addresses. The platform’s automatic request logs with full address and IP address are not stored. Retention 30 days in the region.
  • Every record with content or personal reference receives an expiry date when written, according to the Controller’s retention periods; the database deletes automatically. A daily run deletes media copies.
  • Child protection under § 3(4).
  • AI functions are switched off until an Owner switches them on.
  • Anonymisation for own models only under Annex 5: masking, checking in a second stage, discarding in case of doubt, decoupling, separate storage with logged access; objection per tenant in the dashboard.
  • The Service sends replies to store reviews only after individual approval; before sending, it checks them for links, e-mail addresses, phone numbers and inadmissible requests for ratings.

2.6 Regular review

  • Automated tests and static checks on every change, including tests of tenant isolation, protection against server-side request forgery, signatures, sessions, second factor and retention periods.
  • Deployment only after successful tests; followed by an automatic availability check.
  • Weekly check of dependencies for updates; deployment tooling pinned to fixed versions.
  • Architecture decisions are documented in writing.

2.7 Organisation and control of processing

  • The Service technically implements the Controller’s instructions through its settings (§ 4).
  • Confidentiality under § 5(1); access to tenant data via the infrastructure only under § 5(2).
  • Selection of sub-processors based on their guarantees, in particular certifications and data processing terms (§ 7).
  • Handling of personal data breaches: detection through monitoring and logs, assessment, containment, documentation, notification under § 12.

2.8 Limits of the measures

For complete information:

  • The Service runs in one region and one production environment. Development and operation use the same cloud project; only automated tests have their own database.
  • The audit log does not record read access by team members (e.g. opening a case).
  • Customer-managed keys for encrypting data at rest are not used.
  • Media copies are not backed up and not versioned.
  • There is no on-call service. The Processor may handle disruptions outside business hours only on the next working day.

Annex 3: Sub-processors

As of 10 October 2026. The list is also published at https://limenia.eu/avv/#anlage-3 (English translation: https://limenia.eu/en/dpa/#anlage-3). Changes under § 7.

No. Sub-processor Service Data Place of processing Third country and safeguard Use
U1 Google (Google Cloud) Google Cloud Platform: Cloud Run, Firestore with backups, Cloud Tasks, Cloud Scheduler, Secret Manager, Cloud Logging, Cloud Monitoring all data under § 3 except media copies europe-west3 (Frankfurt am Main); monitoring and administrative logs without content global access for support and maintenance from third countries possible; appropriate safeguards under Art. 44 et seq. GDPR, in particular EU standard contractual clauses or an adequacy decision (EU-US Data Privacy Framework), insofar as the provider is certified always
U2 Google (Firebase) Firebase Hosting: TLS and routing for the domain app.limenia.eu all data passing through the domain, in transit only; no storage worldwide edge nodes routing may pass through nodes in third countries; appropriate safeguards under Art. 44 et seq. GDPR, in particular EU standard contractual clauses or an adequacy decision (EU-US Data Privacy Framework), insofar as the provider is certified always when the domain app.limenia.eu is used
U3 Cloudflare Cloudflare R2 (object storage) media copies (images and videos) EU jurisdiction (storage in data centres in the EU) access from third countries, in particular the USA, possible; appropriate safeguards under Art. 44 et seq. GDPR, in particular EU standard contractual clauses or an adequacy decision (EU-US Data Privacy Framework), insofar as the provider is certified always when Apps send media
U4 Mistral AI SAS, Paris, France language model via the EU endpoint api.eu.mistral.ai inputs and outputs under § 9 data centres in EU and EFTA states no transfer of content to third countries intended; under its terms, Mistral AI may store inputs and outputs for up to 30 days for abuse detection only after opt-in (§ 9)
U5 Google (Google Workspace) mailbox [email protected] personal data the Controller sends by e-mail, e.g. in support requests, forwarded data subject requests or notifications under § 12 according to Google’s terms, also outside the EU appropriate safeguards under Art. 44 et seq. GDPR, in particular EU standard contractual clauses or an adequacy decision (EU-US Data Privacy Framework), insofar as the provider is certified only for e-mail communication

Notes

  • The contracting party is in each case the provider’s company responsible for customers in the European Union under the provider’s contract terms. The Processor provides its name and address on request.
  • The providers in turn use sub-processors, in particular group companies for operation and support. Their published lists apply.
  • Firebase Authentication (Google) is not a sub-processor under this agreement: the Processor processes the team members’ sign-in accounts as a controller in its own right (§ 3(6) no. 1). Memberships, roles and invitations are stored in the database at U1.
  • Technically, the Service can use Gemini via Vertex AI (Google Cloud, region europe-west3) instead of Mistral AI. This is currently not in use. A switch is a change under § 7.
  • The bodies under § 8 (overview in Annex 4) and service providers the Processor uses only for its own purposes (§ 7(6)) are not sub-processors.

Annex 4: Special functions

4.1 General

The functions in this annex are active only if the Controller sets them up. Setting up, using and disconnecting are instructions under § 4. The connected bodies are not sub-processors of the Processor (§ 8).

Body Role Sent Location
Controller’s webhook receivers system of the Controller events under Annex 1 chosen by the Controller
Servers of the media addresses determined by the Controller retrieval of the address determined by the Controller
Controller’s Firebase project (Google) service of the Controller external user ID, action (ban, unban, revoke tokens) Controller’s project
Controller’s Supabase project service of the Controller user ID, ban duration region chosen by the Controller
Controller’s RevenueCat project service of the Controller App User ID, entitlements, action according to RevenueCat’s terms
Google Play Integrity, Apple DeviceCheck services of the Controller under its contracts device token, check identifier, bits Google: worldwide endpoint; Apple: according to Apple, generally the USA
App Store Connect API (Apple), Google Play Developer API independent controllers for their stores approved replies, review IDs worldwide endpoints; Apple, according to Apple, generally the USA
GitHub recipient under the Controller’s contract title and summary of tickets USA
DSA Transparency Database (European Commission) recipient under Art. 24(5) DSA statements of reasons without user IDs and content EU

4.2 Connectors for accounts and purchases

  1. Firebase: The Controller gives a service account of the Processor a narrowly limited role in its Firebase project and labels the project as its own. The Service stores no key for this.
  2. Supabase and RevenueCat: The Controller provides a key of its project. The Service stores it only in Secret Manager, never displays it again and uses it only for the described calls. The Service discards Supabase’s response containing the user object without reading it.
  3. The Service carries out refunds via RevenueCat only after express confirmation in the individual case.
  4. The keys give the Service the rights the Controller grants them. The Controller chooses the minimum rights required and can revoke the keys in its project at any time.

4.3 Device connector

  1. Purpose: A ban should survive a reinstallation of the App, without fingerprinting. For this, the Service reads and sets a few bits that Google (Play Integrity with Device Recall) or Apple (DeviceCheck) store per device and developer account of the Controller.
  2. Data: The device token, the check identifier, a timestamp and, when writing, the bits are sent; for Google also the App’s package name. No user IDs and no content. The Service never stores the tokens, only a summarised result in the user file.
  3. Access: For Android, the Service impersonates a service account in the Controller’s cloud project, without a key. For iOS, the Controller provides a DeviceCheck key, which the Service stores only in Secret Manager.
  4. Apple: For DeviceCheck, the Processor acts as the Controller’s “Service Provider” within the meaning of the Apple Developer Program License Agreement. It uses the tokens and the key only on behalf of and according to the instructions of the Controller, does not pass them on to third parties and complies with terms at least as protective as those of the Apple Developer Program License Agreement. This agreement is the written agreement required for this.
  5. Google: The use of Play Integrity is based on the Controller’s contracts with Google. The Processor uses the access only for the device check of the registered App.
  6. No automatic ban: The Service bans no one because of the bits. A flagged device of another user is only an indication (signal). If the App itself reacts automatically, the Controller is responsible for this.
  7. Reset: After a ban ends and at the request of a data subject, the Service resets the bits at the next check of the device if a team member requests it.
  8. Outage: If Google or Apple cannot be reached, the Service answers “not evaluated” and writes nothing.
  9. Obligations of the Controller: legal basis and assessment under § 25 TDDDG, privacy policy and privacy details in the stores, a way for users to request a reset, and, where necessary, a data protection impact assessment (template under § 11(2)).

4.4 Store reviews

  1. Subject matter: The Service retrieves the reviews of the Controller’s Apps from Apple’s App Store and from Google Play (every 15 minutes, on first connection the last 30 days, at most 7 at Google), stores a copy, classifies it after opt-in (§ 9), offers reply suggestions, sends approved replies and groups bug reports into tickets.
  2. Data: under § 3(2) no. 6. The Service does not request the nickname from Apple and discards the name at Google on import. Of device data, it stores only the Android version and device class. It does not link reviews to user files.
  3. Instructions: connecting a store, providing and disconnecting access (Admin), opt-in to AI classification, hints for replies and the retention period (Owner), approval of each individual reply (from Moderator), deletion of a review and legal hold (Admin). The approval is the instruction to send exactly this text to the store on behalf of the Controller. The Service never sends without approval; there is neither bulk approval nor automatic sending.
  4. Apple: The Apple Developer Program account and the API key belong to the Controller. The Processor acts as the Controller’s “Service Provider” within the meaning of the Apple Developer Program License Agreement, solely on its behalf and under § 4. This agreement is the written agreement required for this; the Processor complies with terms at least as protective as those of the Apple Developer Program License Agreement. It retrieves only reviews and replies of the registered App, uses the key for nothing else and does not pass it on. The Controller creates the key only for Limenia, with the smallest suitable role, and revokes it at the end of the contract or if misuse is suspected.
  5. Google: Access runs via a service account of the Controller in its cloud project, with a stored key or by impersonation. The Controller is Google’s contracting party. The Controller invites the service account in the Play Console only for the App concerned with the necessary rights.
  6. Roles of the stores: Apple and Google are independent controllers for their stores and the publication of reviews and replies. Replies are public.
  7. Content of replies: The Controller is responsible for the content and consequences of each reply, including when it is based on a reply suggestion by the AI or a template. Before sending, the Service checks replies for links outside the registered domains, e-mail addresses, phone numbers, requests for better ratings, incentives, promises of refunds, markup and length. This check is an aid; it does not replace review by the approving team member. The Processor does not warrant that a checked reply complies with the store rules or the law. Measures taken by the stores because of a reply affect the Controller; the Processor’s liability for its own errors under § 17 remains unaffected.
  8. Objection: An Admin can delete an individual review together with its reply suggestion and classification. The Service then creates a block without text and does not retrieve the review again. The Controller changes or deletes the review and the reply in the store itself.
  9. Retention: under Annex 1 (default 183 days). If the Controller disconnects a store, the Service deletes the credentials immediately; stored reviews and tickets remain until their retention period ends. At Google, the Service cannot detect deletions in the store; there, the retention period is the limit.
  10. Suspension: The Processor may suspend retrieval, classification or sending if a security incident, misuse or a request from a store or authority requires it, and informs the Controller without undue delay.
  11. Obligations of the Controller: legal basis, informing reviewers under Art. 14 GDPR (text module under § 11(2)), a data protection impact assessment where necessary, compliance with the store rules and the AI Act.

4.5 GitHub

  1. The Controller installs the Limenia GitHub App (rights only for issues and metadata) on selected repositories of its account and links it in the dashboard. The Controller is GitHub’s contracting party; GitHub is a recipient on its instruction.
  2. On the instruction of a team member, the Service creates one issue per ticket: title, a summary created with AI and marked as such, figures, versions, period and a link back. No names, no device details and no verbatim reviews.
  3. For a public repository, the Service requires an express confirmation. Issues in public repositories are visible to everyone.
  4. After creation, the Service no longer changes the issue. It lies with the Controller and GitHub outside the retention periods of this agreement. GitHub processes in the USA.

4.6 DSA Transparency Database

  1. If the Controller sets up the submission for an App, the Service sends a statement of reasons for every restrictive decision to the European Commission’s Transparency Database (Art. 24(5) DSA). It uses the Controller’s access token for this, which it stores only in Secret Manager.
  2. Sent are the type of restriction, legal or contractual ground, category, type of content, dates, countries, source, information on automation and the identifier of the decision. No user IDs, names, content or information about reporting persons. Instead of the facts, the Service sends a standard text; it sends the team member’s facts only if the Controller expressly switches this on. The Controller then ensures that the facts contain no personal data.
  3. Entries in the Transparency Database are public and remain available under the Commission’s rules. The Service cannot delete them.
  4. The Controller checks whether the obligation under Art. 24(5) DSA applies to it (e.g. the exemption for micro and small enterprises under Art. 19 DSA).

Annex 5: Anonymisation for own models

  1. Purpose: The Processor trains its own models for detecting and assessing content, for example for the moderation of chat messages and the pre-check of reported content. The models are the same for all customers; there is no model per tenant. The Service anonymises the data for this on the Controller’s instruction (§ 2(3) no. 3).
  2. Data used: two separate areas, each with its own objection:
    • Chat: flagged and blocked chat messages with the result of the check and, where available, the confirmation or correction by a team member, plus a sample of at most 2% of unremarkable messages. The Service does not otherwise store unremarkable messages; it keeps the text of the sample only in working memory until it is masked.
    • Reports: texts of reported content or content submitted for pre-moderation with a completed decision by a team member, with category, policy, measure and the results of automated checks.
  3. Never used: images, videos and other media files; user names and display names, also as the subject of a pre-moderation request; cases flagged for child safety, including locked ones; content under legal hold; content whose retention period has expired; free text of team members (facts, notes, reasons); report texts and information about reporting persons; store reviews; signals and device checks; data of tenants that have objected or are being deleted.
  4. Masking: The Service replaces direct identifiers with placeholders without changing the rest of the text: personal names, user names and mentions, e-mail addresses, phone numbers, links and domains, identification numbers such as account and order numbers or IBAN, addresses and location details below city level. It detects them with rules and with a model for names and places, both in the region europe-west3.
  5. Discard in case of doubt: After masking, a stricter second stage checks the text. If it still finds an indication of an identifier or is uncertain, the Service discards the record.
  6. Decoupling: The record contains no identifiers of tenant, App, user, case or content, no timestamps and no context from the report. There is no assignment back to the tenant or the case.
  7. Storage and retention period: in dedicated storage in the region europe-west3, separate from the Service. The Service may only store data there, not read them. Only a few named accounts of the Processor may read them; access is logged. Each file is deleted 365 days after it is created. The Processor does not pass the data on to third parties.
  8. Review and training: Before each training, the Processor reviews a sample itself; without its approval, the data of a month are not used. Training and evaluation take place in the region europe-west3.
  9. Models: The models output only categories and values and generate no text. Before use, the Processor checks whether training texts can be extracted from a model.
  10. Objection: An Owner can object in the dashboard at any time, separately for chat and reports; the audit log records the objection. 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 tenant and therefore cannot be deleted individually; they are deleted when their retention period under no. 7 expires.
  11. Limits: No masking detects every identifier. It may miss indirect descriptions without names, such as “the one from class 7b”, and verbatim quotes that can be found again in a public App. Decoupling, restricted access and the review counter this.
  12. Obligations of the Controller: The Controller checks whether it must inform its end users about the anonymisation (Art. 13 and 14 GDPR). The Processor provides a text module for this (§ 11(2)).

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.