This provision states that Threads collects data about users of third-party federated services who interact with Threads content, including their username, profile picture, the name and IP address of their third-party service, content they share with Threads users, and their interaction activity with Threads content. This collection occurs regardless of whether the third-party user has a Threads account.
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 Threads collects personal data, including IP address-level metadata of third-party service infrastructure, from individuals who are not Threads users but who interact with Threads content via the fediverse. This data collection may engage privacy regulatory frameworks in jurisdictions where those third-party users are located, and may require evaluation regarding lawful basis and notice obligations under GDPR and similar frameworks.
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, individuals who use third-party federated services and interact with Threads content (by following, liking, or replying) have their username, profile picture, third-party service name, server IP address, content, and interaction data collected by Threads, even though they have not created a Threads account. The agreement establishes this collection as a function of the interoperable protocol.
Cross-platform context
See how other platforms handle Third-Party User Data Collection and similar clauses.
Compare across platforms →"We collect information about the Third Party Services and Third Party Users who interact with Threads. If you interact with Threads through a Third Party Service (such as by following Threads users, interacting with Threads content, or by allowing Threads users to search for you, follow you or interact with your content), we collect information about your third-party account and profile (such as your username, profile picture, and the name and IP address of the Third Party Service on which you are registered), your content (such as when you allow Threads users to follow, like, reshare, or have mentions in your posts), and your interactions (such as when you follow, like, reshare, or have mentions in Threads posts).Excerpt from Threads's Privacy Policy
(1) REGULATORY LANDSCAPE: This provision engages GDPR's requirements for a lawful basis for processing, transparency obligations, and the rights of data subjects who are not Threads account holders.
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 Threads collects personal data, including IP address-level metadata of third-party service infrastructure, from individuals who are not Threads users but who interact with Threads content via the fediverse. This data collection may engage privacy regulatory frameworks in jurisdictions where those third-party users are located, and may require evaluation regarding lawful basis and notice obligations under GDPR …
Under this provision, individuals who use third-party federated services and interact with Threads content (by following, liking, or replying) have their username, profile picture, third-party service name, server IP address, content, and interaction data collected by Threads, even though they have not created a Threads account. The agreement establishes this collection as a function of the interoperable protocol.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Threads.