Last updated: 6 May 2026
Cookie Policy
Deadline Engine uses strictly necessary cookies to operate the Service. We also provide controls for analytics and marketing technologies. Those optional categories are only enabled after consent where consent is required under the Privacy and Electronic Communications Regulations (PECR). Continued browsing is not treated as consent.
Strictly necessary cookies
| Name | Purpose | Duration |
|---|---|---|
| sb-<ref>-auth-token | Authentication session, set by Supabase | 7 days |
| sb-<ref>-auth-token-code-verifier | OAuth flow, set transiently during sign-in | Session |
| deadline-engine-cookie-consent-v1 | Local storage key recording your consent choices | 12 months |
Deadline Engine does not currently use a separate CSRF cookie. If one is added later, it will be strictly necessary and documented in this table before launch.
Optional categories
- Analytics: aggregate usage measurement through Plausible, only loaded after explicit consent where required.
- Marketing: marketing measurement, not currently active, and only loaded after consent if added later.
Your preference is stored in your browser localStorage under a versioned Deadline Engine key. We also store a server-side consent record containing the preference state, timestamp, and hashed IP address and user agent. The banner reappears if your consent record is older than 12 months.
Third-party cookies
When you complete a subscription, Stripe sets its own cookies on its checkout domain. We do not set Stripe cookies on deadlineengine.com. Refer to Stripe’s cookie policy for details.
Managing cookies
You can change optional preferences at any time using the Cookie preferences link in the footer. You can also block or delete cookies via your browser settings. Blocking the authentication cookie will prevent you from logging in.