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.
The policy requires that developers delete user data obtained through the Facebook platform upon user request, and establishes that developers must provide a mechanism for users to request such deletion.
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 a contractual obligation on developers to honor user deletion requests for platform-sourced data, creating an operational dependency between developer data retention practices and Meta's platform eligibility requirements.
Interpretive note: The document fragment provided was substantially truncated and consisted largely of CSS styling code; specific clause text could not be directly extracted, so this provision is characterized based on Meta's publicly known Platform Policy structure.
The updated policy removes explicit disclosure that interactions with Meta AI are used to improve Meta's AI systems. The policy previously stated this practice directly; the revised language no longer includes this statement. Under the updated terms, users accessing the policy will see consolidated references to Meta Terms, AI terms, and Privacy Policy rather than separate Meta AI-specific terms, though the Privacy Policy may contain related disclosures about AI training and data use. You can review Meta's Privacy Policy directly to understand how interaction data may be used for AI improvement purposes.
View change record →Under this provision, users whose data has been accessed by third-party Facebook-connected applications have a basis to request deletion of that data from the developer, and the developer's continued platform access depends on honoring such requests.
How other platforms handle this
If you wish to access, review, or make any changes to Personal Data you have provided to us through the Services, please submit a request through our Online Form, or email us at help@skillshare.com...
If you want to see what information we have collected about you, you can request a copy of your data in the Data & Privacy section of your User Settings. You should receive your data packet within 30 days.
If you choose to reveal any personal information about yourself to other users, you do so at your own risk. We strongly encourage you to use caution in disclosing any personal information online.
Monitoring
Meta has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
(1) REGULATORY LANDSCAPE: This provision engages with GDPR Article 17 (right to erasure), CCPA deletion request requirements, and FTC Act principles on unfair data retention practices. Enforcement authorities include EU Data Protection Authorities, the California Privacy Protection Agency, and the FTC. Where developer obligations under this clause may not meet the specificity required for a valid GDPR erasure mechanism, compliance teams should evaluate whether supplementary contractual terms are needed. (2) GOVERNANCE EXPOSURE: Medium. The provision creates a conditional deletion obligation for developers, but the specific timeline, verification mechanism, and scope of covered data are not determinable from the truncated document fragment, creating uncertainty in operationalizing compliance. (3) JURISDICTION FLAGS: EU/EEA developers and those serving California residents face heightened exposure, as GDPR and CCPA both establish enforceable deletion rights that this provision must align with. Developers operating in Illinois, New York, or other states with comprehensive privacy laws should evaluate local deletion right requirements. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and vendor teams should confirm that developer agreements with sub-processors include back-to-back deletion obligations consistent with this clause. The provision may shift liability for deletion failures to the developer rather than Meta, which should be evaluated in vendor contract reviews. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should audit existing deletion request workflows for Facebook-sourced data, confirm that technical mechanisms exist to identify and delete platform data by user, and document the process for responding to deletion requests within applicable legal timeframes. The absence of a specific timeline in the available document text means teams should default to GDPR's one-month standard where applicable.
Regulatory citations, enforcement risk, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
This provision establishes a contractual obligation on developers to honor user deletion requests for platform-sourced data, creating an operational dependency between developer data retention practices and Meta's platform eligibility requirements.
Under this provision, users whose data has been accessed by third-party Facebook-connected applications have a basis to request deletion of that data from the developer, and the developer's continued platform access depends on honoring such requests.
ConductAtlas has identified this type of provision across 295 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.