Loading
Preparing the route surface...
The current page is loading server and route data. This global loading boundary keeps the shell stable while the route finishes rendering.
Loading
The current page is loading server and route data. This global loading boundary keeps the shell stable while the route finishes rendering.
This page explains the current consent and browser-storage behavior used on the public website.
Last updated: May 11, 2026
The website shows a consent banner for optional analytics and performance monitoring. Until you accept analytics, optional analytics storage stays disabled, analytics scripts are not activated, and performance telemetry remains off.
The current website uses browser storage for the following functional purposes:
After a successful ERM sign-in, the website exchanges the Firebase browser sign-in for an HTTP-only session cookie named ai-engineering-erm-session. That cookie is used to protect server-rendered ERM routes and is not intended for analytics, ad targeting, or other marketing use. Because it is HTTP-only, client-side JavaScript cannot read it directly.
If analytics consent is granted and the deployment has a configured measurement ID, the site can enable Google Analytics page-view tracking. The same consent gate also allows Firebase Performance Monitoring to capture Core Web Vitals for site-quality monitoring. If consent is denied, those optional analytics and telemetry paths remain off.
Supported public forms, attachment-upload flows, and customer-portal actions can also request Firebase App Check tokens. Those tokens are short-lived abuse-protection signals rather than marketing cookies. They help the backend distinguish real browser traffic from scripted abuse where App Check is configured, and they are separate from the analytics-consent decision.
The public marketing routes do not currently run a direct customer checkout flow, so there is no purchase-cookie layer for card payments or order completion on these public pages.
Analytics consent is stored locally in the browser. Clearing site storage or revisiting the banner flow resets that preference. If the consent implementation changes materially, this page will be updated alongside the public site behavior.