Cookies and storage
Cookie notice
This list is complete. Everything this site stores in your browser is on it, with its name, its lifetime, and whether it needs your permission.
Last updated:
Where things stand today
No measurement id is configured on this site right now, so no Google Analytics, Google Ads or Meta code loads. That is also why the consent banner does not appear: we do not ask about cookies that do not exist.
Which means exactly one item on the list below can appear on your machine today: the language choice. The rest depend either on your consent, or on there being something to consent to in the first place.
The complete list
NEXT_LOCALE
Cookie
- What it is for
- Remembers whether you read the site in Hungarian or English, so you do not have to switch again on your next visit.
- How long it lives
- One year when you switch language with the control in the header. When the server sets it from your browser’s language preference, it lasts until you close the browser.
- Needs permission?
- No. It stores the setting you asked for, and we use it for nothing else.
brecon-consent
Local storage (localStorage)
- What it is for
- Stores your answer about advertising cookies, so we do not ask again on every page load.
- How long it lives
- 180 days, then we ask again. That applies to a no as well: if you declined, we do not ask again for six months.
- Needs permission?
- No — it stores the decision itself. It is only created when you answer the banner; pressing Esc writes nothing.
brecon-attribution
Local storage (localStorage)
- What it is for
- If you came from an ad, it remembers that ad’s parameters (utm_source, utm_campaign, gclid and their siblings) so our ad account can show which ad brought you here.
- How long it lives
- 90 days.
- Needs permission?
- Yes. It only reaches your machine once you have accepted. Until then it lives at most in the memory of the open tab and disappears when the page reloads. Withdrawing consent deletes it too.
Vercel Analytics, Speed Insights
First-party measurement
- What it is for
- How many page views there were, on which page, and how quickly it loaded. These are our own statistics; they hold no advertising identifier and connect to no Google or Meta account.
- How long it lives
- Our code writes nothing to your browser for this. The script loads from our own domain, at /_vercel/insights and /_vercel/speed-insights, so no third-party host is called. Vercel’s own documentation states the measurement works without cookies.
- Needs permission?
- We did not gate this on consent, because it stores nothing in your browser and serves no advertising purpose.
Google Analytics 4 and Google Ads
Third party
- What it is for
- Once switched on, this measures how many visitors arrive and from which ad, and reports back to Google Ads when someone completes the contact form.
- How long it lives
- Google sets these cookies under its own names (_ga and _gcl_au, for instance) and writes one local-storage entry as well (_gcl_ls). Google decides their lifetimes; the current list is in Google’s own notice.
- Needs permission?
- Yes. The code does not enter the page until you accept — we do not load it in a disabled state, we do not load it at all.
Meta Pixel
Third party
- What it is for
- The same role for Facebook and Instagram ads that Google Ads plays for search.
- How long it lives
- Meta sets the cookie, usually named _fbp, and decides its lifetime.
- Needs permission?
- Yes, and the same way: without consent the code never enters the page.
How to say no, and how to take it back
- The Decline button on the banner. Nothing loads afterwards, and we do not ask again for six months.
- Pressing Esc hides the banner for this page load but stores nothing — silence is not consent, so the next visit asks again.
- The "Cookie settings" control in the footer clears your earlier answer at any time. That deletes the stored campaign record as well, and puts the question back.
- Your browser settings can clear this site’s cookies and local storage too. That forgets your language choice; nothing else changes.
What we do not use
- We use no session storage at all.
- There is no fingerprinting: we generate no identifier for you from your browser’s properties.
- There is no cookie wall. Every part of the site is readable whether you answer the question or decline it.
- The public pages carry no sign-in cookie. The internal system has its own address and is not part of this site.
More detail
What happens to the data you send through the contact form is described in the privacy notice.