Cookie Notice

Effective from: 4 September 2026 · Version: 2.0

How this works

When you first visit, a panel asks you to choose. Until you choose, nothing at all is stored on your device and nothing is requested from anyone else — no analytics, no behavioural signal, no video player, not even the cookie that remembers your answer.

• Accept — we set the analytics cookies in section 2.
• Reject — only the cookie recording your choice is set. The site works exactly the same.
• Manage preferences — choose analytics on its own.

Consent is never assumed. Continuing to browse is not consent, closing the panel is not consent, and there are no pre-ticked boxes.

Video and podcast players are separate, and do not depend on the choice above. They never load on their own. Each shows a button naming what it will load, and nothing reaches the provider until you press it. See section 3.

How to change your mind

Cookie settings, in the footer of every page, reopens the same choice and applies it at once. Withdrawing analytics deletes the analytics cookies already on your device — brix_tense and brix_visit are gone the moment you save.

You can also clear cookies in your browser. That works, but it is not how you withdraw consent from us — the footer control is.

Google Analytics data goes to Google, which may combine it with other data it holds. The behavioural class does not: it stays with us. Where your data travels is in section 7 of the Privacy Notice.

3 · Embedded video, podcast and chart — nothing loads until you press play

80 pages on this site carry a player or a chart from a third party: 26 YouTube, 1 Vimeo, 52 Acast, 1 Datawrapper. None is in the page when it arrives. You see a button naming the provider and saying what pressing it will do. Until then no request is made and nothing is stored.

Pressing the button is your consent for that one player or chart, on that one page. It does not carry over, and it is not affected by your answer to the panel above. Reload the page and it is a button again.

YouTube players load from youtube-nocookie.com, which delays Google's cookies until you actually play. It does not stop Google receiving your IP address and the page you are on — nothing but not loading the player does that, which is why the button exists.

YouTube / Google — 26 pages. Cookies set on Google's own domains once the player runs:

Name	Domain	Purpose	Duration	Class
VISITOR_INFO1_LIVE	youtube.com	Functionality, analytics, recommendations	6 months	Analytics / personalisation
YSC	youtube.com	Security; prevents other sites acting as you	Session	Security
PREF	youtube.com	Playback and page preferences	8 months	Functional
__Secure-YEC	youtube.com	Spam and fraud detection, advertiser billing integrity	13 months	Advertising (in part)
SOCS	google.com	Your cookie choices on Google properties	13 months	Functional
AEC	google.com	Fraud detection protecting advertiser billing	6 months	Advertising (in part)
NID	google.com	Advertising to signed-out users	6 months	Advertising
IDE	doubleclick.net	Personalised Google advertising on non-Google sites	13 months (UK/EEA)	Advertising
test_cookie	doubleclick.net	Checks whether cookies are supported	15 minutes	Functional

Vimeo — 1 page.

Name	Purpose	Duration	Class
vuid	Analytics for the video owner	2 years	Analytics
player	Playback preferences	1 year	Essential to the player
flags	Provider feature flags	1 year	Essential to the player
player_clearance	Bot prevention	7 days	Essential to the player
cf_clearance, _cf_bm, _cfuvid	Cloudflare bot management and rate limiting	1 year / 30 minutes / session	Essential to the player

Acast — 52 pages. Acast is the odd one out and we would rather say so than bury it. When you press play, Acast AB (publ), Kungsgatan 28, 111 35 Stockholm, Sweden, receives your IP address, the address of this page, and which episode you asked for. As measured on 3 September 2026 it stores nothing on your device — no cookie, no local storage. We keep the button anyway: it costs you one press, it makes the choice yours, and it protects you if Acast changes what it does.

Datawrapper — 1 page. One blog post carries a chart, not a player, and it behaves differently again. When you press Load chart, Datawrapper GmbH, Kreutzigerstraße 26, 10247 Berlin, Germany, receives your IP address, your browser details, and the chart you asked for. Datawrapper's own privacy policy states it does not collect your IP address for this purpose, but it also states, in its own words, that "to monitor this we use a self-developed, self-hosted tracking system with cookies" — so, unlike Acast, Datawrapper does set a cookie on your device when the chart loads. Datawrapper does not publish that cookie's name or how long it lasts, so we cannot state it here — we say that plainly rather than guess.

None of these players or charts is necessary for BriX's own service. That is why none starts by itself.

Joint controllership for embedded players

Where a website embeds third-party content that transmits visitor data, the site operator and the provider are joint controllers for the collection and transmission of that data — CJEU, Fashion ID (C-40/17). We embedded the players and the chart and we benefit from them, so it applies to us for YouTube, Vimeo, Acast and Datawrapper alike. Your press is your consent; it does not move the responsibility.

The essential terms, published under Article 26(2) GDPR:

• BriX is responsible for making sure nothing loads before you press, for telling you what pressing does (the button and this page), and for handling your requests about that collection-and-transmission moment.
• The provider is responsible for everything it does with the data once it has it, under its own privacy policy, including its security and how long it keeps it.
• You may exercise your rights against either of us for the part each is responsible for. Write to info@brix.consulting and we will act on our part and point you to theirs.

International transfers

Google, Vimeo and Acast are established outside Slovakia and some transfer to the United States. Datawrapper is established in Germany, inside the EU, so no international-transfer safeguard is needed for it. The safeguards for the others are in section 7 of the Privacy Notice.

Changes to this list

When we add or remove a cookie we update this page and raise the version of the consent record, which makes the panel ask you again. Your previous answer is never silently extended to something new. Where a change alters how a purpose is described — not merely which cookie serves it — any behavioural score built under the old description is reset when you answer again.