Draft — last updated August 2026
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
llmconnect_session |
Keeps you signed in as you move between pages. Without it, you'd need to log in on every request. | Strictly necessary | Ends when your session expires or you log out |
llmconnect_remember |
Only set if you check "Remember me" at login. Lets you stay signed in after closing your browser. | Strictly necessary (opt-in via "Remember me") | 30 days, or until you log out |
Both cookies are set with HttpOnly (inaccessible to JavaScript, reducing exposure to
cross-site scripting), SameSite=Lax (limits cross-site sending), and Secure
once your deployment has SSL enabled. Neither is used for advertising, cross-site tracking, or building a
profile of your browsing outside LLM Connect.
Your browser also keeps a small amount of local data outside of cookies:
Some pages load web fonts from Google Fonts' CDN (fonts.googleapis.com). This is a direct
browser request to Google's servers, not something LLM Connect's backend sees — but it does mean Google
receives standard request information (like your IP address) for that font request, the same as loading
an image from any external site would. We don't control what Google does with that request. If this
matters for your deployment (e.g. you operate in a jurisdiction sensitive to this), the fonts can be
self-hosted instead — ask if you want that changed.
Video/audio calls use public STUN servers (Google's, by default — see Subprocessors) to help your browser establish a peer-to-peer connection. This is a technical requirement of WebRTC, not a cookie, and doesn't route your call content through Google.
Because both of LLM Connect's cookies are required for the login system to function, there isn't an in-app "reject" toggle — turning them off would mean you can't stay signed in. You can still block or delete cookies through your browser's own settings, but doing so will log you out.