Provision record
Meta · Llama API Terms of Service · View original document ↗

User must contact Meta for Privacy Rights requests

Medium severity Explicitdocumentlanguage Common · 295 of 352 platforms
Get alerted the next time Meta changes these terms. Follow Meta →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Meta recorded 18 documented changes in the last 30 days.
Follow Meta →
Monitor governance changes for Meta Monitor emails you the same day this changes. The archive stays free.
Follow Meta →

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.

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

Recent Activity

This document changed recently

Medium Jul 9, 2026

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 →
Medium May 21, 2026

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

Skillshare Medium

You may make a verifiable consumer request related to your personal information twice per 12-month period.

Discord Medium

When you exercise any of your applicable legal rights to access, amend, or delete your personal information, we may request additional information from you for the purpose of confirming your identity.

Anthropic Medium

where the EU GDPR or UK GDPR applies, we will respond within one calendar month of receiving a verifiable request, and where your request is complex...we may extend that period by up to a further two months.

See all platforms with this clause type →

Monitoring

Meta has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.

Follow Meta → Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
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

Applicable regulations

EU AI Act
European Union
BIPA
Illinois, USA
CCPA/CPRA
California, USA
COPPA
United States Federal
Colorado AI Act
US-CO
Connecticut Data Privacy Act Amendments
US-CT
CAN-SPAM
United States Federal
FTC Act Section 5
United States Federal
GDPR
European Union
Indiana Consumer Data Protection Act
US-IN
Kentucky Consumer Data Protection Act
US-KY
TCPA
United States Federal
UK GDPR
United Kingdom
Universal Opt-Out Mechanism Expansion 2026
US
VPPA
United States Federal

Provision details

Document information
Document
Llama API Terms of Service
Entity
Meta
Document last updated
May 11, 2026
Tracking information
First tracked
May 20, 2026
Last verified
May 20, 2026
Record ID
CA-P-060475
Document ID
CA-D-00778
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
f7072746936cd38d60a586cac1eb5e6d0e1d87c7ca1dddf98d6a80c6bb1e16ca
Analysis generated
May 20, 2026 23:34 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Meta
Document: Llama API Terms of Service
Record ID: CA-P-060475
Captured: 2026-05-20 23:34:12 UTC
SHA-256: f7072746936cd38d…
URL: https://conductatlas.com/platform/meta/llama-api-terms-of-service/provision/CA-P-060475/user-must-contact-meta-for-privacy-rights-requests/
Accessed: July 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Related Analysis

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention

Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.

Frequently Asked Questions

What does Meta's User must contact Meta for Privacy Rights requests clause do?

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.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 295 platforms. See the full comparison.

Is ConductAtlas affiliated with Meta?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.