We use cookies that are needed to sign you in and keep the session. We also store your Accept or Reject choice. Analytics (PostHog) loads only if you accept. Error monitoring (Sentry) can run without an analytics cookie, because it is strictly needed to keep the product secure and running. We do not set advertising cookies.
The cookie banner gives Accept and Reject equal weight, plus Cookie settings. Cookie settings opens a panel: strictly necessary stays on; analytics is off unless you turn it on and save. You can open that panel later: . Read the privacy notice.
Needed to run the product
Auth session. Set by Supabase Auth when you sign in. Required to keep you signed in across pages. Removed when you sign out or after the session ends.
Active company. Stored on your device so the company you last opened stays selected after a reload. It is not used for advertising.
Cookie choice (`jos_analytics_consent`). Remembers Accept or Reject for up to 12 months. Needed so we do not ask every time, and so analytics stays off after Reject.
Analytics, only after Accept
PostHog. Product analytics on the EU host (eu.i.posthog.com), loaded through a first-party `/ingest` path. Used for pageviews, signup, onboarding, first Talk message, and checkout viewed. Session replay masks every input and all on-screen text. We never send emails or names. If you are signed in we identify you by an internal user id only. Reject keeps PostHog off. If the PostHog keys are not set, nothing loads.
Error monitoring, no analytics consent needed
Sentry. Sends crash and error reports so we can fix faults and security issues. It does not set a marketing cookie. It is set not to collect personal data. We scrub emails, phone numbers, tokens and Authorization headers from messages, breadcrumbs and URLs. If the Sentry keys are not set, it does nothing.
What we do not use
No Google Analytics. No advertising pixels. No third-party retargeting. If a cookie like that appears on a Juniper OS page, that is a bug. Tell us through the contact form.