Cookie Policy
Effective date: [[EFFECTIVE_DATE]]
This policy explains the cookies and similar technologies used on https://seros.dev and in the Seros application. It supplements the Privacy Policy.
A cookie is a small file a website stores in your browser. We also use similar technologies: local storage, session storage and, in some emails, tracking pixels. This policy uses "cookies" to mean all of them.
1. Categories we use
| Category | What it does | Examples of purpose | Set by | Consent needed in EU/UK | Typical lifetime |
|---|---|---|---|---|---|
| Strictly necessary | Makes the site and app work | Keeping you signed in, session integrity, load balancing, remembering your cookie choices, CSRF protection | Us | No | Session to session, up to 30 days for the login session |
| Security | Detects and prevents abuse | Bot and fraud detection, rate limiting, suspicious login detection | Us and [[TBD_VENDOR]] | No, where strictly necessary for a service you requested | 12 months |
| Functional | Remembers your choices | Language, timezone, interface preferences, dismissed notices | Us | Yes | 12 months |
| Analytics | Tells us how the product is used in aggregate | Which features are used, where people get stuck, error rates | [[TBD_VENDOR]] | Yes | 13 months |
| Marketing and advertising | Not used | We do not run advertising pixels and we do not share data for cross-context behavioural advertising | None | Not applicable | Not applicable |
The specific cookie names, providers and lifetimes must be listed before publication. Run a scan of the live site and fill in a per-cookie table; a category table alone is not sufficient in several EU jurisdictions.
| Cookie name | Category | Provider | Purpose | Expiry |
|---|---|---|---|---|
| [[TBD_COOKIE_NAME]] | [[TBD_CATEGORY]] | [[TBD_VENDOR]] | [[TBD_PURPOSE]] | [[TBD_EXPIRY]] |
2. How consent works
In the EU, EEA and UK, we ask for consent before setting anything that is not strictly necessary. The banner appears on your first visit. Nothing beyond strictly necessary and security cookies is set until you choose. Rejecting is as easy as accepting: the banner has a "Reject all" control with the same prominence as "Accept all", and there is no pre-ticked box.
Elsewhere, including the United States, we set functional and analytics cookies by default and you can turn them off at any time using the same control.
We record your choice and re-ask after 12 months, or sooner if the purposes change.
3. How to change or withdraw your choice
- Use the "Cookie settings" link in the footer of https://seros.dev at any time.
- Withdrawing is as easy as giving consent, and takes effect immediately for future processing. It does not undo processing that already happened.
- You can also block or delete cookies in your browser settings. If you block strictly necessary cookies, sign-in will not work.
- Most browsers offer a "Do Not Track" signal. There is no common standard for responding to it and we do not respond to it. We do honour the Global Privacy Control signal where US state law requires it, treating it as an opt-out of sale and sharing, though we do not sell or share personal information in any event.
4. Third-party cookies
Any cookie set by a provider other than us is listed in the table above and in SUBPROCESSORS.md. We do not permit third parties to use cookies on our site for their own advertising purposes.
5. Changes
We will update this policy when the cookies we use change. The effective date at the top shows the current version.
Questions: privacy@seros.dev.
What I need from you
- Run a cookie scan on the live site and fill the per-cookie table. Do not publish category-only.
- Choose a consent management tool, or build the banner; confirm it blocks scripts before consent rather than only hiding the banner.
- Confirm no advertising or social pixels exist anywhere on the marketing site, including in any embedded form or video.
- Set the consent refresh period.