Last reviewed 27 October 2026
Nothing is stored until the cookie bar is answered. The two items that are stored are named below.
The two keys
| Key | What it holds | Lifetime |
|---|---|---|
03_tampere_age_ok | Your answer to the age question, so it is asked once per device. | Until browsing data is cleared |
03_tampere_consent | Your accept or decline, so the bar stops returning. | Until browsing data is cleared |
Strictly speaking both are local storage, not cookies. They stay in your browser, no other site can read them, and they contain no identifier.
Consent Mode v2
Four Google signals are set to denied in the head of every page, ahead of any other script:
ad_storagead_user_dataad_personalizationanalytics_storage
So every page starts from refusal. Accepting changes all four to granted, and declining leaves them as they were.
What accepting would permit
No tag is on the site today. If one were added, Google Analytics 4 would write _ga and _ga_<id>, lasting two years and recognising a returning reader, and a Google Ads tag would write _gcl_au, lasting ninety days and attributing a visit to an advertisement. Decline and none of them is created.
Changing your answer
Cookie settings in the footer reopens the bar on any page, and your new answer replaces the old one immediately.
Blocking it in the browser
Chrome and Edge under Privacy and security, Firefox under Privacy & Security, Safari under Settings then Privacy. Blocking storage entirely means the age question returns every visit, because the answer has nowhere to live.
Not used on this site
- No social pixels, and no share buttons that load one.
- No device or browser fingerprinting.
- No advertising network beyond the Google tag above, and only with consent.
- No session recording or heatmaps.
- No fonts or scripts from another host at run time; the typefaces are served from this domain.