Cookie Statement
One cookie, eleven stored settings, and nothing that follows you anywhere. This page lists all of it by name, because a cookie statement that describes a category rather than naming the thing is a cookie statement nobody can check.
This document is a draft. It was written from what Leaves actually does rather than from a template, but it has not been reviewed or approved by anybody with legal responsibility, and nothing on this page binds you or us until it has been. Billing is not open, so nobody has been asked to agree to it either.
01 This site stores nothing §
The public site — these pages, at this domain — sets no cookies and puts nothing in your browser's storage. It uses Plausible Analytics for anonymous page views, referrers, countries and the two calls-to-action; there is no tag manager, embedded video or other tracking script.
The site ships no framework or hydration JavaScript. Its only executable code is the small theme switch and Plausible's plain measurement script. Plausible receives no names, email addresses or project content, sets no cookies and creates no persistent identifier.
So there is nothing here that needs a consent banner: the measurement is cookieless, does not identify people and keeps visitor data in the EU. Everything else below is about the application, which is a different host.
02 Cookies in the application §
The application sets one cookie.
sidebar_state
- Purpose
- Whether the navigation sidebar is expanded or collapsed, so it is the way you left it when you come back.
- Lifetime
- Seven days, renewed while you use the application.
- Kind
- First party. It holds one word, says nothing about you, and is never sent anywhere except back to the application that set it.
There is no session cookie beside it, which may be a surprise on a web application. Leaves signs you in with a token held in your browser rather than with a server session, so the cookie almost every other site of this shape sets is simply not set here.
03 What the application keeps in your browser §
Rather more lives in local storage, which is not a cookie and behaves differently in the way that matters: it is never attached to a request. Nothing in this list is sent to our servers, and no other site can read any of it.
It is listed anyway, in full, because it is yours. Two of the names below contain a placeholder in braces standing for a project or a section, so those two have one entry each per project you open.
refresh_token
- Keeps
- The token that keeps you signed in without typing your password again. It expires by itself — 7 days, or 30 if you asked to be remembered — and signing out removes it.
theme
- Keeps
- Light, dark, or whatever your operating system asked for.
locale
- Keeps
- Which language the interface is in.
density
- Keeps
- How tightly lists and tables are packed.
nameOrder
- Keeps
- Whether a person reads given name first or surname first.
dateFormat
- Keeps
- How dates are written out.
active_project_id
- Keeps
- Which project you had open, so the next visit starts where the last one stopped.
nav.{projectId}.{section}
- Keeps
- The last record you were reading in each section of a project, so returning to a list does not lose your place.
tree.{projectId}.{setting}
- Keeps
- How many generations the tree draws, how far siblings extend, and how children are sorted.
tree.canvas.poi
- Keeps
- Which person the tree canvas is centred on.
tree.canvas.viewport
- Keeps
- Where the tree canvas was panned and zoomed to.
04 Why there is no banner §
Dutch and European law require consent for anything stored on your device that is not strictly necessary for a service you asked for. They do not require consent for the rest, and they certainly do not require a banner in front of a site that stores nothing at all.
The cookie remembers whether a panel is open. The stored values are your own settings and the token that keeps you signed in, every one of them set because you asked for the thing it supports. Plausible measures only anonymous public-page and funnel events, without cookies or persistent identifiers; there is no advertising, heatmap or feature analytics anywhere in Leaves. The sub-processors page is the whole account of who is involved.
A banner would therefore be asking your permission for something we do not need permission for, about measurement that sets nothing and identifies nobody, in order to look compliant.
05 Clearing it §
Signing out removes the token and the values that belong to a session. Clearing site data for the application's domain in your browser removes everything listed here; the application will simply start again with its defaults and nothing is lost but your preferences.
The cookie has a seven-day life and renews as you use the application, so leaving it alone is enough to let it lapse.
Deleting your account removes all of it from our side as well, with the effect clause 5 of the Privacy Statement describes.