This update focuses on privacy and security hardening across analytics, user data responses, and third party scripts.
Privacy and security updates
Pageview tracking now sends a sanitized URL to analytics. Only a small allowlist of non-sensitive marketing parameters (like UTMs and ref) is included, which helps prevent accidental collection of authentication and OAuth-related query parameters.
Client-facing user lookups were tightened to avoid returning encrypted credential fields. Public user responses now provide a safe shape intended for the client, including a simple indicator for whether a key is present, without exposing the encrypted value.
Third party scripts loaded in the app now include Subresource Integrity and cross-origin settings. This helps ensure the browser only executes the expected script content and reduces supply chain risk if a hosted script is tampered with.
Access and authorization
The chat API now verifies chat ownership against the authoritative source before returning chat data or initializing streaming. This reduces the chance of accessing chat resources that do not belong to the signed-in user.