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 states that username, name, profile picture, and bio are always public on Threads regardless of whether the user has set their profile to private or public, and are accessible to anyone on or off Meta Products. Post content visibility is configurable via private or public profile settings, but the four enumerated profile fields are not subject to audience restriction.
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 four categories of user data (username, name, profile picture, bio) are permanently public and not subject to the audience controls available for other content. Compliance teams assessing user data minimization or privacy-by-default configurations should note that these fields cannot be restricted regardless of profile setting.
The agreement establishes that username, name, profile picture, and bio are always publicly accessible to anyone, including off-platform and on third-party federated services, and that this is not affected by setting a private profile. Under these terms, users who set a private profile retain control over post content visibility but not over the four enumerated profile data categories.
Cross-platform context
See how other platforms handle Public Profile Data Always Public 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.
"Some of your information on Threads is always public and available to anyone, on or off Meta Products, including your username, name, profile picture, and bio. For content you share, you can set the audience by choosing between a private or public profile. 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. Keep in mind that whether your profile is private or public, your username, name, profile picture, and bio remain public.Excerpt from Threads's Privacy Policy
(1) REGULATORY LANDSCAPE: This provision engages GDPR principles of data minimization and privacy by default, as well as CCPA transparency requirements. EU data protection authorities and the California Privacy Protection Agency are the relevant enforcement bodies. The designation of specific data categories as permanently public regardless of user preference may require evaluation under GDPR's requirement that data processing have a lawful basis and that users have meaningful control over their personal data. (2) GOVERNANCE EXPOSURE: Medium. The provision is clearly disclosed and the data categories are enumerated. However, for users who are minors or who operate in jurisdictions with heightened privacy protections, the permanent public status of these fields without a configurable control may warrant additional review. (3) JURISDICTION FLAGS: EU/EEA users may wish to evaluate whether the permanent public designation of profile fields is consistent with GDPR data minimization and purpose limitation principles. California residents may evaluate this under CCPA. The interaction with federated third-party services means these fields are transmitted beyond Meta's infrastructure. (4) CONTRACT AND VENDOR IMPLICATIONS: Organizations deploying Threads for business communications should note that employee or representative usernames, names, and profile pictures will be permanently public and transmissible to third-party federated services regardless of profile privacy settings. (5) COMPLIANCE CONSIDERATIONS: Privacy teams should ensure that user-facing disclosures clearly communicate the permanent public status of these four profile fields at the point of account creation. Teams supporting GDPR compliance should assess whether the absence of a restriction option for these fields is documented in their data processing records.
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 that four categories of user data (username, name, profile picture, bio) are permanently public and not subject to the audience controls available for other content. Compliance teams assessing user data minimization or privacy-by-default configurations should note that these fields cannot be restricted regardless of profile setting.
The agreement establishes that username, name, profile picture, and bio are always publicly accessible to anyone, including off-platform and on third-party federated services, and that this is not affected by setting a private profile. Under these terms, users who set a private profile retain control over post content visibility but not over the four enumerated profile data categories.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Threads.