Cookies Policy

Cookies are small text files that a website asks your browser to store. Local storage is a similar mechanism with a larger capacity. Pixels are tiny image requests used for analytics. We refer to all of these collectively as “cookies” on this page.

• Essential. Always on — without them the Service can't function. These keep you signed in, remember your shopping cart of dates, secure forms against cross-site request forgery, and load balance traffic. Examples: Supabase auth cookies, CSRF tokens, the cookie that remembers whether the navbar is in light or transparent mode.
• Functional. Off-by-default in regions that require consent; on-by-default elsewhere. These remember non-essential preferences — recently viewed listings, the saved search filters, language and currency.
• Analytics. Off by default, everywhere. This category controls two things, and if you leave it off we load neither. First, browser error monitoring and session replay through Sentry: when you hit an error, we receive a replay of that session — all text and form inputs are masked and media is blocked, but the page structure, your navigation path, and the error details are sent so we can reproduce the fault. Second, product analytics through Vercel Web Analytics, which sets no cookies: we count page views (the address is cut down to the page path, keeping only campaign tags) and four steps — a search, the start of a checkout, a submitted booking, and a published listing — with only coarse details such as a result-count range, the number of nights, or the listing's ID. No name, email, or account ID is sent. We run no advertising tracker.
• Operational third parties. Some providers we rely on set their own cookies when their widgets render — Stripe (payment integrity, fraud prevention) and the map-tile provider (rate limiting). These are essential to the features they support. We also run Sentry on our own servers to catch backend errors; that never touches your browser and sets no cookie.
• Marketing. Currently not used — the Marketing toggle in the preferences dialog exists so your choice is already recorded, but nothing is set today. If we add marketing cookies in the future, they will only activate for users who consented, and we'll update this page first.

If you live in a jurisdiction with cookie-consent requirements (the EEA, UK, or others), the cookie banner that appears on first visit lets you accept or reject non-essential cookies. You can change those choices any time from the “Cookie preferences” link in the site footer.

Outside those jurisdictions, you can still control cookies through your browser's settings — most browsers let you block all cookies, block third-party cookies only, or clear them on exit. Note that blocking essential cookies will prevent the Service from functioning.

We honor Global Privacy Control (GPC) signals where applicable. We currently don't respond to legacy Do-Not-Track headers, since the standard was never widely adopted.

Questions about cookies? support@wheelhouse.mobile.