Cookie policy
Last updated
This list was made by reading the code and checked in a browser on 17 November 2026. If we add anything, we will update this page first.
1. The marketing website (glideworth.com)
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
theme |
Local storage (not a cookie) | Remembers whether you picked light or dark. Written only when you press the theme button. | Until you clear your browser data |
The pages also load Google Tag Manager from www.googletagmanager.com. The official
hosted website is built with a container id; a self-hosted copy is not, unless you set one
yourself. The container measures page views with Google Analytics. Until you accept in the banner,
Google is instructed not to write any analytics or advertising cookie, though loading the script
still sends your IP address and the page address to Google. The calculator pages, where you type
figures, do not load the tag, and the signed-in app does not either.
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
glideworth-consent
|
Local storage (not a cookie) | Remembers whether you accepted or rejected analytics cookies, so the banner does not ask again. | 12 months, then the banner asks again |
_ga, _ga_*
|
Cookie (Google Analytics) | Counts visits and pages viewed. Set only after you accept analytics cookies. | 2 years |
2. The hosted app (app.glideworth.com)
Cookies
All of these are set by our own server, only for app.glideworth.com, and only over HTTPS (__Host- cookies,
Secure). None of them is used for tracking or advertising.
| Name | Purpose | Lifetime | Notes |
|---|---|---|---|
__Host-gw_session |
Keeps you signed in. Holds a random token; the server stores only a hash of it | Up to 30 days. The server ends the session sooner after 7 days without use, or when you sign out | Strictly necessary. HttpOnly, SameSite=Strict |
__Host-gw_csrf |
A second token the app sends back with every change, to stop other websites making changes for you | Same as the session | Strictly necessary. SameSite=Strict. Readable by the app’s own script, by design |
__Host-gw_device |
Recognises a browser you have signed in from before, so that a sign-in from a new device is recorded in your security log and, if you keep sign-in alerts on, emailed to you. Holds a random value; the server stores only a keyed hash of it | Up to 400 days | Security only. HttpOnly, SameSite=Strict |
__Host-gw_signup |
Set when you sign up. Lets the verification link sign you in only in the browser where you chose your password; in any other browser you must enter the password too | Up to 48 hours, as long as the verification link | Security only. HttpOnly, SameSite=Lax, so it is sent when you arrive from your email |
Only if you use “Continue with Google”:
| Name | Purpose | Lifetime | Notes |
|---|---|---|---|
__Host-gw_oidc |
Ties a Google sign-in you start to your browser, so that someone else’s Google sign-in cannot be finished in your browser, and yours cannot be finished in theirs. Holds a random value; the server keeps the details of the sign-in, encrypted | 10 minutes at most. Deleted when Google sends you back | Strictly necessary for a sign-in you asked for. HttpOnly. SameSite=Lax, because it must be sent when Google returns you to us |
__Host-gw_oidc_signup |
Set only if you are new. Lets your browser finish creating the account (name, age confirmation, terms) after Google | 15 minutes at most. Deleted when the account is created | Strictly necessary. HttpOnly, SameSite=Strict |
__Host-gw_oidc_link |
Set only when you link Google to an existing account from your security settings. Holds the pending link until you confirm it | 10 minutes at most | Strictly necessary. HttpOnly, SameSite=Lax |
Google sets its own cookies on its own pages, under its own policy. The app does not load anything from Google; the button is a plain link.
Local storage
The app stores these on your device. Apart from the PostHog identifier, none of them is sent to a third party. Some hold the figures you typed.
| Key | What it holds |
|---|---|
glideworth-ui |
Your display choices: theme, density, reduced motion |
glideworth-prefs and glideworth-chart-prefs |
Interface preferences, such as chart options and tour progress |
glideworth:settings:v1 |
A local copy of your settings |
glideworth:drafts:v1: followed by a household id |
Unsaved edits to a plan, kept so you do not lose them if the page reloads or you go offline. This can contain figures you entered |
glideworth:chart-views:v1: followed by a plan id |
Chart views you saved |
glideworth:sample-doc:v1 |
The sample household, if you used it |
ph_ followed by the PostHog project key |
Hosted app only: PostHog’s random identifier for your browser and its analytics settings, sent to PostHog with each analytics event (section 3) |
glideworth.handoff.v1 |
Only if you came from one of the calculators on this website: the numbers you entered there, so the app can offer to start your plan with them. Removed once you use or decline them, and ignored after 7 days |
Older versions used the same keys starting with cairn (cairn-ui, cairn:drafts:v1: and so on). When the app
starts it copies each old key to its new name and removes the old one, so your settings and drafts carry over.
Cache storage
The app registers a service worker that keeps a copy of the app’s own files in your browser’s cache, so the app opens quickly and can load offline. It holds the program files, not your plans.
On a shared computer, use the “erase local data” control in settings, or clear your browser data, when you finish.
Third parties on app pages
- Bot check (Cloudflare Turnstile). On sign-up, password reset, and sign-in after several failed attempts, the app loads a bot-protection widget from Cloudflare (challenges.cloudflare.com) that checks you are a person. Cloudflare receives your IP address and browser signals. See the sub-processor list. In our check on 17 November 2026, loading the widget in a fresh browser set no cookies, for our site or for Cloudflare. Cloudflare’s own cookie policy applies to anything it stores inside its widget; it lists its challenge cookies as strictly necessary. The widget is not loaded on other pages.
- Payment pages. When you subscribe or manage billing, you go to pages hosted by Stripe, our payment provider. Stripe sets its own cookies there, under its own policy.
3. Analytics and advertising
The marketing website uses Google Analytics, through Google Tag Manager, to count visits (section 1). Its cookies are set only if you accept them in the banner. It sets no advertising cookies. The hosted app (app.glideworth.com) uses PostHog for product analytics and error reports: which pages and features are used, and errors in the app. It keeps a random identifier in local storage under a key starting with ph_, sets no cookie, records no sessions and masks the text of what you click. Signed-in users are linked to their account id and email address. The free calculators and a self-hosted copy load no analytics, advertising or session-recording tools.
4. If you run Glideworth yourself
The self-hosted app uses the same local storage and cache as above. Its sign-in cookies are named
glideworth_session and glideworth_csrf (formerly cairn_session and cairn_csrf, which it still accepts and
replaces), and it does not set the device, sign-up or Google cookies. It has no bot check. Its interactive API
reference at /docs loads its viewer from the jsDelivr content delivery network, so jsDelivr sees your IP address
when you open that page. The hosted service’s API reference does not.
5. Consent
The UK and EU rules on cookies and similar technologies (PECR and the ePrivacy Directive) require consent before storage on your device, unless the storage is strictly necessary to provide something you asked for. The sign-in and anti-forgery cookies are strictly necessary, and so are the Google sign-in cookies, which exist only while a sign-in you started is in progress. The device and sign-up cookies and the bot check exist only to keep your account secure. The remaining storage keeps your own settings and drafts, and the website's theme choice is set by you. Google Analytics cookies on the marketing website are not strictly necessary, so the website asks first: they are set only after you press "Accept analytics", and "Reject" is just as easy. Advertising storage is never granted. You can change your answer at any time with "Cookie settings" at the foot of any page, and the website asks again after 12 months. The hosted app's PostHog identifier (section 3) is analytics storage too, and there is no consent prompt for it yet.
6. Your choices
You can block or delete cookies and local storage in your browser. If you block the sign-in cookies you cannot use the app. The website works without any storage.
7. Questions
privacy@glideworth.com. See also the privacy policy.