1. Essential authentication cookies
Supabase SSR uses secure session cookies so the console can maintain a signed-in session across server-rendered routes. These cookies are required for login, organization access and protected actions. They must not contain raw signal payloads or service credentials.
2. Interface preferences
The console may store a local color-scheme preference so the interface remains consistent between visits. This preference is not used to identify a person or to send operational data to Canario.
3. Analytics
The application can include Vercel Analytics for aggregate product and site measurement. It is disabled unless the explicit environment flag is enabled. Before activation, Canario must confirm the enabled measurement mode, whether it sets or reads any identifier, retention, provider location, consent requirement and opt-out path.
Activation funnel events inside the console are organization-scoped product telemetry such as canary creation, first signal, first alert and checkout milestones. They intentionally exclude raw signal payloads and should not be used as a substitute for a public marketing analytics policy.
4. Your choices
Users can block optional analytics through the browser or the final consent control once implemented. Blocking essential authentication storage prevents sign-in and protected console actions. The final policy must provide the responsible contact and any jurisdiction-specific rights.