1. What cookies are
Cookies are small values stored by a browser and returned with later requests. LegionASI also uses server-side session state. This Policy describes the browser cookies and related storage used by the public application as configured at the last-updated date.
2. Cookies and related technologies
| Category | How it is used | What happens if it is blocked |
|---|---|---|
| Session and authentication | A PHP session identifier lets the application associate requests with login state, short-lived messages, CSRF state, and other server-side session data. | Sign-in and features that depend on a session may not work. Public reading may still work on routes that do not require a session. |
| Security state | Security workflows can use the existing session to hold short-lived verification values. The contact form uses a CSRF token stored in the server session rather than a separate long-lived preference cookie. | Forms and protected actions may be rejected until cookies and the session are available. |
| CAPTCHA provider | Google reCAPTCHA is enabled in the current application configuration for supported forms. Its scripts and provider may set or read cookies or other signals under Google’s policies. | Anti-abuse verification may fail, and a protected form may not submit. |
| Analytics and advertising | Google Analytics is disabled in the current application configuration, and the public site does not intentionally set advertising cookies. | There is no analytics feature to preserve by allowing these categories. |
3. Browser storage
The public LegionASI application relies on the server-side PHP session for authentication and the session state described above. The shared site JavaScript also uses localStorage for a small interface preference controlling the visibility of an optional contacts or employees list; that value is not account data and is not used to store conversation history. The Ternary laboratory uses localStorage for local lab preferences, while the test-chat interfaces use sessionStorage for reading-speed settings and unsent workspace drafts. These browser values are not the application’s source of truth for account or conversation records.
4. Third-party resources
The shared site loads some resources from third-party delivery services, including font, icon, script, and CAPTCHA providers. A browser request to those providers can reveal technical information such as an IP address and user agent to the provider. When an enabled payment flow or external model service is used, that provider may apply its own cookies or tracking technologies under its own terms.
5. Duration
The main PHP session cookie is intended to support a browser session and is normally removed when the session ends, subject to browser and server behavior. Provider cookies can have their own duration. LegionASI does not promise a single duration for every provider-controlled value.
6. How to control cookies
Browser settings can block, delete, or limit cookies. You can also use private browsing controls, content-blocking tools, or provider-specific controls where available. Blocking necessary session cookies can prevent authentication, form submission, and other features from working correctly. Blocking a third-party provider can prevent the provider-dependent feature from completing.
7. Updates
We may update this Policy when the site, configuration, or third-party services change. The date above identifies the current version.
8. Contact
Questions about cookies should be submitted through the Contact page.