Cookie policy
This list was made by reading the code. 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 |
That is all. The site has no analytics, no advertising, no embedded third-party content, no social media buttons, and no fonts or scripts loaded from other companies. The pages themselves make no third-party requests.
2. The app (self-hosted today, and the hosted service when it opens)
The hosted service is not open yet. This section describes what the open-source app does today; the hosted service is planned to run the same code, and anything it would add is listed separately below.
Cookies
| Name | Purpose | Lifetime | Notes |
|---|---|---|---|
glideworth_session |
Keeps you signed in. Holds a random token; the server stores only a hash of it | The length of your session (7 days by default, set by the server’s operator) | Strictly necessary. HttpOnly, SameSite=Strict, Path=/, and Secure when the page is served over HTTPS |
glideworth_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 |
Before the product was renamed to Glideworth, the same cookies were called cairn_session and cairn_csrf. The app
still accepts them, so a sign-in from before the rename stays valid. The next time the app loads and checks that you
are signed in, it replaces them with the names above and deletes the old ones. Signing out deletes both sets.
Local storage
The app stores these on your device. 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 |
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-party code that runs on server pages
- API reference page. The interactive API reference that every server serves at
/docsloads its viewer script from the jsDelivr content delivery network, so jsDelivr sees your IP address when you open that page. Signed-in app screens do not do this. The static API reference on this website loads nothing from other companies. We plan to remove this request before the hosted service opens, and will update this page when we do.
Planned for the hosted service (not built yet)
These are not in the code today. They are listed so that the policy is ready when the hosted service opens.
- A device cookie (
__Host-gw_device, planned name) that recognises a device you have signed in from before, so we can email you when a new device signs in. It lasts up to 90 days and is used only for that security alert. You could turn sign-in alerts off in settings, and the cookie would then not be needed. - Two short-lived cookies for “Continue with Google”, set only if you use that button.
__Host-gw_oidcties a 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). It holds a random value; the server keeps the details of the sign-in, encrypted. It lasts 10 minutes at most and is deleted as soon as Google sends you back. It is SameSite=Lax (not Strict) because it must be sent when Google returns you to our site; it is also HttpOnly, Secure and limited to our host.__Host-gw_oidc_signupis set only if you are new: it holds a random value that lets your browser finish creating the account (name, age confirmation, terms) after Google. It lasts 15 minutes at most and is deleted when the account is created. Both are strictly necessary for a sign-in you asked for. Google itself sets its own cookies on its own pages under its own policy; the app does not load anything from Google. - A bot check at sign-up. On sign-up, password reset and, after several failed attempts, sign-in, a bot-protection widget from Cloudflare (Turnstile) would check that you are a person. It would receive your IP address and browser signals. See the sub-processor list. Anything it sets on your device is used only for that security check. Before the hosted service opens we will test exactly what it sets and list it here. If it set anything that needs your consent, we would ask first or stop using it.
- Payment pages. When you subscribe or manage billing, you would be sent to pages hosted by our payment provider. It sets its own cookies there, under its own policy.
3. Why there is no consent banner
The UK and EU rules on cookies and similar technologies (PECR and the ePrivacy Directive) require consent for storage on your device unless it is strictly necessary to give you 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 cookie and the bot check exist only to keep your account secure. The remaining storage keeps your own settings and drafts for you, and the website’s theme choice is set by you. We use no advertising or analytics technology. So we do not show a banner. If we ever add anything that needs consent, we will ask for it before it is set, and you will be able to refuse.
4. 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.
5. Questions
privacy@glideworth.com. See also the privacy policy.