Compliance

DSA

What the Digital Services Act asks of your app, what Limenia does for you and what remains your job — notice and action, statements of reasons, complaints, trusted flaggers and transparency.

Limenia gives you the moderation workflow the EU Digital Services Act (DSA) expects from online platforms. The tenant stays the provider: it decides, it is responsible for its decisions and texts, and its app must carry out the decisions and talk to its users. This page is guidance for developers, not legal advice.

Overview

DSA Limenia does Your app does
Notice and action (Art. 16) Accepts reports (POST /v1/reports), bundles them into cases, records goodFaith, never refuses reports because of the plan Offers a report function for content and users, sets the reporter from the login, confirms receipt to the reporter
Informing reporters (Art. 16(5)) Sends reports.resolved with the outcome and the deadline for complaints Tells each reporter the outcome in its own words
Statement of reasons (Art. 17) Creates it for every decision, as text and structured fields Shows it to the affected user as plain text, also when the account is blocked
Internal complaint handling (Art. 20) Accepts complaints for six months (POST /v1/appeals), a human decides, sends appeal.resolved with a reasoned answer Offers a complaint function to affected users and reporters, shows the answer
Out-of-court dispute settlement (Art. 21) Names it in the redress text and in every answer to a complaint Nothing beyond showing the texts
Trusted flaggers (Art. 22) Registry per tenant, priority for their reports Sets trustedFlaggerId for people who verifiably act for one
Measures against misuse (Art. 23) Warns and suspends reporters, refuses their reports with 403 reporter_suspended Shows warnings and the end of a suspension
Transparency reports (Art. 15, 24) Counts per month and exports the report templates of the Commission The tenant completes and publishes the report
Transparency database (Art. 24(5)) Optionally submits statements of reasons per app Nothing

Notice and action

  • Every user must be able to report content and other users in your app. Use the report sheet of the Flutter package or your own form, and forward reports with POST /v1/reports.
  • Let the reporter confirm that the report is accurate and complete and send goodFaith: true only if they did (Art. 16(2)(d)).
  • Confirm the receipt in your app; Limenia returns a reportId you can show or store.
  • After the decision, reports.resolved tells you which reports were handled. Tell each reporter the outcome briefly and that they can complain until appealDeadline (see Webhook events).

Statement of reasons

Every decision carries a statement of reasons (Art. 17): the action, its duration, the facts, the policies or laws it is based on, whether it followed a notice (noticeSource: notice, trusted_flagger, own_initiative), whether automated means were used (automatedDetection, automation) and the redress options. The tenant sets the redress text in the dashboard (DSA → Redress).

Show statementOfReasons.text to the affected user for every decision except dismiss, as plain text. If the account is blocked, use a channel outside the app (e-mail, login screen). See Showing the statement of reasons.

Complaints

Affected users can complain against restricting decisions, reporters against any decision on a case they reported, for six months. A human decides every complaint; the answer names the further options (out-of-court dispute settlement, courts). Your app needs a complaint function for both groups. See Complaints.

Trusted flaggers

The tenant registers trusted flaggers in the dashboard (name, recognition reference, areas). Their reports get at least priority high, and statements of reasons say the decision followed a report by a trusted flagger without naming it. Limenia has no separate form or login for trusted flaggers: they report through your app or your own channel, and your backend sets trustedFlaggerId. See Reports.

Misuse

Moderators can warn reporters who frequently send manifestly unfounded reports, and after a delivered warning suspend their reports for up to 365 days. Complaints of affected users are never blocked. See Reporters and misuse.

Transparency

  • Transparency reports: Limenia counts reports, decisions and complaints per month. An admin exports the report templates of the Commission (CSV files) for a period, per app or for all apps. Some parts (orders of authorities, out-of-court disputes, staff, qualitative information) stay empty for the tenant to complete. Limenia never publishes the report.
  • Transparency database: per app, an admin can let Limenia submit the statements of reasons of restricting decisions (remove_content, restrict_content, reject_submission, suspend_user, ban_user) to the DSA transparency database of the Commission, with the tenant’s own token. No personal data and no external IDs are sent; facts are replaced by a standard text unless the tenant opts in. Small and micro enterprises are usually exempt; the tenant decides.

Child safety

Reports with the categories child_safety and protection_of_minors make the case urgent, and Limenia keeps no copy of the media (only the URL you sent). Limenia does not report to authorities; securing evidence and any report to authorities (Art. 18) remain with the tenant. There is no separate alert for urgent cases yet; moderators filter them in the dashboard.

Store requirements

The app tab DSA → Store requirements is a checklist of what the App Store and Google Play expect from apps with user-generated content. Four items are checked automatically (a report has arrived, the webhook is active, a redress text is set, an active policy exists); the others (filtering content, blocking users, contact information, accepting the terms before posting, account deletion in the app and on the web) an admin ticks off. It is guidance, not legal advice.

What remains with the tenant

  • Deciding, and being responsible for decisions, statements of reasons and answers to complaints, also when they are built from templates.
  • Its terms of use and policies.
  • Carrying out decisions in the app and informing its users; Limenia never contacts end users.
  • Checking which DSA obligations apply (for example exemptions for small and micro enterprises).
  • Publishing transparency reports.
  • Data protection duties (see Data protection).