Live feed · updated daily
Recent policy changes
3052 policy changes
detected across 352 platforms. Most platforms don't announce policy changes — these updates were detected automatically.
June 2, 2026
Updated numerical reference in Terms of Service from $2,001.35 to $1,906.77; operational context unclear
Why it matters: Without understanding what amount this figure represents or how it applies to OpenSea's services, the operational significance of this numerical change cannot be determined. Clarification is needed to assess whether this affects fees, transaction thresholds, account balances, or other material terms.
Updated Privacy Policy effective date to June 2, 2026.
Why it matters: This change updates the formal effective date of the Privacy Policy to June 2, 2026. No substantive privacy rights, data practices, or operational obligations have been modified.
Privacy Policy effective date updated to June 2, 2026
Why it matters: The updated effective date reflects when the revised policy takes force. This is an administrative clarification rather than a substantive policy change. Organizations should note the effective date for compliance tracking purposes, but no material changes to privacy practices or user obligations are indicated by this modification.
Rewrote app marketing language describing purchasing power, card, extension, and digital wallet features; removed 'Terms apply' disclaimer.
Why it matters: This change is a routine update to marketing copy and policy document formatting with no operational impact on Affirm's data practices, user rights, or privacy obligations. The removal of boilerplate text is a stylistic revision that does not alter the scope or enforceability of Affirm's actual terms and conditions.
Replaces California-specific privacy reference with unified US regional privacy notice page
Why it matters: The updated terms consolidate privacy notice navigation into a single US regional page, simplifying how users across US jurisdictions can access and exercise privacy rights. This organizational change affects how privacy information is discovered and accessed, though it does not modify substantive privacy rights or data handling practices.
Stay ahead of the changes
You're seeing a fraction of what's changing
ConductAtlas monitors every tracked platform and captures every policy update.
Updated Meta AI Labeling Policy navigation labels to UK English conventions (Help Centre, ad choices, policies)
Why it matters: This change affects how users navigate Meta's support documentation by updating terminology to UK English conventions. The revised language standardizes regional naming conventions in the interface, but does not alter any underlying policy provisions, data practices, or rights.
Added Licensed Materials licensing terms for locally installed software and ChatGPT Sites website creation feature with separate terms reference.
Why it matters: The updated terms establish binding license restrictions for organizations deploying OpenAI's downloadable software components, including prohibitions on modification, redistribution, and sublicensing, and mandate permanent deletion upon service termination. The introduction of ChatGPT Sites creates a new reference to separately published terms, requiring organizations to audit both document sets if offering website creation capabilities. These changes formalize the licensing framework for locally installed materials and introduce new operational governance requirements for customers using downloadable components or the ChatGPT Sites feature.
Removes detailed personal data recipient table, directs users to other policy sections instead
Why it matters: The updated policy consolidates transparency disclosures from a detailed, accessible table into cross-references to other sections. This change reduces the granularity of upfront data-sharing disclosure, potentially affecting how users and organizations understand which parties receive personal information. Depending on regulatory interpretation and jurisdiction, this reduction in accessible transparency may create compliance questions around CCPA, GDPR, and FTC Act standards requiring specific, clear disclosure of data recipients.
Navigation and footer links updated in Kindle Store Terms of Use.
Why it matters: This change does not materially alter the Kindle Store Terms of Use. The modifications are limited to website navigation and footer structure, reflecting current Amazon product categories and merchandise offerings. No substantive changes to consumer rights, obligations, or commercial terms are present.
Added explicit statement linking Threads service use to Meta's AI terms in Terms of Use
Why it matters: The updated terms make explicit that Threads service use includes agreement to Meta's AI terms. This clarification improves transparency about the governing terms but does not appear to establish new restrictions or authorities.
Added footer navigation links to Zillow Terms of Use footer.
Why it matters: This change has no operational significance to the terms governing user rights or obligations. The footer update adds navigation convenience but makes no changes to the substantive legal agreement.
Removes 'Do Not Sell or Share My Personal Information' link from privacy policy footer; opt-out access may require alternate navigation.
Why it matters: The removal of the footer link affects how users can access CCPA opt-out controls from the privacy policy itself. Under the CCPA, companies must make opt-out mechanisms easy to find. The removal of this direct link from the policy footer may create compliance questions unless the opt-out control is prominently linked elsewhere on the site.
Removed 'Do Not Sell or Share My Personal Information' link from Terms footer, reducing direct access to this CCPA-related disclosure.
Why it matters: The 'Do Not Sell or Share My Personal Information' link is typically the primary user-facing pathway to a CCPA-mandated disclosure and opt-out mechanism. Removing this link from the main terms footer may reduce discoverability of the disclosure, which could affect Ancestry's compliance with CCPA requirements for conspicuous access to opt-out rights.
Adds minor data collection disclosure for beneficiaries and AI feature training authorization with non-advice disclaimer.
Why it matters: The updated policy establishes explicit authorization for two practices previously described in narrower or negative terms: collection of minor beneficiary information and use of client data for AI training. This clarification affects how clients should understand what data Wealthfront processes and how it may be used, and creates materiality for compliance teams assessing whether vendor data practices align with their own privacy policies and regulatory obligations. The AI output disclaimer is operationally significant because it establishes that AI-generated recommendations should not be treated as investment advice, which affects how financial advisors and clients may use such outputs.
Expanded cookie tracking disclosure and restructured consent interface to require affirmative opt-in for performance and targeting cookies
Why it matters: The updated privacy notice establishes clearer disclosure of third-party advertising and analytics data sharing and restructures the consent mechanism to require affirmative selection for optional cookies. This shifts the operational model from assumed consent to explicit choice, affecting how user tracking data flows to external partners and creating a new procedural requirement for users to actively configure their tracking preferences.
Formatting updates to Legal Hub navigation and footer links. No substantive policy changes detected.
Why it matters: This change has no material operational significance. The modifications are technical adjustments to how the Legal Hub and footer navigation are displayed on the Terms of Service page, not changes to substantive binding terms or user obligations.
Updated help navigation phrasing in Meta AI Labeling Policy
Why it matters: This change does not materially affect Meta's AI Labeling Policy substance or user obligations. It represents a help center navigation update only, with no new operational implications for policy compliance or user rights.
Adds VeraSafe dispute resolution process for DPF complaints and Right to Restriction for processing limits.
Why it matters: The updated policy establishes a concrete, third-party mechanism for resolving Data Privacy Framework complaints that were previously unresolved through internal processes, providing users an escalation path that is transparent and free. The introduction of an explicit Right to Restriction also operationalizes a user control that strengthens personal data governance, particularly for sensitive information.
Extended seller payment withholding from 30 to 60 days for non-compliance in EU/UK Terms of Service
Why it matters: The updated terms extend Whatnot's authority to withhold seller payments by 100 percent, from a maximum of 30 days to 60 days during compliance disputes. For sellers dependent on regular payment cycles, this doubles the potential cash flow disruption window and may affect financial planning, working capital, and operational continuity. The longer withholding period is material for high-volume sellers and may warrant review under EU unfair contract terms law depending on how the provision is applied.
Extended payment withholding period from 30 to 60 days for non-compliant sellers in EU/UK terms
Why it matters: The updated terms establish a doubled enforcement window during which sellers cannot access withheld payments when they violate platform rules. This extends the period sellers must manage without access to transaction proceeds, affecting working capital and liquidity planning for sellers operating in the EU and UK.
Added disclosures for Microsoft Advertising, OpenAI, and LINE Yahoo as advertising tracking platforms in privacy notice.
Why it matters: The updated privacy notice clarifies which advertising platforms Amplitude uses to measure conversions and website visits from paid advertisements. Users can now review the privacy practices of Microsoft Advertising, OpenAI, and LINE Yahoo by following the links provided in the updated policy.
Technical build timestamp updated on privacy policy page; no policy language changes detected.
Why it matters: This change does not materially affect how Postman's privacy policy operates or what terms users operate under. The detected modification is limited to technical build metadata and does not introduce new privacy practices, data collection authorities, or user obligations.
Expanded fee accrual period definition to include Google Workspace Services alongside GCP Services for threshold-based billing.
Why it matters: The updated terms clarify that spend thresholds now trigger billing accrual periods for Google Workspace Services in the same manner as Google Cloud Platform Services. This affects how billing cycles are calculated and may impact cost forecasting and renewal timelines for customers using both product lines.
Added 30-day retention period for abuse detection; clarified review process for child safety reports.
Why it matters: The updated terms establish explicit operational practices for how AWS Bedrock processes and retains service data for safety purposes. The 30-day retention window is now formally documented, which clarifies data handling practices for organizations that must disclose retention periods in their own customer agreements or privacy policies. The two-step CSAM reporting process (review before reporting) reflects a procedural refinement that may affect how organizations communicate about safety practices to their own customers.
Adds AI autonomy liability framework requiring users to configure settings, monitor output, and accept legal responsibility for AI-driven actions and third-party tool costs.
Why it matters: The updated terms establish a new contractual liability framework for autonomous AI actions. Users are now legally bound by AI-driven actions taken according to their configured settings and must actively manage safeguards, monitor settings, and evaluate output. This creates operational and compliance obligations that require developers to implement approval workflows, cost controls, and human oversight before deploying AI features or third-party integrations. The liability disclaimer for AI-driven consequences shifts risk entirely to users and may create conflicts with downstream customer agreements or regulatory frameworks.
Repository metadata updated; underlying MIT License remains substantively identical.
Why it matters: This change does not create operational significance. The detected modification is repository metadata only; the MIT License governing DeepSeek-R1 model permissions, restrictions, and usage rights remains substantively identical.
Minor timestamp adjustment in Terms of Service footer; no substantive policy changes detected.
Why it matters: This change has no material operational significance. The detected modification is limited to a timestamp display adjustment in the document footer, not a change to substantive policy language, user rights, or obligations.
Timestamp updated in privacy policy from 10:49 PM to 5:44 PM; operational context unclear.
Why it matters: This change is a timestamp correction within the privacy policy document. Without knowing what this timestamp represents, marks, or governs, its operational significance is unclear. If this timestamp denotes an effective date, enforcement deadline, or triggers specific compliance obligations, clarification is needed.
Updated promotional messaging within Terms and Conditions header; no material changes to binding contractual terms.
Why it matters: While the change is minor, monitoring promotional messaging within binding terms documents can identify when platforms reorganize how they present feature announcements or event registrations. This specific change does not alter contractual obligations or user rights but reflects DeepL's current product focus on voice transcription features.
Updated promotional banner text in privacy policy header; no substantive privacy term changes.
Why it matters: This change does not materially affect the substantive privacy protections or data handling practices described in DeepL's Privacy Policy. The update is limited to promotional messaging in the policy header and carries no operational implications for data collection, processing, retention, or user rights.
Updated daily. New changes added as detected.