Cookie Policy
Laysa sets four cookies. Three keep you signed in; the fourth remembers a choice you made on the sessions page. None is used for advertising, and none profiles you.
There is no cookie banner, and that is deliberate.
A banner exists to collect consent for cookies that need it. Laysa sets none of those, so there is nothing to consent to and nothing to click away. Product analytics run without cookies and without cross-site identifiers. If that ever changes, the banner arrives before the cookie does — not after.
The four
| Cookie | What it is for | Lifetime |
|---|---|---|
| __session | Keeps you signed in — it carries the session itself | Refreshed as you use Laysa, and never longer than 7 days |
| __client_uat | Tells the page whether a sign-in exists, before it loads | 1 year |
| clerk_active_context | Remembers which account a request belongs to | Until you close the browser |
| laysa_sessions_view | Remembers whether you left your sessions on the calendar or the list | 1 year |
You may also see a copy of the first three carrying a short suffix. That is how a browser keeps two Laysa environments apart; each copy holds the same thing, for the same time, as the one it doubles.
Signing in also keeps one entry in your browser's local storage, __clerk_environment: the sign-in service's own settings, nothing about you. It is strictly necessary in the same way as the first three cookies.
Blocking them in your browser is your right and it will stop you signing in, which is the honest consequence rather than a threat.