Effective date: June 2, 2026
This Cookie Policy explains how Delego uses cookies, local storage, session storage, and similar technologies on getdelego.app. It should be read together with our Privacy Policy.
What cookies and similar technologies are
Cookies are small text files placed on your device by a website. Local storage and session storage are browser storage mechanisms that work in a similar way but are stored by the browser rather than sent with every request. We use these technologies to keep you signed in, secure the service, remember preferences, measure product usage, diagnose errors, and operate feature flags.
How we classify technologies
| Category | Purpose | Consent |
|---|---|---|
| Strictly necessary | Authentication, account security, session handling, CSRF/security support, routing, and service operation. | Required to provide Delego. These cannot be disabled through our banner. |
| Preferences | Remembering theme, language, sidebar state, selected workspace, and last authentication method. | Used to improve your experience. You can remove them through your browser. |
| Analytics and feature flags | Understanding product usage, measuring page views and events, evaluating feature flags, and improving Delego. | Required for the Delego production service and activated after you accept required technologies in the Delego cookie banner. |
| Session replay and browser diagnostics | Diagnosing errors, performance issues, and broken user flows with PostHog and Sentry browser tools. | Required for the Delego production service and activated after you accept required technologies in the Delego cookie banner. |
Technologies we use
| Name | Type | Purpose | Typical duration |
|---|---|---|---|
| Supabase auth session cookies | Cookie | Keep you signed in, refresh sessions, and protect authenticated routes. | Managed by Supabase session settings. |
| theme | Cookie | Remember light, dark, or system appearance preference. | Up to 1 year. |
| lang | Cookie | Remember selected interface language. | Browser session unless overwritten. |
| sidebar_state | Cookie | Remember dashboard sidebar open or closed state. | Up to 7 days. |
| last-selected-team | Cookie | Remember selected team workspace if team accounts are enabled in the future. | Up to 30 days. |
| delego-cookie-consent and cookie_consent_status | Local storage | Remember whether you accepted the required cookie banner. | Until cleared in your browser or reset by us. |
| Last authentication method | Local storage | Remember whether you last used password, one-time code, magic link, or OAuth sign-in. | Until cleared in your browser. |
| Linear onboarding modal state | Session storage | Avoid showing the same onboarding modal repeatedly during one browser session. | Current browser session. |
| PostHog cookies and local storage | Cookie and local storage | Product analytics, page views, event tracking, session replay, and feature flags. | According to PostHog configuration and browser storage settings. |
| Sentry monitoring and replay storage | Cookie, local storage, session storage, or SDK-managed identifiers depending on Sentry configuration | Error monitoring, performance monitoring, and session replay diagnostics. | According to Sentry configuration and browser storage settings. |
Exact cookie and storage names can change as our providers update their SDKs. We keep this Policy focused on the purpose and category of each technology.
Analytics and replay
In production, we configure PostHog in the EU region for analytics, session replay, and feature flags. Browser-side PostHog analytics, feature flags, and replay start after you accept required technologies in the Delego cookie banner. PostHog may process page URLs, product events, device information, approximate location, user identifiers, email address as an account trait, feature flag evaluations, and replay data showing how the interface behaved during a session.
In production, we configure Sentry for errors, performance monitoring, and session replay. Browser-side Sentry monitoring and replay storage start after you accept required technologies in the Delego cookie banner. Server-side error monitoring may run where necessary to operate, secure, and troubleshoot Delego. Sentry may process stack traces, request paths, request methods, request headers, user identifiers, email address, device information, performance traces, and replay data used to diagnose bugs and service failures.
Do not enter secrets, access tokens, private keys, or other unnecessary sensitive data into Delego screens, Linear prompts, job output, or runner metadata.
How to manage browser storage
- The Delego cookie banner records your acceptance of the required production technologies described in this Policy.
- You can remove cookies, local storage, and session storage from your browser settings. If you do, Delego may ask you to accept the required banner again.
- You can block cookies in your browser. If you block strictly necessary cookies, sign-in and dashboard features may not work.
- You can contact hello@getdelego.app if you need help with privacy or cookie choices.
Changes
We may update this Cookie Policy when we change our website, analytics, monitoring, feature flag, or authentication tools. If the change is material, we will notify users in the application or ask you to accept the updated banner again where required.