Cookie Policy
Last updated: 2026-11-10
1. Summary
Klyrix uses only strictly necessary cookies. We do not set marketing, analytics, or third-party tracking cookies. Where you see a cookie banner, it is for transparency under ePrivacy (EU/UK), KVKK (Türkiye), LGPD (Brazil), and CCPA (California).
2. What cookies we set
| Cookie | Purpose | Duration | Type |
|---|---|---|---|
| sb-<project>-auth-token (.0 / .1), sb-<project>-auth-token-code-verifier | Supabase auth session (split into numbered parts when large); the code-verifier is a one-time value used while completing an email-link sign-in | Up to 400 days; cleared at logout or when a session limit below is reached | Strictly necessary |
| klyrix_last_activity | Idle session timeout (D-077) | 30 minutes | Strictly necessary |
| klyrix_session_started | Absolute session limit (8h) | 8 hours 30 minutes | Strictly necessary |
| klyrix_cookie_consent | Cookie banner preference | localStorage | Strictly necessary |
| NEXT_LOCALE | Language preference (the selected interface language) | 1 year | Strictly necessary |
| vds.system_id / vds.system_slug | Remembers the selected system (workspace) | 1 year | Strictly necessary |
| vds.farm_id / vds.farm_slug | Remembers the selected farm within the system | Up to 1 year | Strictly necessary |
3. Third-party services
We use Stripe for payment processing. When you initiate checkout, Stripe may set cookies on its own domain (js.stripe.com). See Stripe Cookie Settings.
4. Your control
Browser settings allow you to delete cookies and block them. Blocking strictly-necessary cookies will prevent Klyrix from functioning (login will fail). Klyrix does not bypass browser settings.
5. Updates
We update this policy when new cookies are introduced. Material changes are notified via email + 30-day notice for active customers.
6. Contact
Cookie-related questions: privacy@klyrix.com