Remove data breach leak 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.
• Data breaches at companies handling intimate content periodically expose user data including photos and messages. The Ashley Madison, Adult Friend Finder, and several dating app breaches have produced large scale exposure.
• Breach data is typically released through a combination of the dark web, paste sites, and dedicated leak forums. The data may circulate for years after the original breach.
• 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. The company's breach notification, if any has been issued
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
   Preserve the original account access logs The platform that was breached retains access logs that support law enforcement subpoena for the unauthorized access. Do not change passwords or sign out of all sessions before the logs are preserved or you may trigger log rotation.
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
• Class action breach litigation against the original company
• 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.