Cookie Policy

This Cookie Policy explains how Kairne uses cookies and similar technologies when you visit our marketing site, sign in, or use the dashboard. It should be read together with our Privacy Policy.

1. What cookies are

Cookies are small text files stored on your device by your browser. Similar technologies include local storage and session storage. They help websites remember your preferences, keep you signed in, and operate securely.

2. How we use cookies

Kairne uses a minimal set of first-party cookies and storage. We do not use third-party advertising cookies or cross-site tracking pixels.

Strictly necessary cookies

These cookies are required for the Service to function. Without them, you cannot sign in or use authenticated features.

• Authentication session cookies — set by Better Auth to maintain your signed-in session, validate requests, and protect against unauthorized access. Session data is also stored in our database and may be cached in Redis for performance.
• OAuth state cookies — short-lived cookies used during GitHub sign-in to prevent cross-site request forgery and complete the authorization flow securely.

Functional cookies and storage

These improve your experience but are not strictly required for core authentication:

• Sidebar state cookie — remembers whether the dashboard sidebar is expanded or collapsed (approximately 7-day expiry).
• Theme preference — dark or light mode may be stored in local storage by our theme provider so your choice persists across visits.

3. Analytics and public profiles

Pro subscribers can view first-party analytics about visitors to their public profiles (for example, page views and project clicks). This analytics system does not rely on third-party marketing cookies for visitors. Visitor engagement is recorded using server-side events and, for some interactions, the browser sendBeacon API — not persistent cross-site tracking cookies.

Pseudonymous visitor identifiers are derived from a daily hash of technical signals (such as IP address and user-agent combined with a rotating salt) and are not used to advertise to visitors on other websites.

4. Third-party cookies you may encounter

Some features involve third parties that may set their own cookies when you interact with them:

• Stripe — when you subscribe to Pro or open the billing portal, Stripe may use cookies necessary for payment security and fraud prevention.
• GitHub — during OAuth sign-in, GitHub may set cookies as part of its authentication flow.
• Loom— if a profile embeds a Loom video, Loom's embedded player may use cookies or similar storage under Loom's policy.
• GitHub (visitor browser)— public Work tabs may load GitHub contribution data directly from GitHub in the visitor's browser, which can involve GitHub's own cookies or storage.

We do not control third-party cookies. Refer to each provider's policy for details and opt-out options.

5. Managing cookies

Most browsers let you block or delete cookies through settings. Blocking strictly necessary cookies will prevent you from staying signed in or using authenticated parts of the Service.

To end an authenticated session, sign out from the dashboard or revoke sessions in Settings → Security.

6. Do Not Track

There is no widely accepted standard for responding to Do Not Track signals. We do not track you across unrelated third-party websites for advertising purposes.

7. Changes

We may update this Cookie Policy when our use of cookies changes. Check the “Last updated” date at the top of this page for the latest version.

8. Contact

Questions about cookies: support@kairne.dev