Cookies
Last updated: 27 September 2026.
The short version: no advertising and no third-party trackers — no Google Analytics, no Tag Manager, no Meta pixel, no Hotjar, no PostHog, nothing of that family. Nobody else is reading this page over your shoulder. What follows is every cookie the site does set, one by one.
One clarification, because “no analytics at all” would be too flattering to be true: the blog counts visits with Matomo. It is hosted on our own server, so no third party receives anything, and it is configured without cookies — it stores nothing at all on your device. That is also why it adds no row to the tables below and why it needs no consent: consent is about what gets written to your machine, and nothing does. The application itself — everything you use after signing in — carries no analytics of any kind.
Strictly necessary — set without asking
These carry the service you asked for. European law exempts them from consent for exactly that reason: refusing them would mean refusing the site.
| Cookie | What it does | How long |
|---|---|---|
| jwt | Keeps you signed in after you log in. Without it every page would ask for your password again. | 7 days |
| org_scope | For administrators who belong to more than one organisation: remembers which one you are currently acting in. Written when you pick one, rewritten when you switch, removed when you go back to “all organisations”. | Until you change or clear it |
| wr-lang | The language you chose from the footer. It is written only when you click a language: arriving here and being shown Italian because your browser asks for Italian writes nothing. | 1 year |
| wr-consent | Your answer to the cookie banner, with the date you gave it. Remembering a refusal is the only way to respect it. | 6 months |
Optional — only if you accept
| Cookie | What it does | How long |
|---|---|---|
| wr_ref | If you arrived through a partner’s link, this records their code so the introduction is credited to them when you later open an account. It serves us and them, not you, and that is why we ask before writing it. Refuse, and the code still works for the visit you are in: it simply is not kept. | 90 days |
— changing your mind takes one click, in either direction. Saying “essential only” after having accepted also deletes the cookie above, rather than merely noting that you withdrew.
Not cookies, but still storage
Some features keep things in your browser’s own storage instead of a cookie — for instance, the pipeline designer remembers the cloud API token you pasted so you do not have to paste it at every run, with a button next to the field to clear it. That is part of the feature you asked for, it never leaves your browser, and clearing your site data removes it.
If this changes
The day we add something that watches what you do, it appears in this table and in the banner in the same change — and your previous answer stops counting, because it was given about something else. See also the privacy notice for what we hold about you beyond cookies.