Cookie Policy

What a cookie is

A small file a site stores in your browser, and the similar tools that work the same way.

What this site keeps without asking

The site sets no cookie of its own. Your browser keeps your answer to the question about cookies for 365 days. It keeps your pause of the moving photographs until you start them again. Until you close the tab it keeps the country of the page you opened last and what you selected on a page: a package, a card, a figure in a calculator.

What runs without your answer

Two things run before you answer, and go on if you choose Only necessary. Neither sets a cookie or reads one.

• Ahrefs Web Analytics, run by Ahrefs, counts page views. It uses no cookies and no identifier that stays in your browser, and it does not follow a visitor from one day to the next.

Google's tags for Google Analytics and Google Ads load with every permission set to denied. In that state they send Google signals without cookies: one for each page you open and for what the site counts there, such as a request you send. A signal can carry the time, your browser, the address of the page and of the page you came from, whether you arrived by a click on an ad, your answer about cookies as yes or no, and a random number made for that page load. With these signals our reports estimate the visits and requests that were not counted.

Statistics, only if you agree

Contentsquare and Mouseflow load only after you switch Statistics on, and only then does Google Analytics set its cookies and count your visits with them. These tools show us how the pages are read.

• Google Analytics 4, run by Google, counts visits and what visitors do on a page. Cookies on this site: _ga (2 years), _ga_<container-id> (2 years).
• Contentsquare, run by Contentsquare, records how a page is scrolled and clicked. Cookies on this site: _cs_id (13 months), _cs_c (13 months), _cs_s (30 minutes).
• Mouseflow, run by Mouseflow, records how a page is scrolled and clicked. Cookies on this site: mf_user (90 days), mf_<website-id> (until you leave the site).

lg-msgr, in local storage in your browser: the reference code of your visit, added to a message you send us by WhatsApp, Telegram or email. It stays for 3 months, and it is removed when you refuse statistics.

lg-sid, in local storage in your browser: a random identifier of your browser, kept with the reference code so that one visitor gets one code. It stays for 3 months, and it is removed when you refuse statistics.

lg-src, in session storage in your browser: the address you came from, the first page you opened and its campaign labels, sent with a request you send us. It stays until you close the tab, and it is not kept when you refuse statistics.

Marketing, only if you agree

The LinkedIn tag and the Meta pixel load only after you switch Marketing on, and only then does Google Ads set its cookies. These tools show us which ads bring visitors, and the three companies can show our ads to people who have been here. Each of them also reads the cookies it keeps under its own address.

• Google Ads, run by Google, counts the visitors an ad brought and what they did here. Cookies on this site: names that start with _gcl_ (90 days).
• LinkedIn Insight Tag, run by LinkedIn, counts the visitors an ad on LinkedIn brought. Cookies on this site: li_fat_id (30 days), li_giant (7 days), ln_or (1 day).
• Meta pixel, run by Meta, counts the visitors an ad on Facebook or Instagram brought. Cookies on this site: _fbp (90 days), _fbc (90 days).

How to change your choice

Open Cookie settings here or in the footer of any page and set the two switches.

A group you switch off stops at once: where it was running, the page loads again without it, and Google's tags go back to signals without cookies. The site also deletes the cookies that group had set for legarithm.io. Cookies that Google, LinkedIn and Meta keep under their own addresses stay in your browser until they run out or you delete them.

Your answer is kept for 365 days. Then the site asks again.

Other companies

A video opens on YouTube, under YouTube's own policy.

The booking calendar opens from Google Calendar after you send a request, under Google's policy.