Skip to content
Data Stables

Cookie Policy

Last updated: 6 August 2026

Data Stables B.V., Bierstraat 123c, 3011 XA Rotterdam, Netherlands. Contact: reinier@data-stables.nl.

This page describes what this website actually stores in your browser and which third parties it contacts. It covers cookies as well as localStorage, which is a different storage mechanism with the same privacy effect: a value that persists on your device between visits.

Nothing is stored on your device, and no analytics resource is loaded from Google or from us, unless the analytics_consent cookie has the value granted. That value cannot currently be set anywhere on this site, so in practice nothing is stored and nothing is loaded. The one exception is the locale cookie described below, which is written only when you yourself use the language switcher.

What we store in your browser

data_stables_anonymous_id — stored in localStorage, no expiry. Written only once analytics_consent has the value granted; on later visits the existing value is read and reused. A random visitor identifier that lets our analytics recognise a repeat visit from the same browser.

__anon_id — stored in localStorage, no expiry. Written only once analytics_consent has the value granted, and reused on later visits. The same kind of random visitor identifier, written by the analytics library we use.

analytics_consent — a first-party cookie, lifetime one year, SameSite=Lax. Written only once a consent choice exists. It stores whether that choice was granted or denied.

locale — a first-party cookie, lifetime one year, SameSite=Lax. Written only when you use the EN/NL language switcher. It remembers your language preference so we do not send you back to the other language.

Neither localStorage identifier tells us who you are. They are random values; they let us count a returning browser rather than a returning person.

Third parties this site contacts

Google Tag Manager (www.googletagmanager.com, container GTM-KC9L4RZ6) is fetched only once analytics_consent has the value granted. It is the container that holds our analytics configuration. Without that value your browser never requests it, so Google LLC learns neither your IP address nor the page you are on. We also run Google Consent Mode v2, which tells the container what you allow; because the container is now fetched only after a granted value exists, it is told at the moment it loads that analytics storage is granted. Advertising storage, ad personalisation and ad user data are told denied — always, in every state, because we never ask you about advertising and run no advertising tags. Fetching the container does mean your browser makes a request to Google, which reveals your IP address and the page you are on to Google LLC — that request happens only after consent.

Our own analytics endpoint (j.data-stables.nl) is a Jitsu collector we host ourselves on a server in Germany (EU). It only receives events when analytics_consent has the value granted. With no consent value, or with denied, no events are sent to it.

Consent: what is true today

We want to be straight with you rather than describe a situation that does not exist:

  • This site does not currently show a cookie consent banner.
  • The two localStorage identifiers (data_stables_anonymous_id and __anon_id) are not written before analytics_consent has the value granted.
  • The Google Tag Manager container is not loaded before that value exists either, so no request goes to Google.
  • These are analytics identifiers. We do not claim they are strictly necessary for the website to work — the site functions without them.
  • Actual event collection to our own analytics endpoint does wait for analytics_consent=granted.

There is currently no way, anywhere on this site, to set or change analytics_consent. No banner and no settings screen writes it, so unless you set the cookie yourself in your browser's developer tools it never has a value. Because everything our analytics does waits for that value to be granted, the practical consequence today is that nothing is stored in your browser for analytics, no request is made to Google, and no analytics events are being sent to it at all today.

We consider this situation wrong: a site that cannot ask you is a site that cannot honour a yes either. We intend to introduce a consent mechanism that asks before anything non-essential is stored or loaded. Until that exists, this page is the honest description of what happens, and the section below tells you how to clear anything an earlier version of this site may already have stored.

How to remove or block this

Because nothing is stored unless analytics_consent is granted, there is normally nothing here to remove. If you visited while an earlier version of this site was live, that version wrote the two identifiers on your first page view and the old values may still be sitting in your browser.

  • Clear what is already stored. In your browser's settings, use the site-data controls ("Cookies and site data", "Manage data" or equivalent) and delete the entry for data-stables.nl. That removes the cookies and any leftover localStorage identifiers in one step. In most browsers you can also reach the same controls from the padlock icon in the address bar while you are on this site.
  • Block them up front. Most browsers can block cookies and site data for a specific site, which stops the localStorage identifiers from being stored even if consent is later granted. Browsing in a private / incognito window has the same effect for that session, because everything is discarded when you close it.
  • Block the third-party request. Content-blocking extensions and browser tracking-protection settings can stop www.googletagmanager.com from loading. That is a belt-and-braces measure rather than a necessary one: the site itself does not request the container unless analytics_consent is granted.

Removing the identifiers does not break the site. New random values are generated only if analytics_consent is ever set to granted.

More information

See our privacy policy for the legal basis of this processing, retention periods, the processors involved, and your rights — including your right to complain to the Autoriteit Persoonsgegevens.