Get the weekly 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. No account.
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 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 →Monitoring
Threads has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 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. EU data protection authorities have addressed the adequacy of binary audience control mechanisms in social media contexts. The FTC is the relevant US enforcement authority. (2) GOVERNANCE EXPOSURE: Low. The provision clearly describes available controls and their operational effects. The limitation is that only two aggregate profile settings are available (private or public), without granular content-level audience controls beyond individual account blocking. (3) JURISDICTION FLAGS: EU/EEA jurisdictions may evaluate whether the binary private/public structure satisfies GDPR's privacy by default principle, which generally requires that default settings be the most privacy-protective option. The policy does not specify the default setting at account creation. (4) CONTRACT AND VENDOR IMPLICATIONS: Organizations deploying Threads for business communications should note that the public profile setting extends content visibility to third-party federated services and other Meta products. Enterprise privacy assessments should account for the audience control limitations described in this provision. (5) COMPLIANCE CONSIDERATIONS: Privacy teams should verify the default profile setting at account creation and assess whether it is consistent with GDPR's privacy by default requirement. User-facing onboarding materials should clearly explain the difference between private and public profiles and the implications of enabling interoperable capabilities.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
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.