Recent policy changes

Why it matters: The updated terminology aligns Intuit's privacy language with industry standard terminology for SMS collection. The substantive protection—that personal information from text signups will not be shared, sold, or rented for third-party marketing—remains intact and unaffected by this change.

Why it matters: This change is a documentation navigation restructuring. The substantive guidance on model card creation and governance standards remains unchanged.

Why it matters: The updated policy now provides explicit, accessible contact channels for data protection inquiries, satisfying GDPR and UK GDPR transparency requirements. This clarifies how users and organizations can exercise data subject rights and raises questions or concerns about personal data processing directly with a designated officer.

Why it matters: While this change was captured on July 30, 2026, it represents a navigation and documentation restructuring rather than a substantive modification to privacy practices or user protections. No material operational or legal implications are indicated by the change itself.

Why it matters: OpenSea's Privacy Policy was revised on July 30, 2026. The change involves a one-sentence modification with a numerical adjustment, but without clarity on what the modified sentence addresses or what the numerical value represents, the operational significance for data handling, retention, or user privacy cannot be determined.

Why it matters: The modification appears to be a single numerical adjustment in the Terms of Service, detected on July 30, 2026. Without fuller context of the sentence and its application, the practical operational significance remains unclear and should be clarified before assessing compliance or consumer impact.

Why it matters: The updated privacy notice provides more granular disclosure of what merchant page data Affirm's browser extension collects and how it is used. This expanded transparency clarifies the scope of browser extension monitoring and allows users to make more informed decisions about whether to use the extension, with explicit controls now stated (disable, uninstall, hide, or avoid the in-app browser where alternatives exist).

Why it matters: This change does not affect the operational privacy terms users operate under. The substantive policy language remains identical; this is a navigation and structural reorganization of the same content. No changes to Google's data practices, user controls, or privacy protections are introduced by this update.

Why it matters: The updated system card maintains its core governance and safety framework while curating featured research to highlight recent advances in AI benchmarking and scientific computing. This reflects OpenAI's documentation practices but does not alter the substantive disclosures or operational safeguards that define GPT-5.5 deployment.

Why it matters: The substantive safety assessment in the system card remains unchanged. This is an editorial update to supplementary resources that does not alter OpenAI's stated precautionary approach or findings regarding biological harm capability thresholds. Organizations relying on system card documentation for governance or due diligence purposes can continue to reference the unchanged core risk assessment.

Why it matters: This change does not materially affect how the service operates or what users agree to. It represents document reorganization rather than policy substantive changes.

Why it matters: The detected change appears to be a minor formatting or navigation adjustment rather than a substantive modification to DeepL's privacy practices or user data handling. Without visibility into the full text of the modified sentence or the surrounding policy context, the operational significance cannot be reliably determined.

Why it matters: This change has minimal operational significance. The reordering of feature documentation does not alter which capabilities are available, how they function, or under what terms they are offered. Developers will encounter the same API endpoints and features; only their position in the published documentation has changed.

Why it matters: The updated documentation now directs users to the Cohere Trust Center for additional governance and trust-related resources. This is primarily a navigation enhancement rather than a substantive policy change, and does not materially alter operative terms or user obligations.

Why it matters: The change does not materially affect privacy practices, consumer rights, or operational terms. This is a display adjustment only.

Why it matters: A numerical value was modified in OpenSea's binding terms; without visibility into the figure's purpose, operational significance cannot be reliably determined. Organizations using the platform should review the full updated document to confirm whether this change affects pricing, fees, thresholds, or other material terms.

Why it matters: This change affects how users access cookie preference controls when landing on Canva's privacy policy. The underlying cookie consent mechanisms are not eliminated, but users can no longer manage cookie choices directly from the main privacy policy page; they must navigate to a separate cookies policy instead.

Why it matters: The updated address ensures that customer written correspondence reaches Affirm's correct location. Customers submitting billing disputes, consent withdrawal requests, or other written inquiries must use the new Cleveland address to ensure timely processing and response.

Why it matters: This change does not materially affect the Frontier AI Framework itself. It is a documentation maintenance update that refreshes supporting news links without modifying any substantive AI governance, model risk, or control language.

Why it matters: The updated terms materially alter dispute resolution for consumers by replacing universal California jurisdiction with a consumer-favorable approach where consumers can use their home country's courts and laws. This change affects how complaints are filed and resolved. Additionally, the introduction of separate Automated Data Collection Terms with revocable permission creates new compliance obligations for users employing bots or crawlers, and the 30-day advance notice requirement provides greater transparency into future Terms modifications.

Why it matters: The detected change is technical rather than substantive. No modification to operative policy language, enforcement provisions, restrictions, or user obligations occurred. Users continue to operate under the same stated usage policies.

Why it matters: The updated terms establish a clearer distinction between when OpenRouter stores content for debugging/review (opt-in), for processing a specific request (temporary), and when it may be retained longer (per feature documentation). This reorganization defines the scope and purpose of storage more explicitly and adds a contractual restriction stating OpenRouter will not access processing-related storage except for operation, security, troubleshooting, or legal compliance. For users sending batch or large-volume requests, this clarifies both the temporary nature of storage and the limits on how that content may be used.

Why it matters: The updated email addresses determine how quickly and efficiently users and organizations can exercise data subject rights under CCPA, state privacy laws, and other regulations. Consolidating contact points may reduce routing delays, but users must use the correct address to ensure their request reaches the appropriate team.

Why it matters: This change does not materially affect privacy protections or data handling. It is a product marketing update to the policy page header promoting Modal's Kimi K3 product and API offering. The substantive privacy policy remains dated May 2023.

Why it matters: This change announces new Modal products and pricing in the Terms header but does not modify the contractual framework, user obligations, or rights. The operational significance is minimal as the substantive terms remain unchanged.

Why it matters: This change improves user accessibility by offering the Privacy Policy in multiple regional languages and adding navigation links for specific geographic markets. No substantive privacy practices, data protections, or user rights were modified.

Why it matters: This change has no material operational significance. It is a reorganization of the page navigation header that does not affect the substantive terms, consumer rights, data practices, or policy obligations.

Why it matters: This change updates the document header and branding structure but does not modify any substantive privacy terms, data collection practices, or consumer protections. The operational effect is visual and navigational only.

Why it matters: The updated language clarifies a key operational mechanism for customer control over AI training use of their data. By consolidating the opt-out condition from a dual-requirement structure to a single customer opt-out, the revised DPA reduces ambiguity about when Mistral AI may proceed with model training and provides customers with a clear, simplified path to prevent such use. This is particularly material for organizations subject to GDPR or equivalent frameworks, where lawful basis documentation and customer transparency regarding automated processing are regulatory requirements.

Why it matters: The removal of explicit training exclusions for paid services may affect vendor contracts and Data Processing Addenda that organizations relied on to satisfy their own privacy commitments. The expanded definition of Input data to include third-party integration data means Mistral now processes a broader scope of user information for its stated business purposes. Together, these changes may require organizations to renegotiate vendor agreements and revise customer-facing privacy disclosures to reflect the updated scope of data collection and processing.