Cookie notice
Last updated 27 April 2026. How we use cookies on glean.fit.
This notice sits alongside our Privacy Policy and Terms of Service.
Essential cookies only
Today, Glean relies on essential cookies and similar technologies that are strictly necessary to operate the service — for example to keep you signed in and to protect forms (including server actions) against cross-site request forgery. Strictly necessary cookies are exempt from the consent requirement under the Privacy and Electronic Communications (EC Directive) Regulations 2003 ("PECR") in the UK and the ePrivacy Directive in the EU.
We do not use non-essential analytics, advertising, or third-party marketing cookies in the current build. If we add them, we will update this page, revise the "Last updated" date, and — where required — show a consent mechanism before setting non-essential cookies.
Cookie list (essential)
| Name / category | Purpose | Duration |
|---|---|---|
| Session / auth (Better Auth) | Maintains your authenticated session after sign-in; HttpOnly where set by the framework. | Session or configured max-age |
| CSRF / same-origin (Next.js) | Validates that form submissions and server actions originate from our origin. | Session / request-scoped |
Exact cookie names may change with framework or auth library updates; purposes above stay accurate. Use your browser's developer tools to inspect cookies set on our origin.
Local storage and PWA
The installed PWA may cache application assets locally so the shell can load offline. That storage is functional (not used for cross-site tracking). Push notification preferences, if enabled later, will be explained here and in the Privacy Policy.