LUXURYSTAGEHAUS← Back to home

Legal

Cookie Policy

Effective 2026-01-01

This page explains the cookies and similar local-storage entries LuxuryStageHaus uses, what they do, and how you can control them. We pair this with the Privacy Policy.

1. Categories

Strictly necessary (always on)

These are required for the Service to work. We can't turn them off:

  • Authentication (Clerk session cookies) — to keep you signed in.
  • UI locale (lume_ui_lang) — remembers your chrome language across pages.
  • Cookie-banner choice (lsh.cookie-consent in localStorage) — so we don't ask you again next visit.
  • Anonymous session id (ll.session in localStorage) — groups your scroll milestones into one visit, only fires if you allowed analytics.
  • Dashboard helpers (ll.dashboard.lastSeenSubmitted in localStorage) — drives the “new submission” badge.

Analytics (consent-gated)

Our first-party page analytics fire only when you click Accept all in the cookie banner. They count page views, scroll milestones, and language toggles on published listing pages. No third-party trackers, no cross-site identifiers, no advertising cookies. Visitor IPs are salted-hashed before storage and used only to soft-dedupe traffic.

If you click Necessary only, the analytics call is suppressed entirely — no event reaches our server.

2. Third parties

  • Clerk — sets a small number of cookies to manage your authenticated session. See Clerk's privacy notice for specifics.
  • Vercel — our hosting provider may set its own functional cookies for routing and CDN cache purposes.

We do not use third-party advertising networks. We do not embed Google Analytics or comparable services.

3. How to control cookies

  • Use the LuxuryStageHaus cookie banner that appears on first visit to accept or limit non-essential analytics.
  • Clear cookies and local storage in your browser settings to reset your choice (the banner will reappear).
  • Configure your browser to block third-party cookies; the Service will still work, though some Clerk-related flows may need adjustment.

4. Changes

We'll update this page if we change which cookies we use. The list above mirrors the application source — when we add or remove a cookie, the documentation moves with the deploy.

5. Contact

Questions: privacy@luxurystagehaus.example.