DSA Transparency Reporting

platforms demonstrate accountability by publishing regular reports on content moderation operations in jurisdictions like the european union (dsa article 15 and 24), these reports are mandatory, with the annual publication and submission of a transparency report nima automates this process, capturing all necessary data points and generating compliant reports under the dsa, every moderation decision has to be classified twice by the type of violation it concerned, and by the type of action you took you set both mappings once, and every subsequent decision is classified automatically get this right and your transparency report is generated from your live decisions with no manual reclassification leave it incomplete and decisions reach your report uncategorised mapping your policies and actions there are two ways to do this, and they write to the same place use whichever fits how you work map as you go, from policies and actions when you create or edit a policy in configure > trust & safety > policies , assign its dsa infringement category where a policy has sub policies, the mapping is made at sub policy level, matching how enforcement is applied — see policy configuration docid\ r6vgf6m3d k8slkyopppp when you create or edit a moderation action in configure > trust & safety > actions , assign its dsa decision type — for example removal, disabling access, or demonetisation see actions docid\ lsfkyoqsi365x alowit1 map in bulk, from dsa configuration configure > compliance > dsa configuration shows everything on one screen, in two tabs infringement categories — every policy and sub policy, with the dsa infringement category assigned to each actions — every moderation action, with its dsa decision type this is the faster route for initial setup, and the place to check your configuration is complete before generating a report if you classify an action as other , nima requires a short description of what the action does the description is stored with the mapping and appears in your transparency reporting, so write it for an external reader rather than an internal one keeping the mapping complete both mappings are configuration, not one off setup every time you add a policy, a sub policy or a moderation action, classify it — an unmapped item still moderates content correctly, but its decisions carry no dsa classification into your reports generating your report transparency reports are generated from comply > transparency reporting choose the dsa transparency report , set the start and end date of the period you are reporting on, and request it the report is not downloaded in the browser nima generates it in the background and emails you a link when it is ready — the screen confirms this with "your report download has been successfully started and will be sent to your email address" large date ranges take longer, so request the report before you need it rather than on the day the emailed link is valid for 7 days after that it expires and the report has to be regenerated from the same screen download and archive the file when it arrives rather than relying on the email as your record automatic data collection once your mappings are configured, nima automatically captures data for every moderation decision across all sources for each sheet of the dsa transparency report own initiative moderation collects all cases from your user reports docid\ lj5fsignckovcgdmcbsqe and from automated moderation decisions are classified according to how your policies have been mapped to dsa infringement categories, and actions are recorded according to how your moderation actions have been mapped to dsa action types the notices sheet is automatically populated based on the infringement categories selected by users when they submit reports through the illegal content report form docid\ ic7tcb ig zpyofliekr when a report is submitted with "trusted flagger" as the report type, this information is logged and reflected in the transparency data the orders sheet covers legally binding orders received from authorities under dsa article 9 — see lea requests docid\ jwgpuz6es1bqhehohi2u0 for how those reach nima the internal complaints sheet is automatically compiled by nima based on all appeal submissions and their outcomes, providing a complete view of your platform's redress mechanisms transparency dashboards the same page carries live charts alongside the report downloads, so you can see the shape of your moderation activity without waiting for a generated file proactive detection → dsa category — what your automated detection is catching, by dsa infringement category user report illegal content → label — what your users are reporting, by the category they selected on the report form they are useful as a sense check before you generate a report a category that looks empty here will look empty in the report too, and usually points at a missing mapping statements of reasons transparency reporting is periodic and aggregated separately, the dsa requires a statement of reasons to be submitted to the european commission's transparency database for each individual decision — nima automates this too see eu transparency database integration docid\ gu7clevee4s4pm8qf0k4d