Skip to content
LAVESSO

Legal

Cookie policy

Last updated 13 November 2026

This policy lists every cookie and every kind of browser storage that LAVESSO's website and app use on lavesso.com and its subdomains.

Contents

  1. In short
  2. Cookies we use
  3. Local storage and other browser storage
  4. Other websites
  5. Managing cookies
  6. Changes to this policy
  7. Contact

In short

LAVESSO uses only cookies that are strictly necessary to sign you in, keep you signed in and protect sign-in from attack. We do not use analytics, advertising or tracking cookies, and we do not load third-party scripts that set them. Because every cookie is strictly necessary, the law does not require us to ask for consent and we do not show a cookie banner. If that ever changes, we will ask before setting any other cookie.

If you only read the website and do not start signing in, LAVESSO sets no cookies at all.

Cookies we use

All of these are first-party cookies set by LAVESSO. JavaScript in the page cannot read them (HttpOnly), they are sent only over secure connections (Secure) and they are not sent with requests started by other websites, except when you follow a link to LAVESSO (SameSite=Lax). Names starting __Host- are locked to the exact LAVESSO host that set them.

LAVESSO cookies
NamePurposeTypeLifetimeParty
__Host-lavesso-auth-currentRemembers which signed-in session on this browser is the current one.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.The length of a signed-in session: currently 12 hours, never more than 30 days. Removed when you sign out.First party (LAVESSO)
__Host-lavesso-auth-session-<session id>Keeps you signed in. Holds your sign-in session from Supabase. Large values are split into numbered parts ending .0, .1 and so on.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.The length of a signed-in session: currently 12 hours, never more than 30 days. Removed when you sign out.First party (LAVESSO)
__Host-lavesso-auth-flow-<flow id>-code-verifierHolds a one-time security code (PKCE verifier) that links an email link or provider sign-in back to the browser that started it.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.Until that sign-in completes or is replaced; never longer than the session limit above.First party (LAVESSO)
__Host-lavesso-auth-flows-code-verifierLists the sign-ins started on this browser that are still waiting to complete, so each one finds its own security code.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.Until the waiting sign-ins complete; never longer than the session limit above.First party (LAVESSO)
__Host-lavesso-auth-code-verifierA copy of the security code for the most recent sign-in, for links that do not carry their own flow reference.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.Until that sign-in completes; never longer than the session limit above.First party (LAVESSO)
__Host-lavesso-google-flowHolds the sign-in state, a one-time number (nonce) and the security code (PKCE verifier) for a Google sign-in, so only the browser that started it can finish it. Removed when the sign-in finishes.Cookie (HttpOnly, Secure, SameSite=Lax). Strictly necessary.10 minutesFirst party (LAVESSO)

Local storage and other browser storage

LAVESSO does not use local storage, session storage or IndexedDB on lavesso.com. Drafts and appearance choices in the workspace are kept only in the open page and are lost when it reloads.

When error reporting is switched on, our error reporting service (Sentry) is loaded with session tracking, session replay, feedback and offline caching turned off. It sets no cookies and stores nothing in your browser.

Other websites

If you sign in with Google, or pay for prepaid credit by card, you briefly go to Google's sign-in pages or to Stripe's checkout page at checkout.stripe.com. Those companies set their own cookies on their own websites under their own cookie policies. LAVESSO's pages do not load scripts from them.

Managing cookies

You can see and delete cookies in your browser settings. If you block or delete LAVESSO's cookies, you will be signed out and will not be able to sign in until you allow them again. The website still works without them.

Changes to this policy

We update this policy whenever we add, remove or change a cookie. The date at the top shows the latest version.

Contact

Questions about cookies: support@lavesso.com. See also our privacy policy.

  • Privacy
  • Terms
  • Cookies
  • Acceptable use
  • Subprocessors
  • Contact