Cookie policy

What this site stores in your browser, what it does not, and how to change your mind. Short, because the site stores very little.

What cookies are

Cookies are small files a site stores in your browser. This site uses very few of them, and the choice you make below is itself kept in your browser's local storage rather than in a cookie, so it never travels to us with a request.

Categories we use

Four categories: essential, preferences, analytics and marketing. Only the first is on by default. The other three stay off until you switch them on, because under the GDPR a pre-ticked box is not consent. The analytics switch governs Google Analytics and Metricool and nothing else, and the marketing switch the Meta and TikTok pixels and nothing else. Our own counting is described below, sets no cookie, and is not what either switch turns off.

Essential cookies

What the site cannot work without. None of it is a cookie: all of it is kept in your browser’s storage and never travels to us with a request. In local storage, which keeps a value until you clear this site’s data: daleenda.lang.choice, the language you chose, written when you choose one (an older key, daleenda.lang, is removed if found); daleenda.theme, your light or dark preference, written when you change it; and daleenda.cookie-consent, the cookie choice you made and the version of this policy it was made under, written when you choose. In session storage, which your browser empties when you close the tab: dln-chunk-retry, the address of a page that failed to load because the site had just been updated, so that the page is reloaded once rather than over and over. None of these carries an identifier that could be used to recognise you elsewhere, and they are kept whether or not you accept anything else.

Counting visits

We count page views ourselves. That counting sets no cookie, but it keeps one value in your browser’s local storage, dln_vid: a random token that lets us recognise your browser when it returns to this site on a later day, so that we can tell new visitors from returning ones. It is written on your first visit, before you make any cookie choice, and has no expiry date: it stays until you clear this site’s data, and a new one is written on your next visit after that. It is read by this site only, sent only to our own collector, and means nothing anywhere else. The counting records the page you opened, its title and language, the site that linked you here, any campaign tag in the address, the width of your window, whether you are on a phone, tablet or desktop, your country, and how long and how far you read. Your IP address is not stored: it is combined with a secret that is destroyed every night and turned into a fingerprint that cannot be turned back. This rests on our legitimate interest rather than on consent, so it is not what the analytics switch controls. It does not change in response to Global Privacy Control or Do Not Track: a browser that sends either signal is counted like any other. You can object at any time by writing to legal@daleenda.com, and you can stop the token being written by blocking site storage for daleenda.com in your browser. One more value, dln_staff, is written only on the devices of our own staff, when they open a link made for that purpose, so that their visits are left out of the counts; it is never written for anyone who has not opened such a link.

Live chat

If you start a chat, this site keeps two values in your browser’s local storage: dln.chat.visitor, a visitor id, and dln.chat.conversation, a handle for your conversation. They exist so the thread is still there when you come back, and they are read by this site only, sent only to our own chat service and never used to follow you across the web. A third, dln.chat.sound, remembers that you switched the chat’s notification sound off or on, and is written only when you press that switch. None of them expires on its own. Clearing your browser data removes all three, and with the first two any way back to that conversation. Nothing is stored until you start a chat or press the sound switch. What happens to the conversation itself is described in the privacy policy.

The map on the contact page

The contact page offers a map from Google Maps, behind a click: nothing is loaded, and nothing is sent anywhere, until you choose to load it. The button says what loading sends: your IP address goes to Google, which learns you viewed the page and can set and read its own cookies. Loading the map is the consent, asked exactly where it applies, and it is asked again on your next visit rather than remembered: remembering it would itself be storage this page had to disclose. The "Open in Google Maps" link beside the map works without loading anything into this page.

Optional cookies

Preferences, analytics and marketing. Analytics loads Google Analytics, which sets two cookies, _ga and _ga_1SQDX90CR9, that last two years and tell Google which pages you opened here. It also loads Metricool, which sets no cookie and stores nothing in your browser, and tells Metricool which pages you opened here, the site that linked you here and the size of your window. Marketing loads the Meta Pixel, which sets one cookie, _fbp, that lasts ninety days and tells Meta which pages you opened here, which buttons you pressed, and when you sent a form or got in touch; never what you typed into one. It also loads the TikTok Pixel, which sets _ttp for thirteen months and a session cookie, ttcsid, and tells TikTok the same things. Preferences still loads nothing at all. Nothing in this group runs until you switch it on, and switching analytics or marketing off again removes that tag and deletes its cookies rather than merely stopping the reporting.

Managing your choices

Change your mind at any time through the cookie settings link in the footer of every page. Withdrawing consent is exactly as easy as giving it, and takes effect immediately. Clearing your browser's storage for this site has the same result, and the banner will ask again.

Third parties

The site loads its own fonts, its own images and its own content. The pages are served by Firebase Hosting, a Google service, and the site talks to Supabase in Frankfurt, Germany, which stores content pages, applications, chats, bookings and our own visit counts. Our collector on Supabase is contacted on every page view, as described under “Counting visits”, and the chat and the booking and application forms contact Supabase when you use them. The privacy policy names both, and every other provider that processes your data, including those behind email, SMS, WhatsApp and bookings, which your browser does not contact. Five third parties can be contacted from the page itself, and none is until you act: the map on the contact page, described above; Google Analytics and Metricool, which load only if you switch analytics on; and the Meta and TikTok pixels, which load only if you switch marketing on. They are the only things fetched from an advertising network. Separately, and not from your browser, our server reports job applications to Meta, as the privacy policy describes under “Applying for a job”.

Changes to this policy

If a service is ever added that sets cookies or sends what you do here to someone else, this page changes before it goes live and the banner asks again rather than assuming the consent you gave for something else. Google Analytics was added on 30 August 2026 under the analytics category, which is why that switch now names it. The Meta Pixel was added on 25 September 2026 under marketing, which until then loaded nothing, so the banner asked again of anyone who had switched marketing on before that date. The TikTok Pixel was added on 28 September 2026, also under marketing, and the banner asked again for the same reason. Metricool was added on 29 September 2026 under analytics, so the banner asked again of anyone who had switched analytics on before that date. On 30 September 2026 this page was extended to name every value the site keeps in your browser, with its purpose and lifetime; nothing new was added to the site.