Version 2026-08-05.1
Last updated: 5 August 2026
This Cookie Policy explains how we use cookies and similar technologies on the Service. It should be read with our Privacy Policy.
We use two categories: essential technologies required to run the Service, and optional analytics used only if you choose Accept all on our cookie banner.
Clerk authentication cookies and security tokens (when you sign in).
Locale preference storage (`bc-locale`) after you accept essential cookies (or Accept all).
Cookie consent record in local storage (`bc-cookie-consent-v1`), including whether analytics was accepted.
Account Terms version cookie (`bc-terms-version`) after you accept account Terms while signed in.
Signed-in app data in local storage (events, showroom, sync outbox, UX flags) required for the planning workspace.
These are needed for security, preferences you choose, and core product features. They are not used for advertising.
Only if you select Accept all: we set a first-party visitor id cookie (`bc-visitor-id`) and an analytics flag cookie (`bc-analytics`).
We then record approximate visit location (country and city derived from your IP address on our servers), the page path, locale, a hashed form of the IP (not the raw IP), and—when you are signed in—your Account user id. Records are stored in our Bunny database for internal analytics about where visitors come from.
This processing is based on your consent (GDPR Art. 6(1)(a)). You can choose Essential only to refuse analytics. Clearing site data or declining analytics stops new analytics cookies; previously stored events may remain as described in the Privacy Policy.
The Google Maps JavaScript API may load on authenticated event address flows (or when essential consent allows Maps on shared flows) to provide autocomplete and map pin features. It is not an advertising cookie and is not used for visit country/city analytics.
Use the cookie banner choices when shown. You can clear site data in your browser to remove local consent and visitor cookies; the banner may appear again after a policy version change.
Policy version: 2026-08-05.1.