kKronavi
Privacy PolicyTerms of ServiceData Processing AgreementCookie Policy

Legal

Cookie Policy

Effective April 16, 2026

This policy explains exactly which cookies Kronavi sets, why we set them, and why we do not show a cookie consent banner.

1. What cookies we use today

Authentication (strictly necessary)

When you sign in to Kronavi, Supabase Auth sets a session cookie in your browser. This cookie:

  • Identifies your authenticated session so you stay logged in between page loads.
  • Is scoped to kronavi.com (first-party, same-site).
  • Contains only a signed session token — no personal data is stored in the cookie value itself.
  • Expires when you sign out or when the session reaches its maximum age (controlled by Supabase Auth settings).

This cookie is strictly necessary for the Service to function. It cannot be disabled without breaking authentication.

Functional (strictly necessary)

Kronavi may store lightweight preferences in your browser’s localStorage (not cookies) for things like sidebar collapsed/expanded state. These values:

  • Never leave your browser — they are not transmitted to our servers.
  • Contain no personal data.
  • Are cleared when you clear your browser storage.

2. What we do NOT use

  • Analytics cookies: we do not use Google Analytics, Mixpanel, Segment, or any third-party analytics cookie. We collect only server-side diagnostic logs (request path, response code, timestamp) as described in the Privacy Policy.
  • Advertising or tracking cookies: we have no ad-tech integrations. No retargeting, no Facebook Pixel, no cross-site tracking of any kind.
  • Third-party cookies: no third-party scripts that set cookies are loaded on kronavi.com.

3. Why there is no consent banner

Under GDPR and the EU ePrivacy Directive, a cookie consent banner is required only when a site uses non-essential cookies (analytics, advertising, personalisation). Kronavi currently uses only strictly-necessary cookies (authentication). Strictly-necessary cookies are exempt from consent requirements under ePrivacy Recital 25 and Article 5(3).

If this changes — for example, if we add analytics or a third-party chat widget — we will:

  • Update this page to describe the new cookie.
  • Add a consent banner before the new cookie is set.
  • Notify active customers by email of the change.

4. Managing cookies

You can delete or block cookies at any time using your browser’s settings. Note that blocking the Supabase session cookie will prevent you from signing in to Kronavi.

5. Contact

Questions about cookies or this policy? Email privacy@kronavi.com.