This provision describes the audience control mechanisms available to Threads users: a binary private or public profile setting, and the ability to block individual accounts. A private profile limits content visibility to approved followers, while a public profile makes content visible to anyone including third-party federated services and other Meta products. Blocking individual accounts provides an additional restriction layer.
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 the operational scope of Threads' audience control tools, which determine the reach of user content to third-party federated services and other Meta products. The provision conditions fediverse content sharing on whether the user has enabled interoperable capabilities, providing a discrete control point for federated distribution.
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 →The agreement establishes two primary audience control settings (private and public profile) and an individual account blocking mechanism. Under these terms, users with a public profile who have enabled interoperable capabilities will have their content shared with third-party federated services; disabling interoperable capabilities or setting a private profile limits this distribution pathway.
Cross-platform context
See how other platforms handle Profile and Content Audience Controls and similar clauses.
Compare across platforms →"For content you share, you can set the audience by choosing between a private or public profile. With a private profile, only followers you approve can see and interact with the content you share. With a public profile, anyone on or off Threads can see and interact with the content you share, including on Third Party Services (if you enable interoperable capabilities; see below) and on other Meta Products like Facebook and Instagram. You can also restrict the audience for your content by blocking individual accounts from viewing them.Excerpt from Threads's Privacy Policy
(1) REGULATORY LANDSCAPE: This provision engages GDPR's privacy by design and default requirements, as well as CCPA's requirement for accessible privacy controls.
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 the operational scope of Threads' audience control tools, which determine the reach of user content to third-party federated services and other Meta products. The provision conditions fediverse content sharing on whether the user has enabled interoperable capabilities, providing a discrete control point for federated distribution.
The agreement establishes two primary audience control settings (private and public profile) and an individual account blocking mechanism. Under these terms, users with a public profile who have enabled interoperable capabilities will have their content shared with third-party federated services; disabling interoperable capabilities or setting a private profile limits this distribution pathway.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Threads.