Cookie Policy

A few essential cookies and one analytics script. No advertising trackers, no cross-site pixels, no data broker tags. The consent banner therefore has a real “essential only” option that leaves the site fully working.

The session cookie that keeps you signed in; a short-lived state cookie while you sign in with Google or Apple, so the sign-in returns to where it started; and the locale cookie that remembers which of the six languages you chose. Your answer to the consent banner is kept in your browser’s local storage, so the banner does not ask again. For the tab only, and cleared once used, the sign-up keeps what it needs between its steps: that you accepted the Public Offer when you sign up with Google, the plan you chose on the site and the referral code in the link you followed; it may also keep which business’s booking page sent you. None of these can be switched off, because signing in and signing up do not work without them, and they are exempt from consent for that reason. Nothing about where you are is kept in your browser: the approximate country the pricing page and the trial buttons use is asked for on each visit and is written to neither a cookie nor local storage.

One analytics script, loaded only after consent, recording page views, referrer, approximate country and a few named steps — a price quote, a sign-up started or finished, a trial started, a message sent from the contact form — with the plan and country involved, never who you are. It sets no cookie. With consent, the first page of your visit and how you arrived there — the referring site and the campaign tags in the link — are kept in the tab’s session storage, so a sign-up can be credited to what brought it; that may include the business’s booking page that referred you. We use this to decide what to write and where the site loses people. The app’s sign-up screens ask the same question separately, because they are a different site.

A booking page on a business’s own address sets only the essential cookies. A guest manages a booking through the private link sent to them, not through a cookie. A booking page opened from Telegram keeps the launch data Telegram signs for it in the page’s memory only, never in the browser’s storage, so the page knows which Telegram account opened it. Analytics is not loaded on booking pages at all, because the visitor is your client rather than ours.

The footer has a cookie settings link on every page. Withdrawing consent stops the script immediately and clears its identifier. Your browser’s own controls also work; nothing here depends on cookies you cannot delete.