NCMEC Reporting

what is ncmec? the national center for missing & exploited children (ncmec) operates the cybertipline the official us channel for online platforms to report child sexual abuse material (csam) and related offences in the united states, reporting to ncmec is a legal requirement for any online platform that becomes aware of csam on its service nima has a built in ncmec integration once configured, reports are filed automatically whenever a child safety policy violation is confirmed — no manual submission required how it works nima handles ncmec reporting differently depending on how the moderation decision is made cases moderated automatically by ai when an ai rule confirms a child safety policy violation without human review, the case is routed to the ngo/lea review queue this queue is used for moderator to confirm the submission of ncmec reports automatically with all the data required the ngo/lea queues is only a review queue and should not be used for usual moderation decisions by moderators cases moderated by a human moderator when a moderator confirms a child safety policy violation within queues whether the case originated from a user report, a trusted flagger, an lea request, or a proactive detection queue a prompt appears asking them to submit the report to ncmec the moderator completes the submission from the moderation console before you start to connect nima to ncmec, your organisation needs an esp (electronic service provider) account with ncmec , which gives you a username and password for the cybertipline if you don't have one yet, contact ncmec directly to register your platform your nima account team will handle the technical connection once you have your credentials you don't need to set up anything in the platform until that step is complete following the removal of a content, the original url of your content will no longer be available to nima to make sure you send a valid url to ncmec, contact the tremau team to agree on how to share a secured url in the response of the action endpoint when a webhook is sent configuring the workflow step 1 admin setup configuring ncmec reporting this is a one time setup once configured, the integration runs automatically in the background in nima, navigate to settings → external reporting ncmec will be listed as an available reporting agency it comes pre loaded, so there is nothing to add manually step 2 create a reporting rule click add rule a reporting rule tells nima which policy violations should trigger an automatic ncmec report to which review queue ai detected cases should pass through before submission and who at your organisation is listed as the contact on each submission fill in the following fields rule name — a clear internal label, for example ncmec — csam auto report agency — select ncmec policies — choose every child safety policy that should trigger a report when confirmed you can select multiple policies if you select a parent policy (e g child safety ), all sub policies under it are covered automatically review queue — the queue where ai detected cases are sent for human review before submission by default, this queue is ngo/lea review queue once a moderator confirms the violation in that queue, the report fires automatically reporting contact — the first name, last name, and email address of the person at your organisation registered as the responsible contact with ncmec this is the person ncmec will reach out to if they have questions about a report step 3 enable the rule toggle the rule to enabled it will now fire automatically whenever one of the linked policies is confirmed on a case you can pause the rule at any time by toggling it off reports already submitted are not affected what gets sent to ncmec each report is populated directly from the case the secured content url sent back to nima following any take down the reported user's details (name, email, platform id) the date and time of the original report the type of incident, matched to the policy violation confirmed ncmec incident types when submitting a report, you'll be asked to select an incident type choose the one that most accurately describes what was found incident type when to use it child pornography csam — sexual imagery involving a minor child sex trafficking content advertising or facilitating the trafficking of minors child sex tourism content promoting or arranging sexual tourism involving minors child sexual molestation depictions or descriptions of the sexual molestation of a child online enticement of children for sexual acts an adult attempting to solicit a minor into sexual activity unsolicited obscene material sent to a child sexually explicit content sent to a minor without consent misleading domain name a url designed to lure minors to explicit content misleading words or images on the internet text or imagery designed to deceive minors into accessing explicit content important things to know reports cannot be undone once a report has been submitted and accepted by ncmec, it cannot be withdrawn if you are unsure whether a case warrants a report, use your review queue step to verify before confirming one report per piece of content if the same content has already been reported successfully to ncmec, nima will not send a duplicate report — even if the case is re reviewed or the job retries after a failure media files are included automatically for image, video, and audio content, nima uploads the file directly to ncmec as part of the report you don't need to download or attach anything manually sub policies are covered if your reporting rule is linked to a parent policy (e g child safety ), it will automatically apply to all sub policies beneath it you don't need to create separate rules for each sub category