Legal
Cookie Notice
Last updated
We keep this short because the list is short. Louvain uses cookies to keep you signed in and browser storage to remember a few preferences. On our public pages we measure usage if you allow it, from our own domain. Nothing measures what you do inside the product, and we set no advertising cookies unless you ask for them separately.
The short version
- Nothing measures what you do inside the product. No session recording, no click tracking and no page measurement runs on any page behind sign-in. Those pages are full of your own company's knowledge — names, documents, answers — and a script that captures what you clicked would capture that text with it. If you allowed measurement on our public pages, the one thing sent from behind sign-in is your account and workspace identifiers, so your visit and your account count as one person; it carries no page address and nothing on the page. Our servers record a fixed set of named events, described in our Privacy Policy, which carry identifiers and counts and never the content of your sources or your questions.
- On our public pages we measure usage, if you allow it. Which pages are read, what is clicked, how fast they load, and errors — so we can fix what nobody can find. It is asked before anything runs, and declining costs you nothing on this site.
- We run no advertising or cross-site tracking tags at all today. There is a separate switch for them on this page, off until you turn it on, so that if that ever changes it is a choice you made rather than one we announced. Accepting analytics does not turn it on.
- It stays on our own domain. The analytics requests go to
louvain.ai/ph, not to a third-party address in your browser, and we do not link what you do here to your activity on other sites. - If your browser already says no, we listen. Global Privacy Control or Do Not Track means we ask nothing and run nothing beyond what the site needs to work.
We said previously that we ran no analytics script and therefore showed no banner, and that we would ask first if that changed. This is us asking. We also said nothing ran behind sign-in; now, if you allow measurement, your account identifier is sent from there, and nothing else is.
Cookies needed to sign in
| Name | Set by | Purpose | How long |
|---|---|---|---|
louvain_session | Louvain | Keeps you signed in to your workspace. HTTP-only, sent only over HTTPS | Until you sign out, after 7 days without use, or 14 days at most |
brain_session | Louvain | The earlier name of the session cookie. Still read for sessions created before it was renamed; no longer written | Until it expires |
louvain_sso_state | Louvain | Set only while you sign in through your company's identity provider, so the sign-in that comes back is the one you started. HTTP-only | 15 minutes |
__session, __client_uat and variants with a suffix | Clerk, our sign-in provider | Records whether you are signed in, so the sign-in button and the app know which to show | For the length of your sign-in session |
__client | Clerk, on its sign-in domain | Keeps your sign-in with Clerk | For the length of your sign-in session |
Clerk's script loads on our pages so that "Sign in" works and shows the right state. Clerk's own privacy policy describes how it handles sign-in data.
Preferences stored in your browser
These are kept in your browser's local storage, not sent to us with each request, and you can clear them at any time in your browser settings.
| Key | Purpose |
|---|---|
louvain.theme | Your light or dark theme choice (brain.theme is its earlier name) |
louvain.receipts.width | How wide you last made the evidence panel in the app |
louvain.graph.probe | Whether you turned on the connections map's measurement overlay, a developer convenience |
louvain.consent.scheduling | Whether you chose to load HubSpot's calendar on the demo page (see below) |
louvain.consent.analytics | Whether you allowed usage measurement on our public pages |
louvain.consent.advertising | Whether you allowed advertising tags on our public pages |
louvain.sort.… | How you last sorted each kind of file list in the app |
louvain.spaces.unified | Whether you last chose the combined view of your collections and connected drives |
louvain.nudge-prompt.… | That you answered the offer of notifications on Today, so it is not offered again on this browser |
louvain.html-run.… | That you chose to run the scripts of one version of an HTML file in the viewer, so you are not asked again for that version; a new version asks again |
louvain.push.device.… | The identifier of this browser's notification registration for you in one workspace, so it can be turned off. Removed when you sign out |
All of these are needed for the app to work or remember a choice you made; none is used for analytics or advertising, and none is shared with a third party. They stay until you clear them, except where the table says otherwise.
These are kept in your browser's session storage instead, which is cleared when you close the tab:
| Key | Purpose |
|---|---|
louvain.oauth.consent | While you sign in to connect an AI assistant, the connection request you were approving, so the approval can resume after sign-in. Used once, and ignored after 30 minutes |
louvain.zone:… | That this tab already told Louvain your time zone, so notifications respect your quiet hours |
louvain:reload-scroll | Where you were scrolled, when the app reloads itself to pick up a new version, so you return to the same place. Removed once used |
louvain:stale-build-failed-reload | When such a reload last failed, so the app does not retry in a loop |
Set only if you allow usage measurement
| Name | Set by | Purpose | How long |
|---|---|---|---|
ph_…_posthog, a first-party cookie and a local storage entry of the same name | PostHog's library, served from our domain | A random visitor identifier, and once you sign in your account and workspace identifiers, so the pages you read count as one visitor. Sent with analytics requests to louvain.ai/ph | One year, or until you sign out or clear it |
louvain_attribution | Louvain | Set only when you arrive from a campaign link or another site: the campaign tags in that link, the other site's address (its domain only) and the day. The ad click identifier an advertising platform adds to a link is kept only if you have also allowed advertising, below. If you then create a workspace, it is recorded with it so we can tell which campaign led to it, and the cookie is removed. Never anything you type | 90 days from your first visit. Removed at once if you decline or forget your choice (the ad click identifier alone if you withdraw only advertising), if your browser sends Global Privacy Control or Do Not Track, or when you create a workspace. The first visit is kept; later ones do not replace it |
The demo calendar
The calendar on our demo page is drawn by our own site: available times and your booking go to HubSpot from our servers, so no HubSpot code runs in your browser.
If our calendar is unavailable, the page can offer HubSpot's scheduling widget instead. That widget runs HubSpot's code and may set HubSpot cookies, so it loads only after you choose to load it, and we remember that choice in louvain.consent.scheduling. You can also open the calendar directly on HubSpot's site. You can change your choice below.
Managing cookies
You can block or delete cookies in your browser settings. If you block the sign-in cookies, you will not be able to sign in to Louvain.
Questions about this document: privacy@louvain.ai.