Cookies

A banner at the bottom of the page asks before Google Analytics or the Meta pixel loads. Accept allows both. Reject keeps both off. We store that choice in a first-party cookie named de_cookie_consent for one year. The cookie is only the word accepted or rejected. It is not used for advertising.

Change the choice later from Cookie settings in the footer, or from this page: Cookie settings.

You can also block or delete cookies in your browser. Google and Meta offer their own measurement controls in their account settings. Blocking cookies does not stop you reading the site.

Google Analytics, measurement ID G-5D8MR56JEN, loads only after you accept. Google then sets cookies such as _ga and _ga_* to tell new visits from returning ones and to count which pages are opened. IP addresses are processed by Google as part of that measurement. If you reject, this script does not load.

A Meta (Facebook) pixel loads on the marketing pages only after you accept. Meta may then set _fbp. If you arrive from a Meta ad, _fbc may also be set. We use this to see which campaigns lead to a waitlist join or a reservation, and the browser can fire a checkout event when someone starts a reservation payment. If you reject, the pixel does not load and those events are not sent from the browser.

A waitlist join or a successful payment can still send a conversion event from our server to Meta. That is described on the privacy page and is separate from this pixel.

If you later sign in to the product, the auth provider (Supabase) sets its own cookies so the session stays logged in. The public marketing pages do not set those, and the cookie banner does not control them.

We do not use cookies to sell personal information, and we do not embed third-party advertising on the page.