This analysis describes what Meta'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
The updated terms establish new obligations for developers integrating Meta's AI models into their products. The agreement now requires developers to comply with applicable AI labeling, disclosure, provenance-marking, and system classification requirements under applicable law, with responsibility falling on the developer to implement these disclosures to end users. The expanded definition of Inputs now explicitly includes code, libraries, databases, and any content accessed through connectors or integrations, which may broaden what user-submitted content Meta claims the right to process for safety and security purposes.
View change record →The updated terms remove developer restrictions that previously applied to large-scale platforms, meaning companies with more than 700 million monthly active users can now access Meta's AI models without special permission. The terms also eliminate the restriction on EU developers accessing multimodal models and consolidate account management under either managed accounts or Meta accounts. Developers previously subject to these restrictions should review whether the updated terms now permit their use case.
View change record →The updated terms authorize Meta to retain user-submitted content if its systems flag the content for a potential policy violation, in addition to retention tied to legal compliance and contractual rights. This expands the circumstances under which content may be preserved without explicit time limits. Under the revised language, content retention decisions may now be driven by automated policy-violation flagging in addition to legal or contractual necessity. Developers integrating the Llama API should understand that flagged content may be retained indefinitely pending policy review.
View change record →How other platforms handle this
When you use them, we'll validate your request by verifying your identity (for example, by confirming that you're signed in to your Google Account).
If you are an end user in a Workspace not owned by you and wish to update, delete, or receive any information we have about you, you may do so by contacting the organization who owns your ClickUp Workspace.
You may contact our privacy team with any requests of disclosure, correction, or deletion of your personal information. You may also request suspension of use or suspension of sharing of your personal information with certain third parties.
"To the extent that you wish to inform Meta of any Privacy Rights requests individuals make to you pursuant to Applicable Law...you will provide the information necessary for Meta to assist with such compliance and contact Meta through your Accounts.Excerpt from Meta's Llama API Terms of Service
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
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.
The clause states: “To the extent that you wish to inform Meta of any Privacy Rights requests individuals make to you pursuant to Applicable Law...you will provide the information necessary for Meta to assist with such compliance and contact Meta through your Accounts.”
ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.