Cookie Policy

A cookie is a small file a website stores in your browser. Ours do two jobs: keeping you signed in and counting how many people visit which pages. We do not use cookies for advertising, we do not follow you to other websites, and we do not sell or share what they collect with data brokers.

These make the site work. They cannot be turned off through a preference, because without them signing in and access-controlled assistants would not function. They are set only when you actually use the feature — a visitor who never signs in never receives one.

We use Google Analyticsto understand which pages are read and which are ignored. It tells us that a page was viewed; it does not tell us who you are, and we never connect it to conversation content or to a client's data.

Google acts as our analytics provider and is listed in Subprocessors. This involves a transfer of data to the United States — see Privacy for how those transfers are handled.

In the EEA, the UK, Switzerland and Thailand we ask before the analytics cookie is set. Until you answer, the Google Analytics script is not loaded at all — the decision is made on our server, so nothing is running in the background while the question sits on screen. Declining and simply ignoring the banner have exactly the same effect.

Elsewhere, analytics runs unless you opt out, and you can opt out at any time using the methods below. Wherever you are, we honour Global Privacy Control and Do Not Track signals — if your browser sends one, we record that as a refusal and never ask you.

Your answer is stored in a cookie called eai_analytics_consent, which holds nothing but the word “granted” or “denied” and lasts a year. To change your mind, clear that cookie and you will be asked again. If you would like analytics data we already hold about your visits removed, write to [email protected].

We also use Cloudflare Web Analytics, which measures page performance and traffic without setting any cookie and without tracking individuals across visits or sites. Because it stores nothing on your device and builds no profile, it is not part of the consent question above and runs everywhere. We mention it because a cookie policy that quietly omitted a second analytics tool would be misleading even though this one sets no cookie.

Block analytics specifically. Google publishes a browser add-on that opts you out of Google Analytics on every site, available at tools.google.com/dlpage/gaoptout.

Block or clear cookies in your browser. Every major browser lets you delete existing cookies and refuse new ones, either for all sites or for this one. Refusing the strictly necessary cookies will stop sign-in from working, but the public site will still read normally.

Use a content blocker. Standard tracker-blocking extensions stop the analytics script from loading at all. Nothing on the site depends on it.

When you talk to an assistant embedded on a client's website, the only cookie we may set is the access cookie described above, and only where that assistant is access-controlled. We do not place analytics cookies through the embedded widget. The client's own website will have its own cookie practices, governed by their policy rather than this one.

When this policy changes we publish a new version with a dated entry in the revision history below, so you can see exactly what changed and when. The most likely change is the addition of a consent control, which will be an improvement rather than a reduction in your rights.