Cookie policy
This is an inventory, not a statement of intent: it lists what this website stores in your browser, how long it lasts and how you change your mind. Nothing optional is switched on before you accept it. Measured on 11 September 2026 with a real browser on the live site: browsing without answering, or declining, installs no cookies at all; accepting analytics installs two, listed below.
Your decision, and where it lives
The only thing this site stores on its own is your answer to the cookie notice, under the key monea_consent_v1. It is not a cookie: it sits in your browser's local storage, it is never sent to our server and it travels with no request. It holds the date, the version of this policy and one yes/no per category. It stays until you clear your browser data or until this policy changes version — and it cannot be switched off, because without it we would have to ask you again on every single page.
Analytics — off until you turn it on
If you accept analytics, Google Analytics 4 starts through Google Tag Manager, with Consent Mode v2: the tag is configured not to fire at all until you say yes, so until then no request reaches Google Analytics. Once accepted it installs two first-party cookies — _ga and _ga_5SRPYQX00L, both lasting up to 400 days — which tell us which pages work and which do not, and whether an enquiry form was sent. They carry no name, no email and nothing you type into a form; Google Analytics 4 does not store IP addresses. The tag manager script itself (googletagmanager.com) loads on every page and sets no cookie. Measured on the date above: declining, zero requests to Google Analytics and zero cookies; accepting, exactly these two.
Marketing — none today
This category covers advertising tags such as Google Ads or Meta Pixel: measuring campaigns and showing you offers that have to do with what you looked at. Today there is not a single one on this site, and that is measured, not assumed — accepting everything and browsing through contacts no advertising host whatsoever. The day one is added it will only load after you accept this category, and this page will say so.
Functional — the map, and the availability search
The map on the contact page draws its tiles from OpenStreetMap, which means your IP address reaches their servers when the map appears. Together with Google (the tag manager and, if you accept analytics, Google Analytics) it is one of the two third parties this website contacts anywhere, and it obeys your answer: measured on the live site, declining or not answering downloads zero tiles; accepting downloads them. The date search is a booking-engine widget from an external provider that sets its own cookies while you search; it is not connected yet, so today it sets nothing.
What we do not do
Nothing described here identifies you by name, and none of it is sold or handed to anyone to build a profile of you. There are no social network buttons, no embedded video from third-party platforms, no external fonts and no content delivery network: the typefaces, the scripts and the map library are all served from this same domain, which is why the list of third parties above has exactly two entries: Google and OpenStreetMap.
Changing your mind, right now
At the bottom of every page there is a Cookie preferences link: it reopens the panel and lets you switch any category on or off, as many times as you like. Declining sits one click away from accepting, on purpose and at the same size. Clearing your browser data works too: it removes the key above, and the notice simply asks again on your next visit.
If any of this changes
This policy carries a version number, and the answer you gave carries the same one. If we add anything that stores or sends data, the version goes up, your stored answer stops counting and the notice asks again from scratch — silently reusing an old consent for something new is exactly what this mechanism exists to prevent. The inventory above was measured on 11 September 2026 with a real browser, the day analytics was switched on — within the analytics category this policy already described, which is why the version did not change — and it is measured again whenever the site changes.