Live feed · updated daily
Recent policy changes
3559 policy changes
detected across 352 platforms. Most platforms don't announce policy changes — these updates were detected automatically.
June 21, 2026
Clarifies GLM 5.2 Serverless availability with per-token pricing model and Opus-level capability positioning.
Why it matters: The updated language clarifies Fireworks AI's Serverless pricing model as pay-per-token and emphasizes the capability level of the GLM 5.2 model. This helps users understand the cost structure and service offering more explicitly, though it does not modify substantive contractual terms, obligations, or rights.
Privacy policy header updated with revised product messaging and pricing language; no substantive privacy obligations modified.
Why it matters: The updated privacy policy header clarifies product availability and pricing details for transparency, but the change is limited to editorial and marketing language. No substantive modifications to privacy protections, data handling procedures, or user rights appear to have occurred.
Grammar correction in tagline; no operational or policy changes to terms of service.
Why it matters: This change does not materially affect Synthesia's terms of service or the operational rights and obligations they establish. It is a grammatical correction to a marketing description and carries no substantive policy implications.
Wording clarification in policy opening statement; no substantive privacy terms changed
Why it matters: This change does not alter any substantive privacy terms or operational policies. The updated language is a minor rewording of a descriptive headline and has no practical impact on data collection, use, disclosure, or user rights.
Timestamp updated in Terms of Service (routine metadata change, no operational impact).
Why it matters: This change does not materially affect operational significance. The timestamp update is a routine metadata modification with no impact on platform policies, user rights, or compliance frameworks.
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 timestamp in Privacy Policy from 9:25 PM to 5:45 PM in company location reference.
Why it matters: The practical significance of this timestamp change cannot be determined from the available context. If this reference relates to service availability, data processing windows, or compliance timelines, it may warrant further review.
Clarifies data controller structure across 7 legal entities in 6 jurisdictions; discloses ID and organization name sharing via ChatGPT/Claude/Cursor integrations.
Why it matters: The updated policy clarifies that DeepL operates as a multi-entity group with data controllers in multiple jurisdictions, and explicitly discloses that data flows occur when DeepL is accessed through third-party AI tools. Organizations using DeepL, particularly through integrations, may need to update their own data processing agreements and privacy disclosures to account for these arrangements.
Copyright year updated to 2026 in privacy policy footer.
Why it matters: This change has no operational significance. The copyright year update is a routine administrative change that does not affect privacy terms, data practices, or consumer rights.
Updated copyright year from 2025 to 2026 in Terms of Use footer.
Why it matters: This change has no operational significance. It is a routine annual copyright year update that does not modify any substantive terms, user rights, obligations, or policy provisions.
Updated Terms of Service timestamp metadata; no substantive policy changes.
Why it matters: This change updates only the document's publication timestamp and carries no operational significance for users or compliance teams. The substantive terms governing the Uniswap platform remain unchanged.
Removed contact information and footer navigation from terms document; no substantive policy changes.
Why it matters: This change does not materially affect the substantive terms under which users operate. The removal of footer contact information and navigation is a presentation change, not a modification to service obligations, rights, or dispute resolution procedures.
Privacy policy page infrastructure updated; actual policy language changes not available in data provided.
Why it matters: Target's privacy policy was updated on June 21, 2026, but the substantive policy language changes are not visible in the provided data. Any changes to how Target collects, uses, shares, or protects customer data would have operational significance, but cannot be assessed without access to the actual policy text modifications.
Technical update to Target Terms and Conditions; substantive policy language unchanged.
Why it matters: The detected changes are technical updates to page structure and metadata rather than substantive policy modifications. No material changes to Target's contractual obligations, consumer protections, or user rights were identified in the available diff context.
Added reporting period to SOC 3 certification reference in GitHub Copilot Business Privacy Statement.
Why it matters: The updated statement now specifies the exact audit reporting period for the SOC 3 certification, allowing users and customers to locate and review the correct audit document. This improves clarity of compliance documentation without changing any underlying security practices or policies.
Single sentence modification detected in privacy policy; numerical value changed but operational impact unclear from available diff context.
Why it matters: The operational significance of this change cannot be determined from the provided diff context. The numerical adjustment may reflect a fee schedule update, pricing disclosure, or other cost-related modification, but without the complete sentence text and its operational context, the practical implications for users or business partners remain unclear.
Adjusted pricing reference from $1,711.45 to $1,740.92 in Terms of Service.
Why it matters: OpenSea modified a numerical reference in its Terms of Service, representing a 1.7% adjustment to a value of unclear operational purpose. Without context, the materiality cannot be assessed, but if this value governs transaction fees, payment thresholds, or service tiers, the change may affect user costs or account eligibility.
Website infrastructure updated with session tokens and JS bundles; no Privacy Policy changes detected.
Why it matters: The provided diff does not show substantive Privacy Policy changes, only website infrastructure updates. If material policy changes occurred, they are not evident from the code-level infrastructure tokens and JavaScript bundle hashes included in the diff context.
Updated metering notification language for usage limit alerts; no change to underlying usage policies.
Why it matters: The updated language clarifies how Character.AI communicates usage limit information to users, but does not alter the policies, restrictions, or terms governing account usage. This is a presentational rather than substantive change.
Updated privacy policy with minimal substantive changes; primarily technical and formatting adjustments.
Why it matters: The detected changes to Character.AI's privacy policy consist primarily of technical updates to the HTML page rendering and JavaScript bundle identifiers. The substantive policy content changes (1 sentence added, 3 modified) are not visible in the provided diff, so their operational significance cannot be assessed without reviewing the actual policy text.
Localization update: Help Center interface standardized to American English conventions; no substantive policy changes.
Why it matters: This change has minimal operational significance. It standardizes the Help Center user interface from British English to American English conventions and updates navigation labels. No policy substance, user rights, data handling practices, or compliance obligations were modified.
June 19, 2026
Technical infrastructure update to privacy policy page; no substantive policy changes.
Why it matters: This change does not materially affect Postman's privacy policy or user obligations. The modification is limited to the technical infrastructure used to serve the policy document and has no operational significance for privacy practices, data handling, or user rights.
Added country-specific privacy notices for Australia and UK, including formal complaints procedures and 30-day acknowledgment timelines; clarified transaction data collection scope; restructured regul
Why it matters: The updated policy formalizes complaint procedures and response timelines for UK and Australia users, establishing enforceable procedural standards that did not previously have explicit timelines. For merchants and businesses using Checkout, this creates a documented service standard for dispute handling that may need to be reflected in their own customer-facing policies and vendor documentation. The clarification of transaction data collection to include country information makes explicit what was previously implicit in the data types collected.
Clarified OnStar privacy request process and corrected retention schedule language; no material changes to data-sharing permissions.
Why it matters: The updated language clarifies the mechanics of submitting privacy requests and corrects apparent text errors in the retention schedule. While these are editorial changes, clear procedures for exercising consumer privacy rights and accurate disclosure of data retention purposes are foundational to CCPA and similar privacy frameworks. The corrections ensure the policy accurately reflects GM's stated practices without introducing ambiguity.
Reorganized Nest Renew product references in Terms of Service; unclear operational impact.
Why it matters: The reorganization of product references in Google Nest's Terms of Service may indicate changes to how Nest Renew features, benefits, or enrollment processes are communicated to users. However, the provided diff context does not reveal whether any substantive operational changes to the service, data collection, or user obligations accompany this restructuring.
Reorganizes privacy policy structure for data collection sources; no new data types disclosed.
Why it matters: The updated policy clarifies its structure for disclosing data collection sources, but introduces no new data practices, restrictions, or rights. The reorganization may improve readability of the policy without altering its substantive scope.
Stay ahead of the changes
You're seeing a fraction of what's changing
ConductAtlas monitors every tracked platform and captures every policy update.
Asana Terms of Service updated with one sentence modification on June 19, 2026; specific change content not visible.
Why it matters: The change detection identified a modification to Asana's Terms of Service, which would normally warrant review. However, the substantive content of the modified sentence is not visible in the provided documentation, preventing assessment of whether this change materially affects user rights, obligations, or operational terms.
Added structured table of contents to Privacy Policy with 13 navigable sections for clarity.
Why it matters: This change improves the accessibility and readability of Miro's privacy disclosures by organizing them into a clear, numbered structure. Users can now more easily locate specific sections covering data collection, retention, sharing, security, and user rights. No substantive changes to privacy practices or user protections are introduced.
Adds SMS messaging disclosure with restrictions on phone number sharing and explicit opt-out mechanism.
Why it matters: The updated policy discloses a specific communication service (SMS messaging) and establishes contractual and operational restrictions on how Mercury handles phone numbers associated with that service. This clarifies what data Mercury may collect in connection with SMS, how it will be protected, and how users can control receipt of these messages.
Added navigation line referencing competing AI tools to Terms of Service header; no substantive policy modifications.
Why it matters: This change has no operational significance. A navigation reference was added to the Terms of Service header, but no contractual language, user rights, data handling practices, fees, or obligations were modified.
Added competitor platform links to privacy policy footer; no substantive privacy or data handling changes.
Why it matters: This change has no operational significance for privacy rights, data protection, or compliance obligations. The footer addition is a presentation change only; all substantive privacy policies, GDPR procedures, and data handling terms remain identical to the prior version.
Updated daily. New changes added as detected.