Cookie notice

The short answer

mansio.studio does not set a single cookie. Not first-party, not third-party, not technical, not analytical, not advertising. That is why there is no cookie banner: there is nothing to consent to, and a banner asking permission for nothing would be theatre. This is not a promise; it is a consequence of how the site is built. These are static pages with no application server behind them, no accounts and no session. There is nowhere to put a cookie and no reason to.

What is stored in your browser — one key, and it is not a cookie

One single key is stored in your browser, and it is not a cookie. Three differences from a cookie, and all three matter:

• Your language — mansio.taal — en, es or nl — Your browser's localStorage — Until you clear it — So that returning to the home page does not send you back to English if you already chose another language
• It does not travel. A cookie is attached automatically to every request to the server. This never leaves the browser: only the page's own code reads it, on your machine.
• It does not identify. It is not an identifier, it is not random, it is not unique. It is one of three possible words.
• It never reaches Mansio. Mansio cannot read it, and does not know it exists in your browser.
• Under Dutch telecommunications law (Article 11.7a Telecommunicatiewet, implementing the ePrivacy Directive) consent is not required for storage strictly necessary to provide a service the user has explicitly requested. Remembering the language you just chose yourself is exactly that case.
• How to clear it: empty the site's storage in your browser (Chrome and Edge: Settings → Privacy → Site data; Firefox: Settings → Privacy → Cookies and Site Data; Safari: Preferences → Privacy → Manage Website Data). You can also undo it in one click: pressing "EN" in the language switcher sets it back to English.

What is not here, named explicitly

Each technique that is absent is named one by one, so that nothing has to be inferred:

• Session or login cookies — No — there is no login
• Google Analytics, Plausible, Matomo or any other analytics — No — none at all
• Meta, LinkedIn, TikTok or Google Ads pixels — No
• Embedded social media buttons — No — the Instagram link is an ordinary link and loads nothing
• Google Fonts or other remote fonts — No — the typeface is served from mansio.studio
• Embedded video (YouTube, Vimeo) — No
• Embedded maps — No
• Third-party chat, widgets or forms — No — the form is sent to an address on mansio.studio itself, with no form service in between
• Profiling or automated decision-making — No
• The site is additionally served with a Content Security Policy (default-src 'self') that technically prevents the page from loading anything from a third party, even if someone added one by mistake.

The exception: NEL, Cloudflare's network-error telemetry

There is one thing that leaves your browser for a third party, and until today it was not declared. It is told in full, because a notice that leaves out the awkward part is worth nothing.

• What it is. mansio.studio is served through Cloudflare's network. Cloudflare adds two standard browser headers to every response, NEL (Network Error Logging) and Report-To:
• report-to: {"group":"cf-nel","max_age":604800, "endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=…"}]}
• nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
• What it does. It asks your browser to keep an instruction for seven days (604,800 seconds): if a request to this site fails — DNS does not resolve, TLS does not negotiate, the connection drops, the server errors — send a small technical report about that failure to a.nel.cloudflare.com.
• What that report contains. The address requested, the page it came from, the type of error, the elapsed time, the protocol — and, by virtue of being an HTTP request, your IP address. It carries none of the content you typed, no cookies and no session identifier: there are none to carry.
• What it does not do. success_fraction: 0.0 means none of the visits that work are reported. It is not analytics: it does not count visitors, it does not measure page views, and it cannot be used to follow you. It fires only on failure.
• Who put it there. Cloudflare, in its network. Mansio did not put it there, it does not appear in the site's configuration, and Mansio does not read those reports and has no access to them.
• Why it is declared anyway. Because it leaves your browser for a third party, and that is precisely what a cookie notice exists to tell you. Until 30 August 2026 this site claimed to make "not a single request to a third party", and that was inaccurate. It was corrected on the day it was measured rather than left standing.
• Legal basis. Legitimate interests (Art. 6(1)(f) GDPR) in the security and availability of the service, which is also the purpose the technique was designed for. If you would rather not take part, any browser lets you disable network reporting, and blocking network access to a.nel.cloudflare.com with an extension also prevents it.

If this changes

If Mansio ever wanted analytics or any non-essential cookie, this notice would change first, and whatever consent mechanism the law requires would be added. It would not be put in place first and asked about afterwards.