Cookies

The short version

Iriska sets no advertising cookies, runs no third-party analytics, and shares nothing with anyone for their marketing. Everything below is either necessary for the site to work or off by default.

You are asked once. Until you answer, only the strictly necessary cookies are set and nothing optional runs. You can change your answer at any time from the link in the footer, and the change takes effect immediately.

Strictly necessary

These do not ask for consent, because Article 5(3) of the ePrivacy Directive exempts what is strictly necessary to provide a service you asked for. Refusing them means refusing to be able to sign in.

• Your sign-in session, and keeping it alive while you use the site
• Which company you are currently acting as, when you belong to more than one
• Your basket
• The market you are shopping in, so prices are shown in the right VAT context
• The bot check on the sign-in form (Cloudflare Turnstile), which is a security control — a bot check a bot can decline is not a bot check
• Your answer to this cookie notice, so you are not asked again
• Which home you asked for — business or home — when you chose on the front page before signing in; once signed in, your account decides and this cookie is not read (iriska_audience: a functional preference, kept one year, no personal data)

Optional, and off unless you say so

One item, and it will stay a short list: anything added here has to appear in this table before it can run, which is a deliberate obstacle.

• Session replay (Sentry) — a recording of how a page behaved for you when something goes wrong, so a fault can be reproduced rather than guessed at. Genuinely useful, genuinely not necessary.

What is not optional and is not a cookie

Error reports are always collected. When something breaks, the platform records what broke and where. That report sets no cookie and carries no identifier of its own, and without it the platform does not learn it is broken — which would leave the people most careful about their privacy on the most broken version of the site.

This is the distinction the notice draws: recording a fault is not the same as recording you.

Your answer, and changing it

Your choice is stored in a first-party cookie with the version of this notice it answered and the time you gave it, and kept for a year. Storing the version matters: if this notice materially changes, your old answer stops counting and you are asked again, because consent is to a particular statement.

Change it from “Cookie choices” in the footer of any page. Choosing “Essential only” after having accepted stops session replay immediately.