Developers are prohibited from using data obtained through Meta's APIs to make decisions about people's access to housing, jobs, credit, education, or insurance.
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 clause establishes operational boundaries on permissible data uses by restricting application of Platform Data to consequential eligibility determinations. This provision defines categories of prohibited use cases that carry significant downstream effects on individuals' access to financial services, employment, housing, and educational opportunities.
End users on Meta's platforms benefit from this restriction because it prohibits developers from using their profile data, social connections, or activity to determine whether they qualify for loans, jobs, housing, or insurance, which are decisions with major life consequences.
How other platforms handle this
You may not use our Services for any illegal purpose or in violation of any laws or regulations. You may not use the Services to send money to sanctioned countries or individuals on government watchlists. You may not use the Services for gambling, illegal drugs, weapons, or any other prohibited acti...
Customer will not, and will not permit any third party to: (a) copy, modify, or create derivative works based on the Services; (b) reverse engineer, disassemble, decompile, decode, adapt, or otherwise attempt to derive or gain access to any software component of the Services; (c) rent, sell, resell,...
You agree not to post, upload, publish, submit or transmit any content that: (i) infringes, misappropriates or violates a third party's patent, copyright, trademark, trade secret, moral rights or other intellectual property rights, or rights of publicity or privacy; (ii) violates, or encourages any ...
Monitoring
Meta has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"You must not use Platform Data to discriminate against or harm people. You must not use Platform Data to make eligibility determinations about people, including housing, employment, credit, education, or insurance.— Excerpt from Meta's Meta Platform Policy
(1) REGULATORY LANDSCAPE: This provision engages the Equal Credit Opportunity Act, Fair Housing Act, and Title VII of the Civil Rights Act in the US context, as well as GDPR Article 22 provisions on automated decision-making in EU/EEA jurisdictions. The FTC and the Consumer Financial Protection Bureau share jurisdiction over discriminatory uses of data in financial and credit contexts. The Department of Housing and Urban Development has authority over discriminatory housing practices. (2) GOVERNANCE EXPOSURE: High for developers in fintech, insurtech, HR technology, and real estate technology sectors. The prohibition on eligibility determinations is broad and may affect developers who use behavioral or social data as indirect inputs to scoring or ranking systems, even where Meta data is not the primary input. (3) JURISDICTION FLAGS: EU/EEA developers face additional obligations under GDPR Article 22, which restricts automated decision-making with legal or similarly significant effects regardless of contractual terms. Illinois, California, and New York have state-level protections against discriminatory uses of personal data that may independently apply. Developers serving financially underserved populations face heightened regulatory scrutiny. (4) CONTRACT AND VENDOR IMPLICATIONS: Developers should audit any algorithmic systems that ingest Meta platform data to confirm eligibility determination use cases are excluded. Vendor and partner agreements that involve Meta platform data should expressly prohibit downstream eligibility determination uses. This provision should be surfaced during due diligence for any acquisition of a company with Meta API integrations. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should conduct a use-case audit of all Meta platform data flows to identify any applications that could be characterized as eligibility determinations. Algorithmic fairness assessments may be warranted for any system that processes Meta data alongside decision-making outputs. Legal counsel should advise on whether any current products fall within prohibited categories.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
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.
The clause establishes operational boundaries on permissible data uses by restricting application of Platform Data to consequential eligibility determinations. This provision defines categories of prohibited use cases that carry significant downstream effects on individuals' access to financial services, employment, housing, and educational opportunities.
End users on Meta's platforms benefit from this restriction because it prohibits developers from using their profile data, social connections, or activity to determine whether they qualify for loans, jobs, housing, or insurance, which are decisions with major life consequences.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.