Getting started
Concepts
The terms of Limenia — tenant, app, API key, user file, content, report, case, decision, complaint, review request, signal, rule, policy, reporter and trusted flagger.
Tenant
The organisation that uses Limenia, usually the company that runs the apps. Under the DSA the tenant is the provider of the apps and responsible for the decisions; Limenia processes data on its behalf (see Data protection).
- A tenant starts in the status
onboardingand becomesactivewhen an owner finishes the setup wizard (tenant details, retention, policies, first app, API key). Until then the API answers 403tenant_not_activeto reports, complaints, review requests, signals, device checks and updates of users (PUT /v1/subjects);GET /v1/pingreturnstenantStatus. - People in the dashboard have one of four roles: Owner (everything, including billing, retention periods and opt-ins), Admin (team, apps, API keys, webhooks, connectors, policies, rules, trusted flaggers, delivery log), Moderator (decides cases, complaints and reviews, sees user files and media) and Viewer (reads cases and settings, no media and no user files). Everyone in the dashboard signs in with a second factor (an authenticator app), whatever the role.
App
One app of the tenant, for example the iOS and Android app of one product with its backend. Each app has its own API keys, webhook, connectors, review types, signal types and rules.
- The slug (lowercase letters, digits and hyphens, at most 40 characters) cannot be changed and appears in every webhook as
app.slug. - Supported actions restrict the actions moderators can choose to those your app can carry out;
dismissis always possible. Decisions on review requests ignore this setting. - External IDs (
externalUserId,externalContentId) are scoped per app: the same ID in two apps means two different users. - There is no sandbox. Use a separate app as your test app (see Testing).
API key
The secret your backend sends as Authorization: Bearer <key>. A key belongs to exactly one app and determines tenant and app of every request. See API keys.
User file
Limenia’s record of one user of one app, identified by your externalUserId. In the API it is a subject. It holds the display name you sent, the sanction status (active, warned, suspended until a date, banned), counters of reports and violations, flags set by rules, recent signals and, with the device connector, the device state. Moderators can also decide directly on a user file (warn_user, suspend_user, ban_user, restore), without a case. See Users.
Content and snapshot
The thing that is reported or submitted, identified by your externalContentId. With the first report on a content, Limenia stores a snapshot: the text, the context, the link and copies of the media you sent. Later reports do not change it. Limenia never reads content from your app; moderators see only the snapshot. See Reports.
Report
A notice that content or a user may break the rules (Art. 16 DSA). Your backend sends it with POST /v1/reports.
source: user: a user of your app reported it.source: system: your app detected it itself, or Limenia created it (rules, RevenueCat, ban evasion).reasonCategoryis usually the code of a policy.- The reporter is stored only as a pseudonym (a hash), never with your user ID.
Case
The unit moderators work on. Limenia bundles reports into cases:
- Reports on the same content of an app go into one case while it is open or in review. Reports without content are bundled per reported user. After a decision the next report opens a new case.
- Status:
open,in_review(a moderator took it) anddecided. - Priority:
normal,high(for example reports of trusted flaggers, ban evasion) orurgent(child safety). Rules and the optional AI pre-screening can raise the priority, never lower it.
Decision
The result of a moderator’s work. Every decision has exactly one action and a statement of reasons (Art. 17 DSA). Removing content and suspending its author are two decisions.
| Action | Effect |
|---|---|
dismiss |
No violation, nothing happens |
remove_content, restrict_content |
Remove or restrict the content |
warn_user, suspend_user, ban_user |
Warn, temporarily block or permanently block the user |
restore |
Lift an earlier restriction of the content or the account (restoreScope) |
reject_submission |
Review requests only: do not publish the submitted content |
The statement of reasons comes as ready-made text in the tenant’s language and as structured fields (facts, grounds, whether it was based on a notice, automation, redress). Decisions reach your backend as decision.created. See Webhooks.
Complaint
A request of the affected user or of a reporter to review a decision again (internal complaint handling, Art. 20 DSA). In the API it is an appeal. Complaints are possible for six months after the decision; a human always decides. The outcome is upheld (the decision stays) or changed (a new decision replaces it). See Complaints.
Review request
Content your app wants checked before publishing it (pre-moderation), for example profile photos. The dashboard calls them approvals. Each request has a review type created per app (code, guidelines, target time) and ends as approved, restricted or rejected. See Pre-moderation reviews.
Not to be confused with store reviews: the ratings of your app in the App Store and Google Play, which the store reviews connector collects.
Signal and rule
A signal is an observation about a user that is not a report: a score jump, implausibly many actions, many new accounts. Your backend sends signals of signal types you create per app. A signal alone does nothing.
A rule of the app turns signals (or many reports of different people) into an action: open a case, raise the priority of open cases, or flag the user file. Limenia never sanctions because of a rule; a moderator decides. See Signals.
Policy
A rule of the tenant’s terms of use or a legal provision a decision can be based on, with a code (e.g. harassment_hate), a title and a legal basis (terms or law). Policies are the vocabulary of reasonCategory and appear in decisions as policies[]. The tenant edits them in the dashboard; they are never deleted, only deactivated. See Categories.
Reporter
The person who sent a report. Limenia knows reporters only as a hash of app and user ID. Moderators can warn reporters who send many unfounded reports and later suspend their reports (Art. 23 DSA). Reporters learn about the outcome through your app (reports.resolved). See Reporters and misuse.
Trusted flagger
An organisation recognised under Art. 22 DSA whose reports get priority. The tenant registers trusted flaggers in the dashboard; your backend marks a report with trustedFlaggerId when the reporter acts for one. See Trusted flaggers.
AI pre-screening
Optional, switched on by the owner. A language model assesses reported and submitted content against the tenant’s policies, suggests an outcome and can raise the priority. A human always decides; when a moderator confirms a suggestion, the statement of reasons says so (automation: partial). Fully automated decisions (automation: full) are not used. The model receives the content, not user IDs, names or reporter information.
Connectors
Optional links to services of the tenant that carry out decisions directly, in addition to the webhook: Firebase, Supabase, RevenueCat, the device connector, and the store reviews connector, which collects app store ratings.