The terms prohibit developers from using platform-sourced data to make decisions about or to target users based on sensitive personal characteristics including health status, financial information, race, ethnicity, political or religious beliefs, sexual orientation or gender identity, or union membership.
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
This provision establishes categorical prohibitions on specific uses of platform data that intersect with anti-discrimination law and data protection frameworks governing special categories of personal data, creating compliance obligations for any developer whose application processes or could infer such attributes from platform data.
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 →This new provision prohibits discriminatory uses of platform data across protected categories, addressing algorithmic bias and civil rights concerns in AI/ML applications.
View full change record →Under this clause, developers are prohibited from using data obtained through Meta's platform to make decisions about or target users based on health, financial status, race, ethnicity, political or religious beliefs, sexual orientation, gender identity, or union membership, regardless of whether such data was explicitly provided by the user or inferred.
How other platforms handle this
to request that your data be transferred to a third party (data portability)
Your organization may allow you to access and export your data in order to back it up or transfer it to a service outside of Google.
Further, you may take legal actions in relation to any potential breach of your rights regarding the processing of your Personal Information, as well as to lodge complaints before the competent data prot...
"Don't use Platform Data to make decisions about the following sensitive categories or use Platform Data to target people based on sensitive categories including health, financial information, race, ethnicity, political or religious beliefs, sexual orientation or gender identity, or union membership.Excerpt from Meta's Llama API Terms of Service
1.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
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.
This provision establishes categorical prohibitions on specific uses of platform data that intersect with anti-discrimination law and data protection frameworks governing special categories of personal data, creating compliance obligations for any developer whose application processes or could infer such attributes from platform data.
Under this clause, developers are prohibited from using data obtained through Meta's platform to make decisions about or target users based on health, financial status, race, ethnicity, political or religious beliefs, sexual orientation, gender identity, or union membership, regardless of whether such data was explicitly provided by the user or inferred.
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.