Strictly necessary
Required for sign-in, security, routing, or a requested function. These generally cannot be switched off through an optional preference control.
BROWSER STATE / COOKIES
Small browser signals, documented plainly.
This notice distinguishes required session state from optional tracking. It describes the cookie used by this demo and the decisions a production deployment must still make.
Declared cookie inventory
| Name | Category | Purpose | Duration |
|---|---|---|---|
| devopsify_demo_session | Strictly necessary | Records the active demo session so protected demo routes can enforce the authentication boundary. | Session-style browser cookie; exact expiry is a production configuration decision. |
The cookie is set with a path and `SameSite=Lax` in the demo flow. Its presence does not grant access to another tenant or replace server-side authorization.
Cookie categories
Preferences
Remember choices such as locale or presentation settings. A production service should disclose each preference and its lifespan.
Analytics
Measure use and reliability only after the operator establishes the lawful basis, minimizes data, and discloses the analytics provider.
Advertising
Used for advertising or cross-site profiling. No advertising category is declared for this demo.
Your controls
You can inspect, block, or delete cookies through browser controls, although blocking an essential session cookie can prevent sign-in or protected demo routes from working. A production deployment that uses non-essential cookies must provide an appropriate consent and withdrawal experience before placing them.
Questions and changes
Cookie names, vendors, purposes, lifetimes, and consent behavior should be reviewed whenever the web app changes. For the broader data context, read the privacy notice.