Last updated: June 4, 2026
Cookie statement
Short version: this site sets one functional cookie (language preference) and no tracking or marketing cookies. That is why no cookie banner is shown. The detail below makes it concrete.
Cookies set on this site
| Name | Purpose | Retention | Type | Placed by |
|---|---|---|---|---|
| NEXT_LOCALE | Remembers whether you want to see the Dutch or English version of the site. Contains only a language code (nl or en); no personal data. | 1 year | Functional | First-party |
No tracking, no marketing
No ad networks. No third-party pixels (Facebook, Google, LinkedIn, etc.). No profiling or cross-site tracking. The only cookie set is the NEXT_LOCALE cookie noted above, which only remembers your preferred language.
Vercel Analytics and Speed Insights
For visitor insight and conversion measurement I use Vercel Analytics. It is a cookieless, aggregated measurement: no cookies are set and no personal data is recorded. Beyond page-views Vercel also captures a few conversion events (booking-link clicks, mailto/tel clicks, and successful contact-form submissions), all equally cookieless and without personal data. Vercel hashes user-agent + URL daily to deduplicate visits, without storing identifiable data. In addition, Vercel Speed Insights measures page performance (such as load time and visual stability); this too is cookieless and contains no personal data.
Error tracking (own server)
To diagnose bugs and server errors I run a self-hosted GlitchTip instance on a server in the Netherlands, under my own control. When an unexpected browser or server-action error occurs, technical data (URL, error message, stack trace, browser version, IP address) is sent for diagnosis. No cookies are set; the Sentry SDK may use a short session ID in browser storage to group related errors. Logs are kept for at most 90 days. Legal basis: legitimate interest (art. 6(1)(f) GDPR) to keep the site working.
Campaign attribution (UTM): no storage
When you arrive via a campaign link (e.g. a newsletter or LinkedIn post with a ?utm_source=... parameter), those UTM parameters are kept only in the page's working memory. Nothing is written to cookies, localStorage or sessionStorage. Purpose: if you then fill in the contact form, I can see which campaign brought you to the site. The values disappear as soon as you reload or leave the page, and contain no personal data, only marketing-category tags such as 'linkedin' or 'newsletter-may'.
Why no cookie banner?
A consent banner is only required when non-functional (tracking, marketing, profiling) cookies are placed. The NEXT_LOCALE cookie falls under the exception of article 11.7a of the Dutch Telecommunications Act (strictly necessary / functional cookies). A banner here would only add clicks without value to the visitor.
What if that changes?
If at some point this site does add tracking or marketing cookies, a consent manager will be implemented first. Until then: nothing to choose, everything transparent.