# Cookie Policy

_Last updated: 4 September 2026_

> This page lists every cookie landee actually sets — with its name, its lifetime and what it does. If you find a cookie from us that is not listed here, write to support@landee.app.

## In short

Cookies are small notes a site leaves in your browser and reads the next time you open it. Some of them are what makes the service work at all: staying signed in is a cookie remembering that you already signed in.

We split our cookies into three different things, and that is not a formality — the rules differ:

- **technical** — without them the service breaks;
- **audience measurement** — how many people opened a page, from which country, what they clicked; only the owner of that page sees these numbers;
- **set only after you agree** — A/B tests and third-party counters.

We show no ads and sell you to no one. None of the cookies below follows you across other sites.

## What landee sets

| Cookie | What it is for | Lifetime |
|---|---|---|
| `better-auth.*` | Signing in: remembers that you are signed in and protects forms from forged requests. The names start with `better-auth.` — the main one is `better-auth.session_token`. | sign-in session |
| `cookie-consent` | Your own answer to the banner: accepted or declined. Without it the banner would ask the same question every time. | 1 year |
| `landee-tz` | Your time zone. It makes "today" in reports your today, not the server's. | 1 year |
| `sidebar_state` | Whether the side panel in the app is collapsed or expanded. | 7 days |
| `nickname_hint`, `nickname` | The address you typed on the home page while you go and sign up. Without them the name you picked is lost on the way and the wizard asks for it twice. | 30 minutes |
| `UID` | Audience measurement: a random identifier so that opening the same page twice counts as one visitor, not two. It holds nothing about you and cannot be read on other sites. | 1 year |
| `SVID` | Audience measurement: one visit. After an hour without activity the visit is considered finished. | 60 minutes |
| `LABV` | A mark of `test id : variant letter` when a page takes part in an A/B test. It is set so that events are attributed to the variant you actually saw. It is not a person's identifier. | 1 day |

The `better-auth.*`, `UID`, `SVID`, `nickname_hint` and `nickname` cookies carry the `HttpOnly` flag — no script on the page can read them. All cookies are scoped to our domain and set `SameSite=Lax`.

## Why audience measurement works without consent

This is a deliberate decision, and we state it plainly rather than hiding it in fine print.

`UID`, `SVID` and `LABV` count visits to pages built with landee and show those numbers **only to the owner of that page**. They do not follow you across other sites, are not combined with data from other sources, and are neither shared nor sold. The longest of them lives a year — under the thirteen months European regulators treat as the ceiling for measurement of this kind.

It is exactly these limits that put such measurement on a par with strictly necessary cookies: it gives the page owner what a counter in the server log would give, only more accurately.

If you would rather not appear even in that count, blocking cookies in your browser works, and the page will not break because of it.

## What is set only after you agree

Until you press "Accept", none of this exists:

- **`LAB`** — a random seed used to split visitors between A/B test variants, 395 days. It is derived neither from your address nor from your browser — it is simply a random number. While there is no consent you see the control variant of the page and do not enter the test's measurement at all.
- **Google Analytics, Google Tag Manager, Meta** — counters a page owner may connect as their own. These services' scripts are not loaded until you agree; their cookies are set by them, not by landee, and live by their rules.

We deliberately do not derive the test variant from a device "fingerprint" — your address and browser name. Technically that would avoid the need for a cookie, but it is the same processing of your data, only less visible to you.

## How to withdraw consent

As easily as you gave it. The consent banner has a withdraw button: after it the `LAB` cookie is deleted immediately, and third-party counters stop loading the next time the page opens.

This right is written directly into Article 7(3) of the GDPR, and it must work without emails or requests.

## Cookies on pages built with landee

When you open someone's page on a `.landee.app` subdomain or on its author's own domain, the cookies are set by landee — on behalf of and for the needs of that page's author. The list is the same as above.

The author sees aggregate numbers only: how many people, from where, what they clicked. They receive neither your address nor your name.

If the author has connected their own Google Analytics or Meta, those are their tools and they work under those services' policies. We do not load them without your consent.

## How to block cookies in your browser

Every browser can block cookies or delete them on close — look for it in the privacy settings. Your email and password have nothing to do with it: this is a setting of your browser, not of your account.

One honest warning: with cookies blocked entirely you will not be able to stay signed in to landee. Public pages will keep opening normally.

## Changes and questions

We update this page together with the service itself: a new cookie appears — a new row appears in the table. The date at the top shows when the text was last changed.

Questions, objections or a mismatch you have found: support@landee.app.

This Policy supplements the [Privacy Policy](/i/privacy-policy) and the [Terms of Use](/i/terms-and-conditions).