Structa AI · launch readiness

Cookie and browser storage notice

Operational draft · Effective August 18, 2026 · Last updated August 18, 2026

These pages reflect the current product implementation and the supplied operator, contact, and refund decisions. Governing law, retention periods, final pricing/tax treatment, and final legal approval must still be confirmed before formal production launch.

Structa AI currently uses an HttpOnly session cookie for authentication and a small first-party browser-storage identifier for anonymous product analytics and continuity. No advertising or third-party analytics cookies are included.

Essential session cookie

`buildai_session`

This compatibility-named first-party cookie identifies an authenticated session. It is HttpOnly, SameSite=Lax, scoped to the product path, and Secure in production. It expires after the configured 30-day session lifetime or when you sign out.

Anonymous analytics identifier

`structa-analytics-visitor-v1`

This local-storage value is a random identifier used to count returning browsers without storing a name, email, full IP address, or customer message content. The server hashes it before storing analytics events. You can reset it through your browser's site-data controls.

Local browser storage

The frontend may store non-authentication UI state and in-progress form continuity in local storage. Authentication tokens, full analysis payloads, and unlock tokens are intentionally excluded from persisted local state. The service worker may cache static application files to improve loading reliability.

What is not used

No advertising cookies.
No third-party analytics SDK.
No fingerprinting or sale of browser identifiers.
No camera, microphone, location, or other browser permission is requested by the product.

Future changes

If analytics, experiments, or non-essential tracking are expanded later, this notice and legally required consent controls must be updated before enabling them.