This provision states that when users interact with or enable content sharing with third-party federated services, Threads transmits user profile information, post content, attachments, and metadata (including server IP address and interaction timestamps) to those external services, which then store and process that data under their own terms. The policy frames this transmission as user-directed, occurring when users enable interoperable capabilities or interact with third-party content.
This analysis describes what Threads's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that data transmitted to third-party federated services exits Meta's data governance perimeter and becomes subject to the terms and policies of those external services. Compliance teams must account for this data flow boundary when conducting data mapping, assessing data subject rights fulfillment, or evaluating cross-border data transfer obligations.
The updated policy removes FAQ sections that previously addressed how to deactivate or delete a profile, manage personal information, and share data with third parties. Additionally, the policy removes explicit language disclosing that 'Your interactions with AIs will be used to improve AI at Meta' and removes the direction to review Meta's AI terms. Users no longer have these FAQ resources in the policy document, though this change does not necessarily alter the underlying practices or rights; it only removes the documented guidance.
View change record →Under this provision, user profile information, post content, photo and video attachments, and interaction metadata are transmitted to third-party federated services that operate outside Meta's control and under their own privacy terms. The agreement states that users with public profiles may have their information shared with third-party services when those services' users interact with their content, including through likes or replies, without the Threads user needing to initiate the specific interaction.
Cross-platform context
See how other platforms handle Federated Third-Party Data Transmission and similar clauses.
Compare across platforms →"When you interact with content or people from Third Party Services or otherwise make your content available to Third Party Services, please be aware that you are directing us to deliver your information to services not controlled by Meta as necessary to integrate with the interoperable protocol, so that your information can be stored and processed by the Third Party Services. For example, when you have a follower who is a Third Party User, we will share a copy of your post and your information to this follower's Third Party Service so that it can store, process, and deliver the post to your follower. The information we share with the Third Party Service will depend on your activity, but usually will include your profile information (such as your username, name, profile picture, and bio), and could also include things like the content of the comment, interaction, or post, including any attachments such as photos or videos, and certain metadata associated with your interaction, such as IP address of our Threads server and the timestamp of the interaction. Information sent to Third Party Services is no longer in Meta's control and is subject to the terms and policies of those Third Party Services.Excerpt from Threads's Privacy Policy
(1) REGULATORY LANDSCAPE: This provision engages GDPR (particularly provisions related to controller responsibilities, data transfers, and the right to erasure), CCPA (regarding the scope of data sharing disclosures and consumer rights), and potentially ePrivacy Directive …
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision establishes that data transmitted to third-party federated services exits Meta's data governance perimeter and becomes subject to the terms and policies of those external services. Compliance teams must account for this data flow boundary when conducting data mapping, assessing data subject rights fulfillment, or evaluating cross-border data transfer obligations.
Under this provision, user profile information, post content, photo and video attachments, and interaction metadata are transmitted to third-party federated services that operate outside Meta's control and under their own privacy terms. The agreement states that users with public profiles may have their information shared with third-party services when those services' users interact with their content, including through likes or …
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Threads.