Deepfakes created from Facebook tagged photographs on iMessage
facebook source deepfake content on iMessage. iMessage typically responds to NCII notices in under 24 hours. Removal from iMessage requires a properly formatted statutory notice and may benefit from parallel filing through a dedicated NCII portal.
The combined situation
Photographs of you from Facebook, including tagged photos posted by other users, have been used as input to AI deepfake tools. The Facebook tagging system creates a wide attack surface that no individual user can fully restrict. When this scenario plays out on iMessage specifically, removal proceeds through the statutory takedown process under 47 USC 223a combined with the scenario specific response that source cases require.
Why this combination is high risk
iMessage group chats can include up to 32 participants and content can be forwarded to additional chats with one tap. Read receipts and typing indicators provide attribution that supports law enforcement subpoenas. For facebook source deepfake cases, facebook tagged photographs are accessible to a much wider audience than individual privacy settings suggest because the tagging system is governed by the original poster's settings.
How removal proceeds
Apple accepts iMessage NCII reports through its Communication Safety reporting flow. The iOS 17 sensitive content warning system can also be used to flag content for review. Facebook tag history is preserved in Meta records and is recoverable through subpoena even after untagging, which preserves the source connection evidence.
Scan for facebook source deepfake content on iMessage
Free biometric scan in under 60 seconds. $15 to unlock your full report.
Start your free scan