Cookie Policy

Strictly necessary (no consent required):

• essenzi_session, an HttpOnly session cookie that keeps you authenticated and signed in. Essential for the Service to function; it cannot be declined while using the Service. Because it tells our server who is making a request, our server also notes the day of a signed in visit and any checkout you start, as described in Sections 2 and 3 of our Privacy Policy (Service journey records). That record is kept on our server; nothing further is stored on your device for it, and you can object to it at any time.
• essenzi_signed_in, a companion to the session cookie that says only that one is present (its value is "1"). It holds no information about you or your account, and our server never uses it to decide what you can see or do. Our pages read it so that they ask our server who is signed in only when someone may be, so a signed-out visit makes no such request. It is set when you sign in, lasts no longer than your session (at most 7 days), and is removed when you sign out or your session ends.
• Security / fraud-prevention tokens (e.g. CSRF or rate-limiting state) where used, are strictly necessary.
• Stripe, when you reach checkout or billing pages, Stripe may set cookies that are strictly necessary for secure payment processing and fraud prevention.
• hoe_internal, set only in the browsers of House of Essenzi staff, so that our own visits are left out of our measurement and advertising figures. It holds no information about you and is never set for customers.

Non-essential (enabled only with your consent):

• Vercel Analytics and Speed Insights, privacy-friendly, cookieless product and performance analytics that measure aggregate page views, usage and Web Vitals without setting tracking cookies or identifying you individually. Although both are cookieless, we load them only after you accept non-essential cookies.
• Sentry (error monitoring & session replay), captures diagnostic information when errors occur to help us keep the Service reliable, and can record a replay of the affected browser session when an error occurs. In the replay all text and all form inputs are masked and images, video and other media are blocked, so it shows the layout of the page and what was clicked, not the text on it. A replay is not anonymous, so we treat it as personal data. Session replay is enabled only after you accept non-essential cookies; until then, replay is switched off.
• Google Tag Manager & Google Ads, Google Tag Manager loads our measurement and advertising tags, including the Google Ads tag used for conversion and remarketing audiences. These tags run under Google Consent Mode v2: by default all advertising and analytics storage is denied, so no analytics or advertising cookies are set and only Google's cookieless pings are sent. When you accept non-essential cookies we update the consent signal to granted, enabling analytics and ads-measurement cookies; if you decline, the denied default remains.
• Meta Pixel, measures which of our adverts bring people to the House, and sets Meta's _fbp and _fbc click cookies. Meta has no Consent Mode equivalent, so the Pixel is not loaded at all until you accept; declining means it never runs.
• Plausible Analytics, aggregate page-view measurement that sets no cookies and builds no cross-site identifier. As with Vercel, we load it only after you accept non-essential cookies.
• Sign-up marker, a first-party value (hoe_signup) set for 15 minutes when you create an account with Google, and only if you have accepted non-essential cookies, so that the sign-up is counted once in our measurement. It is deleted as soon as it has been read.
• Consent record, a first-party value (essenzi-consent) storing whether you accepted or declined non-essential cookies, so we can honour your choice on return visits.