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 states that Meta retains user data for as long as necessary to provide services, meet legal obligations, or fulfill stated legitimate purposes including safety and security, without specifying fixed retention periods for most data categories.
This analysis describes what Threads'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 that data retention timelines are determined by Meta based on operational and legal necessity criteria rather than fixed periods disclosed to users, which has implications for the operability of deletion requests and data minimization compliance under GDPR and CCPA/CPRA.
Interpretive note: The policy does not specify retention periods for individual data categories, making it difficult to assess the full operational scope of this provision without additional Meta documentation.
Under this clause, personal data collected on Threads may be retained for indeterminate periods based on Meta's assessment of service needs, legal obligations, and safety purposes. Users may submit deletion requests, but the policy's retention language means certain data may be preserved after a deletion request based on the criteria described.
How other platforms handle this
In certain circumstances, the right to data portability, which means that you can request that we provide certain Personal Data we hold about you in a machine-readable format
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.
For data portability requests, We will select a format to provide Your personal information that is readily useable and should allow You to transmit the information from one entity to another entity without hindrance.
Monitoring
Threads has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"We keep information for as long as we need it to provide our products, comply with legal obligations, or for other legitimate purposes, such as to maintain safety, security, and integrity.Excerpt from Threads's Privacy Policy
1. REGULATORY LANDSCAPE: GDPR Article 5(1)(e) requires that personal data be kept in a form that permits identification for no longer than is necessary for the specified purpose (storage limitation principle). Vague retention language that relies on open-ended operational and legal necessity criteria may create tension with this principle and has been the subject of regulatory scrutiny in the EU. CCPA/CPRA requires disclosure of retention periods or the criteria used to determine them. 2. GOVERNANCE EXPOSURE: Medium. The absence of specific retention period disclosures for individual data categories is a noted gap in many large platform privacy policies and has been flagged by EU supervisory authorities. For organizations that rely on Meta platform data in their own data processing activities, this ambiguity complicates their own retention schedule alignment. 3. JURISDICTION FLAGS: EU/EEA supervisory authorities apply the storage limitation principle strictly, and data protection impact assessments for Threads-related processing should account for indefinite retention risk. California's CPRA requires disclosure of retention periods or the criteria used to determine them, and the absence of specific periods may attract CPPA scrutiny. 4. CONTRACT AND VENDOR IMPLICATIONS: Where Meta acts as a service provider or processor, its retention practices should be assessed against the data processing agreements in place. If Meta retains data beyond the period permitted by the service provider agreement, this may affect the classification of the relationship. 5. COMPLIANCE CONSIDERATIONS: Legal teams should document how Meta's retention practices interact with their own data lifecycle management and deletion obligations. Deletion request workflows should be tested to confirm that requests submitted via Meta's portal result in deletion consistent with the policy's stated criteria.
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 that data retention timelines are determined by Meta based on operational and legal necessity criteria rather than fixed periods disclosed to users, which has implications for the operability of deletion requests and data minimization compliance under GDPR and CCPA/CPRA.
Under this clause, personal data collected on Threads may be retained for indeterminate periods based on Meta's assessment of service needs, legal obligations, and safety purposes. Users may submit deletion requests, but the policy's retention language means certain data may be preserved after a deletion request based on the criteria described.
ConductAtlas has identified this type of provision across 294 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Threads.