Cookie policy
Last updated: 4 October 2026
This policy explains how Behavr uses cookies and similar technologies on behavr.ai and in the Behavr application. It sits alongside our Privacy policy.
Contact: hello@behavr.ai
What cookies are
Cookies are small text files a site stores in your browser. They let a site remember things between pages and visits: that you are signed in, what you chose last time, or how you found the site. We also use local storage, which works the same way for our purposes.
This site does not ask for cookie consent
There is no cookie banner on behavr.ai because this site stores nothing on your device: no cookies, no local storage. There is nothing to accept or decline, so asking would be a formality rather than a choice.
The Behavr application at app.behavr.ai is different: signing in needs cookies. Those are listed below. Nothing in the application sets an analytics cookie either.
The categories we use
Strictly necessary. These make the application work and keep it secure. They keep you signed in, protect against cross-site request forgery, route you to the right server, and protect the sign-in service from automated abuse. They cannot be switched off, and we do not ask consent for them because the application cannot run safely without them.
Analytics. Neither the site nor the application sets an analytics cookie. On this marketing site we use Vercel Web Analytics: visitors are identified by a hash of the incoming request, which is discarded after 24 hours, and it records the page, the referrer, approximate location from your IP, and your browser and device type, all as aggregate counts. The Behavr application uses PostHog, which is configured to keep its data in memory for the length of a page visit rather than in a cookie or in local storage, and to link events to your Behavr user ID.
Marketing. We do not use marketing cookies and we do not advertise.
We do not use cookies to build advertising profiles, and we do not sell what they collect.
The cookies we set
This marketing site, behavr.ai, sets none. Every cookie below is set by the Behavr application at app.behavr.ai and by the providers behind it. Several sit on the .behavr.ai parent domain, so your browser sends them to this site too.
| Name | Set by | Category | Purpose | Expires |
|---|---|---|---|---|
__session | Clerk, on app.behavr.ai | Necessary | Keeps you signed in | 60 seconds, refreshed while you stay signed in. The session itself ends after 7 days. |
__client | Clerk, on clerk.behavr.ai | Necessary | Identifies your browser to the sign-in service | 400 days |
__client_uat and __client_uat_bpOXPj5A | Clerk, on .behavr.ai | Necessary | Tells the site whether a session exists. behavr.ai reads it to decide whether the navigation shows “Open app” | 400 days |
__cf_bm | Cloudflare, via Clerk, on clerk.behavr.ai | Essential, security | Tells automated traffic from real visitors, so the sign-in service can block bots | 30 minutes |
_cfuvid | Cloudflare, via Clerk, on clerk.behavr.ai | Essential, security | Applies rate limits per visitor, so the sign-in service cannot be flooded | When you close your browser |
Every row above except __session was checked against a real browser session on 3 October 2026.__session only exists once you are signed in, so its row comes from Clerk’s documentation instead. Recheck the table whenever the application’s providers change. Most of these cookies are set by the providers listed in our Privacy policy rather than by us directly.
No analytics appears in the table above, because neither tool sets a cookie: Vercel Web Analytics on this site is cookieless by design, and PostHog in the application is configured for memory persistence.
This site reads one of them, and only one: __client_uat, to tell whether you are already signed in. If you are, the navigation shows “Open app” instead of “Sign in” and “Get started”. The value is read in your browser and never sent anywhere, and we do not set it or change it.
__cf_bm and _cfuvid are set by Cloudflare on Clerk’s domain rather than by us directly, because Clerk runs its sign-in service behind Cloudflare. They are essential security cookies: they exist to tell real visitors from automated traffic and to apply rate limits. They are not used for analytics or advertising, and they do not follow you to other sites.
The application also writes one local storage key, __clerk_environment, which the sign-in service uses to cache its configuration. It is removed when you clear site data for behavr.ai in your browser.
Stripe sets its own fraud-prevention cookies in the application when you reach payment. They are not set on this marketing site.
Your choices
On this site. There is nothing to turn off, because nothing is stored on your device. The analytics described above are counted without a cookie and without anything that identifies you.
In your browser. You can block or delete cookies in your browser settings. Blocking the necessary cookies above will stop you signing in to the application.
Global Privacy Control. Where your browser sends the Global Privacy Control signal, we do not load the analytics script on this site at all.
Changes
We will post any change here and update the date at the top. If we ever add something to this site that stores data on your device, we will ask for your consent before it runs.
Questions: hello@behavr.ai