File the StopNCII hash for ex partner deepfake on Mastodon

Why this matters for ex partner deepfake on Mastodon

Ex partners commonly retain photographs from the relationship that are easily fed into AI nudify or face swap tools. The technical barrier is now under five minutes per image.
Federated content spreads across multiple instances through reposts and replies. Removing from the originating instance does not remove from the cached copies on every instance that federated the post.
Revenge motivated deepfake distribution follows a documented escalation curve. The first 72 hours after creation typically determine whether the content reaches the wider re upload audience or stays contained to the original platform.
Social platform distribution drives the majority of secondary discovery because account based interactions surface content to the victim's existing network within hours.
Ex partner deepfake cases benefit from the documented relationship history because the source photographs establish access and motive simultaneously. This is particularly relevant when the action you are pursuing is file the StopNCII hash, because after the initial platform removal is in progress. the hash submission provides ongoing prevention against re upload across the partner platform network.

How removal works

The four step deepfake removal process under the TAKE IT DOWN Act of 2026.

What to do, step by step

01
Forensically preserve every instance before any other action Capture full page screenshots with the URL bar visible, save the highest resolution copy of the deepfake images available, and document any visible AI generator fingerprints including watermarks, edge blending artifacts, and skin texture inconsistencies. Full page screenshots of every URL where the deepfake content appears, with the URL bar visible
02
Run a biometric scan to find every copy across platforms ex partner deepfake content distributed on Mastodon rarely stays there. ScanErase indexes 2.4 billion face embeddings across 200 plus platforms and identifies every current hosting location in a single scan, including mirror copies and AI generated variants.
03
Submit the perceptual hash to StopNCII.org Generate the perceptual hash on your own device using the StopNCII.org tool. Submit only the hash, not the image itself. The hash will be propagated to Mastodon and other StopNCII.org partner platforms within 48 hours, preventing identical re upload across the partner network.
04
Do not contact the perpetrator before notices are filed Do not contact the ex partner before evidence is preserved and notices are filed. Confrontation gives them time to delete content, claim the AI nature is a defense, and craft a denial. All communication during the active removal phase should be through counsel. The perpetrator's behavior during this period is critical evidence.
05
Coordinate the Mastodon platform removal pipeline Mastodon is federated across thousands of independent instances. Removal requires identifying the specific instance hosting the content and contacting that instance's admin directly.
06
Escalate through hosting and CDN if required Each Mastodon instance has its own admin. Most instance admins are responsive to NCII reports. The fediverse operates a shared block list which can prevent the originating instance from federating with mainstream instances.
07
File the complete evidence record for the legal track StopNCII.org operates under the legal framework of the Revenge Porn Helpline (UK) provides the foundational legal basis for this action. Document every notice sent, every platform response, and every confirmation in a single evidence file. ScanErase produces this Verified Removal Package automatically as your case progresses.

The 48 hour statutory deadline

Statutory 48 hour removal timeline: 47 USC 223a requires platforms to remove non-consensual intimate imagery within 48 hours of a valid notice.

Legal context

StopNCII.org operates under the legal framework of the Revenge Porn Helpline (UK)
Participating platforms enforce hash matches under their own terms of service
Most Mastodon instance admins comply quickly with NCII reports. The Mastodon Server Covenant explicitly prohibits NCII content, which gives leverage even with instances outside US jurisdiction.
ex partner deepfake statutory basis: 47 USC 223a TAKE IT DOWN Act for the 48 hour platform removal obligation, applicable to AI generated NCII
State NCII criminal statutes in 48 states with felony provisions in 16 states for distribution of AI generated intimate imagery

Frequently asked questions

What if the perpetrator was previously in a consensual relationship with me?

A prior consensual relationship is not a defense to AI generated NCII production or distribution. Consent to a relationship is not consent to AI deepfake creation, and the TAKE IT DOWN Act explicitly removes consent at creation as a defense for the distribution of deepfake content.

How long will Mastodon actually take to remove the deepfake content?

Mastodon typically responds in approximately 48 hours when a properly formatted statutory notice is filed. ScanErase files the notice within 5 minutes of authorization and tracks compliance through your Verified Removal Package.

Will the platform notify the perpetrator that I filed the takedown notice?

Most platforms provide some notification to the account that posted the content, but the notification typically does not identify you. Your name and contact information are not shared with the perpetrator. The notification is limited to the fact that content was removed under a statutory NCII notice.

What if the perpetrator re uploads the deepfake to Mastodon after removal?

Mastodon retains hash signatures of removed NCII content which prevents identical re uploads to the same platform. A follow-up ScanErase scan checks for re uploads across all 200 plus indexed platforms, including AI generated variant versions, so you can file a new notice as soon as matches reappear.

Will the file the StopNCII hash action reveal my identity to Mastodon or the perpetrator?

Permanent perceptual hash record across the StopNCII.org partner network. Future upload attempts of the matching deepfake to participating platforms are blocked at the upload stage. The disclosure scope is limited to what the action requires. Your scan and removal process is not disclosed to employers, family, or any third parties beyond the recipients required by the specific legal procedure.

I searched my ex made deepfakes of me and found this guide. What is the very first thing I should do right now?

Before any other action, forensically preserve the evidence with full page screenshots and the highest resolution file copies you can obtain. Do not contact the ex partner before evidence is preserved and notices are filed. Confrontation gives them time to delete content, claim the AI nature is a defense, and craft a denial. Once evidence is preserved, the Mastodon takedown notice and the file the StopNCII hash action can proceed in parallel.

Submit a perceptual hash to StopNCII.org for ex partner deepfake on Mastodon