Cookies

We use as few cookies as possible, only those that are technically necessary to run this site. No tracking cookies, no advertising cookies, no analytics cookies. (How we count internally, without cookies: privacy policy, section 5.)

Which cookies we set

tb_session

Stores your sign-in state after a successful sign-in (sign-in link or Google). Duration: 30 days. Technically necessary: without it you would have to re-authenticate on every page load. HttpOnly + SameSite=Lax.

tb_claim

Set when you request a sign-in link; ties the link to the browser you requested it from, so clicking it logs in the right browser. Duration: 15 minutes, then deleted automatically (also removed the moment you sign in). Technically necessary for the login flow. HttpOnly + SameSite=Lax.

tb_oidc

Set only when you click “Sign in with Google”; links Google's reply to your click (with one-time check values), so nobody else can slip their sign-in into your browser. Duration: 10 minutes, deleted the moment you are back from Google. Technically necessary for signing in with Google. HttpOnly + SameSite=Lax.

tb_passkey

Set only when you add a passkey or sign in with one; links your device's reply to your click (with a one-time check value), so a reply cannot be replayed from another browser. Duration: 5 minutes, path /api/passkey, deleted once the step is done. Technically necessary for passkeys. HttpOnly + SameSite=Lax.

tb_lang

Stores your language preference (DE/EN). Duration: until the end of your browser session. Technically necessary for personalization: without it the page would reset to the default language on every new page within a visit. It is only set when you actively switch the language or choose "Stay in English" on a page opened in English, so it records a setting you explicitly requested. A cookie set before this change keeps its old expiry date, at most one year from the last switch. The next time you switch, we replace it with the session cookie.

tb_consent

Records that you made a choice in the cookie notice, so it doesn't reappear on every visit. Duration: 1 year. Which choice you made ("Accept all" or "Accept necessary only") is stored in your browser's localStorage (see below), not in the cookie itself. Technically necessary: a record of your consent choice is itself exempt from consent. Set only once you pick an option in the cookie notice or save your choices in the cookie settings.

Local storage (browser)

We use the browser's localStorage to:

• Auto-save your form drafts while you configure a trip, also before you sign in (so a reload or signing in doesn't lose your work).
• Remember which cookie choice you made (the tb_consent cookie above only records that a choice exists).
• Remember your display preference (light/dark theme).
• Remember which hotel you picked for each stop in a report (“I'll take this one”), so your choice is still there the next time you open the report on this device.
• Remember which guided tours with our mascot Tibo you have seen or declined, so he does not ask again, and whether he should only peek in from the edge.

The data in this list stays in your browser and is never sent to us. The chat with Tibo is different, see below.

On the pricing page we also use the browser's sessionStorage to remember a valid creator code (discount code) until you close the tab, so you don't have to enter it again.

Chat with Tibo

When you are signed in, you can ask our mascot Tibo general questions about your trip in the trip form and in your briefing. For that we use your browser's storage as follows:

• History of the Tibo chat (your questions and Tibo's answers), per tab: it survives a reload and ends when you close the tab (sessionStorage).
• Tibo's notepad in the trip form, per tab (sessionStorage). When you start the search, it moves over to the briefing.
• Tibo's notepad for each of your briefings, until you delete it (localStorage).

The notepad is a short list that our server creates from the chat: destinations, dates, nights, budget, location, amenities and the number of children (without their ages). It carries a signature from our server and the ID of your account.

Unlike the data above, the chat does not stay in your browser alone. With each new question your browser sends the notepad and questions and answers from the history back to us. We pass the notepad and your last two questions with Tibo's answers on to Anthropic together with your question, so that Tibo knows the context (privacy policy, section 6). Without a valid signature we discard them. We store none of it on our server.

Deleting: the delete button at the chat in your briefing clears notepad and history. The next time you open the trip form, your browser deletes notepads for briefings that no longer exist in your account. Stored chat data of another account, or of an account that has signed out, is deleted the next time you open the trip form.

Notice, consent & settings

Under §165 TKG 2021 and the GDPR, consent is only required for non-essential storage access (analytics, ads, profiling). All cookies listed above are technically necessary and therefore exempt, and we currently use no non-essential storage at all.

On your first visit you still see a notice with two equally prominent buttons, "Accept all" and "Accept necessary only". Today both lead to the same result, because there is no optional category to switch on. The notice stays in place as a precaution: should we ever introduce statistics or marketing cookies, they stay off until you agree in an updated notice. Legal pages (like this one) don't show the notice, so you can read them undisturbed.

Maps in reports need no consent either. Our server fetches the map image and delivers it from our own server, so your browser never contacts a map service and your IP address is not transmitted to any map provider.

Via Cookie settings in the footer you can review and change your choice at any time.