Compliance
Data protection
What to send to Limenia and what not, how reporters are pseudonymised, how long data is kept and where it is hosted.
Roles
The tenant is the controller for the data of its users. Limenia processes it on the tenant’s behalf under a data processing agreement: German original, English translation. Services the tenant connects itself (Firebase, Supabase, RevenueCat, Google Play Integrity, Apple DeviceCheck, the store APIs, GitHub) are the tenant’s own services, not sub-processors of Limenia.
What to send
Send only what moderators need to decide:
- The reported content and its context, everything else as IDs.
- No e-mail addresses, phone numbers, IP addresses, device identifiers or locations in
externalUserId,displayNameorcontext. externalUserId: a stable, pseudonymous ID of your system (for connectors the Firebase UID, the Supabase user UUID or the RevenueCat App User ID), never an e-mail address.displayName: only what other users see anyway.- The only exception are HMACs of e-mail address and phone number in
identifiersfor ban evasion across apps, never the plain values. - Never send device tokens, API keys or session tokens in any field.
Pseudonymised reporters
Reporters are stored only as a truncated SHA-256 hash of app ID and reporter ID (a pseudonym). Limenia cannot tell you who reported something; reports.resolved returns your own report IDs instead. To check a complaint of a reporter, Limenia compares hashes.
Hosting and security
- Data is stored in the EU. Media copies are kept in private object storage and shown to moderators only through short-lived signed links, blurred by default.
- Limenia logs IDs, never content.
- Reports with the categories
child_safetyandprotection_of_minorskeep no media copy at all, only the URL. - The optional AI pre-screening runs in the EU or EFTA, only after the owner opted in, and receives content without user IDs, names or reporter information.
- Limenia trains its own moderation models only with anonymised data: names, user names, contact details, links and IDs are masked, and the text is cut off from tenant, app, user and time. Media, user and display names and child-safety cases are never used. The owner can opt out in the dashboard at any time (DPA, Annex 5).
Retention
Retention is set by the tenant (owner, dashboard Settings → Retention); deletion is automatic, usually within a day after the period ends.
| Data | Default |
|---|---|
| Snapshots of reported content and media copies | 183 days |
| Decisions, decided cases, complaints, user files | 365 days |
| Copies of approved review requests | 30 days |
| Signals and device checks | 30 days |
| Store reviews and tickets | 183 days |
| Audit log | 730 days |
| Delivery log | 90 days |
| Idempotency keys | 24 hours |
- A legal hold on a case suspends its deletion until it is released.
- There is no deletion API for apps, and no per-user deletion. Data of a deleted account stays until its retention ends. For a request of a data subject, contact Limenia.
- Identifiers live as long as the user file they belong to.
Duties of the tenant
- Name the processing by Limenia in the privacy policy of the app (reports, moderation, complaints; device checks and store reviews if you use them).
- With the device connector: cover the device check in the privacy policy and the store privacy labels, decide on consent for reading device information, and offer users a way to ask for a reset.
- With ban evasion across apps (coming soon): a data protection impact assessment and a note in the privacy notices of all apps that take part.
- Keep logs of your own backend free of content and personal data (see the hard rules).