Cookie policy

This site sets four cookies of its own: pb-consent (your choice), pb-region (whether we ask first), pb-attr (the campaign that brought you) and pb-exp (a page-test bucket). Google's analytics cookies are set only after you choose Allow in the European Union, the European Economic Area, the United Kingdom and Switzerland; elsewhere analytics runs until you decline it in Cookie settings.

Which cookies does the site set itself?

pb-consent holds your choice, granted or declined, for 365 days from the day you make it. pb-region holds eu or other, the result of the one region check, for 7 days, so the check is not repeated on every visit. pb-attr holds, for 90 days, what the link you arrived by already said: the utm parameters and ad click ids in its address, the site that referred you, the page you landed on and the time, for your first visit and your latest one; when you send a form or book a session that record is attached to it so we know which campaign brought you. pb-exp holds a number from 0 to 99 for 365 days, so a page we are testing in two versions shows you the same version each time. pb-attr and pb-exp are set only where analytics may run: outside the regions above by default, inside them after you choose Allow. None of the four identifies you, and none is read by anyone but this site.

Signing in to the demo platform sets Supabase's session cookies (their names start with sb-), which hold your login and are read only by our server. The assistant in the corner of the page and the demo dashboard keep a few values in your browser's session storage for the tab (a conversation id, a mute setting, a welcome flag); those are not cookies and are not sent to us.

When does the consent banner appear?

Only when no pb-consent cookie exists and the country of your connection is in the European Union, the European Economic Area, the United Kingdom, or Switzerland. The banner offers Allow and Decline and links here. Until you choose, analytics stays off. Outside those regions no banner is shown.

What runs when you allow analytics?

The Google tag loads Google Analytics, which measures page views and which calls to action are clicked: booking, phone, text, form, demo, and guide events. Google sets its own cookies for that, documented by Google. The consent signal we send Google covers analytics storage, ad storage, ad user data, and ad personalization together; Allow grants all four, Decline denies all four. If your browser sends the Global Privacy Control signal, the three advertising signals are denied whatever you choose here.

What runs without asking?

Outside the regions above, the same Google analytics runs by default, and so do pb-attr and pb-exp. On the live deployment, Vercel's analytics and speed measurement scripts also run, under Vercel's privacy policy; they set no cookies. The Cookie settings control at the bottom of every page opens the same Allow and Decline choice for you wherever you are.

What about embedded content?

Embedded videos load from YouTube in privacy-enhanced mode (youtube-nocookie.com); YouTube's own policy covers what it stores when you play one. The map on the Evansville page is an embed served by Google and may set Google cookies when it loads.

How do you change your choice?

Use the Cookie settings control at the bottom of any page: it opens the Allow and Decline choice again, wherever you are, and your new choice replaces the old one. Deleting the pb-consent cookie in your browser has the same effect on your next visit; deleting pb-region only repeats the region check.

How do we change this policy?

We post the new version here with a new effective date.