Cookie Policy

Stacklinx does not set an authentication cookie. When you sign in on the web, the app stores a JSON Web Token in localStorage under the key token. Later requests send it as Authorization: Bearer. Signing out, or clearing site data, removes it. The mobile app stores the session in the platform keychain instead of localStorage.

The same browser may also hold these localStorage keys, which are not cookies: impersonationToken while an administrator is viewing the product as another user, theme and darkMode for appearance, aiAnalystChats for analyst chat drafts kept on the device, and keys that start with sidebar- for sidebar layout. After you register, sessionStorage may hold a short-lived sl-new-account flag so the next sign-in can open onboarding. That flag is removed when you sign in.

The website includes PostHog. PostHog loads only when the deployment has a NEXT_PUBLIC_POSTHOG_KEY. When it loads, it is configured with persistence localStorage+cookie, so it writes both a cookie and localStorage. It records page views, page leaves, product events (such as signing up), and, under PostHog’s defaults, session recordings. The cookie is sent to the PostHog host configured for that deployment (by default the PostHog US ingest host).

If that key is not set, PostHog does not load and Stacklinx does not set an analytics cookie. There is no separate advertising cookie, and no analytics cookie from any other vendor in the web app.

Umami, when a workspace uses it, is a product the customer connects for their own sites. It is not a cookie set by the Stacklinx marketing site.

Blocking cookies in your browser blocks the PostHog cookie on deployments where analytics is on. It does not sign you out, because the session token is in localStorage. Clearing this site’s cookies and site data removes the token and signs you out.

Questions: privacy@stacklinx.com. How we use the resulting data is in the Privacy Policy.