This update focuses on protecting sensitive data and reducing the risk of accidental exposure in a few key areas.
Privacy and data protection
Pageview analytics now send a sanitized URL that only keeps a small allowlist of non-sensitive marketing parameters. This helps prevent sensitive query parameters from being captured by third-party analytics.
Client-facing user lookups were updated to exclude encrypted secret fields from responses. You can still tell whether a user has an OpenRouter key via a boolean flag, without returning the encrypted value.
Security hardening
Third-party scripts now include Subresource Integrity (SRI) and the appropriate cross-origin setting. This helps ensure only the expected script content runs, reducing supply-chain risk if a hosted script is ever altered.
PII redaction in server logging now uses a cryptographic hash (SHA-256) instead of a weak non-cryptographic hash. This makes redacted values significantly harder to reverse in practice.
The chat API now verifies chat ownership via the authoritative source before returning chat data or initializing streaming state. This adds an extra guardrail against unauthorized access.