Hardening, everywhere rather than just the product
The application has enforced a strict Content Security Policy with a per-request nonce for some time. The surfaces around it were not held to the same standard.
The marketing site, this status page and our internal console now all send a
Content Security Policy, X-Content-Type-Options: nosniff, a
frame-ancestors restriction and a strict referrer policy. One posture across
everything on the domain, rather than one strong surface and several quiet
ones.
Nothing about this changes how any page behaves for you. It narrows what a compromised or injected script would be permitted to do.
Seven languages, at parity
Localised pages existed in all seven languages, but some of them were thin — present, indexed, and missing the content the English page carried. Pricing was the worst case: a localised pricing page that didn't show the plans or prices.
Pricing, product, trust and MCP pages are now complete in every language, and a build-time check now fails if a localised page exists but is empty. A missing translation is a visible gap rather than a page that quietly says less.
Available now.