Analytics consent

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.

Local storage currently used

The current website uses browser storage for the following functional purposes:

• Storing the analytics-consent choice so the banner state persists between visits.
• Storing estimator draft answers and the anonymous estimate-session ID while a pricing request is in progress.
• Persisting Firebase Authentication state in the browser for invited customer-portal access and ERM sign-in initiation.

Session cookies used by the internal ERM

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.

Optional analytics behavior

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.

App Check and non-cookie anti-abuse tokens

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.

What the site does not currently do

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.

Changing your preference

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.