Cookie policy
One cookie. It keeps you signed in.
No advertising network, no cross site pixel, no session replay. This page exists so you can verify that in under a minute instead of taking our word for it.
- Last updated
- 14 February 2026
- Cookies set
- 1 (strictly necessary)
- Third party scripts
- 0
- Consent banner
- Not required
The short version
We set one cookie. It keeps you signed in. There is no advertising network on this site, no cross-site tracking pixel, and no third party analytics script loading in the background while you read.
That is not a marketing position, it is a practical one. We sell a product to security teams. Loading nine trackers on the page where we explain trust boundaries would be a difficult conversation.
If you are here because a cookie banner sent you and you wanted the list, it is the single row in the table below. You can close this tab with a clear conscience.
Exactly what is stored
The cookie is set with HttpOnly so browser scripts cannot read it, SameSite=Lax so it is not sent on cross-site requests, and Secure in production so it never travels over plain HTTP.
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
| sentryllm_session | Holds an opaque session token so the console knows which workspace you are in. It contains no personal data, only a random string that maps to a row in our sessions table. | Strictly necessary | 14 days, or until you sign out |
Local storage and similar technologies
The marketing site uses none. The console stores nothing in local storage that survives a sign out. Your sidebar state and the trace replay position live in memory for as long as the tab is open and are gone when you close it.
We do not use web beacons, fingerprinting, or session replay tooling. If we ever add product analytics we will list the vendor here before we turn it on, not after.