Developers cannot merge or supplement data they receive from Meta's APIs with data from other sources unless they have Meta's written permission to do so.
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 operates to control how Platform Data may be processed and integrated downstream. It establishes a consent requirement as a procedural gate for data combination activities, thereby reserving Meta's authority to approve or deny specific data linkage requests.
This provision restricts developers from combining users' Meta platform data with data from other sources without Meta's permission, which limits certain data enrichment practices that could otherwise create more comprehensive user profiles without users' knowledge.
How other platforms handle this
Please note that we do not knowingly sell the personal information of minors under 16 years of age without legally-required affirmative authorization. Please note that we do not knowingly sell the personal information of minors under 16 years of age.
Don't claim to be human when directly and sincerely asked, use AI to deceive people about its fundamental nature, or impersonate real people or organizations in misleading ways.
You may not use Runway's tools to build or support systems designed for mass surveillance, tracking of individuals without their consent, or the unlawful monitoring of protected groups or activities.
Monitoring
Meta has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"You will not combine or supplement information you receive from us, including Platform Data, with other data from other sources without our prior written consent.— Excerpt from Meta's Meta Platform Policy
REGULATORY LANDSCAPE: This restriction aligns with GDPR data minimization and purpose limitation principles, which restrict processing personal data beyond its original purpose. The CCPA's provisions on data sharing and the concept of combining datasets to enable identification or profiling are also relevant. The FTC has scrutinized data combination practices in the context of consumer protection enforcement. GOVERNANCE EXPOSURE: High for developers operating data analytics, identity verification, or audience targeting businesses, where combining Meta platform data with CRM or third-party data is a common operational practice. Developers in these sectors must obtain explicit written consent from Meta before implementing such data combinations. JURISDICTION FLAGS: EU/EEA developers face dual obligations: compliance with this contractual restriction and compliance with GDPR's requirements that any data combination be based on a valid legal basis and that users be informed. The combination of these requirements creates a high compliance burden in EU markets. CONTRACT AND VENDOR IMPLICATIONS: Developers who use third-party data management platforms, customer data platforms, or identity resolution services should audit whether their use of those services involves combining Meta platform data with other data sources, as such combinations may violate this provision without prior written consent. COMPLIANCE CONSIDERATIONS: Compliance teams should map all data flows involving Meta platform data and identify any points where that data is joined, merged, or enriched with other data sources. Written consent from Meta should be obtained before implementing any such integrations, and documentation of consent should be maintained.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional 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 operates to control how Platform Data may be processed and integrated downstream. It establishes a consent requirement as a procedural gate for data combination activities, thereby reserving Meta's authority to approve or deny specific data linkage requests.
This provision restricts developers from combining users' Meta platform data with data from other sources without Meta's permission, which limits certain data enrichment practices that could otherwise create more comprehensive user profiles without users' knowledge.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.