Remove revenge after breakup content from Mastodon

Why this happens on Mastodon

• 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.
• Post breakup distribution typically occurs within the first 90 days after the relationship ends. The distribution is rarely random and often involves coordinated posting across multiple platforms.
• Many ex partners attach identifying information including the victim's name, employer, school, or contact details. This identifying context creates additional civil claims beyond the NCII statutes.
• Cross platform spread is the rule, not the exception. Content first appearing on Mastodon typically reaches between four and twelve additional platforms within 72 hours through reposts, mirrors, and screenshot redistribution.

The takedown process

What to do, step by step

1. 01
   Document every instance before reporting Capture full page screenshots with the URL bar visible, the posting account handle, and the upload timestamp. Full page screenshot of every URL where the content appears, including any attached identifying information
2. 02
   Run a biometric scan to find every copy across platforms Content first appearing 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 AI generated derivatives.
3. 03
   Dispatch the takedown notice to Mastodon Mastodon is federated across thousands of independent instances. Removal requires identifying the specific instance hosting the content and contacting that instance's admin directly.
4. 04
   Do not contact the ex partner before notices are filed Do not communicate with the ex partner during the active distribution period. Communications can be edited and selectively shared to suggest reconciliation or consent. All communication should be through counsel. All communication during the active removal phase should be through counsel. The ex partner's behavior during this period is critical evidence.
5. 05
   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.
6. 06
   File a police report and preserve the legal record 47 USC 223a TAKE IT DOWN Act for platform removal provides the federal basis for the takedown. Document every notice sent, every platform response, and every removal confirmation in a single evidence file. ScanErase produces this Verified Removal Package automatically as your case progresses.

Legal context

• 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.
• 47 USC 223a TAKE IT DOWN Act for platform removal
• State revenge porn statutes which exist in 48 states with criminal penalties
• Capture the full federated URL including the instance domain, the original post URL, and any reblogs from other instances. Each instance must be reported separately for full removal.